tamilrockers.nz

tamilrockers.nz is SSL secured

Free website and domain report on tamilrockers.nz

Last Updated: 21st May, 2023 Update Now
Overview

Snoop Summary for tamilrockers.nz

This is a free and comprehensive report about tamilrockers.nz. The domain tamilrockers.nz is currently hosted on a server located in Canada with the IP address 104.247.81.50, where CAD is the local currency and the local language is English. Tamilrockers.nz has the potential to be earning an estimated $2 USD per day from advertising revenue. If tamilrockers.nz was to be sold it would possibly be worth $1,645 USD (based on the daily revenue potential of the website over a 24 month period). Tamilrockers.nz receives an estimated 786 unique visitors every day - a decent amount of traffic! This report was last updated 21st May, 2023.

What is tamilrockers.nz?

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

About tamilrockers.nz

Site Preview: tamilrockers.nz tamilrockers.nz
Title: tamilrockers.nz
Description: See related links to what you are looking for.
Keywords and Tags: bengali movies, bengali tv shows, bollywood movies, bollywood tv shows, hindi movies, hindi tv shows, malayalam movies, malayalam tv shows, potential illegal software, punjabi movies, punjabi tv shows, tamil movies, tamil tv shows, tamilrockers nz, tamilrockers nz tamil movies, tamilrockers nz telugu, telugu movies, telugu tv shows, vaagai sooda vaa poraney poraney karaoke sing along version
Related Terms: ivan thanthiran tamilrockers, mechanic resurrection tamilrockers, moviesda tamilrockers, neeya naana tamilrockers, tamilrockers kuttymovies 2020, tamilrockers moviesda, tamilrockers tags and forums, tamilrockers wc, unakkaga ellam unakkaga tamilrockers, vaanavil vaazhkai tamilrockers hd
Fav Icon:
Age: Over 4 years old
Domain Created: 8th February, 2019
Domain Updated: 17th April, 2023
Domain Expires:
Review

Snoop Score

2/5

Valuation

$1,645 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 920,209
Alexa Reach:
SEMrush Rank (US): 24,367,089
SEMrush Authority Score:
Moz Domain Authority: 19
Moz Page Authority: 31

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 4 0
Traffic: 0 0
Cost: $0 USD $0 USD
Traffic

Visitors

Daily Visitors: 786
Monthly Visitors: 23,923
Yearly Visitors: 286,890
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $2 USD
Monthly Revenue: $68 USD
Yearly Revenue: $818 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

1
Keyword: tamilrockers nz
Ranked Page: http://tamilrockers.nz/index.php/topic/38643-new-member-in-tamilrockers/page-6

2
Keyword: tamilrockers nz tamil movies
Ranked Page: http://tamilrockers.nz/index.php/topic/7839-dhoom2-2006-dvd9-untouched-download-tamil-movie/page-3

3
Keyword: vaagai sooda vaa poraney poraney karaoke sing along version
Ranked Page: http://tamilrockers.nz/index.php/topic/609-mp3-vaagai-suda-va-2011-acd-rip-tamilrockerscom/

4
Keyword: tamilrockers nz telugu
Ranked Page: http://tamilrockers.nz/index.php/topic/51917-bajirao-mastani-20151080p-blu-ray-original-audios-tamil-telugu-hindi-x264-9gb-esubs/

Domain Analysis

Value Length
Domain: tamilrockers.nz 15
Domain Name: tamilrockers 12
Extension (TLD): nz 2

Page Speed Analysis

Average Load Time: 1.89 seconds
Load Time Comparison: Faster than 45% of sites

PageSpeed Insights

Avg. (All Categories) 74
Performance 99
Accessibility 85
Best Practices 83
SEO 80
PWA 25
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
99

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for tamilrockers.nz. 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.
Largest Contentful Paint — 0.8 s
The timing of the largest text or image that is painted.
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).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data
Speed Index — 0.7 s
The time taken for the page contents to be visibly populated.

Audits

