hdvd9.in

hdvd9.in is SSL secured

Free website and domain report on hdvd9.in

Last Updated: 31st October, 2023 Update Now
Overview

Snoop Summary for hdvd9.in

This is a free and comprehensive report about hdvd9.in. If hdvd9.in was to be sold it would possibly be worth $427 USD (based on the daily revenue potential of the website over a 24 month period). Hdvd9.in receives an estimated 200 unique visitors every day - a decent amount of traffic! This report was last updated 31st October, 2023.

About hdvd9.in

Site Preview: hdvd9.in hdvd9.in
Title:
Description: hdvd9 whatapp Video Songs, hdvd9 whatapp bollywood movie video, hdvd9 whatapp video Download, mp4 hindi movie songs download
Keywords and Tags: entertainment
Related Terms:
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

1/5

Valuation

$427 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 6,430,427
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 7
Moz Page Authority: 23

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 200
Monthly Visitors: 6,100
Yearly Visitors: 73,146
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $17 USD
Yearly Revenue: $208 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: hdvd9.in 8
Domain Name: hdvd9 5
Extension (TLD): in 2

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 79
Performance 100
Accessibility 80
Best Practices 77
SEO 100
Progressive Web App 38
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
100

Performance

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

Metrics

First Contentful Paint — 0.3 s
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 0.3 s
The time taken for the primary content of the page to be rendered.
Speed Index — 0.4 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 0.3 s
The time taken for the page to become fully interactive.
First CPU Idle — 0.3 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.

Other

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive hdvd9.in as laggy when the latency is higher than 0.05 seconds.
Total Blocking Time — 0 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).
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://hdvd9.in/
0
384.90199996158
6896
22461
200
text/html
Document
http://hdvd9.in/style_hdvd9.css
395.30699996976
439.916000003
849
1947
200
text/css
Stylesheet
http://hdvd9.in/hdvd9.png
395.51099995151
540.96699994989
6886
6648
200
image/png
Image
https://img.youtube.com/vi//default.jpg
395.79399995273
399.48599995114
1582
1097
404
image/jpeg
Image
http://widget.supercounters.com/ssl/online_t.js
396.4659999474
463.94200000213
1289
1717
200
application/javascript
Script
http://c1.popads.net/pop.js
442.36599997384
507.76299997233
9608
31739
200
application/javascript
Script
http://www.supercounters.com/fc.php?id=1384336&w=1&v=1&ua=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_13_6)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F74.0.3694.0%20Safari%2F537.36%20Chrome-Lighthouse&url=http%3A%2F%2Fhdvd9.in%2F&ref=&sw=800&sh=600&rand=66&label=Online&fcolor=
468.7649999978
536.52899997542
303
58
200
application/x-javascript
Script
http://c.adsco.re/
616.54799996177
645.10599995265
1673
0
403
text/html
Script
http://serve.popads.net/c?_=e1&v=4&siteId=3096929&minBid=&popundersPerIP=&blockedCountries=&documentRef=&s=800,600,1,800,600
749.90999995498
824.47999995202
202
0
200
text/html
Script
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)
408.934
5.87
465.712
21.919
532.259
5.407
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources — Potential savings of 60 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Hdvd9.in should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Size (Bytes) Potential Savings (Ms)
http://hdvd9.in/style_hdvd9.css
849
70
Properly size images
Images can slow down the page's load time. Hdvd9.in should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Hdvd9.in should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Hdvd9.in should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Hdvd9.in should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Hdvd9.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
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
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.
Server response times are low (TTFB) — Root document took 390 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Hdvd9.in should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Hdvd9.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.

Diagnostics

