hotstar.in

hotstar.in is SSL secured

Free website and domain report on hotstar.in

Last Updated: 9th July, 2023 Update Now
Overview

Snoop Summary for hotstar.in

This is a free and comprehensive report about hotstar.in. Hotstar.in is hosted in Singapore on a server with an IP address of 52.219.129.21, where SGD is the local currency and the local language is Mandarin. Our records indicate that hotstar.in is owned/operated by Novi Digital Entertainment Pvt. Ltd.. If hotstar.in was to be sold it would possibly be worth $112 USD (based on the daily revenue potential of the website over a 24 month period). Hotstar.in receives an estimated 49 unique visitors every day - a small amount of traffic. This report was last updated 9th July, 2023.

About hotstar.in

Site Preview: hotstar.in hotstar.in
Title: Error
Description: Watch latest TV shows, movies and live cricket on Hotstar - premium Indian streaming platform with more than 100,000 hours of drama and movies in 8 languages.
Keywords and Tags: entertainment, streaming media
Related Terms: hotstar offer, hotstar party, hotstar watch party extension, hotstar.com, how to activate hotstar premium free, sadda haq hotstar serial, suvreen guggal hotstar serial, tere liye hotstar serial, us hotstar, watch hotstar premium free
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

1/5

Valuation

$112 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 9,127,873
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 10
Moz Page Authority: 25

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 49
Monthly Visitors: 1,491
Yearly Visitors: 17,885
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $0 USD
Monthly Revenue: $4 USD
Yearly Revenue: $51 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: hotstar.in 10
Domain Name: hotstar 7
Extension (TLD): in 2

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 78
Performance 65
Accessibility 85
Best Practices 77
SEO 83
PWA 78
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.hotstar.com/us
Updated: 15th November, 2021

0.89 seconds
First Contentful Paint (FCP)
89%
7%
4%

0.01 seconds
First Input Delay (FID)
89%
7%
4%