Time to Interactive — 0.7 s
The time taken for the page to become fully interactive.
Max Potential First Input Delay — 40 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 Network Request Time (Ms) Network End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://tamilrockers.nz/
http/1.1
1.2300000190735
195.85000002384
6421
16206
200
text/html
Document
http://www.google.com/adsense/domains/caf.js?abp=1
http/1.1
202.69900000095
215.74099993706
54786
148192
200
text/javascript
Script
http://tamilrockers.nz/track.php?domain=tamilrockers.nz&toggle=browserjs&uid=MTY4MDUxNDEyMy40MTI2OmY2Njg3NGMwNGQzZDIzMWMwNzhlZDExYWJhYzlhYTlmNDYxOGZhZGMzMzRkOTM5NmIyNTU0YTMyYjZhMzg0ZmY6NjQyYTljNGI2NGJlNg%3D%3D
http/1.1
242.54499995708
324.95599997044
608
0
200
text/html
XHR
http://d38psrni17bvxu.cloudfront.net/themes/cleanPeppermintBlack_657d9013/img/arrows.png
http/1.1
326.2879999876
365.54499995708
11816
11375
200
image/png
Image
http://tamilrockers.nz/ls.php?t=642a9c4b&token=798ecfc1ac867185dc774de68e275ad2f50dd17c
http/1.1
333.06299996376
423.63600003719
865
16
201
text/javascript
XHR
https://partner.googleadservices.com/gampad/cookie.js?domain=tamilrockers.nz&client=dp-teaminternet04_3ph&product=SAS&callback=__sasCookie
h2
345.8409999609
353.47299993038
768
370
200
text/javascript
Script
https://www.google.com/afs/ads?adtest=off&psid=6016880802&pcsa=false&channel=000002%2Cbucket003&client=dp-teaminternet04_3ph&r=m&hl=en&rpbu=http%3A%2F%2Ftamilrockers.nz%2F%3Fts%3DfENsZWFuUGVwcGVybWludEJsYWNrfHw1Y2U4NHxidWNrZXQwMDN8fHx8fHw2NDJhOWM0YjY0YjlhfHx8MTY4MDUxNDEyMy40MjQ1fGFjYWZjNjk1NDcwYmZmYjFjZDU2MDEzYmIwNjRkZWEyNGQyNDRkYzF8fHx8fDF8fDB8MHx8fHwxfHx8fHwwfDB8fHx8fHx8fFpIQXRkR1ZoYldsdWRHVnlibVYwTURSZk0zQm98ZDgyZjM2MWZiZjFhMmNkYjk1Y2Y3NmRjNjczMTAzZDYzZWVlNTdiZHwwfDB8fDB8fHwwfDB8VzEwPXx8MXxXMTA9fDc5OGVjZmMxYWM4NjcxODVkYzc3NGRlNjhlMjc1YWQyZjUwZGQxN2N8MHxkcC10ZWFtaW50ZXJuZXQwNF8zcGh8MHww&max_radlink_len=40&type=3&uiopt=true&swp=as-drid-2114370249365848&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17301140%2C17301144%2C17301146&format=r3%7Cs&nocache=1841680514123605&num=0&output=afd_ads&domain_name=tamilrockers.nz&v=3&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1680514123608&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=754&frm=0&cl=518347065&uio=--&cont=tc&jsid=caf&jsv=518347065&rurl=http%3A%2F%2Ftamilrockers.nz%2F&adbw=master-1%3A530
h2
361.03499996662
464.60699999332
3262
6687
200
text/html
Document
https://www.google.com/adsense/domains/caf.js?pac=0
h2
477.06299996376
493.6669999361
54675
148092
200
text/javascript
Script
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%23ffffff
h2
549.98899996281
563.04299986362
1070
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
h2
551.25599992275
564.88300001621
974
200
200
image/svg+xml
Image
http://tamilrockers.nz/track.php?domain=tamilrockers.nz&caf=1&toggle=answercheck&answer=yes&uid=MTY4MDUxNDEyMy40MTI2OmY2Njg3NGMwNGQzZDIzMWMwNzhlZDExYWJhYzlhYTlmNDYxOGZhZGMzMzRkOTM5NmIyNTU0YTMyYjZhMzg0ZmY6NjQyYTljNGI2NGJlNg%3D%3D
http/1.1
552.8370000124
743.45299994946
610
0
200
text/html
XHR
https://www.google.com/afs/gen_204?client=dp-teaminternet04_3ph&output=uds_ads_only&zx=i7odq789gauv&aqid=S5wqZMH4KKeR0_wP9Zi24A4&psid=6016880802&pbt=bs&adbx=410&adby=93&adbh=497&adbw=530&adbah=160%2C160%2C160&adbn=master-1&eawp=partner-dp-teaminternet04_3ph&errv=518347065&csala=8%7C0%7C126%7C36%7C275&lle=0&llm=1000&ifv=1&usr=1
h2
2293.1000000238
2311.3189998865
1550
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-teaminternet04_3ph&output=uds_ads_only&zx=ox0pl34o97pl&aqid=S5wqZMH4KKeR0_wP9Zi24A4&psid=6016880802&pbt=bv&adbx=410&adby=93&adbh=497&adbw=530&adbah=160%2C160%2C160&adbn=master-1&eawp=partner-dp-teaminternet04_3ph&errv=518347065&csala=8%7C0%7C126%7C36%7C275&lle=0&llm=1000&ifv=1&usr=1
h2
2794.1649999619
2815.7799999714
1188
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)
198.906
8.616
229.939
8.289
238.26
87.176
330.379
32.655
467.915
9.34
507.904
42.166
550.912
193.133
744.057
19.246
774.511
9.777
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. Tamilrockers.nz should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Tamilrockers.nz should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Tamilrockers.nz should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Tamilrockers.nz should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Tamilrockers.nz should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 63 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?abp=1
54786
32874
https://www.google.com/adsense/domains/caf.js?pac=0
54675
31374
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 200 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://tamilrockers.nz/
195.611
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Tamilrockers.nz should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Tamilrockers.nz 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
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. about preloading LCP elements.
Avoids enormous network payloads — Total size was 135 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://www.google.com/adsense/domains/caf.js?abp=1
54786
https://www.google.com/adsense/domains/caf.js?pac=0
54675
http://d38psrni17bvxu.cloudfront.net/themes/cleanPeppermintBlack_657d9013/img/arrows.png
11816
http://tamilrockers.nz/
6421
https://www.google.com/afs/ads?adtest=off&psid=6016880802&pcsa=false&channel=000002%2Cbucket003&client=dp-teaminternet04_3ph&r=m&hl=en&rpbu=http%3A%2F%2Ftamilrockers.nz%2F%3Fts%3DfENsZWFuUGVwcGVybWludEJsYWNrfHw1Y2U4NHxidWNrZXQwMDN8fHx8fHw2NDJhOWM0YjY0YjlhfHx8MTY4MDUxNDEyMy40MjQ1fGFjYWZjNjk1NDcwYmZmYjFjZDU2MDEzYmIwNjRkZWEyNGQyNDRkYzF8fHx8fDF8fDB8MHx8fHwxfHx8fHwwfDB8fHx8fHx8fFpIQXRkR1ZoYldsdWRHVnlibVYwTURSZk0zQm98ZDgyZjM2MWZiZjFhMmNkYjk1Y2Y3NmRjNjczMTAzZDYzZWVlNTdiZHwwfDB8fDB8fHwwfDB8VzEwPXx8MXxXMTA9fDc5OGVjZmMxYWM4NjcxODVkYzc3NGRlNjhlMjc1YWQyZjUwZGQxN2N8MHxkcC10ZWFtaW50ZXJuZXQwNF8zcGh8MHww&max_radlink_len=40&type=3&uiopt=true&swp=as-drid-2114370249365848&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17301140%2C17301144%2C17301146&format=r3%7Cs&nocache=1841680514123605&num=0&output=afd_ads&domain_name=tamilrockers.nz&v=3&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1680514123608&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=754&frm=0&cl=518347065&uio=--&cont=tc&jsid=caf&jsv=518347065&rurl=http%3A%2F%2Ftamilrockers.nz%2F&adbw=master-1%3A530
3262
https://www.google.com/afs/gen_204?client=dp-teaminternet04_3ph&output=uds_ads_only&zx=i7odq789gauv&aqid=S5wqZMH4KKeR0_wP9Zi24A4&psid=6016880802&pbt=bs&adbx=410&adby=93&adbh=497&adbw=530&adbah=160%2C160%2C160&adbn=master-1&eawp=partner-dp-teaminternet04_3ph&errv=518347065&csala=8%7C0%7C126%7C36%7C275&lle=0&llm=1000&ifv=1&usr=1
1550
https://www.google.com/afs/gen_204?client=dp-teaminternet04_3ph&output=uds_ads_only&zx=ox0pl34o97pl&aqid=S5wqZMH4KKeR0_wP9Zi24A4&psid=6016880802&pbt=bv&adbx=410&adby=93&adbh=497&adbw=530&adbah=160%2C160%2C160&adbn=master-1&eawp=partner-dp-teaminternet04_3ph&errv=518347065&csala=8%7C0%7C126%7C36%7C275&lle=0&llm=1000&ifv=1&usr=1
1188
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%23ffffff
1070
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
974
http://tamilrockers.nz/ls.php?t=642a9c4b&token=798ecfc1ac867185dc774de68e275ad2f50dd17c
865
Uses efficient cache policy on static assets — 3 resources found
Tamilrockers.nz 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://d38psrni17bvxu.cloudfront.net/themes/cleanPeppermintBlack_657d9013/img/arrows.png
0
11816
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%23ffffff
82800000
1070
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
82800000
974
Avoids an excessive DOM size — 27 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
Maximum DOM Depth
Maximum Child Elements
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Tamilrockers.nz 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.4 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://www.google.com/adsense/domains/caf.js?abp=1
212.383
206.225
3.665
http://tamilrockers.nz/
141.717
118.568
2.857
https://www.google.com/adsense/domains/caf.js?pac=0
127.742
87.976000000001
3.384
Minimizes main-thread work — 0.5 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
417.882
Other
68.477
Style & Layout
24.679
Script Parsing & Compilation
12.018
Parse HTML & CSS
10.239
Rendering
3.785
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 — 13 requests • 135 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
13
138593
Script
3
110229
Image
5
16598
Document
2
9683
Other
3
2083
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
9
130089
Minimize third-party usage — Third-party code blocked the main thread for 140 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)
Other Google APIs/SDKs
115461
141.387
cloudfront.net
11816
0
googleusercontent.com
2044
0
Google/Doubleclick Ads
768
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. about optimal lazy loading.
Element
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 — 2 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?abp=1
493
193
http://tamilrockers.nz/
190
87
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 tamilrockers.nz on mobile screens.

