khatrimaza.net

khatrimaza.net may not be SSL secured

Free website and domain report on khatrimaza.net

Last Updated: 18th December, 2021 Update Now
Overview

Snoop Summary for khatrimaza.net

This is a free and comprehensive report about khatrimaza.net. The domain khatrimaza.net is currently hosted on a server located in Canada with the IP address 104.247.81.54, where CAD is the local currency and the local language is English. Our records indicate that khatrimaza.net is owned/operated by Hush Whois Protection Ltd.. If khatrimaza.net was to be sold it would possibly be worth $262 USD (based on the daily revenue potential of the website over a 24 month period). Khatrimaza.net is somewhat popular with an estimated 121 daily unique visitors. This report was last updated 18th December, 2021.

What is khatrimaza.net?

Khatrimaza.net offers dubbed hindi/bollywood movies and tv series online, including full feature films with english subtitles. We advise against visiting websites like khatrimaza.net due to their potentially illegal/unsafe content.

About khatrimaza.net

Site Preview: khatrimaza.net khatrimaza.net
Title: khatrimaza.net
Description: This domain may be for sale!
Keywords and Tags: bengali movies, bengali tv shows, bollywood movies, bollywood tv shows, hindi movies, hindi tv shows, malayalam movies, malayalam tv shows, parked domain, punjabi movies, punjabi tv shows, tamil movies, tamil tv shows, telugu movies, telugu tv shows
Related Terms: khatrimaza blue, khatrimaza bollywood, khatrimaza full .org, khatrimaza full pro, khatrimaza movie, khatrimaza org in, khatrimaza pink, khatrimaza pro, khatrimaza website, khatrimaza. in
Fav Icon:
Age: Over 8 years old
Domain Created: 12th July, 2016
Domain Updated: 17th August, 2021
Domain Expires: 12th July, 2022
Review

Snoop Score

1/5

Valuation

