vatandownload.com

vatandownload.com is SSL secured

Free website and domain report on vatandownload.com

Last Updated: 10th February, 2023 Update Now
Overview

Snoop Summary for vatandownload.com

This is a free and comprehensive report about vatandownload.com. The domain vatandownload.com is currently hosted on a server located in United States with the IP address 104.21.235.216, where the local currency is USD and English is the local language. Our records indicate that vatandownload.com is owned/operated by Domain ID Shield Service CO., Limited. Vatandownload.com is expected to earn an estimated $20 USD per day from advertising revenue. The sale of vatandownload.com would possibly be worth $14,478 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Vatandownload.com receives an estimated 6,954 unique visitors every day - a huge amount of traffic! This report was last updated 10th February, 2023.

About vatandownload.com

Site Preview: vatandownload.com vatandownload.com
Title: VatanDownload-وطن دانلود
Description: اولین و بزرگترین سایت دانلود نرم افزار و موبایل ایران - با لینک مستقیم
Keywords and Tags: blogs, wiki
Related Terms:
Fav Icon:
Age: Over 15 years old
Domain Created: 20th January, 2009
Domain Updated: 29th May, 2022
Domain Expires: 20th January, 2025
Review

Snoop Score

3/5 (Great!)

Valuation

$14,478 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 61,240
Alexa Reach: 0.0015%
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Rank By Country

Country Alexa Rank
Canada Flag Canada 43,503
Iran, Islamic Republic Of Flag Iran, Islamic Republic Of 6,747
United States Flag United States 19,822

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 6,954
Monthly Visitors: 211,658
Yearly Visitors: 2,538,210
Note: All visitors figures are estimates.

Visitors By Country

Country Visitors (Unique) Percentage
Canada Flag Canada Daily: 181
Monthly: 5,503
Yearly: 65,993
2.6%
Iran, Islamic Republic Of Flag Iran, Islamic Republic Of Daily: 1,558
Monthly: 47,411
Yearly: 568,559
22.4%
Other Daily: 1,648
Monthly: 50,163
Yearly: 601,556
23.7%
United States Flag United States Daily: 3,567
Monthly: 108,580
Yearly: 1,302,102
51.3%
Note: All visitors figures are estimates.
Revenue

Revenue

Daily Revenue: $20 USD
Monthly Revenue: $603 USD
Yearly Revenue: $7,234 USD
Note: All revenue figures are estimates.

Revenue By Country

Country Revenue Percentage
Canada Flag Canada Daily: $0 USD
Monthly: $3 USD
Yearly: $30 USD
0.4%
Iran, Islamic Republic Of Flag Iran, Islamic Republic Of Daily: $0 USD
Monthly: $0 USD
Yearly: $0 USD
<0.1%
Other Daily: $0 USD
Monthly: $0 USD
Yearly: $0 USD
<0.1%
United States Flag United States Daily: $20 USD
Monthly: $601 USD
Yearly: $7,204 USD
99.6%
Note: All revenue figures are estimates.
SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: vatandownload.com 17
Domain Name: vatandownload 13
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 2.27 seconds
Load Time Comparison: Faster than 36% of sites

PageSpeed Insights

Avg. (All Categories) 79
Performance 99
Accessibility 100
Best Practices 92
SEO 80
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
99