Budgets

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

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. Tamilrockers.nz 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://www.google.com/adsense/domains/caf.js?abp=1
54786
270
85

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of tamilrockers.nz. 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 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.

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>`, `<ol>` or `<menu>` 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"]`
Tamilrockers.nz 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.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that tamilrockers.nz 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.
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 input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers. about user-friendly input fields.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

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

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
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://tamilrockers.nz/
Allowed
http://www.google.com/adsense/domains/caf.js?abp=1
Allowed
http://tamilrockers.nz/track.php?domain=tamilrockers.nz&toggle=browserjs&uid=MTY4MDUxNDEyMy40MTI2OmY2Njg3NGMwNGQzZDIzMWMwNzhlZDExYWJhYzlhYTlmNDYxOGZhZGMzMzRkOTM5NmIyNTU0YTMyYjZhMzg0ZmY6NjQyYTljNGI2NGJlNg%3D%3D
Allowed
http://d38psrni17bvxu.cloudfront.net/themes/cleanPeppermintBlack_657d9013/img/arrows.png
Allowed
http://tamilrockers.nz/ls.php?t=642a9c4b&token=798ecfc1ac867185dc774de68e275ad2f50dd17c
Allowed
http://tamilrockers.nz/track.php?domain=tamilrockers.nz&caf=1&toggle=answercheck&answer=yes&uid=MTY4MDUxNDEyMy40MTI2OmY2Njg3NGMwNGQzZDIzMWMwNzhlZDExYWJhYzlhYTlmNDYxOGZhZGMzMzRkOTM5NmIyNTU0YTMyYjZhMzg0ZmY6NjQyYTljNGI2NGJlNg%3D%3D
Allowed

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

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for tamilrockers.nz. 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 tamilrockers.nz 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.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

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

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