$262 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 7,844,655
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 6
Moz Page Authority: 20

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 121
Monthly Visitors: 3,683
Yearly Visitors: 44,165
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $0 USD
Monthly Revenue: $10 USD
Yearly Revenue: $126 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: khatrimaza.net 14
Domain Name: khatrimaza 10
Extension (TLD): net 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

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

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for khatrimaza.net. 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.
Speed Index — 0.9 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.0 s
The timing of the largest text or image that is painted.
Time to Interactive — 1.2 s
The time taken for the page to become fully interactive.
Total Blocking Time — 90 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).
Cumulative Layout Shift — 0.002
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 1.1 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 110 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.9 s
The time taken for the primary content of the page to be rendered.
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 khatrimaza.net as laggy when the latency is higher than 0.05 seconds.
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://khatrimaza.net/
http/1.1
0
250.74600009248
5738
11323
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
http/1.1
269.02500004508
289.06600002665
61240
172018
200
text/javascript
Script
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
http/1.1
269.28500004578
287.36800001934
827
829
200
text/css
Stylesheet
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermintBlank_0f14f9d7/style.css
http/1.1
269.66600003652
308.48800006788
1055
1417
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Poppins:300
h2
270.00300004147
286.49600001518
1156
1032
200
text/css
Stylesheet
http://c.parkingcrew.net/scripts/sale_form.js
http/1.1
270.35000000615
578.23500002269
1005
761
200
application/javascript
Script
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
http/1.1
270.83100005984
298.72200009413
7454
7000
200
application/javascript
Script
http://khatrimaza.net/track.php?domain=khatrimaza.net&toggle=browserjs&uid=MTYyMjIyMzMyOC40MTY5OmVkYjA2YjI0ZGExZDQ3ZjM3NGRjZjUwMGNiYjg2YWQ2MDdmZTRmZjg5NmQ4YzY2OTVlMDUxM2M4YWIzYjU4ZGQ6NjBiMTI5ZTA2NWM5MA%3D%3D
http/1.1
584.46500007994
671.51600006036
608
0
200
text/html
XHR
http://khatrimaza.net/ls.php
http/1.1
674.70400000457
759.87700000405
864
0
201
text/javascript
XHR
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermintBlank_0f14f9d7/img/arrows.png
http/1.1
684.84300002456
713.89900008217
15986
15544
200
image/png
Image
https://fonts.gstatic.com/s/poppins/v15/pxiByp8kv8JHgFVrLDz8Z1xlFd2JQEk.woff2
h2
685.40700001176
687.86800000817
8455
7848
200
font/woff2
Font
https://www.google.com/afs/ads/i/iframe.html
h2
698.34300002549
702.9830000829
1605
1243
200
text/html
Document
https://www.google.com/dp/ads?adtest=off&channel=000002%2Cbucket101&cpp=0&hl=en&pcsa=false&client=dp-teaminternet01&r=m&psid=9161284804&type=3&max_radlink_len=40&swp=as-drid-oo-1808423912321928&terms=Free%20Hollywood%20Movie%20in%20Hindi%2CFull%20Movie%20HD%20Free%20Download&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300494%2C17300496&format=r5%7Cs&num=0&output=afd_ads&domain_name=khatrimaza.net&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1622223328928&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=864&frm=0&uio=ff2sa16fa2sl1sr1-sa14st24lt34-&cont=tc&csize=w522h0&inames=master-1&jsv=27785&rurl=http%3A%2F%2Fkhatrimaza.net%2F
h2
702.43000006303
948.97400005721
8202
10668
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
h2
965.79400007613
980.61800003052
61863
173008
200
text/javascript
Script
https://fonts.googleapis.com/css?family=Roboto
h2
1018.4390000068
1033.9010000462
1266
2022
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Poppins
h2
1041.7240000097
1060.230000061
1152
1020
200
text/css
Stylesheet
http://khatrimaza.net/track.php?domain=khatrimaza.net&caf=1&toggle=answercheck&answer=yes&uid=MTYyMjIyMzMyOC40MTY5OmVkYjA2YjI0ZGExZDQ3ZjM3NGRjZjUwMGNiYjg2YWQ2MDdmZTRmZjg5NmQ4YzY2OTVlMDUxM2M4YWIzYjU4ZGQ6NjBiMTI5ZTA2NWM5MA%3D%3D
http/1.1
1048.0620000744
1198.2570000691
610
0
200
text/html
XHR
https://www.gstatic.com/domainads/images/chevron-white.png
h2
1202.1570000798
1204.9420000985
737
189
200
image/png
Image
https://www.google.com/js/bg/KuNSwD19LyUwkNIxnIPRrIMMZbJxFq5FsqrfPaukpnw.js
h2
1208.415000001
1212.6510000089
6407
14703
200
text/javascript
Script
https://fonts.gstatic.com/s/roboto/v27/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
1212.0090000099
1215.6820000382
11640
11032
200
font/woff2
Font
https://fonts.gstatic.com/s/poppins/v15/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
h2
1217.6120000659
1220.3410000075
8507
7900
200
font/woff2
Font
https://www.google.com/js/bg/KuNSwD19LyUwkNIxnIPRrIMMZbJxFq5FsqrfPaukpnw.js
h2
1354.6050000004
1354.747000034
6407
14703
200
text/javascript
Script
https://www.google.com/afs/gen_204?client=dp-teaminternet01&output=uds_ads_only&zx=5yl3hu3nxdzl&aqid=4SmxYLS4CIeamgS7tZ6IAw&psid=9161284804&pbt=bs&adbx=414&adby=119&adbh=330&adbw=522&adbn=master-1&eawp=partner-dp-teaminternet01&errv=2778577214847641062&csadii=22&csadr=523&lle=0&llm=1000&ifv=1&usr=0
h2
2725.3690001089
2744.6220000274
461
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-teaminternet01&output=uds_ads_only&zx=kk6uyb8d61g8&psid=9161284804&pbt=bs&adbx=415&adby=466&adbh=20&adbw=521&adbn=slave-1-1&eawp=partner-dp-teaminternet01&errv=2778577214847641062&csadii=16&csadr=531&lle=0&llm=1000&ifv=1&usr=0
h2
2726.2250001077
2750.9070000378
461
0
204
text/html
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
284.29
11.384
336.3
15.638
608.401
125.951
737.886
6.889
981.145
10.604
1019.86
55.142
1075.62
152.399
1228.035
6.543
1237.251
5.681
1255.878
17.131
1273.119
106.342
1384.497
6.277
1392.466
110.707
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Khatrimaza.net should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Khatrimaza.net should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Khatrimaza.net should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Khatrimaza.net should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Khatrimaza.net 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 — Potential savings of 5 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
7000
5173
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 250 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://khatrimaza.net/
251.741
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Khatrimaza.net should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Khatrimaza.net 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 — Potential savings of 110 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermintBlank_0f14f9d7/img/arrows.png
110

