thewatchseries.to

thewatchseries.to is SSL secured

Free website and domain report on thewatchseries.to

Last Updated: 5th October, 2022 Update Now
Overview

Snoop Summary for thewatchseries.to

This is a free and comprehensive report about thewatchseries.to. The domain thewatchseries.to is currently hosted on a server located in Netherlands with the IP address 185.107.56.194, where EUR is the local currency and the local language is Dutch. Thewatchseries.to has the potential to be earning an estimated $1 USD per day from advertising revenue. If thewatchseries.to was to be sold it would possibly be worth $1,044 USD (based on the daily revenue potential of the website over a 24 month period). Thewatchseries.to receives an estimated 497 unique visitors every day - a decent amount of traffic! This report was last updated 5th October, 2022.

What is thewatchseries.to?

Thewatchseries.to enables you to watch or download movies and tv series online, including full feature films. We advise against visiting websites like thewatchseries.to due to their potentially illegal/unsafe content.

About thewatchseries.to

Site Preview: thewatchseries.to thewatchseries.to
Title:
Description:
Keywords and Tags: bollywood movies, bollywood tv shows, download movies, download tv shows, full feature films, hollywood movies, hollywood tv shows, potential illegal software, watch movies, watch tv shows
Related Terms:
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

1/5

Valuation

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

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 1,128,239
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 497
Monthly Visitors: 15,127
Yearly Visitors: 181,405
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $43 USD
Yearly Revenue: $517 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: thewatchseries.to 17
Domain Name: thewatchseries 14
Extension (TLD): to 2

Page Speed Analysis

Average Load Time: 0.25 seconds
Load Time Comparison: Faster than 99% of sites

PageSpeed Insights

Avg. (All Categories) 76
Performance 89
Accessibility 78
Best Practices 92
SEO 100
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://ww1.thewatchseries.to/
Updated: 5th October, 2022

3.66 seconds
First Contentful Paint (FCP)
34%
32%
34%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

Simulate loading on desktop
89

Performance

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

Metrics