Manual Checks

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

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 tamilrockers.nz. 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 tamilrockers.nz 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
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) 74
Performance 88
Accessibility 86
Best Practices 83
SEO 83
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://tamilrockers.nz/
Updated: 1st January, 2023
Simulate loading on mobile
88

Performance

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

Metrics

Time to Interactive — 3.1 s
The time taken for the page to become fully interactive.
Speed Index — 2.8 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 50 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
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Properly size images
Images can slow down the page's load time. Tamilrockers.nz should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Tamilrockers.nz should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Tamilrockers.nz should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Tamilrockers.nz should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Tamilrockers.nz 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 — Potential savings of 24 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://d38psrni17bvxu.cloudfront.net/themes/MobileCleanBlack_8909f63e/bg-inv.jpg
50845
24799.85
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://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
7006
5184
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 120 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://tamilrockers.nz/
115.549
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Tamilrockers.nz should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Tamilrockers.nz 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 178 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?pac=0
54378
http://www.google.com/adsense/domains/caf.js
54333
http://d38psrni17bvxu.cloudfront.net/themes/MobileCleanBlack_8909f63e/bg-inv.jpg
51288
http://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
7460
http://tamilrockers.nz/
5847
https://www.google.com/afs/ads?adtest=off&psid=3164365637&pcsa=false&channel=000002%2Cbucket003&client=dp-teaminternet04_3ph&r=m&hl=en&max_radlink_len=40&type=3&uiopt=true&swp=as-drid-2114370249365848&oe=UTF-8&ie=UTF-8&fexp=21404&format=r1&nocache=9691672583231621&num=0&output=afd_ads&domain_name=tamilrockers.nz&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1672583231623&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=918&frm=0&cl=493016327&uio=-&cont=tc&jsid=caf&jsv=493016327&rurl=http%3A%2F%2Ftamilrockers.nz%2F&adbw=master-1%3A360
2556
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
1194
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%23ffffff
1186
https://www.google.com/afs/gen_204?client=dp-teaminternet04_3ph&output=uds_ads_only&zx=6lm2xs5mluw6&aqid=P5ixY5yKKoyQmAT0wpfoAg&psid=3164365637&pbt=bs&adbx=0&adby=133&adbh=502&adbw=360&adbah=171%2C171%2C145&adbn=master-1&eawp=partner-dp-teaminternet04_3ph&errv=493016327&csala=9%7C0%7C125%7C36%7C120&lle=0&llm=1000&ifv=1&usr=1
893
https://partner.googleadservices.com/gampad/cookie.js?domain=tamilrockers.nz&client=dp-teaminternet04_3ph&product=SAS&callback=__sasCookie
884
Avoids an excessive DOM size — 28 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
28
Maximum DOM Depth
6
Maximum Child Elements
16
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Tamilrockers.nz 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.9 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://www.google.com/adsense/domains/caf.js
317.632
292.324
12.468
http://tamilrockers.nz/
265.424
134.924
15.3
http://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
245.156
242.708
1.46
https://www.google.com/adsense/domains/caf.js?pac=0
203.316
151.38
12.648
Unattributable
110.584
9.296
0
https://www.google.com/afs/ads?adtest=off&psid=3164365637&pcsa=false&channel=000002%2Cbucket003&client=dp-teaminternet04_3ph&r=m&hl=en&max_radlink_len=40&type=3&uiopt=true&swp=as-drid-2114370249365848&oe=UTF-8&ie=UTF-8&fexp=21404&format=r1&nocache=9691672583231621&num=0&output=afd_ads&domain_name=tamilrockers.nz&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1672583231623&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=918&frm=0&cl=493016327&uio=-&cont=tc&jsid=caf&jsv=493016327&rurl=http%3A%2F%2Ftamilrockers.nz%2F&adbw=master-1%3A360
90.884
9.4
8.956
Minimizes main-thread work — 1.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
844.76
Other
190.428
Style & Layout
78.736
Script Parsing & Compilation
51.336
Parse HTML & CSS
44.612
Rendering
28.924
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 — 14 requests • 178 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
14
182633
Script
4
117055
Image
5
55092
Document
2
8403
Other
3
2083
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
10
174703
Minimize third-party usage — Third-party code blocked the main thread for 220 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)
112691
217.308
884
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 — 4 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://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
1309
245
http://www.google.com/adsense/domains/caf.js
2020
230
https://www.google.com/adsense/domains/caf.js?pac=0
3029
144
http://www.google.com/adsense/domains/caf.js
1953
67
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 tamilrockers.nz 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.

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://tamilrockers.nz/
http/1.1
0
114.55900000874
5847
10868
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
http/1.1
127.1640000632
141.11900003627
54333
147308
200
text/javascript
Script
http://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
http/1.1
127.49800004531
160.19299998879
7460
7006
200
application/javascript
Script
http://d38psrni17bvxu.cloudfront.net/themes/MobileCleanBlack_8909f63e/bg-inv.jpg
http/1.1
174.05200004578
218.89500005636
51288
50845
200
image/jpeg
Image
http://tamilrockers.nz/track.php?domain=tamilrockers.nz&toggle=browserjs&uid=MTY3MjU4MzIzMS40MjU1OmI2YmQzMjYzN2Q5OTQwMmUzYzM4YzIyMTEyNTdlYWUzZTU5ODIwYmJlNjdjYzcyNjY2NzJiMWNlYjIwM2E5ZDI6NjNiMTk4M2Y2N2UwZA%3D%3D
http/1.1
187.12000001688
242.55900003482
608
0
200
text/html
XHR
http://tamilrockers.nz/ls.php
http/1.1
247.21599998884
302.73900006432
865
0
201
text/javascript
XHR
https://partner.googleadservices.com/gampad/cookie.js?domain=tamilrockers.nz&client=dp-teaminternet04_3ph&product=SAS&callback=__sasCookie
h2
256.30400003865
261.88800006639
884
370
200
text/javascript
Script
https://www.google.com/afs/ads?adtest=off&psid=3164365637&pcsa=false&channel=000002%2Cbucket003&client=dp-teaminternet04_3ph&r=m&hl=en&max_radlink_len=40&type=3&uiopt=true&swp=as-drid-2114370249365848&oe=UTF-8&ie=UTF-8&fexp=21404&format=r1&nocache=9691672583231621&num=0&output=afd_ads&domain_name=tamilrockers.nz&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1672583231623&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=918&frm=0&cl=493016327&uio=-&cont=tc&jsid=caf&jsv=493016327&rurl=http%3A%2F%2Ftamilrockers.nz%2F&adbw=master-1%3A360
h2
272.44800003245
373.30800003838
2556
5471
200
text/html
Document
https://www.google.com/adsense/domains/caf.js?pac=0
h2
387.83500005957
402.91800000705
54378
147281
200
text/javascript
Script
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%23ffffff
h2
453.91400007065
457.54199998919
1186
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
h2
454.06899997033
459.82900005765
1194
444
200
image/svg+xml
Image
http://tamilrockers.nz/track.php?domain=tamilrockers.nz&caf=1&toggle=answercheck&answer=yes&uid=MTY3MjU4MzIzMS40MjU1OmI2YmQzMjYzN2Q5OTQwMmUzYzM4YzIyMTEyNTdlYWUzZTU5ODIwYmJlNjdjYzcyNjY2NzJiMWNlYjIwM2E5ZDI6NjNiMTk4M2Y2N2UwZA%3D%3D
http/1.1
457.2010000702
512.1860000072
610
0
200
text/html
XHR
https://www.google.com/afs/gen_204?client=dp-teaminternet04_3ph&output=uds_ads_only&zx=6lm2xs5mluw6&aqid=P5ixY5yKKoyQmAT0wpfoAg&psid=3164365637&pbt=bs&adbx=0&adby=133&adbh=502&adbw=360&adbah=171%2C171%2C145&adbn=master-1&eawp=partner-dp-teaminternet04_3ph&errv=493016327&csala=9%7C0%7C125%7C36%7C120&lle=0&llm=1000&ifv=1&usr=1
h2
2051.2100000633
2068.8109999755
893
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-teaminternet04_3ph&output=uds_ads_only&zx=f919dd62s07t&aqid=P5ixY5yKKoyQmAT0wpfoAg&psid=3164365637&pbt=bv&adbx=0&adby=133&adbh=502&adbw=360&adbah=171%2C171%2C145&adbn=master-1&eawp=partner-dp-teaminternet04_3ph&errv=493016327&csala=9%7C0%7C125%7C36%7C120&lle=0&llm=1000&ifv=1&usr=1
h2
2551.5189999714
2568.5920000542
531
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)
121.213
12.357
160.079
10.895
174.564
8.991
183.925
61.289
245.288
33.362
379.808
10.11
420.928
35.893
457.528
57.464
515.008
9.044
524.523
5.534
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 2.8 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 3.2 s
The timing of the largest text or image that is painted.