Diagnostics

Avoids enormous network payloads — Total size was 209 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js
61863
http://www.google.com/adsense/domains/caf.js
61240
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermintBlank_0f14f9d7/img/arrows.png
15986
https://fonts.gstatic.com/s/roboto/v27/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
11640
https://fonts.gstatic.com/s/poppins/v15/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
8507
https://fonts.gstatic.com/s/poppins/v15/pxiByp8kv8JHgFVrLDz8Z1xlFd2JQEk.woff2
8455
https://www.google.com/dp/ads?adtest=off&channel=000002%2Cbucket101&cpp=0&hl=en&pcsa=false&client=dp-teaminternet01&r=m&psid=9161284804&type=3&max_radlink_len=40&swp=as-drid-oo-1808423912321928&terms=Free%20Hollywood%20Movie%20in%20Hindi%2CFull%20Movie%20HD%20Free%20Download&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300494%2C17300496&format=r5%7Cs&num=0&output=afd_ads&domain_name=khatrimaza.net&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1622223328928&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=864&frm=0&uio=ff2sa16fa2sl1sr1-sa14st24lt34-&cont=tc&csize=w522h0&inames=master-1&jsv=27785&rurl=http%3A%2F%2Fkhatrimaza.net%2F
8202
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
7454
https://www.google.com/js/bg/KuNSwD19LyUwkNIxnIPRrIMMZbJxFq5FsqrfPaukpnw.js
6407
https://www.google.com/js/bg/KuNSwD19LyUwkNIxnIPRrIMMZbJxFq5FsqrfPaukpnw.js
6407
Uses efficient cache policy on static assets — 5 resources found
Khatrimaza.net 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://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermintBlank_0f14f9d7/img/arrows.png
0
15986
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
0
7454
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermintBlank_0f14f9d7/style.css
0
1055
http://c.parkingcrew.net/scripts/sale_form.js
0
1005
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
0
827
Avoids an excessive DOM size — 39 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
39
Maximum DOM Depth
8
Maximum Child Elements
14
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Khatrimaza.net 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.6 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.google.com/adsense/domains/caf.js
288.347
262.456
9.906
http://www.google.com/adsense/domains/caf.js
182.933
166.206
6.235
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
90.912
90.471
0.441
http://khatrimaza.net/
55.292
28.412
3.083
Minimizes main-thread work — 0.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
562.955
Other
61.335
Style & Layout
26.44
Script Parsing & Compilation
25.437
Parse HTML & CSS
12.098
Rendering
7.424
Garbage Collection
6.224
Keep request counts low and transfer sizes small — 24 requests • 209 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
24
213706
Script
6
144376
Font
3
28602
Image
4
17645
Document
3
15545
Stylesheet
5
5456
Other
3
2082
Media
0
0
Third-party
20
205886
Minimize third-party usage — Third-party code blocked the main thread for 230 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)
146646
189.093
26327
38.373
32176
0
737
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
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
div
0.0024132387706856
0.00060413889189157
0.00060413889189157
0.00060413889189157
0.00060413889189157
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoid long main-thread tasks — 5 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
http://www.google.com/adsense/domains/caf.js
633
152
https://www.google.com/js/bg/KuNSwD19LyUwkNIxnIPRrIMMZbJxFq5FsqrfPaukpnw.js
1116
111
https://www.google.com/js/bg/KuNSwD19LyUwkNIxnIPRrIMMZbJxFq5FsqrfPaukpnw.js
1008
106
http://c.parkingcrew.net/scripts/sale_form.js
570
63
https://www.google.com/adsense/domains/caf.js
944
55
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.

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.

Opportunities