Time to Interactive — 1.4 s
The time taken for the page to become fully interactive.
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.016
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://thewatchseries.to/
http/1.1
0
72.031999996398
834
473
200
text/html
Document
http://thewatchseries.to/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTY2NDk2MTcxMCwiaWF0IjoxNjY0OTU0NTEwLCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIyc2RobWppOWc3dGhtNDhjaHMzM2lpaTgiLCJuYmYiOjE2NjQ5NTQ1MTAsInRzIjoxNjY0OTU0NTEwMjk4MDgzfQ.ZhtykDMZ2PxmS_43LYHlcMytPHmshE69ZTHC3KvMQ48&sid=6109075a-447e-11ed-9056-309fb7184721
http/1.1
92.789999966044
721.05400002329
426
0
302
text/plain
http://ww1.thewatchseries.to/
http/1.1
721.42399998847
892.20800000476
2069
1751
200
text/html
Document
http://ww1.thewatchseries.to/js/parking.2.97.2.js
http/1.1
898.45799998147
1299.5789999841
22670
69189
200
application/javascript
Script
http://ww1.thewatchseries.to/_fd
http/1.1
1313.8269999763
1446.071000013
2428
3705
200
text/html
Fetch
https://www.google.com/adsense/domains/caf.js
h2
1314.9829999893
1337.5130000059
54886
148096
200
text/javascript
Script
http://ww1.thewatchseries.to/px.gif?ch=1&rn=5.055728472247646
http/1.1
1316.9440000202
1472.3760000197
421
42
200
image/gif
Image
http://ww1.thewatchseries.to/px.gif?ch=2&rn=5.055728472247646
http/1.1
1317.2710000072
1616.0130000208
421
42
200
image/gif
Image
https://partner.googleadservices.com/gampad/cookie.js?domain=ww1.thewatchseries.to&client=dp-bodis30_3ph&product=SAS&callback=__sasCookie
h2
1625.401999976
1637.0860000025
832
194
200
text/javascript
Script
https://www.google.com/afs/ads?psid=3872471141&pcsa=false&channel=pid-bodis-gcontrol102%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol307%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol429&client=dp-bodis30_3ph&r=m&hl=en&max_radlink_len=60&type=3&uiopt=false&swp=as-drid-2898040491288658&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300001%2C17300953%2C17300956%2C17301010%2C17301013%2C17301068%2C17301071%2C17301094%2C17301097&format=r3&nocache=2661664954624857&num=0&output=afd_ads&domain_name=ww1.thewatchseries.to&v=3&bsl=8&pac=1&u_his=2&u_tz=-420&dt=1664954624859&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=76&frm=0&cl=478777160&uio=-&cont=rs&jsid=caf&jsv=478777160&rurl=http%3A%2F%2Fww1.thewatchseries.to%2F&referer=http%3A%2F%2Fthewatchseries.to%2F&adbw=master-1%3A1334
h2
1641.4189999923
1730.7670000009
2363
5924
200
text/html
Document
https://www.google.com/adsense/domains/caf.js?pac=1
h2
1744.4510000059
1757.0280000218
54878
148071
200
text/javascript
Script
https://fonts.googleapis.com/css?family=Michroma&display=swap
h2
1780.7869999669
1798.0930000194
1087
396
200
text/css
Stylesheet
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2302198b
h2
1796.7429999844
1802.6459999965
1188
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
h2
1796.9600000069
1803.03000001
1194
444
200
image/svg+xml
Image
https://fonts.gstatic.com/s/michroma/v16/PN_zRfy9qWD8fEagAPg9pTn5_PDb.woff2
h2
1814.4590000156
1818.1110000005
10819
9892
200
font/woff2
Font
http://ww1.thewatchseries.to/_tr
http/1.1
1849.8559999862
1895.5629999982
564
2
200
text/html
Fetch
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=s1obawycxzgu&aqid=ADE9Y9afOIGdmwSiuaX4Cw&psid=3872471141&pbt=bs&adbx=425&adby=65.8125&adbh=500&adbw=500&adbah=150%2C150%2C184&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=478777160&csala=9%7C0%7C111%7C30%7C47&lle=0&llm=1000&ifv=1&usr=1
h2
3326.4339999878
3343.7510000076
713
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=aqvxkxxdqgkb&aqid=ADE9Y9afOIGdmwSiuaX4Cw&psid=3872471141&pbt=bv&adbx=425&adby=65.8125&adbh=500&adbw=500&adbah=150%2C150%2C184&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=478777160&csala=9%7C0%7C111%7C30%7C47&lle=0&llm=1000&ifv=1&usr=1
h2
3827.0720000146
3845.5100000137
351
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)
-11.457
9.543
807.472
9.635
1216.142
13.39
1263.166
8.649
1529.362
25.646
1645.772
8.751
1681.063
28.37
1733.788
28.375
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

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Thewatchseries.to should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Thewatchseries.to should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Thewatchseries.to should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Thewatchseries.to should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Thewatchseries.to should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Thewatchseries.to 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 64 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.google.com/adsense/domains/caf.js
54886
33170
https://www.google.com/adsense/domains/caf.js?pac=1
54878
32004
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 170 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://ww1.thewatchseries.to/
171.778
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Thewatchseries.to should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
http://ww1.thewatchseries.to/js/parking.2.97.2.js
144
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 154 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
54886
https://www.google.com/adsense/domains/caf.js?pac=1
54878
http://ww1.thewatchseries.to/js/parking.2.97.2.js
22670
https://fonts.gstatic.com/s/michroma/v16/PN_zRfy9qWD8fEagAPg9pTn5_PDb.woff2
10819
http://ww1.thewatchseries.to/_fd
2428
https://www.google.com/afs/ads?psid=3872471141&pcsa=false&channel=pid-bodis-gcontrol102%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol307%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol429&client=dp-bodis30_3ph&r=m&hl=en&max_radlink_len=60&type=3&uiopt=false&swp=as-drid-2898040491288658&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300001%2C17300953%2C17300956%2C17301010%2C17301013%2C17301068%2C17301071%2C17301094%2C17301097&format=r3&nocache=2661664954624857&num=0&output=afd_ads&domain_name=ww1.thewatchseries.to&v=3&bsl=8&pac=1&u_his=2&u_tz=-420&dt=1664954624859&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=76&frm=0&cl=478777160&uio=-&cont=rs&jsid=caf&jsv=478777160&rurl=http%3A%2F%2Fww1.thewatchseries.to%2F&referer=http%3A%2F%2Fthewatchseries.to%2F&adbw=master-1%3A1334
2363
http://ww1.thewatchseries.to/
2069
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=%2302198b
1188
https://fonts.googleapis.com/css?family=Michroma&display=swap
1087
Uses efficient cache policy on static assets — 2 resources found
Thewatchseries.to can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://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=%2302198b
82800000
1188
Avoids an excessive DOM size — 18 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
18
Maximum DOM Depth
7
Maximum Child Elements
5
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Thewatchseries.to should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
http://ww1.thewatchseries.to/js/parking.2.97.2.js
62.994
56.331
1.034
https://www.google.com/adsense/domains/caf.js?pac=1
51.422
37.457
2.327
Minimizes main-thread work — 0.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
116.142
Other
59.917
Style & Layout
16.763
Script Parsing & Compilation
11.143
Rendering
7.646
Parse HTML & CSS
6.675
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 — 18 requests • 154 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
18
158144
Script
4
133266
Font
1
10819
Document
3
5266
Image
6
4288
Other
3
3418
Stylesheet
1
1087
Media
0
0
Third-party
10
128311
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
113191
0
11906
0
832
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 — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.01587962962963
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of thewatchseries.to on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Metrics