Simulate loading on desktop
65

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for hotstar.in. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.6 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.9 s
The time taken for the page to become fully interactive.
Cumulative Layout Shift — 0.001
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Hotstar.in should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 7 KiB
Images can slow down the page's load time. Hotstar.in should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
7534
6697
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Hotstar.in should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Hotstar.in should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Hotstar.in should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Hotstar.in should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 420 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.hotstar.com/us
417.898
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Hotstar.in should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 8 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.hotstar.com/assets/vendor~main.89.4e766b6d9863cbd02b93.js
6375
https://www.hotstar.com/assets/main.055324e6dfb74346acf6.js
1040
https://www.hotstar.com/assets/2.2.a85ecab1f76a680730e2.js
226
https://www.hotstar.com/assets/landing-page.39.9f027526a835ae4d5127.js
65
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 852 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.hotstar.com/assets/main.055324e6dfb74346acf6.js
357084
https://www.hotstar.com/assets/landing-page.39.9f027526a835ae4d5127.js
141789
https://www.hotstar.com/assets/vendor~main.89.4e766b6d9863cbd02b93.js
134867
https://www.hotstar.com/assets/2.2.a85ecab1f76a680730e2.js
36757
https://www.hotstar.com/us
32686
https://www.hotstar.com/assets/search-bar.66.6cf17b35a23d281d5560.js
32467
https://secure-media.hotstarext.com/web-messages/core/info/v260.json
29693
https://www.hotstar.com/assets/common-chunk-main.0.8e33dae0c8282ca58ddc.js
19576
https://www.hotstar.com/assets/2220b001005f901871764a12537e6407.svg
13776
https://secure-media.hotstarext.com/web-assets/prod/roboto-medium.woff2
11486
Uses efficient cache policy on static assets — 4 resources found
Hotstar.in can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://secure-media.hotstarext.com/web-assets/prod/roboto-regular.woff2
59000
11445
https://secure-media.hotstarext.com/web-assets/prod/roboto-medium.woff2
487000
11486
https://secure-media.hotstarext.com/web-assets/prod/images/brand-logos/hotstar-logo-dark.svg
514000
1242
https://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
3600000
7855
Avoids an excessive DOM size — 169 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
169
Maximum DOM Depth
15
Maximum Child Elements
9
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Hotstar.in should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures — 1 user timing
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
sentry-tracing-init
Mark
1772.031
JavaScript execution time — 0.8 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.hotstar.com/assets/vendor~main.89.4e766b6d9863cbd02b93.js
381.421
348.084
9.73
https://www.hotstar.com/assets/2.2.a85ecab1f76a680730e2.js
255.59
251.024
2.873
https://www.hotstar.com/us
141.551
6.032
7.013
Unattributable
100.218
15.711
0.186
https://www.hotstar.com/assets/top-navigation-bar.75.d1564d581b3d20066115.js
97.677
97.073
0.279
https://www.hotstar.com/assets/main.055324e6dfb74346acf6.js
92.643
46.44
24.232
Minimizes main-thread work — 1.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
832.864
Other
134.238
Script Parsing & Compilation
62.533
Style & Layout
50.182
Parse HTML & CSS
30.74
Rendering
29.757
Garbage Collection
18.23
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 29 requests • 852 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
29
871948
Script
14
751157
Other
9
42301
Document
1
32686
Font
2
22931
Image
3
22873
Stylesheet
0
0
Media
0
0
Third-party
6
61863
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0014287477745673
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 3 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.hotstar.com/assets/2.2.a85ecab1f76a680730e2.js
1653
248
https://www.hotstar.com/assets/main.055324e6dfb74346acf6.js
1440
213
https://www.hotstar.com/assets/top-navigation-bar.75.d1564d581b3d20066115.js
1901
98
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of hotstar.in on mobile screens.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://hotstar.in/
http/1.1
0
517.18500000425
335
0
301
text/plain
http://www.hotstar.com/
http/1.1
517.75499992073
562.71299999207
552
0
302
text/plain
http://www.hotstar.com/us
http/1.1
563.04799998179
736.14299995825
550
0
301
text/plain
https://www.hotstar.com/us
h2
736.48600000888
1153.3930001315
32686
159939
200
text/html
Document
https://www.hotstar.com/assets/main.055324e6dfb74346acf6.js
h2
1170.8750000689
1335.0190001074
357084
1459399
200
application/javascript
Script
https://www.hotstar.com/assets/vendor~main.89.4e766b6d9863cbd02b93.js
h2
1171.4139999822
1326.7540000379
134867
437386
200
application/javascript
Script
https://www.hotstar.com/assets/common-chunk-main.0.8e33dae0c8282ca58ddc.js
h2
1171.6400000732
1252.9680000152
19576
71544
200
application/javascript
Script
https://www.hotstar.com/assets/landing-page.39.9f027526a835ae4d5127.js
h2
1172.1320000943
1329.8190000933
141789
623218
200
application/javascript
Script
https://secure-media.hotstarext.com/web-assets/prod/roboto-regular.woff2
h2
1214.1760000959
1331.6669999622
11445
11016
200
font/woff2
Font
https://secure-media.hotstarext.com/web-messages/core/info/v260.json
h2
1803.1600001268
2115.0110000744
29693
140452
200
application/json
Fetch
https://api.hotstar.com/um/v3/users
h2
2154.7139999457
2478.8410000037
1037
0
403
text/html
Preflight
https://secure-media.hotstarext.com/web-messages/core/error/v52.json
h2
2125.1900000498
2201.3630000874
7662
36191
200
application/json
Fetch
https://api.hotstar.com/um/v3/users
2153.6189999897
2496.6669999994
0
0
-1
Fetch
https://www.hotstar.com/assets/2.2.a85ecab1f76a680730e2.js
h2
2165.5620001256
2198.9450000692
36757
149504
200
application/javascript
Script
https://api.hotstar.com/o/v1/page/1557?offset=0&size=20&tao=0&tas=20
h2
2456.6329999361
2685.5500000529
1101
0
200
text/html
Preflight
https://www.hotstar.com/assets/top-navigation-bar.75.d1564d581b3d20066115.js
h2
2431.4610001165
2503.3279999625
3823
10824
200
application/javascript
Script
https://www.hotstar.com/assets/search-bar.66.6cf17b35a23d281d5560.js
h2
2431.7429999355
2529.9810001161
32467
171771
200
application/javascript
Script
https://www.hotstar.com/assets/exit-kids-loader.37.3c31428fbbcac4c4874f.js
h2
2431.9559999276
2580.6660000235
1408
1879
200
application/javascript
Script
https://www.hotstar.com/assets/sign-in-header-component.68.6a64ae28b3f22ad6b599.js
h2
2432.9490000382
2504.4279999565
2443
4726
200
application/javascript
Script
https://www.hotstar.com/assets/SignInModal.21.3c38237e98ad089e591e.js
h2
2436.0030000098
2503.9620001335
8987
31027
200
application/javascript
Script
https://www.hotstar.com/assets/ParentalLockModal.17.bd95e50ed15635ed9c6a.js
h2
2436.8370000739
2669.9129999615
3957
8999
200
application/javascript
Script
https://www.hotstar.com/assets/PreSunsetModal.18.c26935cde98bc7acd0a0.js
h2
2437.9249999765
2506.1659999192
2460
6330
200
application/javascript
Script
https://www.hotstar.com/assets/PreSunsetPaywallModal.19.9238d878280b190f8827.js
h2
2439.2669999506
2511.5569999907
2482
6281
200
application/javascript
Script
https://www.hotstar.com/assets/Footer.16.8c94716ce8e65316dba3.js
h2
2439.9220000487
2539.7050001193
3057
8968
200
application/javascript
Script
https://api.hotstar.com/o/v1/page/1557?offset=0&size=20&tao=0&tas=20
h2
2686.1529999878
2928.1290001236
1371
177
475
text/html
Fetch
https://www.hotstar.com/assets/2220b001005f901871764a12537e6407.svg
h2
2462.3650000431
2533.9780000504
13776
38904
200
image/svg+xml
Image
https://secure-media.hotstarext.com/web-assets/prod/images/brand-logos/hotstar-logo-dark.svg
h2
2621.5119999833
2889.8010000121
1242
1701
200
image/svg+xml
Image
https://secure-media.hotstarext.com/web-assets/prod/roboto-medium.woff2
h2
2636.5990000777
2884.2589999549
11486
11056
200
font/woff2
Font
https://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
h2
2696.2119999807
2962.7040000632
7855
7534
200
image/png
Image
data
2727.6820000261
2727.8720000759
0
507
200
image/svg+xml
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1205.525
10.858
1221.272
6.689
1229.098
6.009
1238.682
11.013
1249.743
14.942
1268.678
5.468
1455.791
425.1
2167.962
45.622
2257.17
248.443
2505.704
9.56
2515.282
18.218
2543.225
9.057
2552.913
6.743
2560.436
6.16
2571.793
97.732
2669.573
9.312
2678.905
7.69
2686.903
10.36
2702.837
6.171
2712.462
6.492
2718.969
5.797
2730.909
13.215
2749.038
11.775
2760.852
8.688
2771.897
9.153
2781.196
5.853
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

