watchepisodes.com

watchepisodes.com is SSL secured

Free website and domain report on watchepisodes.com

Last Updated: 22nd July, 2022 Update Now
Overview

Snoop Summary for watchepisodes.com

This is a free and comprehensive report about watchepisodes.com. The domain watchepisodes.com is currently hosted on a server located in Netherlands with the IP address 185.107.56.193, where the local currency is EUR and Dutch is the local language. Our records indicate that watchepisodes.com is privately registered by Super Privacy Service LTD c/o Dynadot. If watchepisodes.com was to be sold it would possibly be worth $724 USD (based on the daily revenue potential of the website over a 24 month period). Watchepisodes.com is somewhat popular with an estimated 343 daily unique visitors. This report was last updated 22nd July, 2022.

About watchepisodes.com

Site Preview: watchepisodes.com watchepisodes.com
Title:
Description:
Keywords and Tags: potential illegal software
Related Terms:
Fav Icon:
Age: Over 19 years old
Domain Created: 10th February, 2005
Domain Updated: 3rd January, 2022
Domain Expires: 9th November, 2022
Review

Snoop Score

2/5

Valuation

$724 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 3,878,320
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: 343
Monthly Visitors: 10,440
Yearly Visitors: 125,195
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $30 USD
Yearly Revenue: $357 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: watchepisodes.com 17
Domain Name: watchepisodes 13
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.66 seconds
Load Time Comparison: Faster than 49% of sites

PageSpeed Insights

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

Performance

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

Metrics