First Contentful Paint — 1.4 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.7 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.5 s
The timing of the largest text or image that is painted.

Audits

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

Other

Avoid multiple page redirects — Potential savings of 260 ms
Redirects can cause additional delays before the page can begin loading. Thewatchseries.to should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://thewatchseries.to/
190
http://thewatchseries.to/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTY2NDk2MTcxMCwiaWF0IjoxNjY0OTU0NTEwLCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIyc2RobWppOWc3dGhtNDhjaHMzM2lpaTgiLCJuYmYiOjE2NjQ5NTQ1MTAsInRzIjoxNjY0OTU0NTEwMjk4MDgzfQ.ZhtykDMZ2PxmS_43LYHlcMytPHmshE69ZTHC3KvMQ48&sid=6109075a-447e-11ed-9056-309fb7184721
70
http://ww1.thewatchseries.to/
0
78

Accessibility

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

Manual Checks

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

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

Audits

Does not use HTTPS — 8 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://thewatchseries.to/
Allowed
http://thewatchseries.to/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTY2NDk2MTcxMCwiaWF0IjoxNjY0OTU0NTEwLCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIyc2RobWppOWc3dGhtNDhjaHMzM2lpaTgiLCJuYmYiOjE2NjQ5NTQ1MTAsInRzIjoxNjY0OTU0NTEwMjk4MDgzfQ.ZhtykDMZ2PxmS_43LYHlcMytPHmshE69ZTHC3KvMQ48&sid=6109075a-447e-11ed-9056-309fb7184721
Allowed
http://ww1.thewatchseries.to/
Allowed
http://ww1.thewatchseries.to/js/parking.2.97.2.js
Allowed
http://ww1.thewatchseries.to/_fd
Allowed
http://ww1.thewatchseries.to/px.gif?ch=1&rn=5.055728472247646
Allowed
http://ww1.thewatchseries.to/px.gif?ch=2&rn=5.055728472247646
Allowed
http://ww1.thewatchseries.to/_tr
Allowed
100