Performance

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

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.7 s
The time taken for the page to become fully interactive.
Speed Index — 0.7 s
The time taken for the page contents to be visibly populated.
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).
Largest Contentful Paint — 0.7 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.7 s
The time taken for the primary content of the page to be rendered.
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://vatandownload.com/
http/1.1
0
89.762000017799
1428
1559
200
text/html
Document
https://fonts.googleapis.com/css?family=Open+Sans:400,700%7CPoppins:400,500
h2
94.69200001331
101.68000002159
1498
7434
200
text/css
Stylesheet
http://vatandownload.com/common-css/ionicons.css
http/1.1
95.098000019789
187.270000024
9618
57193
200
text/css
Stylesheet
http://vatandownload.com/common-css/jquery.classycountdown.css
http/1.1
95.203000004403
184.33200000436
1073
508
200
text/css
Stylesheet
http://vatandownload.com/03-comming-soon/css/styles.css
http/1.1
95.329000003403
201.44500001334
2055
3905
200
text/css
Stylesheet
http://vatandownload.com/03-comming-soon/css/responsive.css
http/1.1
95.436000003247
182.85300000571
1038
1369
200
text/css
Stylesheet
http://vatandownload.com/images/countdown-3-1600x900.jpg
http/1.1
205.0000000163
447.66400000663
138524
137789
200
image/jpeg
Image
https://fonts.gstatic.com/s/poppins/v20/pxiByp8kv8JHgFVrLGT9Z1xlFd2JQEk.woff2
h2
205.48400000553
208.08500002022
8558
7748
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v34/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2
h2
205.72399999946
209.52500001295
40184
39372
200
font/woff2
Font
https://fonts.gstatic.com/s/poppins/v20/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
h2
208.71900001657
211.40200001537
8695
7884
200
font/woff2
Font
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)
92.982
8.013
203.424
6.667
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.

Other

Properly size images
Images can slow down the page's load time. Vatandownload.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Vatandownload.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Vatandownload.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Vatandownload.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Vatandownload.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 47 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://vatandownload.com/images/countdown-3-1600x900.jpg
137789
48191.65
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 90 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)
http://vatandownload.com/
90.756
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Vatandownload.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Vatandownload.com 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
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.
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 208 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://vatandownload.com/images/countdown-3-1600x900.jpg
138524
https://fonts.gstatic.com/s/opensans/v34/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2
40184
http://vatandownload.com/common-css/ionicons.css
9618
https://fonts.gstatic.com/s/poppins/v20/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
8695
https://fonts.gstatic.com/s/poppins/v20/pxiByp8kv8JHgFVrLGT9Z1xlFd2JQEk.woff2
8558
http://vatandownload.com/03-comming-soon/css/styles.css
2055
https://fonts.googleapis.com/css?family=Open+Sans:400,700%7CPoppins:400,500
1498
http://vatandownload.com/
1428
http://vatandownload.com/common-css/jquery.classycountdown.css
1073
http://vatandownload.com/03-comming-soon/css/responsive.css
1038
Avoids an excessive DOM size — 7 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
7
Maximum DOM Depth
6
Maximum Child Elements
3
Avoid chaining critical requests — 7 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Vatandownload.com 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
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.
Minimizes main-thread work — 0.0 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.098
Style & Layout
8.494
Script Evaluation
4.638
Parse HTML & CSS
2.547
Rendering
1.547
Script Parsing & Compilation
1.223
Keep request counts low and transfer sizes small — 10 requests • 208 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
10
212671
Image
1
138524
Font
3
57437
Stylesheet
5
15282
Document
1
1428
Media
0
0
Script
0
0
Other
0
0
Third-party
4
58935
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 Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
58935
0
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
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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 vatandownload.com on mobile screens.
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.

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.

Other

Eliminate render-blocking resources — Potential savings of 540 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Vatandownload.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css?family=Open+Sans:400,700%7CPoppins:400,500
1498
230
http://vatandownload.com/common-css/ionicons.css
9618
110
http://vatandownload.com/common-css/jquery.classycountdown.css
1073
110
http://vatandownload.com/03-comming-soon/css/styles.css
2055
110
http://vatandownload.com/03-comming-soon/css/responsive.css
1038
110
Serve static assets with an efficient cache policy — 5 resources found
Vatandownload.com 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)
http://vatandownload.com/images/countdown-3-1600x900.jpg
14400000
138524
http://vatandownload.com/common-css/ionicons.css
14400000
9618
http://vatandownload.com/03-comming-soon/css/styles.css
14400000
2055
http://vatandownload.com/common-css/jquery.classycountdown.css
14400000
1073
http://vatandownload.com/03-comming-soon/css/responsive.css
14400000
1038