Largest Contentful Paint — 2.2 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 250 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 1.5 s
The time taken for the primary content of the page to be rendered.

Other

Reduce unused JavaScript — Potential savings of 327 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.hotstar.com/assets/main.055324e6dfb74346acf6.js
357084
149876
https://www.hotstar.com/assets/landing-page.39.9f027526a835ae4d5127.js
141789
74584
https://www.hotstar.com/assets/vendor~main.89.4e766b6d9863cbd02b93.js
134867
57194
https://www.hotstar.com/assets/search-bar.66.6cf17b35a23d281d5560.js
32467
29301
https://www.hotstar.com/assets/2.2.a85ecab1f76a680730e2.js
36757
24298
Avoid multiple page redirects — Potential savings of 450 ms
Redirects can cause additional delays before the page can begin loading. Hotstar.in should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://hotstar.in/
190
http://www.hotstar.com/
190
http://www.hotstar.com/us
70
https://www.hotstar.com/us
0

Metrics

Speed Index — 2.5 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 400 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
https://secure-media.hotstarext.com/web-assets/prod/images/brand-logos/hotstar-logo-dark.svg
85

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of hotstar.in. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Hotstar.in may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
77

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that hotstar.in should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
React
core-js
core-js-global@2.6.12; core-js-pure@2.6.12; core-js-pure@2.6.12; core-js-pure@3.0.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.