Eliminate render-blocking resources — Potential savings of 490 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Khatrimaza.net should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
827
190
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermintBlank_0f14f9d7/style.css
1055
190
https://fonts.googleapis.com/css?family=Poppins:300
1156
230
http://www.google.com/adsense/domains/caf.js
61240
310
Remove unused JavaScript — Potential savings of 74 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.google.com/adsense/domains/caf.js
61240
40379
https://www.google.com/adsense/domains/caf.js
61863
35074

Diagnostics

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/v15/pxiByp8kv8JHgFVrLDz8Z1xlFd2JQEk.woff2
2.4609999964014
https://fonts.gstatic.com/s/roboto/v27/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
3.6730000283569
https://fonts.gstatic.com/s/poppins/v15/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
2.7289999416098
Avoid `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.
Source
86

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of khatrimaza.net. 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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

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"]`
Khatrimaza.net may provide assistance to deaf or hearing-impaired users with captions on videos.

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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements

Manual Checks

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

Best Practices

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

Audits

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

Audits

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

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
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 — 10 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://khatrimaza.net/
Allowed
http://www.google.com/adsense/domains/caf.js
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermintBlank_0f14f9d7/style.css
Allowed
http://c.parkingcrew.net/scripts/sale_form.js
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
Allowed
http://khatrimaza.net/track.php?domain=khatrimaza.net&toggle=browserjs&uid=MTYyMjIyMzMyOC40MTY5OmVkYjA2YjI0ZGExZDQ3ZjM3NGRjZjUwMGNiYjg2YWQ2MDdmZTRmZjg5NmQ4YzY2OTVlMDUxM2M4YWIzYjU4ZGQ6NjBiMTI5ZTA2NWM5MA%3D%3D
Allowed
http://khatrimaza.net/ls.php
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermintBlank_0f14f9d7/img/arrows.png
Allowed
http://khatrimaza.net/track.php?domain=khatrimaza.net&caf=1&toggle=answercheck&answer=yes&uid=MTYyMjIyMzMyOC40MTY5OmVkYjA2YjI0ZGExZDQ3ZjM3NGRjZjUwMGNiYjg2YWQ2MDdmZTRmZjg5NmQ4YzY2OTVlMDUxM2M4YWIzYjU4ZGQ6NjBiMTI5ZTA2NWM5MA%3D%3D
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
90

SEO

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

Crawling and Indexing

Page is 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.
Blocking Directive Source

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

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 khatrimaza.net. 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 khatrimaza.net 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.
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.
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) 61
Performance 63
Accessibility 53
Best Practices 80
SEO 83
Progressive Web App 25
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
63

Performance

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

Metrics

Speed Index — 2.9 s
The time taken for the page contents to be visibly populated.

Opportunities

Properly size images
Images can slow down the page's load time. Khatrimaza.net should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Khatrimaza.net should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Khatrimaza.net should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Khatrimaza.net should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Khatrimaza.net 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 — Potential savings of 5 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
7000
5173
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 110 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://khatrimaza.net/
108.346
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Khatrimaza.net should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Khatrimaza.net 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.

Diagnostics