SEO

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

Manual Checks

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

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of thewatchseries.to. 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 thewatchseries.to on mobile screens.

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 74
Performance 65
Accessibility 85
Best Practices 92
SEO 100
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://ww1.thewatchseries.to/
Updated: 5th October, 2022

4.07 seconds
First Contentful Paint (FCP)
35%
25%
40%

0.02 seconds
First Input Delay (FID)
100%
0%
0%

Simulate loading on mobile
65

Performance

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

Metrics

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.033
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://thewatchseries.to/
http/1.1
0
138.0440001376
834
473
200
text/html
Document
http://thewatchseries.to/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTY2NDk2MTg3MiwiaWF0IjoxNjY0OTU0NjcyLCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIyc2RobXQxNHVubmpnZWxndW8ybGZ1bWEiLCJuYmYiOjE2NjQ5NTQ2NzIsInRzIjoxNjY0OTU0NjcyODkzNzExfQ.QNVgrsEV_3ny22XO91kry52PKKCweoDEKz4ONobwZ4U&sid=c1f33036-447e-11ed-8827-a48874382cbe
http/1.1
152.8370003216
1011.6910003126
426
0
302
text/plain
http://ww1.thewatchseries.to/
http/1.1
1012.2250001878
1349.8110002838
2047
1759
200
text/html
Document
http://ww1.thewatchseries.to/js/parking.2.97.2.js
http/1.1
1369.5930000395
1573.8700004295
22670
69189
200
application/javascript
Script
http://ww1.thewatchseries.to/_fd
http/1.1
1592.5190001726
1674.1360002197
2427
3705
200
text/html
Fetch
https://www.google.com/adsense/domains/caf.js
h2
1597.6580004208
1613.5840001516
54749
147917
200
text/javascript
Script
http://ww1.thewatchseries.to/px.gif?ch=1&rn=5.094477529305743
http/1.1
1600.7380001247
1765.2520001866
421
42
200
image/gif
Image
http://ww1.thewatchseries.to/px.gif?ch=2&rn=5.094477529305743
http/1.1
1601.2300001457
1637.8920003772
421
42
200
image/gif
Image
https://partner.googleadservices.com/gampad/cookie.js?domain=ww1.thewatchseries.to&client=dp-bodis30_3ph&product=SAS&callback=__sasCookie
h2
1786.8400001898
1797.4030002952
830
194
200
text/javascript
Script
https://www.google.com/afs/ads?psid=3872471141&pcsa=false&channel=pid-bodis-gcontrol102%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol307%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol429&client=dp-bodis30_3ph&r=m&hl=en&max_radlink_len=60&type=3&uiopt=false&swp=as-drid-2898040491288658&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17300930%2C17300932%2C17300953%2C17300956%2C17301063%2C17301066%2C17301094%2C17301097&format=r3&nocache=6471664954674557&num=0&output=afd_ads&domain_name=ww1.thewatchseries.to&v=3&bsl=8&pac=2&u_his=2&u_tz=-420&dt=1664954674559&u_w=360&u_h=640&biw=360&bih=640&psw=344&psh=76&frm=0&cl=478519958&uio=-&cont=rs&jsid=caf&jsv=478519958&rurl=http%3A%2F%2Fww1.thewatchseries.to%2F&referer=http%3A%2F%2Fthewatchseries.to%2F&adbw=master-1%3A344
h2
1821.3650002144
1962.2400002554
2436
5992
200
text/html
Document
https://www.google.com/adsense/domains/caf.js?pac=2
h2
1977.7520000935
1994.6770002134
54885
148118
200
text/javascript
Script
https://fonts.googleapis.com/css?family=Michroma&display=swap
h2
2022.7630003355
2030.6460000575
1087
396
200
text/css
Stylesheet
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2302198b
h2
2052.7530000545
2059.1620001942
1188
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
h2
2052.9880002141
2059.678000398
1193
444
200
image/svg+xml
Image
https://fonts.gstatic.com/s/michroma/v16/PN_zRfy9qWD8fEagAPg9pTn5_PDb.woff2
h2
2093.526000157
2097.3300002515
10819
9892
200
font/woff2
Font
http://ww1.thewatchseries.to/_tr
http/1.1
2158.2610001788
2428.8440002128
549
2
200
text/html
Fetch
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=wo8xaunqmgj5&aqid=MjE9Y6XYKIT1ogbchbiICg&psid=3872471141&pbt=bs&adbx=0&adby=65.8125&adbh=602&adbw=360&adbah=184%2C218%2C184&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=478519958&csala=28%7C0%7C165%7C37%7C92&lle=0&llm=1000&ifv=1&usr=1
h2
3614.7390003316
3651.9420002587
689
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=5hng7q13fbad&aqid=MjE9Y6XYKIT1ogbchbiICg&psid=3872471141&pbt=bv&adbx=0&adby=65.8125&adbh=602&adbw=360&adbah=184%2C218%2C184&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=478519958&csala=28%7C0%7C165%7C37%7C92&lle=0&llm=1000&ifv=1&usr=1
h2
4115.8900000155
4152.0960000344
327
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)
-8.911
7.419
1208.721
14.747
1428.653
22.136
1476.413
15.218
1616.377
56.532
1815.41
9.479
1857.262
46.498
1905.614
6.309
1913.644
8.091
1921.756
9.649
1939.574
6.486
1955.981
52.048
2008.308
13.329
3458.041
5.571
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

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Thewatchseries.to should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Thewatchseries.to should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Thewatchseries.to should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Thewatchseries.to should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Thewatchseries.to should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Thewatchseries.to should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 340 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://ww1.thewatchseries.to/
338.575
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Thewatchseries.to should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
http://ww1.thewatchseries.to/js/parking.2.97.2.js
144
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 154 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=2
54885
https://www.google.com/adsense/domains/caf.js
54749
http://ww1.thewatchseries.to/js/parking.2.97.2.js
22670
https://fonts.gstatic.com/s/michroma/v16/PN_zRfy9qWD8fEagAPg9pTn5_PDb.woff2
10819
https://www.google.com/afs/ads?psid=3872471141&pcsa=false&channel=pid-bodis-gcontrol102%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol307%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol429&client=dp-bodis30_3ph&r=m&hl=en&max_radlink_len=60&type=3&uiopt=false&swp=as-drid-2898040491288658&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17300930%2C17300932%2C17300953%2C17300956%2C17301063%2C17301066%2C17301094%2C17301097&format=r3&nocache=6471664954674557&num=0&output=afd_ads&domain_name=ww1.thewatchseries.to&v=3&bsl=8&pac=2&u_his=2&u_tz=-420&dt=1664954674559&u_w=360&u_h=640&biw=360&bih=640&psw=344&psh=76&frm=0&cl=478519958&uio=-&cont=rs&jsid=caf&jsv=478519958&rurl=http%3A%2F%2Fww1.thewatchseries.to%2F&referer=http%3A%2F%2Fthewatchseries.to%2F&adbw=master-1%3A344
2436
http://ww1.thewatchseries.to/_fd
2427
http://ww1.thewatchseries.to/
2047
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
1193
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2302198b
1188
https://fonts.googleapis.com/css?family=Michroma&display=swap
1087
Uses efficient cache policy on static assets — 2 resources found
Thewatchseries.to can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
82800000
1193
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2302198b
82800000
1188
Avoids an excessive DOM size — 18 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
18
Maximum DOM Depth
7
Maximum Child Elements
5
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Thewatchseries.to 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://ww1.thewatchseries.to/js/parking.2.97.2.js
461.532
436.596
3.744
https://www.google.com/adsense/domains/caf.js?pac=2
408.968
266.536
8.92
https://www.google.com/adsense/domains/caf.js
175.1
92.856
10.904
http://ww1.thewatchseries.to/
163.22
18.192
11.268
Unattributable
140.224
5.004
0
https://www.google.com/afs/ads?psid=3872471141&pcsa=false&channel=pid-bodis-gcontrol102%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol307%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol429&client=dp-bodis30_3ph&r=m&hl=en&max_radlink_len=60&type=3&uiopt=false&swp=as-drid-2898040491288658&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17300930%2C17300932%2C17300953%2C17300956%2C17301063%2C17301066%2C17301094%2C17301097&format=r3&nocache=6471664954674557&num=0&output=afd_ads&domain_name=ww1.thewatchseries.to&v=3&bsl=8&pac=2&u_his=2&u_tz=-420&dt=1664954674559&u_w=360&u_h=640&biw=360&bih=640&psw=344&psh=76&frm=0&cl=478519958&uio=-&cont=rs&jsid=caf&jsv=478519958&rurl=http%3A%2F%2Fww1.thewatchseries.to%2F&referer=http%3A%2F%2Fthewatchseries.to%2F&adbw=master-1%3A344
111.792
10.332
6.936
Minimizes main-thread work — 1.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
836.584
Other
345.5
Style & Layout
140.624
Rendering
59.044
Parse HTML & CSS
52.552
Script Parsing & Compilation
42.576
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 — 18 requests • 154 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
18
157998
Script
4
133134
Font
1
10819
Document
3
5317
Image
6
4239
Other
3
3402
Stylesheet
1
1087
Media
0
0
Third-party
10
128203
Minimize third-party usage — Third-party code blocked the main thread for 80 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)
113086
79.304
11906
0
830
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 — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.03349609375
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 6 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
http://ww1.thewatchseries.to/js/parking.2.97.2.js
3113
208
https://www.google.com/adsense/domains/caf.js?pac=2
3689
186
http://ww1.thewatchseries.to/js/parking.2.97.2.js
3000
113
http://ww1.thewatchseries.to/js/parking.2.97.2.js
1770
89
https://www.google.com/adsense/domains/caf.js
2939
61
http://ww1.thewatchseries.to/
639
59
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 thewatchseries.to on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Metrics