Avoids enormous network payloads — Total size was 29 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
http://c1.popads.net/pop.js
9608
http://hdvd9.in/
6896
http://hdvd9.in/hdvd9.png
6886
http://c.adsco.re/
1673
https://img.youtube.com/vi//default.jpg
1582
http://widget.supercounters.com/ssl/online_t.js
1289
http://hdvd9.in/style_hdvd9.css
849
http://www.supercounters.com/fc.php?id=1384336&w=1&v=1&ua=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_13_6)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F74.0.3694.0%20Safari%2F537.36%20Chrome-Lighthouse&url=http%3A%2F%2Fhdvd9.in%2F&ref=&sw=800&sh=600&rand=66&label=Online&fcolor=
303
http://serve.popads.net/c?_=e1&v=4&siteId=3096929&minBid=&popundersPerIP=&blockedCountries=&documentRef=&s=800,600,1,800,600
202
Uses efficient cache policy on static assets — 6 resources found
Hdvd9.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) Size (Bytes)
http://c1.popads.net/pop.js
0
9608
http://hdvd9.in/hdvd9.png
0
6886
http://hdvd9.in/style_hdvd9.css
0
849
http://www.supercounters.com/fc.php?id=1384336&w=1&v=1&ua=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_13_6)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F74.0.3694.0%20Safari%2F537.36%20Chrome-Lighthouse&url=http%3A%2F%2Fhdvd9.in%2F&ref=&sw=800&sh=600&rand=66&label=Online&fcolor=
0
303
http://serve.popads.net/c?_=e1&v=4&siteId=3096929&minBid=&popundersPerIP=&blockedCountries=&documentRef=&s=800,600,1,800,600
0
202
http://widget.supercounters.com/ssl/online_t.js
14400000
1289
Avoids an excessive DOM size — 285 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
285
Maximum DOM Depth
5
Maximum Child Elements
176
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Hdvd9.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
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 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)
Other
53.883
2.233
0.856
Minimizes main-thread work — 0.1 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)
Other
20.124
Style & Layout
18.636
Script Evaluation
17.928
Rendering
9.7
Parse HTML & CSS
3.865
Script Parsing & Compilation
2.635
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 — 9 requests • 29 KB
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
9
29288
Script
5
13075
Image
2
8468
Document
1
6896
Stylesheet
1
849
Media
0
0
Font
0
0
Other
0
0
Third-party
6
14657
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Size (Bytes) Main-Thread Blocking Time (Ms)
9810
0
1673
0
1582
0

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.
80

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of hdvd9.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.
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.
`[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-*]` 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.

Audio and video

`<audio>` elements contain a `<track>` element with `[kind="captions"]`
Hdvd9.in may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Hdvd9.in may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Hdvd9.in may provide relevant information that dialogue cannot, by using audio descriptions.

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.
`<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.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` 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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
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.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Internationalization and localization