Audits

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

Other

Reduce unused JavaScript — Potential savings of 63 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
54333
32863
https://www.google.com/adsense/domains/caf.js?pac=0
54378
31464
Serve static assets with an efficient cache policy — 4 resources found
Tamilrockers.nz 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://d38psrni17bvxu.cloudfront.net/themes/MobileCleanBlack_8909f63e/bg-inv.jpg
0
51288
http://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
0
7460
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
82800000
1194
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%23ffffff
82800000
1186

Other

Eliminate render-blocking resources — Potential savings of 1,170 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Tamilrockers.nz 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://www.google.com/adsense/domains/caf.js
54333
1080
First Contentful Paint (3G) — 5516 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
86

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of tamilrockers.nz. 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 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.

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"]`
Tamilrockers.nz 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.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that tamilrockers.nz 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.
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 — 7 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://tamilrockers.nz/
Allowed
http://www.google.com/adsense/domains/caf.js
Allowed
http://d38psrni17bvxu.cloudfront.net/scripts/maincaf.js
Allowed
http://d38psrni17bvxu.cloudfront.net/themes/MobileCleanBlack_8909f63e/bg-inv.jpg
Allowed
http://tamilrockers.nz/track.php?domain=tamilrockers.nz&toggle=browserjs&uid=MTY3MjU4MzIzMS40MjU1OmI2YmQzMjYzN2Q5OTQwMmUzYzM4YzIyMTEyNTdlYWUzZTU5ODIwYmJlNjdjYzcyNjY2NzJiMWNlYjIwM2E5ZDI6NjNiMTk4M2Y2N2UwZA%3D%3D
Allowed
http://tamilrockers.nz/ls.php
Allowed
http://tamilrockers.nz/track.php?domain=tamilrockers.nz&caf=1&toggle=answercheck&answer=yes&uid=MTY3MjU4MzIzMS40MjU1OmI2YmQzMjYzN2Q5OTQwMmUzYzM4YzIyMTEyNTdlYWUzZTU5ODIwYmJlNjdjYzcyNjY2NzJiMWNlYjIwM2E5ZDI6NjNiMTk4M2Y2N2UwZA%3D%3D
Allowed

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 tamilrockers.nz. 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 tamilrockers.nz on mobile screens.
Document uses legible font sizes — 92.86% 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
.si133
7.14%
10px
92.86%
≥ 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.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

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

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

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
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 tamilrockers.nz. 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 tamilrockers.nz 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.247.81.50
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:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
New Zealand Domain Name Registry Limited 93.190.235.135
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: tamilrockers.nz
Issued By: R3
Valid From: 11th May, 2023
Valid To: 9th August, 2023
Subject: CN = tamilrockers.nz
Hash: 03a37e82
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x032915571152810CE26371CDDCB61D705B9A
Serial Number (Hex): 032915571152810CE26371CDDCB61D705B9A
Valid From: 11th May, 2024
Valid To: 9th August, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: 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 : May 11 17:15:00.357 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:2C:47:AB:1E:FF:7C:67:E5:EC:95:75:1C:
DA:52:E9:3B:DA:E5:FA:7D:38:8B:72:61:5F:DF:77:C1:
01:27:6C:9E:02:20:18:0D:CA:85:9D:D8:E6:4B:59:5D:
49:4F:AE:41:E8:B3:ED:08:0C:9B:05:3C:55:D3:E4:0E:
56:06:1B:36:40:4A
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
Timestamp : May 11 17:15:00.394 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:73:7D:75:5A:BC:1B:8D:92:01:59:72:39:
2A:FC:81:59:4D:B5:65:1F:F8:28:41:4D:34:37:41:A5:
5A:84:38:65:02:20:6B:64:58:26:D4:15:8D:F4:89:49:
83:1C:A8:01:F1:92:A6:6D:A5:6E:B1:45:EC:0F:DC:E1:
CB:DC:12:26:79:44
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:tamilrockers.nz
Technical