Audits

Does not use HTTPS — 4 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://hotstar.in/
Allowed
http://www.hotstar.com/
Allowed
http://www.hotstar.com/us
Allowed
http://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
Automatically upgraded to HTTPS

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Access to fetch at 'https://api.hotstar.com/um/v3/users' from origin 'https://www.hotstar.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.
error in guest signup :: [object Object]
Failed to load resource: net::ERR_FAILED
Failed to load resource: the server responded with a status of 475 (Internal Server Error)
Object
Object
Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.hotstar.com/assets/main.055324e6dfb74346acf6.js
https://www.hotstar.com/assets/landing-page.39.9f027526a835ae4d5127.js
Issues were logged in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.
Issue type
Mixed content
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for hotstar.in. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of hotstar.in on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
78

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of hotstar.in. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of hotstar.in on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest has a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 73
Performance 35
Accessibility 86
Best Practices 77
SEO 86
PWA 80
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.hotstar.com/us
Updated: 15th November, 2021

1.23 seconds
First Contentful Paint (FCP)
85%
8%
7%

0.04 seconds
First Input Delay (FID)
83%
7%
10%

Simulate loading on mobile
35

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for hotstar.in. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Hotstar.in should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Hotstar.in should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Hotstar.in should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Hotstar.in should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Hotstar.in should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Hotstar.in should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 340 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.hotstar.com/us
339.564
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Hotstar.in should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 872 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.hotstar.com/assets/main.055324e6dfb74346acf6.js
357084
https://www.hotstar.com/assets/landing-page.39.9f027526a835ae4d5127.js
141789
https://www.hotstar.com/assets/vendor~main.89.4e766b6d9863cbd02b93.js
134867
https://www.hotstar.com/assets/2.2.a85ecab1f76a680730e2.js
36757
https://www.hotstar.com/us
32686
https://www.hotstar.com/assets/search-bar.66.6cf17b35a23d281d5560.js
32467
https://secure-media.hotstarext.com/web-messages/core/info/v260.json
29693
https://www.hotstar.com/assets/common-chunk-main.0.8e33dae0c8282ca58ddc.js
19576
https://www.hotstar.com/assets/2220b001005f901871764a12537e6407.svg
13776
https://secure-media.hotstarext.com/web-assets/prod/roboto-medium.woff2
11486
Avoids an excessive DOM size — 145 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
145
Maximum DOM Depth
15
Maximum Child Elements
9
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Hotstar.in should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures — 1 user timing
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
sentry-tracing-init
Mark
1870.632
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 32 requests • 872 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
32
892960
Script
15
755584
Other
9
42318
Font
4
39499
Document
1
32686
Image
3
22873
Stylesheet
0
0
Media
0
0
Third-party
7
73314
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 6 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.hotstar.com/assets/2.2.a85ecab1f76a680730e2.js
7567
825
https://www.hotstar.com/assets/main.055324e6dfb74346acf6.js
6870
697
https://www.hotstar.com/assets/main.055324e6dfb74346acf6.js
5220
154
https://www.hotstar.com/assets/Footer.16.8c94716ce8e65316dba3.js
9028
79
https://www.hotstar.com/assets/bottom-navigation-bar.27.7321233d74b2b97a0e26.js
8899
76
https://www.hotstar.com/assets/search-bar.66.6cf17b35a23d281d5560.js
8842
57
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of hotstar.in on mobile screens.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://hotstar.in/
http/1.1
0
496.34399986826
335
0
301
text/plain
http://www.hotstar.com/
http/1.1
496.70899985358
538.37700001895
552
0
302
text/plain
http://www.hotstar.com/us
http/1.1
538.70199993253
605.0909999758
565
0
301
text/plain
https://www.hotstar.com/us
h2
605.49400001764
944.06699994579
32686
159939
200
text/html
Document
https://www.hotstar.com/assets/main.055324e6dfb74346acf6.js
h2
958.9660000056
1516.0260000266
357084
1459399
200
application/javascript
Script
https://www.hotstar.com/assets/vendor~main.89.4e766b6d9863cbd02b93.js
h2
959.34199984185
1098.2569998596
134867
437386
200
application/javascript
Script
https://www.hotstar.com/assets/common-chunk-main.0.8e33dae0c8282ca58ddc.js
h2
959.53099988401
1058.3249998745
19576
71544
200
application/javascript
Script
https://www.hotstar.com/assets/landing-page.39.9f027526a835ae4d5127.js
h2
959.84399993904
1105.9419999365
141789
623218
200
application/javascript
Script
https://secure-media.hotstarext.com/web-assets/prod/roboto-regular.woff2
h2
994.62499981746
1092.370999977
11446
11016
200
font/woff2
Font
https://secure-media.hotstarext.com/web-messages/core/info/v260.json
h2
1897.7659998927
2025.781000033
29693
140452
200
application/json
Fetch
https://api.hotstar.com/um/v3/users
h2
2061.4419998601
2350.4810000304
1039
0
403
text/html
Preflight
https://secure-media.hotstarext.com/web-messages/core/error/v52.json
h2
2037.1719999239
2082.6369998977
7662
36191
200
application/json
Fetch
https://api.hotstar.com/um/v3/users
2060.2809998672
2393.3659999166
0
0
-1
Fetch
https://www.hotstar.com/assets/2.2.a85ecab1f76a680730e2.js
h2
2070.1069999486
2156.4779998735
36757
149504
200
application/javascript
Script
https://api.hotstar.com/o/v1/page/1557?offset=0&size=20&tao=0&tas=20
h2
2371.5989999473
2814.160999842
1101
0
200
text/html
Preflight
https://www.hotstar.com/assets/top-navigation-bar.75.d1564d581b3d20066115.js
h2
2333.2599999849
2403.983999975
3823
10824
200
application/javascript
Script
https://www.hotstar.com/assets/search-bar.66.6cf17b35a23d281d5560.js
h2
2334.1339998879
2659.0089998208
32467
171771
200
application/javascript
Script
https://www.hotstar.com/assets/exit-kids-loader.37.3c31428fbbcac4c4874f.js
h2
2334.8289998248
2364.580999827
1408
1879
200
application/javascript
Script
https://www.hotstar.com/assets/sign-in-header-component.68.6a64ae28b3f22ad6b599.js
h2
2335.3420000058
2690.6810000073
2443
4726
200
application/javascript
Script
https://www.hotstar.com/assets/bottom-navigation-bar.27.7321233d74b2b97a0e26.js
h2
2336.015000008
2420.303999912
4427
12845
200
application/javascript
Script
https://www.hotstar.com/assets/SignInModal.21.3c38237e98ad089e591e.js
h2
2338.310000021
2426.1759999208
8987
31027
200
application/javascript
Script
https://www.hotstar.com/assets/ParentalLockModal.17.bd95e50ed15635ed9c6a.js
h2
2339.0359999612
2448.1669999659
3957
8999
200
application/javascript
Script
https://www.hotstar.com/assets/PreSunsetModal.18.c26935cde98bc7acd0a0.js
h2
2339.820999885
2430.6349998806
2460
6330
200
application/javascript
Script
https://www.hotstar.com/assets/PreSunsetPaywallModal.19.9238d878280b190f8827.js
h2
2340.620999923
2424.6079998557
2482
6281
200
application/javascript
Script
https://www.hotstar.com/assets/Footer.16.8c94716ce8e65316dba3.js
h2
2341.4429998957
2434.312999947
3057
8968
200
application/javascript
Script
https://api.hotstar.com/o/v1/page/1557?offset=0&size=20&tao=0&tas=20
h2
2814.752999926
2893.1989998091
1371
177
475
text/html
Fetch
https://www.hotstar.com/assets/2220b001005f901871764a12537e6407.svg
h2
2376.7249998637
2448.7359998748
13776
38904
200
image/svg+xml
Image
https://www.hotstar.com/assets/14242f8b93118f629a606a5dfb905ecb.ttf
h2
2378.0499999411
2619.7809998412
5117
4612
200
font/ttf
Font
https://secure-media.hotstarext.com/web-assets/prod/roboto-medium.woff2
h2
2378.6730000284
2637.0149999857
11486
11056
200
font/woff2
Font
https://secure-media.hotstarext.com/web-assets/prod/roboto-bold.woff2
h2
2381.5639999229
2639.8259999696
11450
11020
200
font/woff2
Font
https://secure-media.hotstarext.com/web-assets/prod/images/brand-logos/hotstar-logo-dark.svg
h2
2426.6119999811
2662.3639999889
1242
1701
200
image/svg+xml
Image
https://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
h2
2527.4379998446
2621.7979998328
7855
7534
200
image/png
Image
data
2683.5319998208
2683.6490000132
0
507
200
image/svg+xml
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
986.349
9.167
999.389
5.646
1013.488
9.266
1022.79
12.419
1611.069
348.371
2070.159
38.558
2205.018
206.344
2411.465
18.712
2430.947
7.561
2449.389
5.644
2455.383
9.393
2472.831
19.03
2491.899
5.619
2508.327
8.8
2524.143
9.01
2545.639
19.868
2565.722
5.499
2705.188
14.168
2719.415
5.517
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 2.1 s
The time taken for the first image or text on the page to be rendered.