`<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.

Contrast

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

Internationalization and localization

`<html>` element does not have 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.
Failing Elements

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.

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.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
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 hdvd9.in should incorporate. This includes practices such as protecting pages with HTTPS.

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
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.
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.
Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
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.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
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 deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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.

Other

Does not use HTTPS — 8 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
http://hdvd9.in/
http://hdvd9.in/style_hdvd9.css
http://hdvd9.in/hdvd9.png
http://widget.supercounters.com/ssl/online_t.js
http://c1.popads.net/pop.js
http://www.supercounters.com/fc.php?id=1384336&w=1&v=1&ua=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_13_6)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F74.0.3694.0%20Safari%2F537.36%20Chrome-Lighthouse&url=http%3A%2F%2Fhdvd9.in%2F&ref=&sw=800&sh=600&rand=66&label=Online&fcolor=
http://c.adsco.re/
http://serve.popads.net/c?_=e1&v=4&siteId=3096929&minBid=&popundersPerIP=&blockedCountries=&documentRef=&s=800,600,1,800,600
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.
URL Description
http://c.adsco.re/
Failed to load resource: the server responded with a status of 403 (Forbidden)
https://img.youtube.com/vi//default.jpg
Failed to load resource: the server responded with a status of 404 (Not Found)
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for hdvd9.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 hdvd9.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.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the 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.

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.
38

Progressive Web App

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

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

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 hdvd9.in on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 8 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
http://hdvd9.in/
http://hdvd9.in/style_hdvd9.css
http://hdvd9.in/hdvd9.png
http://widget.supercounters.com/ssl/online_t.js
http://c1.popads.net/pop.js
http://www.supercounters.com/fc.php?id=1384336&w=1&v=1&ua=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_13_6)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F74.0.3694.0%20Safari%2F537.36%20Chrome-Lighthouse&url=http%3A%2F%2Fhdvd9.in%2F&ref=&sw=800&sh=600&rand=66&label=Online&fcolor=
http://c.adsco.re/
http://serve.popads.net/c?_=e1&v=4&siteId=3096929&minBid=&popundersPerIP=&blockedCountries=&documentRef=&s=800,600,1,800,600
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.
Web app manifest does not 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.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set 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
Does not provide 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.

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) 78
Performance 100
Accessibility 80
Best Practices 77
SEO 93
Progressive Web App 41
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
100

Performance

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

Metrics

First Contentful Paint — 0.9 s
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 0.9 s
The time taken for the primary content of the page to be rendered.
Speed Index — 0.9 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 0.9 s
The time taken for the page to become fully interactive.
First CPU Idle — 0.9 s
The time taken for the page's main thread to be quiet enough to handle input.

Other

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive hdvd9.in as laggy when the latency is higher than 0.05 seconds.
Total Blocking Time — 0 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).
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://hdvd9.in/
0
103.30900002737
6896
22461
200
text/html
Document
http://hdvd9.in/style_hdvd9.css
131.67700002668
156.11999999965
849
1947
200
text/css
Stylesheet
http://hdvd9.in/hdvd9.png
132.31400004588
175.07300002035
6886
6648
200
image/png
Image
https://img.youtube.com/vi//default.jpg
132.44800001848
137.38000002922
1582
1097
404
image/jpeg
Image
http://widget.supercounters.com/ssl/online_t.js
138.7050000485
166.46999999648
1289
1717
200
application/javascript
Script
http://c1.popads.net/pop.js
162.20800002338
231.84800002491
9609
31739
200
application/javascript
Script
http://www.supercounters.com/fc.php?id=1384336&w=1&v=1&ua=Mozilla%2F5.0%20(Linux%3B%20Android%206.0.1%3B%20Nexus%205%20Build%2FMRA58N)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F74.0.3694.0%20Mobile%20Safari%2F537.36%20Chrome-Lighthouse&url=http%3A%2F%2Fhdvd9.in%2F&ref=&sw=412&sh=660&rand=9&label=Online&fcolor=
250.35099999513
320.90600003721
303
58
200
application/x-javascript
Script
http://c.adsco.re/
367.79600003501
406.13000001758
1673
0
403
text/html
Script
http://serve.popads.net/c?_=e1&v=4&siteId=3096929&minBid=&popundersPerIP=&blockedCountries=&documentRef=&s=412,660,1,412,660
519.03700002003
599.47700001067
202
0
200
text/html
Script
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)
134.936
9.233
145.187
12.109
158.643
17.37
176.228
6.161
186.287
7.113
193.472
75.967
284.35
10.828
536.826
11.287
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
First Contentful Paint (3G) — 1560 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources — Potential savings of 0 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Hdvd9.in should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Size (Bytes) Potential Savings (Ms)
http://hdvd9.in/style_hdvd9.css
849
180
Properly size images
Images can slow down the page's load time. Hdvd9.in should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Hdvd9.in should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Hdvd9.in should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Hdvd9.in should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Hdvd9.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
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
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.
Server response times are low (TTFB) — Root document took 100 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Hdvd9.in should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Hdvd9.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.

Diagnostics

Avoids enormous network payloads — Total size was 29 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
http://c1.popads.net/pop.js
9609
http://hdvd9.in/
6896
http://hdvd9.in/hdvd9.png
6886
http://c.adsco.re/
1673
https://img.youtube.com/vi//default.jpg
1582
http://widget.supercounters.com/ssl/online_t.js
1289
http://hdvd9.in/style_hdvd9.css
849
http://www.supercounters.com/fc.php?id=1384336&w=1&v=1&ua=Mozilla%2F5.0%20(Linux%3B%20Android%206.0.1%3B%20Nexus%205%20Build%2FMRA58N)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F74.0.3694.0%20Mobile%20Safari%2F537.36%20Chrome-Lighthouse&url=http%3A%2F%2Fhdvd9.in%2F&ref=&sw=412&sh=660&rand=9&label=Online&fcolor=
303
http://serve.popads.net/c?_=e1&v=4&siteId=3096929&minBid=&popundersPerIP=&blockedCountries=&documentRef=&s=412,660,1,412,660
202
Uses efficient cache policy on static assets — 6 resources found
Hdvd9.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) Size (Bytes)
http://c1.popads.net/pop.js
0
9609
http://hdvd9.in/hdvd9.png
0
6886
http://hdvd9.in/style_hdvd9.css
0
849
http://www.supercounters.com/fc.php?id=1384336&w=1&v=1&ua=Mozilla%2F5.0%20(Linux%3B%20Android%206.0.1%3B%20Nexus%205%20Build%2FMRA58N)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F74.0.3694.0%20Mobile%20Safari%2F537.36%20Chrome-Lighthouse&url=http%3A%2F%2Fhdvd9.in%2F&ref=&sw=412&sh=660&rand=9&label=Online&fcolor=
0
303
http://serve.popads.net/c?_=e1&v=4&siteId=3096929&minBid=&popundersPerIP=&blockedCountries=&documentRef=&s=412,660,1,412,660
0
202
http://widget.supercounters.com/ssl/online_t.js
14400000
1289
Avoids an excessive DOM size — 285 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
285
Maximum DOM Depth
5
Maximum Child Elements
176
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Hdvd9.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
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 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)
Other
619.112
16.764
3.792
http://c1.popads.net/pop.js
115.412
96.68
3.928
Minimizes main-thread work — 0.8 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)
Style & Layout
279.22
Other
191.82
Script Evaluation
159.268
Parse HTML & CSS
78.24
Rendering
64.632
Script Parsing & Compilation
11.756
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 — 9 requests • 29 KB
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
9
29289
Script
5
13076
Image
2
8468
Document
1
6896
Stylesheet
1
849
Media
0
0
Font
0
0
Other
0
0
Third-party
6
14658
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Size (Bytes) Main-Thread Blocking Time (Ms)
9811
0
1673
0
1582
0

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.

Metrics

Max Potential First Input Delay — 150 ms
Users could experience a delay when interacting with the page.
80

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of hdvd9.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.
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.
`[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-*]` 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.

Audio and video

`<audio>` elements contain a `<track>` element with `[kind="captions"]`
Hdvd9.in may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Hdvd9.in may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Hdvd9.in may provide relevant information that dialogue cannot, by using audio descriptions.

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.
`<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.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` 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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
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.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Internationalization and localization

`<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.