Avoids enormous network payloads — Total size was 173 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js
61409
http://www.google.com/adsense/domains/caf.js
61229
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_d339b490/img/bg10wide.png
11011
https://www.google.com/dp/ads?adtest=off&channel=000002%2Cbucket038&cpp=0&hl=en&pcsa=false&client=dp-teaminternet01&r=m&psid=1993564836&type=3&max_radlink_len=40&swp=as-drid-oo-1808423912321928&terms=Free%20Hollywood%20Movie%20in%20Hindi%2CFull%20Movie%20HD%20Free%20Download&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300494%2C17300496&format=r5%7Cs&num=0&output=afd_ads&domain_name=khatrimaza.net&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1622223341956&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=377&frm=0&uio=ff2sa16fa2sl1sr1-ff1fa1sa13st16lt50-ff1fa1&cont=tc&csize=w316h0&inames=master-1&jsv=27785&rurl=http%3A%2F%2Fkhatrimaza.net%2F
8879
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
7454
https://www.google.com/js/bg/KuNSwD19LyUwkNIxnIPRrIMMZbJxFq5FsqrfPaukpnw.js
6407
https://www.google.com/js/bg/KuNSwD19LyUwkNIxnIPRrIMMZbJxFq5FsqrfPaukpnw.js
6406
http://khatrimaza.net/
5749
https://www.google.com/afs/ads/i/iframe.html
1464
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_d339b490/style.css
1164
Uses efficient cache policy on static assets — 7 resources found
Khatrimaza.net 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://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_d339b490/img/bg10wide.png
0
11011
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
0
7454
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_d339b490/style.css
0
1164
http://c.parkingcrew.net/scripts/sale_form.js
0
1005
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefaultmobile.css
0
640
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
82800000
824
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
82800000
726
Avoids an excessive DOM size — 37 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
37
Maximum DOM Depth
5
Maximum Child Elements
15
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Khatrimaza.net 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.
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 — 19 requests • 173 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
19
177371
Script
6
143910
Document
3
16092
Image
5
13483
Other
3
2082
Stylesheet
2
1804
Media
0
0
Font
0
0
Third-party
15
169540
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
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.21680196126302
0.12270100911458
Avoid long main-thread tasks — 5 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.google.com/js/bg/KuNSwD19LyUwkNIxnIPRrIMMZbJxFq5FsqrfPaukpnw.js
3245
627
https://www.google.com/js/bg/KuNSwD19LyUwkNIxnIPRrIMMZbJxFq5FsqrfPaukpnw.js
3872
605
http://www.google.com/adsense/domains/caf.js
2049
276
https://www.google.com/adsense/domains/caf.js
2947
220
http://c.parkingcrew.net/scripts/sale_form.js
1867
182
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.

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

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://khatrimaza.net/
http/1.1
0
107.34899999807
5749
11356
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
http/1.1
118.22699999902
133.30100000167
61229
172009
200
text/javascript
Script
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefaultmobile.css
http/1.1
118.40900000243
146.62900000258
640
220
200
text/css
Stylesheet
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_d339b490/style.css
http/1.1
118.57900000177
146.23299999948
1164
1728
200
text/css
Stylesheet
http://c.parkingcrew.net/scripts/sale_form.js
http/1.1
118.84100000316
447.83800000005
1005
761
200
application/javascript
Script
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
http/1.1
119.16100000235
146.89499999804
7454
7000
200
application/javascript
Script
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_d339b490/img/bg10wide.png
http/1.1
156.15300000354
183.29500000254
11011
10569
200
image/png
Image
http://khatrimaza.net/track.php?domain=khatrimaza.net&toggle=browserjs&uid=MTYyMjIyMzM0MS41MTA4OmI1NzE4ZjI1YTNlMTAxZTI3MmVmN2QwMzA4ZjE0YmM5MDIzZWUxMGY3NDM4NzMwNDYzZGE4NmRiY2E3NGE0OGE6NjBiMTI5ZWQ3Y2I1Zg%3D%3D
http/1.1
453.3470000024
512.19500000298
608
0
200
text/html
XHR
http://khatrimaza.net/ls.php
http/1.1
514.62700000411
574.23099999869
864
0
201
text/javascript
XHR
https://www.google.com/afs/ads/i/iframe.html
h2
533.30699999788
537.39199999836
1464
1243
200
text/html
Document
https://www.google.com/dp/ads?adtest=off&channel=000002%2Cbucket038&cpp=0&hl=en&pcsa=false&client=dp-teaminternet01&r=m&psid=1993564836&type=3&max_radlink_len=40&swp=as-drid-oo-1808423912321928&terms=Free%20Hollywood%20Movie%20in%20Hindi%2CFull%20Movie%20HD%20Free%20Download&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300494%2C17300496&format=r5%7Cs&num=0&output=afd_ads&domain_name=khatrimaza.net&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1622223341956&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=377&frm=0&uio=ff2sa16fa2sl1sr1-ff1fa1sa13st16lt50-ff1fa1&cont=tc&csize=w316h0&inames=master-1&jsv=27785&rurl=http%3A%2F%2Fkhatrimaza.net%2F
h2
536.7069999993
641.97799999965
8879
13815
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
h2
652.69899999839
667.13899999741
61409
172009
200
text/javascript
Script
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
h2
723.91500000231
729.73600000114
824
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
h2
724.04800000368
730.13200000423
726
200
200
image/svg+xml
Image
http://khatrimaza.net/track.php?domain=khatrimaza.net&caf=1&toggle=answercheck&answer=yes&uid=MTYyMjIyMzM0MS41MTA4OmI1NzE4ZjI1YTNlMTAxZTI3MmVmN2QwMzA4ZjE0YmM5MDIzZWUxMGY3NDM4NzMwNDYzZGE4NmRiY2E3NGE0OGE6NjBiMTI5ZWQ3Y2I1Zg%3D%3D
http/1.1
733.75099999976
796.24200000399
610
0
200
text/html
XHR
https://www.google.com/js/bg/KuNSwD19LyUwkNIxnIPRrIMMZbJxFq5FsqrfPaukpnw.js
h2
825.9640000033
831.49099999719
6406
14703
200
text/javascript
Script
https://www.google.com/js/bg/KuNSwD19LyUwkNIxnIPRrIMMZbJxFq5FsqrfPaukpnw.js
h2
854.7980000003
858.2779999997
6407
14703
200
text/javascript
Script
https://www.google.com/afs/gen_204?client=dp-teaminternet01&output=uds_ads_only&zx=i52l6fuvfkd7&aqid=7imxYIHsAeuXmwTGpq6oCA&psid=1993564836&pbt=bs&adbx=10&adby=66.46875&adbh=357&adbw=340&adbah=64%2C64%2C64%2C64%2C64&adbn=master-1&eawp=partner-dp-teaminternet01&errv=2778577214847641062&csadii=18&csadr=315&lle=0&llm=1000&ifv=1&usr=1
h2
2354.0320000029
2373.0419999993
461
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-teaminternet01&output=uds_ads_only&zx=9ttyfhgvp2up&psid=1993564836&pbt=bs&adbx=10&adby=448.46875&adbh=18&adbw=340&adbn=slave-1-1&eawp=partner-dp-teaminternet01&errv=2778577214847641062&csadii=14&csadr=320&lle=0&llm=1000&ifv=1&usr=1
h2
2356.0579999976
2379.8620000016
461
0
204
text/html
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
138.344
5.964
173.075
8.656
183.18
6.28
476.784
91.059
569.118
6.181
672.633
5.776
704.491
55.036
760.131
69.002
829.153
12.027
855.065
18.912
883.135
7.831
891.123
156.77
1051.96
151.25
2376.511
5.891
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Metrics