Time to Interactive — 1.0 s
The time taken for the page to become fully interactive.
Speed Index — 1.0 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 1.2 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://watchepisodes.com/
http/1.1
0
190.46600000001
834
473
200
text/html
Document
http://watchepisodes.com/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTY1ODUwNjg3NiwiaWF0IjoxNjU4NDk5Njc2LCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIyczIycGFvaGJtbGVtOHIzYzgwamMzNDciLCJuYmYiOjE2NTg0OTk2NzYsInRzIjoxNjU4NDk5Njc2MDIxNTExfQ.jXVS9ek6Rqu1I1sbNFlr0LQ8LtrbrrA3juIK99uvHEY&sid=8bff0378-09c9-11ed-b2fc-509633e0e806
http/1.1
205.01700002933
540.85200000554
411
0
302
text/plain
http://ww1.watchepisodes.com/
http/1.1
541.17099998984
625.28099998599
3277
2551
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
h2
631.78400002653
644.90600000136
53848
146224
200
text/javascript
Script
https://img1.wsimg.com/parking-lander/static/js/2.fd9305fa.chunk.js
h2
631.99399999576
669.67400000431
136258
430169
200
application/javascript
Script
https://img1.wsimg.com/parking-lander/static/js/main.b2dc4f09.chunk.js
h2
632.07599997986
660.78299999936
54496
257717
200
application/javascript
Script
https://api.aws.parking.godaddy.com/v1/domains/domain?domain=ww1.watchepisodes.com&portfolioId=
h2
769.48100002483
826.31899998523
727
0
200
Preflight
https://api.aws.parking.godaddy.com/v1/domains/domain?domain=ww1.watchepisodes.com&portfolioId=
h2
826.75499998732
858.88299997896
1658
963
200
application/json
Fetch
https://partner.googleadservices.com/gampad/cookie.js?domain=ww1.watchepisodes.com&client=dp-namemedia08_3ph&product=SAS&callback=__sasCookie
h2
888.81999999285
901.33600000991
826
194
200
text/javascript
Script
https://www.google.com/afs/ads?adsafe=low&adtest=off&psid=9841729664&pcsa=false&channel=08272&domain_name=watchepisodes.com&client=dp-namemedia08_3ph&r=m&type=3&uiopt=true&swp=as-drid-2927860770008733&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300953%2C17300956%2C17301025%2C17301028&format=r3&nocache=3811658499676737&num=0&output=afd_ads&v=3&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1658499676739&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=940&frm=0&uio=-&cont=relatedLinks&jsid=caf&jsv=461880972&rurl=http%3A%2F%2Fww1.watchepisodes.com%2F&referer=http%3A%2F%2Fwatchepisodes.com%2F&adbw=master-1%3A500
h2
899.21699999832
997.58900003508
2225
5410
200
text/html
Document
https://www.google.com/adsense/domains/caf.js?pac=0
h2
1007.7600000077
1020.4249999952
53839
146208
200
text/javascript
Script
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
h2
1055.0309999962
1061.6259999806
1188
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
h2
1055.2400000161
1061.3219999941
1089
200
200
image/svg+xml
Image
https://api.aws.parking.godaddy.com/v1/parkingEvents
h2
1059.3900000094
1133.3970000269
619
0
200
text/plain
Preflight
https://api.aws.parking.godaddy.com/v1/parkingEvents
h2
1133.8659999892
1153.227999981
539
0
200
text/plain
Fetch
https://www.google.com/afs/gen_204?client=dp-namemedia08_3ph&output=uds_ads_only&zx=5b7mj8c7a981&aqid=XLLaYqWgMIz0ogaW2J_QCA&psid=9841729664&pbt=bs&adbx=425&adby=135&adbh=472&adbw=500&adbah=152%2C152%2C152&adbn=master-1&eawp=partner-dp-namemedia08_3ph&errv=461880972&csala=5%7C0%7C115%7C29%7C36&lle=0&llm=1000&ifv=1&usr=1
h2
2577.0860000048
2598.8539999817
713
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-namemedia08_3ph&output=uds_ads_only&zx=brlv1l4xuq5n&aqid=XLLaYqWgMIz0ogaW2J_QCA&psid=9841729664&pbt=bv&adbx=425&adby=135&adbh=472&adbw=500&adbah=152%2C152%2C152&adbn=master-1&eawp=partner-dp-namemedia08_3ph&errv=461880972&csala=5%7C0%7C115%7C29%7C36&lle=0&llm=1000&ifv=1&usr=1
h2
3078.1410000054
3102.5140000274
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)
216.594
8.159
651.329
8.778
679.887
6.366
713.926
7.512
721.485
71.331
884.793
15.936
900.739
5.098
906.102
16.522
1023.386
5.511
1054.95
23.529
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 — Potential savings of 80 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Watchepisodes.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.google.com/adsense/domains/caf.js
53848
310
Properly size images
Images can slow down the page's load time. Watchepisodes.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Watchepisodes.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Watchepisodes.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Watchepisodes.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Watchepisodes.com 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 90 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://ww1.watchepisodes.com/
85.104
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Watchepisodes.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 21 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)
https://img1.wsimg.com/parking-lander/static/js/2.fd9305fa.chunk.js
21196
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 306 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://img1.wsimg.com/parking-lander/static/js/2.fd9305fa.chunk.js
136258
https://img1.wsimg.com/parking-lander/static/js/main.b2dc4f09.chunk.js
54496
https://www.google.com/adsense/domains/caf.js
53848
https://www.google.com/adsense/domains/caf.js?pac=0
53839
http://ww1.watchepisodes.com/
3277
https://www.google.com/afs/ads?adsafe=low&adtest=off&psid=9841729664&pcsa=false&channel=08272&domain_name=watchepisodes.com&client=dp-namemedia08_3ph&r=m&type=3&uiopt=true&swp=as-drid-2927860770008733&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300953%2C17300956%2C17301025%2C17301028&format=r3&nocache=3811658499676737&num=0&output=afd_ads&v=3&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1658499676739&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=940&frm=0&uio=-&cont=relatedLinks&jsid=caf&jsv=461880972&rurl=http%3A%2F%2Fww1.watchepisodes.com%2F&referer=http%3A%2F%2Fwatchepisodes.com%2F&adbw=master-1%3A500
2225
https://api.aws.parking.godaddy.com/v1/domains/domain?domain=ww1.watchepisodes.com&portfolioId=
1658
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
1188
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
1089
http://watchepisodes.com/
834
Uses efficient cache policy on static assets — 2 resources found
Watchepisodes.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
82800000
1188
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
82800000
1089
Avoids an excessive DOM size — 55 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
55
Maximum DOM Depth
10
Maximum Child Elements
9
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Watchepisodes.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.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)
https://img1.wsimg.com/parking-lander/static/js/main.b2dc4f09.chunk.js
70.528
67.032
3.229
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
145.609
Other
41.19
Script Parsing & Compilation
17.775
Style & Layout
9.734
Parse HTML & CSS
6.79
Rendering
4.867
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 — 17 requests • 306 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
17
312898
Script
5
299267
Document
3
6336
Other
5
3954
Image
4
3341
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
14
308376
Minimize third-party usage — Third-party code blocked the main thread for 20 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)
194297
16.439
110976
0
826
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 — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://img1.wsimg.com/parking-lander/static/js/main.b2dc4f09.chunk.js
920
71
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 watchepisodes.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Metrics

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

Audits

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