Other

Avoid serving legacy JavaScript to modern browsers — Potential savings of 8 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.hotstar.com/assets/vendor~main.89.4e766b6d9863cbd02b93.js
6375
https://www.hotstar.com/assets/main.055324e6dfb74346acf6.js
1040
https://www.hotstar.com/assets/2.2.a85ecab1f76a680730e2.js
226
https://www.hotstar.com/assets/landing-page.39.9f027526a835ae4d5127.js
65
Serve static assets with an efficient cache policy — 5 resources found
Hotstar.in can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://secure-media.hotstarext.com/web-assets/prod/roboto-regular.woff2
105000
11446
https://secure-media.hotstarext.com/web-assets/prod/roboto-bold.woff2
245000
11450
https://secure-media.hotstarext.com/web-assets/prod/roboto-medium.woff2
458000
11486
https://secure-media.hotstarext.com/web-assets/prod/images/brand-logos/hotstar-logo-dark.svg
473000
1242
https://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
3600000
7855
Reduce JavaScript execution time — 2.5 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.hotstar.com/assets/vendor~main.89.4e766b6d9863cbd02b93.js
1229.504
1123.348
32.368
https://www.hotstar.com/assets/2.2.a85ecab1f76a680730e2.js
844.692
769.556
9.764
https://www.hotstar.com/us
488.72
17.612
25.128
https://www.hotstar.com/assets/main.055324e6dfb74346acf6.js
319.592
158.196
89.388
Unattributable
307.808
55.056
0.652
https://www.hotstar.com/assets/Footer.16.8c94716ce8e65316dba3.js
129.544
126.88
0.768
https://www.hotstar.com/assets/bottom-navigation-bar.27.7321233d74b2b97a0e26.js
75.916
73.772
1.3
https://www.hotstar.com/assets/search-bar.66.6cf17b35a23d281d5560.js
56.432
38.752
12.164
Minimize main-thread work — 3.6 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
2490.188
Other
478.928
Script Parsing & Compilation
223.672
Style & Layout
205.916
Parse HTML & CSS
95.752
Rendering
83.796
Garbage Collection
58.044
First Contentful Paint (3G) — 4028 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Metrics