Other

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/poppins/v20/pxiByp8kv8JHgFVrLGT9Z1xlFd2JQEk.woff2
2.6010000146925
https://fonts.gstatic.com/s/opensans/v34/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2
3.8010000134818
https://fonts.gstatic.com/s/poppins/v20/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
2.6829999987967
100

Accessibility

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

Audio and video

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that vatandownload.com 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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 6 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://vatandownload.com/
Allowed
http://vatandownload.com/common-css/ionicons.css
Allowed
http://vatandownload.com/common-css/jquery.classycountdown.css
Allowed
http://vatandownload.com/03-comming-soon/css/styles.css
Allowed
http://vatandownload.com/03-comming-soon/css/responsive.css
Allowed
http://vatandownload.com/images/countdown-3-1600x900.jpg
Allowed
80

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for vatandownload.com. 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 vatandownload.com 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.
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.
Links are 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.
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.

Content Best Practices

Document does not have 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.

Crawling and Indexing

robots.txt is not valid — 35 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<!DOCTYPE HTML>
Syntax not understood
2
<html lang="en">
Syntax not understood
3
<head>
Syntax not understood
4
<title>Under Maintenance</title>
Syntax not understood
5
<meta http-equiv="X-UA-Compatible" content="IE=edge">
Syntax not understood
6
<meta name="viewport" content="width=device-width, initial-scale=1">
Syntax not understood
7
<meta charset="UTF-8">
Syntax not understood
10
<!-- Font -->
Syntax not understood
12
<link href="https://fonts.googleapis.com/css?family=Open+Sans:400,700%7CPoppins:400,500" rel="stylesheet">
Unknown directive
15
<link href="common-css/ionicons.css" rel="stylesheet">
Syntax not understood
18
<link rel="stylesheet" href="common-css/jquery.classycountdown.css" />
Syntax not understood
20
<link href="03-comming-soon/css/styles.css" rel="stylesheet">
Syntax not understood
22
<link href="03-comming-soon/css/responsive.css" rel="stylesheet">
Syntax not understood
24
</head>
Syntax not understood
25
<body>
Syntax not understood
27
<div class="main-area center-text" style="background-image:url(images/countdown-3-1600x900.jpg);">
Unknown directive
29
<div class="display-table">
Syntax not understood
30
<div class="display-table-cell">
Syntax not understood
32
<h1 class="title font-white"><b>Comming Soon</b></h1>
Syntax not understood
33
<p class="desc font-white">Our website is currently undergoing scheduled maintenance.
Syntax not understood
34
We Should be back shortly. Thank you for your patience.</p>
Syntax not understood
36
<!-- <a class="notify-btn" href="#"><b>NOTIFY US</b></a> -->
Syntax not understood
38
<ul class="social-btn font-white">
Syntax not understood
39
<!--
Syntax not understood
40
<li><a href="#">facebook</a></li>
Syntax not understood
41
<li><a href="#">twitter</a></li>
Syntax not understood
42
<li><a href="#">google</a></li>
Syntax not understood
43
<li><a href="#">instagram</a></li>
Syntax not understood
44
-->
Syntax not understood
45
</ul><!-- social-btn -->
Syntax not understood
47
</div><!-- display-table -->
Syntax not understood
48
</div><!-- display-table-cell -->
Syntax not understood
49
</div><!-- main-area -->
Syntax not understood
51
</body>
Syntax not understood
52
</html>
Syntax not understood

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

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 vatandownload.com. This includes details about web app manifests.

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 vatandownload.com on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

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
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.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

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) 80
Performance 94
Accessibility 100
Best Practices 92
SEO 83
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
94

Performance

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

Metrics