Contrast

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

Internationalization and localization

`<html>` element does not have 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.
Failing Elements

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.

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.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
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 hdvd9.in should incorporate. This includes practices such as protecting pages with HTTPS.

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
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.
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.
Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
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.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
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 deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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.

Other

Does not use HTTPS — 8 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
http://hdvd9.in/
http://hdvd9.in/style_hdvd9.css
http://hdvd9.in/hdvd9.png
http://widget.supercounters.com/ssl/online_t.js
http://c1.popads.net/pop.js
http://www.supercounters.com/fc.php?id=1384336&w=1&v=1&ua=Mozilla%2F5.0%20(Linux%3B%20Android%206.0.1%3B%20Nexus%205%20Build%2FMRA58N)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F74.0.3694.0%20Mobile%20Safari%2F537.36%20Chrome-Lighthouse&url=http%3A%2F%2Fhdvd9.in%2F&ref=&sw=412&sh=660&rand=9&label=Online&fcolor=
http://c.adsco.re/
http://serve.popads.net/c?_=e1&v=4&siteId=3096929&minBid=&popundersPerIP=&blockedCountries=&documentRef=&s=412,660,1,412,660
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.
URL Description
http://c.adsco.re/
Failed to load resource: the server responded with a status of 403 (Forbidden)
https://img.youtube.com/vi//default.jpg
Failed to load resource: the server responded with a status of 404 (Not Found)
93

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for hdvd9.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 hdvd9.in on mobile screens.
Document uses legible font sizes — 100% 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
Legible text
100.00%
≥ 12px

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.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the 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.

Mobile Friendly

Tap targets are not sized appropriately — 24% 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.
Tap Target Size Overlapping Target
a
10x6
a
10x6
134x22
182x24
182x24
185x24
185x24
215x24
215x24
193x24
375x24
375x24
345x24
357x24
291x24
214x24
214x24
222x24
196x24
156x24
316x24
316x24
218x24
208x24
167x24
167x24
244x24
231x24
231x24
345x24
345x24
212x24
331x24
229x24
229x24
229x24
195x24
203x24
299x24
282x24
369x24
268x24
268x24
228x24
291x24
333x24
275x24
275x24
180x24
180x24
299x24
299x24
353x24
197x24
197x24
271x24
233x24
252x24
346x24
223x24
178x24
170x24
170x24
350x24
368x24
254x24
371x24
231x24
199x24
171x24
188x24
188x24
273x24
317x24
204x24
204x24
206x24
222x24
182x24
216x24
201x24
209x24
232x24
178x24
173x24
170x24
170x24
300x24
220x24
316x24
316x24
199x24
199x24
288x24
360x24
360x24
226x24
311x24
331x24
208x24
202x24
265x24
306x24
178x24
226x24
289x24
175x24
175x24
268x24
308x24
302x24
275x24
187x24
201x24
245x24
164x24
164x24
281x24
218x24
250x24
165x24
165x24
288x24
288x24
349x24
218x24
143x24
208x24
327x24
215x24
230x24
234x24
301x24
209x24
207x24
207x24
189x24
285x24
339x24
203x24
203x24
321x24
273x24
192x24
229x24
229x24
341x24
341x24
318x24
232x24
293x24
293x24
253x24
247x24
200x24
241x24
200x24
261x24
301x24
320x24
299x24
229x24
303x24
303x24
259x24
183x24
271x24
275x24
153x24

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.
41