Time to Interactive — 8.4 s
The time taken for the page to become fully interactive.
Speed Index — 6.8 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 1,500 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 9.4 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 830 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 6.7 s
The time taken for the primary content of the page to be rendered.

Other

Reduce unused JavaScript — Potential savings of 327 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.hotstar.com/assets/main.055324e6dfb74346acf6.js
357084
149867
https://www.hotstar.com/assets/landing-page.39.9f027526a835ae4d5127.js
141789
74566
https://www.hotstar.com/assets/vendor~main.89.4e766b6d9863cbd02b93.js
134867
57406
https://www.hotstar.com/assets/search-bar.66.6cf17b35a23d281d5560.js
32467
29007
https://www.hotstar.com/assets/2.2.a85ecab1f76a680730e2.js
36757
24298
Avoid multiple page redirects — Potential savings of 1,440 ms
Redirects can cause additional delays before the page can begin loading. Hotstar.in should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://hotstar.in/
630
http://www.hotstar.com/
630
http://www.hotstar.com/us
180
https://www.hotstar.com/us
0
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
https://secure-media.hotstarext.com/web-assets/prod/images/brand-logos/hotstar-logo-dark.svg
86

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of hotstar.in. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Hotstar.in may provide assistance to deaf or hearing-impaired users with captions on videos.

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
77

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that hotstar.in should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
React
core-js
core-js-global@2.6.12; core-js-pure@2.6.12; core-js-pure@2.6.12
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.