DNS Lookup

A Records

Host IP Address Class TTL
tamilrockers.nz. 104.247.81.50 IN 600

NS Records

Host Nameserver Class TTL
tamilrockers.nz. ns2.parkingcrew.net. IN 3600
tamilrockers.nz. ns1.parkingcrew.net. IN 3600

MX Records

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

SOA Records

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

TXT Records

Host Value Class TTL
tamilrockers.nz. v=spf1 IN 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 21st May, 2023
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBALquDFETXRn0Hr05fUP7EJT77xYnPmRbpMy4vk8KYiHnkNpednjOANJcaXDXcKQJN0nXKZJL7TciJD8AoHXK158CAwEAAQ==_OLKc6YtEQaiiA5rurIheQES4x0Pm/OQ8FxGkHmhGbI9BWgpe9lZHpH0uAvJhQqCF24dWp/x5/xEK13CZeFACzw==
Accept-CH: ua-mobile
Accept-CH-Lifetime: 30
X-Domain: tamilrockers.nz
X-Subdomain:

Whois Lookup

Created: 8th February, 2019
Changed: 17th April, 2023
Expires:
Registrar: 1API
Status: ok
Nameservers: ns1.parkingcrew.net
ns2.parkingcrew.net
Full Whois: Domain Name: tamilrockers.nz
Registrar URL: http://1api.de
Updated Date: 2023-04-17T13:12:21Z
Creation Date: 2019-08-02T12:34:00Z
Original Created: 2017-04-30T19:48:56Z
Registrar: 1API
Domain Status: ok https://icann.org/epp#ok
Name Server: ns1.parkingcrew.net
Name Server: ns2.parkingcrew.net
DNSSEC: unsigned
URL of the Domain Name Commission Limited Inaccuracy Complaint Form: https://dnc.org.nz/enquiry-form/
>>> Last update of WHOIS database: 2023-05-21T17:05:40Z <<<