Time to Interactive — 4.9 s
The time taken for the page to become fully interactive.
Speed Index — 5.7 s
The time taken for the page contents to be visibly populated.

Other

Reduce unused JavaScript — Potential savings of 64 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.google.com/adsense/domains/caf.js
54749
33127
https://www.google.com/adsense/domains/caf.js?pac=2
54885
31992

Metrics

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

Audits

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

Other

Avoid multiple page redirects — Potential savings of 810 ms
Redirects can cause additional delays before the page can begin loading. Thewatchseries.to should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://thewatchseries.to/
630
http://thewatchseries.to/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTY2NDk2MTg3MiwiaWF0IjoxNjY0OTU0NjcyLCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIyc2RobXQxNHVubmpnZWxndW8ybGZ1bWEiLCJuYmYiOjE2NjQ5NTQ2NzIsInRzIjoxNjY0OTU0NjcyODkzNzExfQ.QNVgrsEV_3ny22XO91kry52PKKCweoDEKz4ONobwZ4U&sid=c1f33036-447e-11ed-8827-a48874382cbe
180
http://ww1.thewatchseries.to/
0
First Contentful Paint (3G) — 9299 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
85

Accessibility

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

Contrast

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

Tables and lists

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

Internationalization and localization

`<html>` element has a 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"]`
Thewatchseries.to may provide assistance to deaf or hearing-impaired users with captions on videos.

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