Audits

Does not use HTTPS — 4 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://hotstar.in/
Allowed
http://www.hotstar.com/
Allowed
http://www.hotstar.com/us
Allowed
http://secure-media.hotstar.com/static/sunset/us/assets/web/disney_bundle.png
Automatically upgraded to HTTPS

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Access to fetch at 'https://api.hotstar.com/um/v3/users' from origin 'https://www.hotstar.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.
error in guest signup :: [object Object]
Failed to load resource: net::ERR_FAILED
Failed to load resource: the server responded with a status of 475 (Internal Server Error)
Object
Object
Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.hotstar.com/assets/main.055324e6dfb74346acf6.js
https://www.hotstar.com/assets/landing-page.39.9f027526a835ae4d5127.js
Issues were logged in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.
Issue type
Mixed content
86

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for hotstar.in. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of hotstar.in on mobile screens.
Document uses legible font sizes — 98.33% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
.bottom-navigation-container .link-container .nav-link
1.67%
10px
98.33%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
80

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of hotstar.in. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of hotstar.in on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest has a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 52.219.129.21
Continent: Asia
Country: Singapore
Singapore Flag
Region:
City:
Longitude: 103.8547
Latitude: 1.2929
Currencies: SGD
Languages: Mandarin
English
Malay
Tamil

Web Hosting Provider

Name IP Address
Amazon Technologies Inc.
Registration

Domain Registrant

Private Registration: No
Name:
Organization: Novi Digital Entertainment Pvt. Ltd.
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.hotstar.com
Issued By: DigiCert TLS RSA SHA256 2020 CA1
Valid From: 1st August, 2022
Valid To: 2nd August, 2023
Subject: CN = *.hotstar.com
O = Novi Digital Entertainment Pvt. Ltd.
L = Mumbai
S = IN
Hash: 82b80758
Issuer: CN = DigiCert TLS RSA SHA256 2020 CA1
O = DigiCert Inc
S = US
Version: 2
Serial Number: 4569658515481608202741299608321359513
Serial Number (Hex): 0370158F3FCA3C5B8814DE587C097E99
Valid From: 1st August, 2024
Valid To: 2nd August, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:B7:6B:A2:EA:A8:AA:84:8C:79:EA:B4:DA:0F:98:B2:C5:95:76:B9:F4
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/DigiCertTLSRSASHA2562020CA1-4.crl