Progressive Web App

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

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

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 hdvd9.in on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 8 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
http://hdvd9.in/
http://hdvd9.in/style_hdvd9.css
http://hdvd9.in/hdvd9.png
http://widget.supercounters.com/ssl/online_t.js
http://c1.popads.net/pop.js
http://www.supercounters.com/fc.php?id=1384336&w=1&v=1&ua=Mozilla%2F5.0%20(Linux%3B%20Android%206.0.1%3B%20Nexus%205%20Build%2FMRA58N)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F74.0.3694.0%20Mobile%20Safari%2F537.36%20Chrome-Lighthouse&url=http%3A%2F%2Fhdvd9.in%2F&ref=&sw=412&sh=660&rand=9&label=Online&fcolor=
http://c.adsco.re/
http://serve.popads.net/c?_=e1&v=4&siteId=3096929&minBid=&popundersPerIP=&blockedCountries=&documentRef=&s=412,660,1,412,660
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.
Web app manifest does not 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.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set 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
Does not provide 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.

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:
Continent:
Country:
Region:
City:
Longitude:
Latitude:
Currencies:
Languages:

Web Hosting Provider

Name IP Address
Oath Holdings Inc.
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
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: Unknown
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: www.hdvd9.in
Issued By: GTS CA 1D4
Valid From: 26th May, 2021
Valid To: 24th August, 2021
Subject: CN = www.hdvd9.in
Hash: f8eef0fa
Issuer: CN = GTS CA 1D4
O = Google Trust Services LLC
S = US
Version: 2
Serial Number: 0xFA0A76ACA852529D0A00000000DA213C
Serial Number (Hex): FA0A76ACA852529D0A00000000DA213C
Valid From: 26th May, 2025
Valid To: 24th August, 2025
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:25:E2:18:0E:B2:57:91:94:2A:E5:D4:5D:86:90:83:DE:53:B3:B8:92
Extended Key Usage: TLS Web Server Authentication
CRL Distribution Points:
Full Name:
URI:http://crls.pki.goog/gts1d4/iNbeROK640A.crl

Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.11129.2.5.3

Authority Information Access: OCSP - URI:http://ocsp.pki.goog/gts1d4
CA Issuers - URI:http://pki.goog/repo/certs/gts1d4.der

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
Timestamp : May 26 09:31:45.507 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:91:2C:89:F9:15:10:D8:73:6C:E7:44:
28:62:79:1C:AB:70:8F:25:FB:3D:8F:9D:C2:10:39:7A:
5B:DB:F6:D6:1D:02:21:00:9F:D7:FA:CE:04:65:BC:B0:
37:E9:F4:B3:77:98:0D:C3:AF:98:99:7E:B4:6A:1E:A2:
00:7C:D3:EC:98:43:06:8A
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
Timestamp : May 26 09:31:45.521 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:59:78:73:BB:B2:46:2D:00:FF:82:17:AC:
AE:67:D9:7E:F6:15:3C:C5:6F:44:D2:09:DC:67:E0:D2:
A7:84:99:E6:02:21:00:C9:5A:5E:1D:91:53:1E:86:2E:
04:8C:68:27:7C:98:D8:8D:53:3E:3B:11:7C:28:D1:9F:
70:04:FE:2A:06:78:C6
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.hdvd9.in
Technical

DNS Lookup

A Records

Host IP Address Class TTL
hdvd9.in. 67.195.197.25 IN 119

NS Records

Host Nameserver Class TTL
hdvd9.in. yns1.yahoo.com. IN 21599
hdvd9.in. yns2.yahoo.com. IN 21599

MX Records

Priority Host Server Class TTL
10 hdvd9.in. mx-biz.mail.am0.yahoodns.net. IN 119

SOA Records

Domain Name Primary NS Responsible Email TTL
hdvd9.in. hidden-master.yahoo.com. geo-support.yahoo-inc.com. 119

TXT Records

Host Value Class TTL
hdvd9.in. i=507&m=geo-siteexp-mx2-1 IN 119

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Expires: 26th May, 2021
Date: 26th May, 2021
Cache-Control: private, max-age=0
Server: GSE
Last-Modified: 12th April, 2021
ETag: "66c36e1b-63ed-491a-8430-48496321a32c"
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Length: 0

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: yns1.yahoo.com
yns2.yahoo.com
Full Whois:

Nameservers

Name IP Address
yns1.yahoo.com 34.195.51.6
yns2.yahoo.com 52.3.46.62
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
$735 USD 1/5
$235 USD 1/5

Sites hosted on the same IP address