Other

Reduce unused JavaScript — Potential savings of 168 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://img1.wsimg.com/parking-lander/static/js/2.fd9305fa.chunk.js
136258
63881
https://img1.wsimg.com/parking-lander/static/js/main.b2dc4f09.chunk.js
54496
44205
https://www.google.com/adsense/domains/caf.js
53848
32394
https://www.google.com/adsense/domains/caf.js?pac=0
53839
31761
Avoid multiple page redirects — Potential savings of 260 ms
Redirects can cause additional delays before the page can begin loading. Watchepisodes.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://watchepisodes.com/
190
http://watchepisodes.com/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTY1ODUwNjg3NiwiaWF0IjoxNjU4NDk5Njc2LCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIyczIycGFvaGJtbGVtOHIzYzgwamMzNDciLCJuYmYiOjE2NTg0OTk2NzYsInRzIjoxNjU4NDk5Njc2MDIxNTExfQ.jXVS9ek6Rqu1I1sbNFlr0LQ8LtrbrrA3juIK99uvHEY&sid=8bff0378-09c9-11ed-b2fc-509633e0e806
70
http://ww1.watchepisodes.com/
0
85

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of watchepisodes.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
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 `[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"]`
Watchepisodes.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Document doesn't have 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.
Failing Elements
`<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.
92

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
React
core-js
core-js-global@3.22.4
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.
URL Map URL
https://img1.wsimg.com/parking-lander/static/js/main.b2dc4f09.chunk.js
https://img1.wsimg.com/parking-lander/static/js/main.b2dc4f09.chunk.js.map
https://img1.wsimg.com/parking-lander/static/js/2.fd9305fa.chunk.js
https://img1.wsimg.com/parking-lander/static/js/2.fd9305fa.chunk.js.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 3 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://watchepisodes.com/
Allowed
http://watchepisodes.com/?js=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJKb2tlbiIsImV4cCI6MTY1ODUwNjg3NiwiaWF0IjoxNjU4NDk5Njc2LCJpc3MiOiJKb2tlbiIsImpzIjoxLCJqdGkiOiIyczIycGFvaGJtbGVtOHIzYzgwamMzNDciLCJuYmYiOjE2NTg0OTk2NzYsInRzIjoxNjU4NDk5Njc2MDIxNTExfQ.jXVS9ek6Rqu1I1sbNFlr0LQ8LtrbrrA3juIK99uvHEY&sid=8bff0378-09c9-11ed-b2fc-509633e0e806
Allowed
http://ww1.watchepisodes.com/
Allowed
70

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for watchepisodes.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of watchepisodes.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

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.

Content Best Practices

Document doesn't have 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.
Failing Elements
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

Page is blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
Blocking Directive Source

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
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 watchepisodes.com. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of watchepisodes.com on mobile screens.

Installable

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

PWA Optimized

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

Manual Checks

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

Performance

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

Metrics

Total Blocking Time — 150 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.053
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. Watchepisodes.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Watchepisodes.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Watchepisodes.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Watchepisodes.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Watchepisodes.com 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 10 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.watchepisodes.com/
11.242
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Watchepisodes.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://watchepisodes.com/
630
http://ww1.watchepisodes.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Watchepisodes.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 21 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)
https://img1.wsimg.com/parking-lander/static/js/2.fd9305fa.chunk.js
21196
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 305 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://img1.wsimg.com/parking-lander/static/js/2.fd9305fa.chunk.js
136258
https://img1.wsimg.com/parking-lander/static/js/main.b2dc4f09.chunk.js
54496
https://www.google.com/adsense/domains/caf.js
53877
https://www.google.com/adsense/domains/caf.js?pac=0
53839
http://ww1.watchepisodes.com/
3277
https://www.google.com/afs/ads?adsafe=low&adtest=off&psid=3767353295&pcsa=false&channel=08272&domain_name=watchepisodes.com&client=dp-namemedia08_3ph&r=m&type=3&swp=as-drid-2927860770008733&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300953%2C17300956%2C17301030%2C17301033&format=r3&nocache=7121658499694948&num=0&output=afd_ads&v=3&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1658499694949&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=242&frm=0&uio=-&cont=relatedLinks&jsid=caf&jsv=461880972&rurl=http%3A%2F%2Fww1.watchepisodes.com%2F&adbw=master-1%3A360
2355
https://api.aws.parking.godaddy.com/v1/domains/domain?domain=ww1.watchepisodes.com&portfolioId=
1658
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
1188
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
1090
https://partner.googleadservices.com/gampad/cookie.js?domain=ww1.watchepisodes.com&client=dp-namemedia08_3ph&product=SAS&callback=__sasCookie
828
Uses efficient cache policy on static assets — 2 resources found
Watchepisodes.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
82800000
1188
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
82800000
1090
Avoids an excessive DOM size — 21 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
21
Maximum DOM Depth
8
Maximum Child Elements
4
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Watchepisodes.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.7 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://img1.wsimg.com/parking-lander/static/js/main.b2dc4f09.chunk.js
310.66
295.072
14.516
https://www.google.com/adsense/domains/caf.js?pac=0
159.708
105.556
9.5
Unattributable
146.488
74.744
0.56
https://img1.wsimg.com/parking-lander/static/js/2.fd9305fa.chunk.js
126.676
77.984
26.644
http://ww1.watchepisodes.com/
122.536
14.316
7.78
https://www.google.com/adsense/domains/caf.js
82.352
66.008
10.876
https://www.google.com/afs/ads?adsafe=low&adtest=off&psid=3767353295&pcsa=false&channel=08272&domain_name=watchepisodes.com&client=dp-namemedia08_3ph&r=m&type=3&swp=as-drid-2927860770008733&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300953%2C17300956%2C17301030%2C17301033&format=r3&nocache=7121658499694948&num=0&output=afd_ads&v=3&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1658499694949&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=242&frm=0&uio=-&cont=relatedLinks&jsid=caf&jsv=461880972&rurl=http%3A%2F%2Fww1.watchepisodes.com%2F&adbw=master-1%3A360
56.2
6.42
5.484
Minimizes main-thread work — 1.0 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
642.408
Other
175.652
Script Parsing & Compilation
75.628
Style & Layout
46.38
Rendering
37.524
Parse HTML & CSS
30.012
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 — 16 requests • 305 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
16
312178
Script
5
299298
Document
2
5632
Other
5
3954
Image
4
3294
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
14
308490
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.0525146484375
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)
https://img1.wsimg.com/parking-lander/static/js/main.b2dc4f09.chunk.js
3593
314
https://www.google.com/adsense/domains/caf.js?pac=0
4343
99
Unattributable
3143
61
http://ww1.watchepisodes.com/
1260
53
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 watchepisodes.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

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://watchepisodes.com/
http/1.1
0
331.66999998502
411
0
302
text/plain
http://ww1.watchepisodes.com/
http/1.1
332.1139998734
342.36299991608
3277
2551
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
h2
357.55099984817
371.87599996105
53877
146265
200
text/javascript
Script
https://img1.wsimg.com/parking-lander/static/js/2.fd9305fa.chunk.js
h2
358.15699980594
477.07299981266
136258
430169
200
application/javascript
Script
https://img1.wsimg.com/parking-lander/static/js/main.b2dc4f09.chunk.js
h2
358.382999897
444.87999984995
54496
257717
200
application/javascript
Script
https://api.aws.parking.godaddy.com/v1/domains/domain?domain=ww1.watchepisodes.com&portfolioId=
h2
588.10399984941
628.28899989836
727
0
200
Preflight
https://api.aws.parking.godaddy.com/v1/domains/domain?domain=ww1.watchepisodes.com&portfolioId=
h2
628.83699988015
655.48099996522
1658
963
200
application/json
Fetch
https://partner.googleadservices.com/gampad/cookie.js?domain=ww1.watchepisodes.com&client=dp-namemedia08_3ph&product=SAS&callback=__sasCookie
h2
680.92299997807
687.39799992181
828
194
200
text/javascript
Script
https://www.google.com/afs/ads?adsafe=low&adtest=off&psid=3767353295&pcsa=false&channel=08272&domain_name=watchepisodes.com&client=dp-namemedia08_3ph&r=m&type=3&swp=as-drid-2927860770008733&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300953%2C17300956%2C17301030%2C17301033&format=r3&nocache=7121658499694948&num=0&output=afd_ads&v=3&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1658499694949&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=242&frm=0&uio=-&cont=relatedLinks&jsid=caf&jsv=461880972&rurl=http%3A%2F%2Fww1.watchepisodes.com%2F&adbw=master-1%3A360
h2
695.01699996181
834.95099982247
2355
5277
200
text/html
Document
https://www.google.com/adsense/domains/caf.js?pac=0
h2
846.95899998769
859.55099994317
53839
146208
200
text/javascript
Script
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
h2
892.41299987771
900.18499991857
1188
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
h2
892.57599995472
899.67999979854
1090
200
200
image/svg+xml
Image
https://api.aws.parking.godaddy.com/v1/parkingEvents
h2
916.65599984117
936.05899997056
539
0
200
text/plain
Fetch
https://api.aws.parking.godaddy.com/v1/parkingEvents
h2
898.27299979515
916.19599983096
619
0
200
text/plain
Preflight
https://www.google.com/afs/gen_204?client=dp-namemedia08_3ph&output=uds_ads_only&zx=7vvzxznclqym&aqid=b7LaYpGUA9LCowbat634Ag&psid=3767353295&pbt=bs&adbx=0&adby=179&adbh=478&adbw=360&adbah=152%2C152%2C152&adbn=master-1&eawp=partner-dp-namemedia08_3ph&errv=461880972&csala=9%7C0%7C158%7C26%7C45&lle=0&llm=1000&ifv=1&usr=1
h2
2422.5199997891
2442.3399998341
689
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-namemedia08_3ph&output=uds_ads_only&zx=7pa716fjulh&aqid=b7LaYpGUA9LCowbat634Ag&psid=3767353295&pbt=bv&adbx=0&adby=179&adbh=478&adbw=360&adbah=152%2C152%2C152&adbn=master-1&eawp=partner-dp-namemedia08_3ph&errv=461880972&csala=9%7C0%7C158%7C26%7C45&lle=0&llm=1000&ifv=1&usr=1
h2
2923.3169998042
2945.3129998874
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)
380.408
13.184
422.015
9.81
436.817
5.972
535.622
8.443
544.1
78.594
693.6
15.127
708.903
22.798
872.448
7.018
902.654
24.861
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

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

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 450 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Watchepisodes.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.google.com/adsense/domains/caf.js
53877
1230

Metrics

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

Audits

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

Other

Reduce unused JavaScript — Potential savings of 168 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://img1.wsimg.com/parking-lander/static/js/2.fd9305fa.chunk.js
136258
63979
https://img1.wsimg.com/parking-lander/static/js/main.b2dc4f09.chunk.js
54496
44629
https://www.google.com/adsense/domains/caf.js
53877
32403
https://www.google.com/adsense/domains/caf.js?pac=0
53839
31410
Reduce the impact of third-party code — Third-party code blocked the main thread for 270 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)
194297
254.744
111087
14.668
828
0
First Contentful Paint (3G) — 7357 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 watchepisodes.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
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 `[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"]`
Watchepisodes.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Document doesn't have 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.
Failing Elements
`<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.
92

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
React
core-js
core-js-global@3.22.4
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.
URL Map URL
https://img1.wsimg.com/parking-lander/static/js/main.b2dc4f09.chunk.js
https://img1.wsimg.com/parking-lander/static/js/main.b2dc4f09.chunk.js.map
https://img1.wsimg.com/parking-lander/static/js/2.fd9305fa.chunk.js
https://img1.wsimg.com/parking-lander/static/js/2.fd9305fa.chunk.js.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 2 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://watchepisodes.com/
Allowed
http://ww1.watchepisodes.com/
Allowed
75

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for watchepisodes.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of watchepisodes.com on mobile screens.
Document uses legible font sizes — 85.96% 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
.footerLine
14.04%
11px
85.96%
≥ 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.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

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.

Content Best Practices

Document doesn't have 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.
Failing Elements
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

Page is blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
Blocking Directive Source

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
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 watchepisodes.com. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of watchepisodes.com on mobile screens.

Installable

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

PWA Optimized

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

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 185.107.56.193
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: Yes
Name: Super Privacy Service LTD c/o Dynadot
Organization:
Country: US
City: San Mateo
State: California
Post Code: 94401
Email:
Phone: +1.6505854708
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
DYNADOT LLC 104.16.153.132
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: watchepisodes.com
Issued By: R3
Valid From: 5th July, 2022
Valid To: 3rd October, 2022
Subject: CN = watchepisodes.com
Hash: 8e9c7bde
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x0471390A41B686642C0CB3975DEF88EF3D9B
Serial Number (Hex): 0471390A41B686642C0CB3975DEF88EF3D9B
Valid From: 5th July, 2024
Valid To: 3rd October, 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 : Jul 5 12:15:47.013 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:58:E9:A4:7D:1D:5C:83:22:6E:F0:C5:63:
A3:6A:C9:C2:A4:26:9B:7D:96:DC:5B:04:A9:E0:41:C2:
36:4F:08:0D:02:21:00:CF:AC:65:52:CD:90:BE:B5:BF:
5E:FF:6F:E4:FB:CB:22:FE:A6:A7:6B:52:0B:86:EB:14:
22:D7:7D:EA:8A:A1:8C
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
Timestamp : Jul 5 12:15:47.382 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:76:D3:A9:74:C5:EF:74:0B:CF:4A:9F:A3:
01:EF:3C:F2:73:3B:6F:69:20:00:A4:99:70:B0:45:3A:
15:8C:EA:6C:02:20:42:82:F5:24:8A:C1:CE:E0:94:47:
F3:CF:59:89:D1:78:D1:71:F8:25:9A:9B:76:E1:D2:96:
7F:4C:A9:2F:C6:25
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:watchepisodes.com
DNS:*.watchepisodes.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
watchepisodes.com. 74.63.241.25 IN 600

NS Records

Host Nameserver Class TTL
watchepisodes.com. ns1.magpiedns.com. IN 600
watchepisodes.com. ns2.magpiedns.com. IN 600

SOA Records

Domain Name Primary NS Responsible Email TTL
watchepisodes.com. ns1.magpiedns.com. admin.watchepisodes.com. 600

HTTP Response Headers

Whois Lookup

Created: 10th February, 2005
Changed: 3rd January, 2022
Expires: 9th November, 2022
Registrar: DYNADOT LLC
Status: clientTransferProhibited
Nameservers: ns1.brainydns.com
ns2.brainydns.com
Owner Name: Super Privacy Service LTD c/o Dynadot
Owner Street: PO Box 701
Owner Post Code: 94401
Owner City: San Mateo
Owner State: California
Owner Country: US
Owner Phone: +1.6505854708
Owner Email: https://www.dynadot.com/domain/contact-request?domain=watchepisodes.com
Admin Name: Super Privacy Service LTD c/o Dynadot
Admin Street: PO Box 701
Admin Post Code: 94401
Admin City: San Mateo
Admin State: California
Admin Country: US
Admin Phone: +1.6505854708
Admin Email: https://www.dynadot.com/domain/contact-request?domain=watchepisodes.com
Tech Name: Super Privacy Service LTD c/o Dynadot
Tech Street: PO Box 701
Tech Post Code: 94401
Tech City: San Mateo
Tech State: California
Tech Country: US
Tech Phone: +1.6505854708
Tech Email: https://www.dynadot.com/domain/contact-request?domain=watchepisodes.com
Full Whois: Domain Name: WATCHEPISODES.COM
Registry Domain ID: 142065901_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.dynadot.com
Registrar URL: http://www.dynadot.com
Updated Date: 2022-01-03T14:49:53.0Z
Creation Date: 2005-02-10T10:10:08.0Z
Registrar Registration Expiration Date: 2022-11-09T11:59:59.0Z
Registrar: DYNADOT LLC
Registrar IANA ID: 472
Registrar Abuse Contact Email: abuse@dynadot.com
Registrar Abuse Contact Phone: +1.6502620100
Domain Status: clientTransferProhibited
Registry Registrant ID:
Registrant Name: Super Privacy Service LTD c/o Dynadot
Registrant Street: PO Box 701
Registrant Street:
Registrant City: San Mateo
Registrant State/Province: California
Registrant Postal Code: 94401
Registrant Country: US
Registrant Phone: +1.6505854708
Registrant Email: https://www.dynadot.com/domain/contact-request?domain=watchepisodes.com
Registry Admin ID:
Admin Name: Super Privacy Service LTD c/o Dynadot
Admin Street: PO Box 701
Admin Street:
Admin City: San Mateo
Admin State/Province: California
Admin Postal Code: 94401
Admin Country: US
Admin Phone: +1.6505854708
Admin Email: https://www.dynadot.com/domain/contact-request?domain=watchepisodes.com
Registry Tech ID:
Tech Name: Super Privacy Service LTD c/o Dynadot
Tech Street: PO Box 701
Tech Street:
Tech City: San Mateo
Tech State/Province: California
Tech Postal Code: 94401
Tech Country: US
Tech Phone: +1.6505854708
Tech Email: https://www.dynadot.com/domain/contact-request?domain=watchepisodes.com
Name Server: ns1.brainydns.com
Name Server: ns2.brainydns.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-01-03 06:49:53 -0800 <<<

Nameservers

Name IP Address
ns1.brainydns.com 207.244.67.194
ns2.brainydns.com 185.107.56.51
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$403 USD 1/5
$784 USD 1/5
$853 USD 1/5