Full Name:
URI:http://crl4.digicert.com/DigiCertTLSRSASHA2562020CA1-4.crl

Certificate Policies: Policy: 2.23.140.1.2.2
CPS: http://www.digicert.com/CPS

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/DigiCertTLSRSASHA2562020CA1-1.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Aug 1 03:40:10.278 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:09:58:85:62:3F:A9:4D:D2:17:0E:31:F1:
00:34:9A:7C:EB:F0:71:25:A9:22:DD:A5:46:13:97:67:
FA:21:B2:62:02:21:00:D5:E4:7F:C6:87:7F:7F:22:4E:
6F:65:B1:E7:12:64:18:7A:4E:BB:2C:C9:40:19:35:84:
16:35:A7:76:BC:1B:CB
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 35:CF:19:1B:BF:B1:6C:57:BF:0F:AD:4C:6D:42:CB:BB:
B6:27:20:26:51:EA:3F:E1:2A:EF:A8:03:C3:3B:D6:4C
Timestamp : Aug 1 03:40:10.270 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:68:08:E9:6E:F1:AF:AB:74:44:A6:D8:7B:
A3:61:EA:E5:8A:E0:07:31:81:FA:AE:43:38:12:01:A7:
2A:D3:37:C7:02:21:00:96:91:EE:1D:BC:D3:69:1F:67:
AC:82:81:D9:74:43:CE:57:77:6B:C0:ED:5A:E0:F2:C3:
8A:72:B0:8C:4C:BB:A2
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B3:73:77:07:E1:84:50:F8:63:86:D6:05:A9:DC:11:09:
4A:79:2D:B1:67:0C:0B:87:DC:F0:03:0E:79:36:A5:9A
Timestamp : Aug 1 03:40:10.317 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:12:02:3D:29:21:0B:54:79:6D:6B:FC:40:
CE:63:72:CE:C5:FD:38:0D:BE:8B:B2:C2:3F:F3:57:C3:
F5:E4:86:4A:02:20:01:84:B8:7A:37:6D:C8:E6:F6:B6:
F1:97:56:E9:97:4A:07:8E:38:FE:37:B2:2F:9B:B7:7A:
08:A9:12:27:45:16
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:hotstar.com
DNS:*.hotstar.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
hotstar.in. 52.219.125.9 IN 5

NS Records

Host Nameserver Class TTL
hotstar.in. ns-1426.awsdns-50.org. IN 21600
hotstar.in. ns-1589.awsdns-06.co.uk. IN 21600
hotstar.in. ns-164.awsdns-20.com. IN 21600
hotstar.in. ns-586.awsdns-09.net. IN 21600

SOA Records

Domain Name Primary NS Responsible Email TTL
hotstar.in. ns-586.awsdns-09.net. awsdns-hostmaster.amazon.com. 900

HTTP Response Headers

HTTP-Code: HTTP/1.1 475 Unknown
Server: AkamaiGHost
Content-Type: text/html
Cache-Control: max-age=31536000
Expires: 10th March, 2024
Date: 11th March, 2023
Mime-Version: 1.0
Content-Length: 176
Connection: keep-alive
Set-Cookie: *
X-cachestatus:
X-cacheTTL: -1
x-origin-date: 1678527318
X-ASNno: 14061
Akamai-GRN: 0.989f4d68.1678527318.7f42a3e

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: ns-1426.awsdns-50.org
ns-1589.awsdns-06.co.uk
ns-164.awsdns-20.com
ns-586.awsdns-09.net
Full Whois:

Nameservers

Name IP Address
ns-1426.awsdns-50.org 205.251.197.146
ns-1589.awsdns-06.co.uk 205.251.198.53
ns-164.awsdns-20.com 205.251.192.164
ns-586.awsdns-09.net 205.251.194.74
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5
$132,589,519 USD 5/5

Sites hosted on the same IP address