Time to Interactive — 2.5 s
The time taken for the page to become fully interactive.
Speed Index — 2.5 s
The time taken for the page contents to be visibly populated.
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).
Largest Contentful Paint — 2.5 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
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://vatandownload.com/
http/1.1
0
91.144999954849
1435
1559
200
text/html
Document
https://fonts.googleapis.com/css?family=Open+Sans:400,700%7CPoppins:400,500
h2
98.036999814212
103.76099986024
1498
7434
200
text/css
Stylesheet
http://vatandownload.com/common-css/ionicons.css
http/1.1
98.13699987717
170.45899992809
9628
57193
200
text/css
Stylesheet
http://vatandownload.com/common-css/jquery.classycountdown.css
http/1.1
98.396999994293
184.5350000076
1064
508
200
text/css
Stylesheet
http://vatandownload.com/03-comming-soon/css/styles.css
http/1.1
98.555999808013
177.54799989052
2067
3905
200
text/css
Stylesheet
http://vatandownload.com/03-comming-soon/css/responsive.css
http/1.1
98.668999969959
131.67599984445
1047
1369
200
text/css
Stylesheet
http://vatandownload.com/images/countdown-3-1600x900.jpg
http/1.1
187.94999993406
415.42500001378
138526
137789
200
image/jpeg
Image
https://fonts.gstatic.com/s/poppins/v20/pxiByp8kv8JHgFVrLGT9Z1xlFd2JQEk.woff2
h2
188.49999993108
192.48799979687
8559
7748
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v34/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2
h2
188.6199999135
191.44700001925
40184
39372
200
font/woff2
Font
https://fonts.gstatic.com/s/poppins/v20/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
h2
191.94299983792
194.65899979696
8695
7884
200
font/woff2
Font
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)
94.266
7.947
186.407
6.323
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.

Other

Properly size images
Images can slow down the page's load time. Vatandownload.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Vatandownload.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Vatandownload.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Vatandownload.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Vatandownload.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
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 90 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)
http://vatandownload.com/
92.14
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Vatandownload.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Vatandownload.com 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
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.
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 208 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://vatandownload.com/images/countdown-3-1600x900.jpg
138526
https://fonts.gstatic.com/s/opensans/v34/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2
40184
http://vatandownload.com/common-css/ionicons.css
9628
https://fonts.gstatic.com/s/poppins/v20/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
8695
https://fonts.gstatic.com/s/poppins/v20/pxiByp8kv8JHgFVrLGT9Z1xlFd2JQEk.woff2
8559
http://vatandownload.com/03-comming-soon/css/styles.css
2067
https://fonts.googleapis.com/css?family=Open+Sans:400,700%7CPoppins:400,500
1498
http://vatandownload.com/
1435
http://vatandownload.com/common-css/jquery.classycountdown.css
1064
http://vatandownload.com/03-comming-soon/css/responsive.css
1047
Avoids an excessive DOM size — 7 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
7
Maximum DOM Depth
6
Maximum Child Elements
3
Avoid chaining critical requests — 7 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Vatandownload.com 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)
http://vatandownload.com/
84.332
10.856
5.128
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
74.976
Style & Layout
30.48
Script Evaluation
16.568
Parse HTML & CSS
12.132
Script Parsing & Compilation
5.128
Rendering
4.948
Keep request counts low and transfer sizes small — 10 requests • 208 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
10
212703
Image
1
138526
Font
3
57438
Stylesheet
5
15304
Document
1
1435
Media
0
0
Script
0
0
Other
0
0
Third-party
4
58936
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 Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
58936
0
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
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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 vatandownload.com on mobile screens.
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.

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.

Metrics

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

Audits

First Meaningful Paint — 2.5 s
The time taken for the primary content of the page to be rendered.

Other