First Contentful Paint — 2.9 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 3.0 s
The timing of the largest text or image that is painted.
Time to Interactive — 4.4 s
The time taken for the page to become fully interactive.

Other

First CPU Idle — 4.2 s
The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 2.9 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 5922 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Remove unused JavaScript — Potential savings of 69 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.google.com/adsense/domains/caf.js
61229
40353
https://www.google.com/adsense/domains/caf.js
61409
29949

Diagnostics

Reduce JavaScript execution time — 2.2 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.google.com/adsense/domains/caf.js
1525.74
1405.952
32.488
http://www.google.com/adsense/domains/caf.js
378.192
322.628
15.052
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
248.484
246.584
1.9
http://khatrimaza.net/
175.464
89.916
8.916
Unattributable
153.04
20.68
3.904
https://www.google.com/afs/ads/i/iframe.html
53.32
14.94
3.324
https://www.google.com/js/bg/KuNSwD19LyUwkNIxnIPRrIMMZbJxFq5FsqrfPaukpnw.js
51.148
28.1
9.412
Minimize main-thread work — 2.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
2140.872
Other
223.848
Style & Layout
103.976
Script Parsing & Compilation
82.984
Garbage Collection
39.768
Parse HTML & CSS
35.548
Rendering
31.488

Metrics

Total Blocking Time — 1,190 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).
Cumulative Layout Shift — 0.34
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 630 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 310 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 khatrimaza.net as laggy when the latency is higher than 0.05 seconds.

Opportunities