Manual Checks

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

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

Audits

Does not use HTTPS — 8 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://thewatchseries.to/
Allowed
http://thewatchseries.to/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTY2NDk2MTg3MiwiaWF0IjoxNjY0OTU0NjcyLCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIyc2RobXQxNHVubmpnZWxndW8ybGZ1bWEiLCJuYmYiOjE2NjQ5NTQ2NzIsInRzIjoxNjY0OTU0NjcyODkzNzExfQ.QNVgrsEV_3ny22XO91kry52PKKCweoDEKz4ONobwZ4U&sid=c1f33036-447e-11ed-8827-a48874382cbe
Allowed
http://ww1.thewatchseries.to/
Allowed
http://ww1.thewatchseries.to/js/parking.2.97.2.js
Allowed
http://ww1.thewatchseries.to/_fd
Allowed
http://ww1.thewatchseries.to/px.gif?ch=1&rn=5.094477529305743
Allowed
http://ww1.thewatchseries.to/px.gif?ch=2&rn=5.094477529305743
Allowed
http://ww1.thewatchseries.to/_tr
Allowed
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for thewatchseries.to. 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 thewatchseries.to on mobile screens.
Document uses legible font sizes — 75% 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
.privacy
16.67%
11px
.si133
8.33%
10px
75.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
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.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
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 thewatchseries.to. 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 thewatchseries.to 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: 185.107.56.194
Continent: Europe
Country: Netherlands
Netherlands Flag
Region:
City:
Longitude: 4.8995
Latitude: 52.3824
Currencies: EUR
Languages: Dutch