Serve images in next-gen formats — Potential savings of 47 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://vatandownload.com/images/countdown-3-1600x900.jpg
137789
48191.65
Serve static assets with an efficient cache policy — 5 resources found
Vatandownload.com 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)
http://vatandownload.com/images/countdown-3-1600x900.jpg
14400000
138526
http://vatandownload.com/common-css/ionicons.css
14400000
9628
http://vatandownload.com/03-comming-soon/css/styles.css
14400000
2067
http://vatandownload.com/common-css/jquery.classycountdown.css
14400000
1064
http://vatandownload.com/03-comming-soon/css/responsive.css
14400000
1047

Other

Eliminate render-blocking resources — Potential savings of 1,840 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Vatandownload.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css?family=Open+Sans:400,700%7CPoppins:400,500
1498
780
http://vatandownload.com/common-css/ionicons.css
9628
330
http://vatandownload.com/common-css/jquery.classycountdown.css
1064
330
http://vatandownload.com/03-comming-soon/css/styles.css
2067
330
http://vatandownload.com/03-comming-soon/css/responsive.css
1047
330
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/poppins/v20/pxiByp8kv8JHgFVrLGT9Z1xlFd2JQEk.woff2
3.9879998657852
https://fonts.gstatic.com/s/opensans/v34/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2
2.8270001057535
https://fonts.gstatic.com/s/poppins/v20/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
2.7159999590367
First Contentful Paint (3G) — 4890 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
100

Accessibility

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

Audio and video

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that vatandownload.com 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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 6 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://vatandownload.com/
Allowed
http://vatandownload.com/common-css/ionicons.css
Allowed
http://vatandownload.com/common-css/jquery.classycountdown.css
Allowed
http://vatandownload.com/03-comming-soon/css/styles.css
Allowed
http://vatandownload.com/03-comming-soon/css/responsive.css
Allowed
http://vatandownload.com/images/countdown-3-1600x900.jpg
Allowed
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for vatandownload.com. 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 vatandownload.com 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
100.00%
≥ 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.
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.
Links are 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.
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.

Content Best Practices

Document does not have 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.

Crawling and Indexing

robots.txt is not valid — 35 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<!DOCTYPE HTML>
Syntax not understood
2
<html lang="en">
Syntax not understood
3
<head>
Syntax not understood
4
<title>Under Maintenance</title>
Syntax not understood
5
<meta http-equiv="X-UA-Compatible" content="IE=edge">
Syntax not understood
6
<meta name="viewport" content="width=device-width, initial-scale=1">
Syntax not understood
7
<meta charset="UTF-8">
Syntax not understood
10
<!-- Font -->
Syntax not understood
12
<link href="https://fonts.googleapis.com/css?family=Open+Sans:400,700%7CPoppins:400,500" rel="stylesheet">
Unknown directive
15
<link href="common-css/ionicons.css" rel="stylesheet">
Syntax not understood
18
<link rel="stylesheet" href="common-css/jquery.classycountdown.css" />
Syntax not understood
20
<link href="03-comming-soon/css/styles.css" rel="stylesheet">
Syntax not understood
22
<link href="03-comming-soon/css/responsive.css" rel="stylesheet">
Syntax not understood
24
</head>
Syntax not understood
25
<body>
Syntax not understood
27
<div class="main-area center-text" style="background-image:url(images/countdown-3-1600x900.jpg);">
Unknown directive
29
<div class="display-table">
Syntax not understood
30
<div class="display-table-cell">
Syntax not understood
32
<h1 class="title font-white"><b>Comming Soon</b></h1>
Syntax not understood
33
<p class="desc font-white">Our website is currently undergoing scheduled maintenance.
Syntax not understood
34
We Should be back shortly. Thank you for your patience.</p>
Syntax not understood
36
<!-- <a class="notify-btn" href="#"><b>NOTIFY US</b></a> -->
Syntax not understood
38
<ul class="social-btn font-white">
Syntax not understood
39
<!--
Syntax not understood
40
<li><a href="#">facebook</a></li>
Syntax not understood
41
<li><a href="#">twitter</a></li>
Syntax not understood
42
<li><a href="#">google</a></li>
Syntax not understood
43
<li><a href="#">instagram</a></li>
Syntax not understood
44
-->
Syntax not understood
45
</ul><!-- social-btn -->
Syntax not understood
47
</div><!-- display-table -->
Syntax not understood
48
</div><!-- display-table-cell -->
Syntax not understood
49
</div><!-- main-area -->
Syntax not understood
51
</body>
Syntax not understood
52
</html>
Syntax not understood

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

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 vatandownload.com. This includes details about web app manifests.

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 vatandownload.com on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

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
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.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

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: 104.21.235.216
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