% Terms of Use
%
% By submitting a WHOIS query you are entering into an agreement with Domain
% Name Commission Ltd on the following terms and conditions, and subject to
% all relevant .nz Policies and procedures as found at https://dnc.org.nz/.
%
% It is prohibited to:
% - Send high volume WHOIS queries with the effect of downloading part of or
% all of the .nz Register or collecting register data or records;
% - Access the .nz Register in bulk through the WHOIS service (ie. where a
% user is able to access WHOIS data other than by sending individual queries
% to the database);
% - Use WHOIS data to allow, enable, or otherwise support mass unsolicited
% commercial advertising, or mass solicitations to registrants or to
% undertake market research via direct mail, electronic mail, SMS, telephone
% or any other medium;
% - Use WHOIS data in contravention of any applicable data and privacy laws,
% including the Unsolicited Electronic Messages Act 2007;
% - Store or compile WHOIS data to build up a secondary register of
% information;
% - Publish historical or non-current versions of WHOIS data; and
% - Publish any WHOIS data in bulk.
%
% Copyright Domain Name Commission Limited (a company wholly-owned by Internet
% New Zealand Incorporated) which may enforce its rights against any person or
% entity that undertakes any prohibited activity without its written
% permission.
%
% The WHOIS service is provided by Internet New Zealand Incorporated.
%
% Additional information may be available at https://www.dnc.org.nz

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
$10 USD 1/5
$1,204 USD 2/5
$449 USD 1/5
$942 USD 2/5
$449 USD 1/5

Sites hosted on the same IP address