Web Hosting Provider

Name IP Address
Serverhosting
Registration

Domain Registrant

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

Domain Registrar

Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: thewatchseries.to
Issued By: R3
Valid From: 16th September, 2022
Valid To: 15th December, 2022
Subject: CN = thewatchseries.to
Hash: e7b36edd
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03379AAB0D796EAA4A1B3ADBB154B1FD24A5
Serial Number (Hex): 03379AAB0D796EAA4A1B3ADBB154B1FD24A5
Valid From: 16th September, 2024
Valid To: 15th December, 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 : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
Timestamp : Sep 16 22:42:27.993 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:48:92:23:EB:EE:13:A2:C9:E1:06:9F:42:
A9:25:89:BF:0E:E9:48:0F:3F:BF:30:C0:0A:16:A5:83:
54:CB:22:4F:02:21:00:FD:04:D8:7B:FA:F1:02:2A:4B:
D8:42:D6:3E:EA:D3:66:33:9D:38:D7:4E:C8:25:9F:3E:
88:45:95:F3:0B:05:64
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DF:A5:5E:AB:68:82:4F:1F:6C:AD:EE:B8:5F:4E:3E:5A:
EA:CD:A2:12:A4:6A:5E:8E:3B:12:C0:20:44:5C:2A:73
Timestamp : Sep 16 22:42:28.478 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:B7:63:90:6A:5B:42:37:9F:81:A9:6C:
E9:13:55:04:D8:CD:2C:48:FA:E9:52:15:8E:DB:47:EA:
1A:66:EE:70:74:02:21:00:E3:1D:DF:BE:16:3F:40:0A:
99:60:66:A4:88:54:69:F1:8B:00:65:7E:F1:26:69:8C:
35:10:85:36:A0:1B:CF:FE
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:thewatchseries.to
DNS:*.thewatchseries.to
Technical

DNS Lookup

A Records

Host IP Address Class TTL
thewatchseries.to. 23.82.12.34 IN 600

NS Records

Host Nameserver Class TTL
thewatchseries.to. ns1.emu-dns.com. IN 600
thewatchseries.to. ns2.emu-dns.com. IN 600

SOA Records

Domain Name Primary NS Responsible Email TTL
thewatchseries.to. ns1.emu-dns.com. admin.thewatchseries.to. 600

HTTP Response Headers

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: ns1.koaladns.com
ns2.koaladns.com
Full Whois: Tonic whoisd V1.1
thewatchseries ns1.brainydns.com
thewatchseries ns2.brainydns.com

Nameservers

Name IP Address
ns1.koaladns.com 207.244.67.194
ns2.koaladns.com 5.79.65.15
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

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

Sites hosted on the same IP address

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