Private Registration: No
Name: Domain ID Shield Service
Organization: Domain ID Shield Service CO., Limited
Country: HK
City: Hong Kong
State: Hong Kong
Post Code: 253-261
Email: whoisprivacy@domainidshield.com
Phone: +852.30697157
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Onlinenic Inc 216.245.209.236
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 17th June, 2022
Valid To: 17th June, 2023
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: c959965e
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 11725690522880293398650173264630643151
Serial Number (Hex): 08D2492D718B5A3AF93BA756BB5BF9CF
Valid From: 17th June, 2024
Valid To: 17th June, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.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/CloudflareIncECCCA-3.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 : Jun 17 01:10:10.429 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:23:12:47:42:C9:47:0C:57:89:54:A0:93:
80:F3:F3:98:D7:9B:BC:C4:B6:D7:66:E2:B0:A9:57:39:
B9:A4:61:E7:02:20:5E:AD:7F:DF:FC:73:C0:52:7C:55:
44:70:6D:C9:CF:74:4B:F2:B4:21:21:7D:BE:FF:8F:98:
9D:52:27:9D:29:86
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 : Jun 17 01:10:10.444 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:11:83:04:4A:DD:5F:4B:F4:17:04:10:39:
93:FB:D2:EE:1D:62:8B:5F:2A:32:84:E8:26:B9:7A:15:
20:36:BC:06:02:20:5B:96:2A:35:13:BB:EA:40:38:4D:
B3:57:7B:10:37:F0:82:D2:7B:9D:04:04:44:95:A6:CF:
C7:59:F1:BE:6C:E2
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
Timestamp : Jun 17 01:10:10.418 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:12:64:D3:ED:37:03:C8:36:A0:C6:41:00:
5A:51:7E:F0:80:B7:48:60:ED:CF:06:73:6E:FD:D1:FE:
B0:E0:B8:D4:02:20:5B:5D:57:2D:C2:13:5F:5C:E5:EE:
FC:60:84:75:E4:35:EA:3A:FF:8C:69:4B:4E:48:42:64:
46:FC:D6:7C:1B:AB
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:sni.cloudflaressl.com
DNS:vatandownload.com
DNS:*.vatandownload.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 10th February, 2023
Content-Type: text/html
Server: cloudflare
Connection: keep-alive
Last-Modified: 22nd December, 2020
Vary: Accept-Encoding
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=PCP6J1CCQmtIpyhxNAwrGbCNxBZqroqyIRpwfSZEj8xYI7Z%2F%2B6SMyDNw%2FNSV%2FMlie2ngAJ5WoiIt2dCkqile9jzI3PnDnKLScrRrSgadDKUPZ0K1COBZ3ClrxP6wN%2Fmgue%2BnUQ%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 797355b258f615d3-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created: 20th January, 2009
Changed: 29th May, 2022
Expires: 20th January, 2025
Registrar: Onlinenic Inc
Status: clientTransferProhibited
Nameservers: bayan.ns.cloudflare.com
maya.ns.cloudflare.com
Owner Name: Domain ID Shield Service
Owner Organization: Domain ID Shield Service CO., Limited
Owner Street: RM 1902 EASEY COMM BLDG 253-261 HENNESSY ROAD WANCHAI
Owner Post Code: 253-261
Owner City: Hong Kong
Owner State: Hong Kong
Owner Country: HK
Owner Phone: +852.30697157
Owner Email: whoisprivacy@domainidshield.com
Admin Name: Domain ID Shield Service
Admin Organization: Domain ID Shield Service CO., Limited
Admin Street: RM 1902 EASEY COMM BLDG 253-261 HENNESSY ROAD WANCHAI
Admin Post Code: 253-261
Admin City: Hong Kong
Admin State: Hong Kong
Admin Country: HK
Admin Phone: +852.30697157
Admin Email: whoisprivacy@domainidshield.com
Tech Name: Domain ID Shield Service
Tech Organization: Domain ID Shield Service CO., Limited
Tech Street: RM 1902 EASEY COMM BLDG 253-261 HENNESSY ROAD WANCHAI
Tech Post Code: 253-261
Tech City: Hong Kong
Tech State: Hong Kong
Tech Country: HK
Tech Phone: +852.30697157
Tech Email: whoisprivacy@domainidshield.com
Full Whois: Domain Name: vatandownload.com
Registry Domain ID: 1538308676_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.onlinenic.com
Registrar URL: http://www.onlinenic.com
Updated Date: 2022-05-29T06:35:41Z
Creation Date: 2009-01-20T04:00:00Z
Registrar Registration Expiration Date: 2025-01-20T04:00:00Z
Registrar: Onlinenic Inc
Registrar IANA ID: 82
Registrar Abuse Contact Email: abuse@onlinenic.com
Registrar Abuse Contact Phone: +1.5107698492
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Domain ID Shield Service
Registrant Organization: Domain ID Shield Service CO., Limited
Registrant Street: RM 1902 EASEY COMM BLDG 253-261 HENNESSY ROAD WANCHAI
Registrant City: Hong Kong
Registrant State/Province: Hong Kong
Registrant Postal Code: 253-261
Registrant Country: HK
Registrant Phone: +852.30697157
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: whoisprivacy@domainidshield.com
Registry Admin ID: Not Available From Registry
Admin Name: Domain ID Shield Service
Admin Organization: Domain ID Shield Service CO., Limited
Admin Street: RM 1902 EASEY COMM BLDG 253-261 HENNESSY ROAD WANCHAI
Admin City: Hong Kong
Admin State/Province: Hong Kong
Admin Postal Code: 253-261
Admin Country: HK
Admin Phone: +852.30697157
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: whoisprivacy@domainidshield.com
Registry Tech ID: Not Available From Registry
Tech Name: Domain ID Shield Service
Tech Organization: Domain ID Shield Service CO., Limited
Tech Street: RM 1902 EASEY COMM BLDG 253-261 HENNESSY ROAD WANCHAI
Tech City: Hong Kong
Tech State/Province: Hong Kong
Tech Postal Code: 253-261
Tech Country: HK
Tech Phone: +852.30697157
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: whoisprivacy@domainidshield.com
Name Server: bayan.ns.cloudflare.com
Name Server: maya.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-05-29T06:35:41Z <<<



For more information on Whois status codes, please visit https://icann.org/epp

This data is provided by OnlineNIC, Inc.
for information purposes, and to assist persons obtaining information
about or related to domain name registration records.
OnlineNIC, Inc. does not guarantee its accuracy.
By submitting a WHOIS query, you agree that you will use this data
only for lawful purposes and that, under no circumstances, you will
use this data to
1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via E-mail
(spam); or
2) enable high volume, automated, electronic processes that apply
to this WHOIS server.
These terms may be changed without prior notice.
By submitting this query, you agree to abide by this policy.

Nameservers

Name IP Address
bayan.ns.cloudflare.com 108.162.193.72
maya.ns.cloudflare.com 108.162.192.194
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$10 USD 1/5
0/5

Sites hosted on the same IP address