Eliminate render-blocking resources — Potential savings of 1,600 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Khatrimaza.net should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefaultmobile.css
640
630
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_d339b490/style.css
1164
630
http://www.google.com/adsense/domains/caf.js
61229
1080

Diagnostics

Reduce the impact of third-party code — Third-party code blocked the main thread for 1,450 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)
146716
1256.672
21274
189.108
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
Avoid `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.
Source
53

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of khatrimaza.net. 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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

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 valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

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

Audio and video

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

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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
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

Best practices

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

Manual Checks

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

Best Practices

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

Audits

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

Audits

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

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
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 — 10 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://khatrimaza.net/
Allowed
http://www.google.com/adsense/domains/caf.js
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefaultmobile.css
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_d339b490/style.css
Allowed
http://c.parkingcrew.net/scripts/sale_form.js
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_d339b490/img/bg10wide.png
Allowed
http://khatrimaza.net/track.php?domain=khatrimaza.net&toggle=browserjs&uid=MTYyMjIyMzM0MS41MTA4OmI1NzE4ZjI1YTNlMTAxZTI3MmVmN2QwMzA4ZjE0YmM5MDIzZWUxMGY3NDM4NzMwNDYzZGE4NmRiY2E3NGE0OGE6NjBiMTI5ZWQ3Y2I1Zg%3D%3D
Allowed
http://khatrimaza.net/ls.php
Allowed
http://khatrimaza.net/track.php?domain=khatrimaza.net&caf=1&toggle=answercheck&answer=yes&uid=MTYyMjIyMzM0MS41MTA4OmI1NzE4ZjI1YTNlMTAxZTI3MmVmN2QwMzA4ZjE0YmM5MDIzZWUxMGY3NDM4NzMwNDYzZGE4NmRiY2E3NGE0OGE6NjBiMTI5ZWQ3Y2I1Zg%3D%3D
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for khatrimaza.net. 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 khatrimaza.net on mobile screens.
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
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.
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.

Crawling and Indexing

Page is 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.
Blocking Directive Source

Mobile Friendly

Document doesn't use legible font sizes — 8.43% 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
#sub
91.57%
10px
8.43%
≥ 12px

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

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 khatrimaza.net. 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 khatrimaza.net 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.
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.
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.247.81.54
Continent: North America
Country: Canada
Canada Flag
Region:
City:
Longitude: -79.3716
Latitude: 43.6319
Currencies: CAD
Languages: English
French

Web Hosting Provider

Name IP Address
Team Internet AG
Registration

Domain Registrant

Private Registration: No
Name: Domain Admin
Organization: Hush Whois Protection Ltd.
Country: SC
City: Providence, Mahe
State: SC
Post Code: 10001
Email: 289626@hush.sc
Phone: +248.4293949
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

Technical

DNS Lookup

A Records

Host IP Address Class TTL
khatrimaza.net. 104.247.81.54 IN 600

NS Records

Host Nameserver Class TTL
khatrimaza.net. ns2.parkingcrew.net. IN 3600
khatrimaza.net. ns1.parkingcrew.net. IN 3600

MX Records

Priority Host Server Class TTL
5 khatrimaza.net. mail.h-email.net. IN 3600

SOA Records

Domain Name Primary NS Responsible Email TTL
khatrimaza.net. ns1.parkingcrew.net. hostmaster.khatrimaza.net. 10800

TXT Records

Host Value Class TTL
khatrimaza.net. v=spf1 IN 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 18th December, 2021
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBALquDFETXRn0Hr05fUP7EJT77xYnPmRbpMy4vk8KYiHnkNpednjOANJcaXDXcKQJN0nXKZJL7TciJD8AoHXK158CAwEAAQ==_e0JwNJ4j5UWIaqZK7UEl1OFudbULcA2QuAcWqYk/o+BRXjZr1xcGCxfb0ai8+McYGfhKWqjYXs9gOGT6XGQE0g==
Accept-CH: ua-mobile
Accept-CH-Lifetime: 30

Whois Lookup

Created: 12th July, 2016
Changed: 17th August, 2021
Expires: 12th July, 2022
Registrar: Key-Systems GmbH
Status: ok
Nameservers: ns1.parkingcrew.net
ns2.parkingcrew.net
Owner Name: Domain Admin
Owner Organization: Hush Whois Protection Ltd.
Owner Street: Suite 1 Mec Complex Avenue d Aroha
Owner Post Code: 10001
Owner City: Providence, Mahe
Owner Country: SC
Owner Phone: +248.4293949
Owner Email: 289626@hush.sc
Admin Name: Domain Admin
Admin Organization: Hush Whois Protection Ltd.
Admin Street: Suite 1 Mec Complex Avenue d Aroha
Admin Post Code: 10001
Admin City: Providence, Mahe
Admin Country: SC
Admin Phone: +248.4293949
Admin Email: 289626@hush.sc
Tech Name: Domain Admin
Tech Organization: Hush Whois Protection Ltd.
Tech Street: Suite 1 Mec Complex Avenue d Aroha
Tech Post Code: 10001
Tech City: Providence, Mahe
Tech Country: SC
Tech Phone: +248.4293949
Tech Email: 289626@hush.sc
Billing Name: Domain Admin
Billing Organization: Hush Whois Protection Ltd.
Billing Street: Suite 1 Mec Complex Avenue d Aroha
Billing Post Code: 10001
Billing City: Providence, Mahe
Billing Country: SC
Billing Phone: +248.4293949
Billing Fax: +248.4293949
Billing Email: 289626@hush.sc
Full Whois: Domain Name: khatrimaza.net
Registry Domain ID: 2042295164_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.rrpproxy.net
Registrar URL:
Updated Date: 2021-08-17T01:14:25Z
Creation Date: 2016-07-12T18:30:59Z
Registrar Registration Expiration Date: 2022-07-12T18:30:59Z
Registrar: Key-Systems GmbH
Registrar IANA ID: 269
Registrar Abuse Contact Email: abusereport@key-systems.net
Registrar Abuse Contact Phone: +49.68949396850
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: Domain Admin
Registrant Organization: Hush Whois Protection Ltd.
Registrant Street: Suite 1 Mec Complex Avenue d Aroha
Registrant City: Providence, Mahe
Registrant State/Province:
Registrant Postal Code: 10001
Registrant Country: SC
Registrant Phone: +248.4293949
Registrant Phone Ext:
Registrant Fax: +248.4293949
Registrant Fax Ext:
Registrant Email: 289626@hush.sc
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: Domain Admin
Admin Organization: Hush Whois Protection Ltd.
Admin Street: Suite 1 Mec Complex Avenue d Aroha
Admin City: Providence, Mahe
Admin State/Province:
Admin Postal Code: 10001
Admin Country: SC
Admin Phone: +248.4293949
Admin Phone Ext:
Admin Fax: +248.4293949
Admin Fax Ext:
Admin Email: 289626@hush.sc
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: Domain Admin
Tech Organization: Hush Whois Protection Ltd.
Tech Street: Suite 1 Mec Complex Avenue d Aroha
Tech City: Providence, Mahe
Tech State/Province:
Tech Postal Code: 10001
Tech Country: SC
Tech Phone: +248.4293949
Tech Phone Ext:
Tech Fax: +248.4293949
Tech Fax Ext:
Tech Email: 289626@hush.sc
Registry Billing ID: REDACTED FOR PRIVACY
Billing Name: Domain Admin
Billing Organization: Hush Whois Protection Ltd.
Billing Street: Suite 1 Mec Complex Avenue d Aroha
Billing City: Providence, Mahe
Billing State/Province:
Billing Postal Code: 10001
Billing Country: SC
Billing Phone: +248.4293949
Billing Phone Ext:
Billing Fax: +248.4293949
Billing Fax Ext:
Billing Email: 289626@hush.sc
Name Server: ns1.parkingcrew.net
Name Server: ns2.parkingcrew.net
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: https://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-12-18T12:00:54Z <<<

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

To contact the registered registrant please proceed to:
https://www.domain-contact.org


This data is provided by
for information purposes, and to assist persons obtaining information
about or related to domain name registration records.
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
ns1.parkingcrew.net 13.248.158.159
ns2.parkingcrew.net 76.223.21.9
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$1,046 USD 1/5
$305 USD 1/5
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$2,656 USD 2/5
0/5
$601 USD 1/5