watchparty.me

watchparty.me is SSL secured

Free website and domain report on watchparty.me

Last Updated: 16th November, 2024
Overview

Snoop Summary for watchparty.me

This is a free and comprehensive report about watchparty.me. The domain watchparty.me is currently hosted on a server located in United States with the IP address 172.67.134.223, where the local currency is USD and English is the local language. Our records indicate that watchparty.me is privately registered by Privacy service provided by Withheld for Privacy ehf. Watchparty.me has the potential to be earning an estimated $11 USD per day from advertising revenue. If watchparty.me was to be sold it would possibly be worth $8,120 USD (based on the daily revenue potential of the website over a 24 month period). Watchparty.me is quite popular with an estimated 3,898 daily unique visitors. This report was last updated 16th November, 2024.

About watchparty.me

Site Preview: watchparty.me watchparty.me
Title: WatchParty
Description: Watch together with friends. Chat and react in real time to the same stream, whether it's YouTube, your own video, or a virtual browser.
Keywords and Tags: streaming media
Related Terms:
Fav Icon:
Age: Over 4 years old
Domain Created: 9th April, 2020
Domain Updated: 7th June, 2024
Domain Expires: 9th April, 2026
Review

Snoop Score

2/5

Valuation

$8,120 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 160,328
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: 3,898
Monthly Visitors: 118,643
Yearly Visitors: 1,422,770
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $11 USD
Monthly Revenue: $338 USD
Yearly Revenue: $4,055 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: watchparty.me 13
Domain Name: watchparty 10
Extension (TLD): me 2
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 82
Performance 60
Accessibility 93
Best Practices 92
SEO 100
PWA 67
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.watchparty.me/
Updated: 12th December, 2022

2.44 seconds
First Contentful Paint (FCP)
59%
25%
16%

0.01 seconds
First Input Delay (FID)
96%
3%
1%

Simulate loading on desktop
60

Performance

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

Metrics

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

Other

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Watchparty.me should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Watchparty.me should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Watchparty.me should consider minifying JS files.
Reduce unused CSS — Potential savings of 76 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Watchparty.me should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/semantic.min.css
80636
78222
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 220 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)
https://www.watchparty.me/
215.557
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Watchparty.me should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://watchparty.me/
190
https://www.watchparty.me/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Watchparty.me 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)
https://www.watchparty.me/static/js/main.ed47634f.js
53
https://js.stripe.com/v3
41
https://m.stripe.network/out-4.5.42.js
35
Avoids an excessive DOM size — 132 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
132
Maximum DOM Depth
10
Maximum Child Elements
9
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Watchparty.me should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.4 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.watchparty.me/static/js/main.ed47634f.js
335.221
271.621
38.755
https://www.watchparty.me/
109.999
4.091
1.822
https://m.stripe.network/inner.html
92.83
83.591
1.278
Unattributable
70.169
1.875
0
Minimizes main-thread work — 0.9 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
501.075
Other
105.159
Rendering
77.281
Script Parsing & Compilation
62.191
Style & Layout
55.365
Parse HTML & CSS
27.494
Garbage Collection
22.697
Keep request counts low and transfer sizes small — 23 requests • 3,210 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
23
3286698
Image
3
2396800
Script
7
671190
Font
4
124958
Stylesheet
3
86677
Document
3
5070
Other
3
2003
Media
0
0
Third-party
16
496156
Minimize third-party usage — Third-party code blocked the main thread for 30 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)
122850
25.427
190518
0
100845
0
44333
0
21279
0
16331
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.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.064788314289467
0.04909604236905
0.043560083983364
0.037201640351806
0.006263541487804
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 — 3 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.watchparty.me/static/js/main.ed47634f.js
1500
326
https://m.stripe.network/out-4.5.42.js
2486
90
https://cdn.jsdelivr.net/npm/hls.js@latest
1021
50
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 watchparty.me 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://watchparty.me/
http/1.1
0
83.102999997209
727
0
301
text/plain
https://www.watchparty.me/
h2
83.593999996083
298.15599999711
1490
1538
200
text/html
Document
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/semantic.min.css
h2
304.61500000092
361.62299999705
80636
628512
200
text/css
Stylesheet
https://www.watchparty.me/static/js/main.ed47634f.js
h2
305.2899999966
469.86399999878
386739
1700836
200
application/javascript
Script
https://www.watchparty.me/static/css/main.40cbba6b.css
h2
305.48199999612
393.54399999866
4786
15636
200
text/css
Stylesheet
https://cdn.jsdelivr.net/npm/hls.js@latest
h2
305.61899999884
346.30800000014
100845
344695
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-45337794-6
h2
314.065999999
334.79000000079
44333
111580
200
application/javascript
Script
https://fonts.googleapis.com/css?family=Lato:400,700,400italic,700italic&subset=latin
h2
372.01700000151
388.85899999877
1255
2726
200
text/css
Stylesheet
https://www.google-analytics.com/analytics.js
h2
477.36099999747
482.25799999636
20664
50230
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=1552329641&t=pageview&_s=1&dl=https%3A%2F%2Fwww.watchparty.me%2F&ul=en-us&de=UTF-8&dt=WatchParty&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAACAAI~&jid=1471402240&gjid=1798482879&cid=218689443.1670812989&tid=UA-45337794-6&_gid=90837551.1670812989&_r=1&gtm=2oubu0&z=774101351
h2
512.09599999856
515.73900000221
615
1
200
text/plain
XHR
https://js.stripe.com/v3
h2
881.6319999969
923.99699999805
100731
413798
200
text/javascript
Script
https://www.watchparty.me/screenshot4.png
h2
882.21099999646
1013.4909999979
729940
729158
200
image/png
Image
https://www.watchparty.me/screenshot18.png
h2
882.51899999887
1004.608999996
672171
671387
200
image/png
Image
https://www.watchparty.me/screenshot14.png
h2
882.77099999686
1035.7060000024
994689
993911
200
image/png
Image
data
886.16300000285
886.31100000202
0
960
200
image/png
Image
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/themes/default/assets/fonts/icons.woff2
h2
889.60299999599
909.89799999807
41148
40148
200
application/octet-stream
Font
https://fonts.gstatic.com/s/lato/v23/S6u9w4BMUTPHh6UVSwiPGQ3q5d0.woff2
h2
890.23599999928
894.12599999923
15076
14148
200
font/woff2
Font
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/themes/default/assets/fonts/brand-icons.woff2
h2
890.50699999643
913.2529999988
55489
54488
200
application/octet-stream
Font
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/themes/default/assets/fonts/outline-icons.woff2
h2
890.74599999731
910.31900000235
13245
12240
200
application/octet-stream
Font
https://js.stripe.com/v3/m-outer-93afeeb17bc37e711759584dbfc50d47.html
h2
1064.8880000008
1082.405000001
1527
200
200
text/html
Document
https://js.stripe.com/v3/fingerprinted/js/m-outer-8cb24ab2d649fd36a488d04d8c457933.js
h2
1116.3789999991
1133.842999996
1304
631
200
text/javascript
Script
https://m.stripe.network/inner.html
h2
1144.0769999972
1188.3109999981
2053
930
200
text/html
Document
https://m.stripe.network/out-4.5.42.js
h2
1203.9989999976
1222.8170000017
16574
88253
200
text/javascript
Script
https://m.stripe.com/6
h2
1328.8580000008
1419.0699999963
661
156
200
application/json
XHR
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)
302
11.146
367.518
29.112
398.548
49.599
448.16
10.613
460.635
8.21
469.225
9.214
489.928
23.637
553.559
12.267
565.838
326.277
892.137
34.127
928.671
5.894
936.61
5.118
944.551
7.856
968.8
41.518
1026.002
28.418
1058.965
5.477
1064.983
40.243
1105.309
6.887
1193.167
8.589
1231.17
90.405
1323.623
6.091
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 1.3 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 2.6 s
The time taken for the page to become fully interactive.
Total Blocking Time — 300 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.201
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 440 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Watchparty.me 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://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/semantic.min.css
80636
350
Reduce unused JavaScript — Potential savings of 341 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.watchparty.me/static/js/main.ed47634f.js
386739
164107
https://cdn.jsdelivr.net/npm/hls.js@latest
100845
88500
https://js.stripe.com/v3
100731
74532
https://www.googletagmanager.com/gtag/js?id=UA-45337794-6
44333
21937
Preload Largest Contentful Paint image — Potential savings of 440 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.watchparty.me/screenshot4.png
440
Avoid enormous network payloads — Total size was 3,210 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.watchparty.me/screenshot14.png
994689
https://www.watchparty.me/screenshot4.png
729940
https://www.watchparty.me/screenshot18.png
672171
https://www.watchparty.me/static/js/main.ed47634f.js
386739
https://cdn.jsdelivr.net/npm/hls.js@latest
100845
https://js.stripe.com/v3
100731
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/semantic.min.css
80636
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/themes/default/assets/fonts/brand-icons.woff2
55489
https://www.googletagmanager.com/gtag/js?id=UA-45337794-6
44333
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/themes/default/assets/fonts/icons.woff2
41148

Metrics

Largest Contentful Paint — 3.0 s
The timing of the largest text or image that is painted.

Audits

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

Other

Properly size images — Potential savings of 2,221 KiB
Images can slow down the page's load time. Watchparty.me should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.watchparty.me/screenshot14.png
993911
961685
https://www.watchparty.me/screenshot4.png
729158
684978
https://www.watchparty.me/screenshot18.png
671387
627959
Serve images in next-gen formats — Potential savings of 1,579 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.watchparty.me/screenshot14.png
993911
559320.55
https://www.watchparty.me/screenshot18.png
671387
530681.8
https://www.watchparty.me/screenshot4.png
729158
527157.1
Serve static assets with an efficient cache policy — 9 resources found
Watchparty.me 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://js.stripe.com/v3
60000
100731
https://m.stripe.network/out-4.5.42.js
300000
16574
https://www.google-analytics.com/analytics.js
7200000
20664
https://www.watchparty.me/screenshot14.png
14400000
994689
https://www.watchparty.me/screenshot4.png
14400000
729940
https://www.watchparty.me/screenshot18.png
14400000
672171
https://www.watchparty.me/static/js/main.ed47634f.js
14400000
386739
https://www.watchparty.me/static/css/main.40cbba6b.css
14400000
4786
https://cdn.jsdelivr.net/npm/hls.js@latest
604800000
100845
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/themes/default/assets/fonts/icons.woff2
20.295000002079
https://fonts.gstatic.com/s/lato/v23/S6u9w4BMUTPHh6UVSwiPGQ3q5d0.woff2
3.8899999999558
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/themes/default/assets/fonts/brand-icons.woff2
22.746000002371
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/themes/default/assets/fonts/outline-icons.woff2
19.573000005039
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://www.watchparty.me/screenshot14.png
https://www.watchparty.me/screenshot4.png
https://www.watchparty.me/screenshot18.png
93

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of watchparty.me. 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 `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

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

ARIA

ARIA input fields do not 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.
Failing Elements

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

Links do not 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.

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 watchparty.me 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
Create React App
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://cdn.jsdelivr.net/npm/hls.js@latest
https://cdn.jsdelivr.net/npm/hls.min.js.map
https://www.watchparty.me/static/js/main.ed47634f.js
https://www.watchparty.me/static/js/main.ed47634f.js.map
https://js.stripe.com/v3/fingerprinted/js/m-outer-8cb24ab2d649fd36a488d04d8c457933.js
https://js.stripe.com/v3/sourcemaps/m-outer-cb35da7c5fc15bbeac1d5d83b92ec8a6.js.map
https://js.stripe.com/v3
https://js.stripe.com/v3/sourcemaps/stripe-81adcffd0022c9ea1a206a1f4e8ac487.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 — 1 insecure request 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://watchparty.me/
Allowed
100

SEO

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

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

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Sets 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
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 watchparty.me on mobile screens.
Provides 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.

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
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) 76
Performance 26
Accessibility 93
Best Practices 92
SEO 97
PWA 70
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.watchparty.me/
Updated: 12th December, 2022

2.98 seconds
First Contentful Paint (FCP)
48%
28%
24%

0.05 seconds
First Input Delay (FID)
85%
12%
3%

Simulate loading on mobile
26

Performance

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

Metrics

Cumulative Layout Shift — 0.017
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Watchparty.me should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Watchparty.me should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Watchparty.me should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
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)
https://www.watchparty.me/
88.742
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Watchparty.me should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://watchparty.me/
630
https://www.watchparty.me/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Watchparty.me 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.
Avoids an excessive DOM size — 133 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
133
Maximum DOM Depth
10
Maximum Child Elements
9
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Watchparty.me 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.
Keep request counts low and transfer sizes small — 29 requests • 3,527 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
29
3611660
Image
3
2396790
Script
10
993959
Font
4
124950
Stylesheet
3
86667
Document
4
5760
Other
5
3534
Media
0
0
Third-party
22
821153
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.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0089131945937004
0.007750603994522
0.00069970730506102
5.682373046875E-5
5.1839192708333E-5
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 — 10 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.watchparty.me/static/js/main.ed47634f.js
6810
1167
https://m.stripe.network/out-4.5.42.js
11337
378
https://js.stripe.com/v3
10107
237
https://cdn.jsdelivr.net/npm/hls.js@latest
4290
209
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/semantic.min.css
3840
128
https://apis.google.com/_/scs/abc-static/_/js/k=gapi.lb.en.geaHZXF2-fw.O/m=gapi_iframes/rt=j/sv=1/d=1/ed=1/rs=AHpOoo9yYF5eCIYPx4UH9gpJptM2Q_GGxQ/cb=gapi.loaded_0?le=scs
8190
98
https://www.google-analytics.com/analytics.js
4499
82
https://watchparty-273604.firebaseapp.com/__/auth/iframe.js
13170
69
https://www.watchparty.me/
634
65
https://js.stripe.com/v3/m-outer-93afeeb17bc37e711759584dbfc50d47.html
10344
61
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 watchparty.me 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://watchparty.me/
http/1.1
0
58.792999945581
708
0
301
text/plain
https://www.watchparty.me/
h2
59.232999919914
146.97999996133
1488
1538
200
text/html
Document
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/semantic.min.css
h2
154.63399991859
205.46899992041
80632
628512
200
text/css
Stylesheet
https://www.watchparty.me/static/js/main.ed47634f.js
h2
154.73499998916
260.09399991017
386741
1700836
200
application/javascript
Script
https://www.watchparty.me/static/css/main.40cbba6b.css
h2
154.91699997801
216.74800000619
4780
15636
200
text/css
Stylesheet
https://cdn.jsdelivr.net/npm/hls.js@latest
h2
155.17099993303
192.81599996611
100843
344695
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-45337794-6
h2
158.99899997748
172.51499998383
44333
111580
200
application/javascript
Script
https://fonts.googleapis.com/css?family=Lato:400,700,400italic,700italic&subset=latin
h2
212.60199998505
228.7789999973
1255
2726
200
text/css
Stylesheet
https://www.google-analytics.com/analytics.js
h2
327.53899996169
332.04799995292
20664
50230
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=1004165355&t=pageview&_s=1&dl=https%3A%2F%2Fwww.watchparty.me%2F&ul=en-us&de=UTF-8&dt=WatchParty&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUABAAAAACAAI~&jid=1281828557&gjid=2055883545&cid=1536480756.1670813013&tid=UA-45337794-6&_gid=368182541.1670813013&_r=1&gtm=2oubu0&z=1486688926
h2
358.03799994756
361.89800000284
615
1
200
text/plain
XHR
https://js.stripe.com/v3
h2
662.59999992326
692.67099990975
100930
413798
200
text/javascript
Script
https://www.watchparty.me/screenshot4.png
h2
662.93399990536
2729.4539998984
729934
729158
200
image/png
Image
https://www.watchparty.me/screenshot18.png
h2
663.20999991149
728.42199995648
672169
671387
200
image/png
Image
https://www.watchparty.me/screenshot14.png
h2
663.43399998732
734.09299994819
994687
993911
200
image/png
Image
data
666.62999999244
666.77899996284
0
960
200
image/png
Image
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/themes/default/assets/fonts/icons.woff2
h2
670.00399995595
691.30999990739
41147
40148
200
application/octet-stream
Font
https://fonts.gstatic.com/s/lato/v23/S6u9w4BMUTPHh6UVSwiPGQ3q5d0.woff2
h2
670.14599998947
673.4249999281
15076
14148
200
font/woff2
Font
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/themes/default/assets/fonts/brand-icons.woff2
h2
670.37299997173
693.41299997177
55486
54488
200
application/octet-stream
Font
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/themes/default/assets/fonts/outline-icons.woff2
h2
670.97499989904
693.72199999634
13241
12240
200
application/octet-stream
Font
https://apis.google.com/js/api.js?onload=__iframefcb523216
h2
817.40999990143
827.39499991294
7853
17589
200
text/javascript
Script
https://apis.google.com/_/scs/abc-static/_/js/k=gapi.lb.en.geaHZXF2-fw.O/m=gapi_iframes/rt=j/sv=1/d=1/ed=1/rs=AHpOoo9yYF5eCIYPx4UH9gpJptM2Q_GGxQ/cb=gapi.loaded_0?le=scs
h2
834.68099997845
840.76499997173
32305
95454
200
text/javascript
Script
https://watchparty-273604.firebaseapp.com/__/auth/iframe?apiKey=AIzaSyA2fkXeFokJ-Ei_jnzDso5AmjbIaMdzuEc&appName=%5BDEFAULT%5D&v=9.9.1&eid=p&usegapi=1&jsh=m%3B%2F_%2Fscs%2Fabc-static%2F_%2Fjs%2Fk%3Dgapi.lb.en.geaHZXF2-fw.O%2Fd%3D1%2Frs%3DAHpOoo9yYF5eCIYPx4UH9gpJptM2Q_GGxQ%2Fm%3D__features__
h2
870.82899990492
1049.990999978
799
335
200
text/html
Document
https://watchparty-273604.firebaseapp.com/__/auth/iframe.js
h2
1061.7670000065
1323.4930000035
284415
283942
200
text/javascript
Script
https://www.googleapis.com/identitytoolkit/v3/relyingparty/getProjectConfig?key=AIzaSyA2fkXeFokJ-Ei_jnzDso5AmjbIaMdzuEc&cb=1670813014152
h2
1385.1070000092
1402.0199999213
908
232
200
application/json
XHR
https://www.googleapis.com/identitytoolkit/v3/relyingparty/getProjectConfig?key=AIzaSyA2fkXeFokJ-Ei_jnzDso5AmjbIaMdzuEc&cb=1670813014152
h2
1379.7769999364
1384.7229999956
642
0
200
text/html
Preflight
https://js.stripe.com/v3/m-outer-93afeeb17bc37e711759584dbfc50d47.html
h2
2743.4839999769
2759.401999996
1420
200
200
text/html
Document
https://js.stripe.com/v3/fingerprinted/js/m-outer-8cb24ab2d649fd36a488d04d8c457933.js
h2
2784.9329999881
2800.55299995
975
631
200
text/javascript
Script
https://m.stripe.network/inner.html
h2
2806.1489999527
2843.3319999604
2053
930
200
text/html
Document
https://m.stripe.network/out-4.5.42.js
h2
2856.8449999439
2882.9999999143
14900
88253
200
text/javascript
Script
https://m.stripe.com/6
h2
2993.5069999192
3334.9129999988
661
156
200
application/json
XHR
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)
150.173
8.285
209.366
32.121
243.68
52.15
295.842
8.344
310.391
7.633
318.526
9.895
338.927
20.503
371.575
8.979
380.562
291.73
672.316
32.372
704.747
5.318
724.387
8.269
746.114
59.315
848.159
24.427
1053.591
9.173
1344.909
17.13
1370.536
9.324
2737.962
5.663
2747.034
30.483
2777.544
8.231
2847.047
8.427
2889.626
94.502
2986.209
7.561
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

Reduce unused CSS — Potential savings of 76 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Watchparty.me should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/semantic.min.css
80632
78108
Avoid serving legacy JavaScript to modern browsers — Potential savings of 29 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://watchparty-273604.firebaseapp.com/__/auth/iframe.js
22180
https://apis.google.com/_/scs/abc-static/_/js/k=gapi.lb.en.geaHZXF2-fw.O/m=gapi_iframes/rt=j/sv=1/d=1/ed=1/rs=AHpOoo9yYF5eCIYPx4UH9gpJptM2Q_GGxQ/cb=gapi.loaded_0?le=scs
7494
https://www.watchparty.me/static/js/main.ed47634f.js
53
https://js.stripe.com/v3
41
https://m.stripe.network/out-4.5.42.js
31
Avoid enormous network payloads — Total size was 3,527 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.watchparty.me/screenshot14.png
994687
https://www.watchparty.me/screenshot4.png
729934
https://www.watchparty.me/screenshot18.png
672169
https://www.watchparty.me/static/js/main.ed47634f.js
386741
https://watchparty-273604.firebaseapp.com/__/auth/iframe.js
284415
https://js.stripe.com/v3
100930
https://cdn.jsdelivr.net/npm/hls.js@latest
100843
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/semantic.min.css
80632
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/themes/default/assets/fonts/brand-icons.woff2
55486
https://www.googletagmanager.com/gtag/js?id=UA-45337794-6
44333
Reduce JavaScript execution time — 2.4 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.watchparty.me/static/js/main.ed47634f.js
1190.984
1011.812
112.284
https://m.stripe.network/inner.html
403.024
370.036
5.816
https://www.watchparty.me/
319.488
13.888
5.612
Unattributable
284.368
6.248
0
https://js.stripe.com/v3
274.516
155.016
23.664
https://cdn.jsdelivr.net/npm/hls.js@latest
208.6
175.72
32.188
https://js.stripe.com/v3/m-outer-93afeeb17bc37e711759584dbfc50d47.html
163.428
5.736
3.812
https://watchparty-273604.firebaseapp.com/__/auth/iframe.js
161.176
128.928
21.736
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/semantic.min.css
128.484
0
0
https://apis.google.com/_/scs/abc-static/_/js/k=gapi.lb.en.geaHZXF2-fw.O/m=gapi_iframes/rt=j/sv=1/d=1/ed=1/rs=AHpOoo9yYF5eCIYPx4UH9gpJptM2Q_GGxQ/cb=gapi.loaded_0?le=scs
107.836
99.94
6.472
https://www.google-analytics.com/analytics.js
86.048
79.42
3.096
https://www.googletagmanager.com/gtag/js?id=UA-45337794-6
77.148
66.992
8.8
https://m.stripe.network/out-4.5.42.js
53.484
41.912
5.812
Minimize main-thread work — 3.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
2193.228
Other
422.66
Script Parsing & Compilation
236.916
Style & Layout
207.76
Garbage Collection
178.98
Rendering
178.952
Parse HTML & CSS
130.224

Metrics

First Contentful Paint — 4.8 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 12.3 s
The time taken for the page to become fully interactive.
Speed Index — 6.0 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 1,540 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 — 14.0 s
The timing of the largest text or image that is painted.

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 1,950 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Watchparty.me 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://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/semantic.min.css
80632
1680
https://www.watchparty.me/static/css/main.40cbba6b.css
4780
150
Properly size images — Potential savings of 2,089 KiB
Images can slow down the page's load time. Watchparty.me should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.watchparty.me/screenshot14.png
993911
925527
https://www.watchparty.me/screenshot4.png
729158
635140
https://www.watchparty.me/screenshot18.png
671387
578866
Reduce unused JavaScript — Potential savings of 510 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://watchparty-273604.firebaseapp.com/__/auth/iframe.js
284415
175100
https://www.watchparty.me/static/js/main.ed47634f.js
386741
162459
https://cdn.jsdelivr.net/npm/hls.js@latest
100843
88498
https://js.stripe.com/v3
100930
74680
https://www.googletagmanager.com/gtag/js?id=UA-45337794-6
44333
21937
Serve images in next-gen formats — Potential savings of 1,579 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.watchparty.me/screenshot14.png
993911
559320.55
https://www.watchparty.me/screenshot18.png
671387
530681.8
https://www.watchparty.me/screenshot4.png
729158
527157.1
Enable text compression — Potential savings of 190 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://watchparty-273604.firebaseapp.com/__/auth/iframe.js
283942
194737
Preload Largest Contentful Paint image — Potential savings of 3,600 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.watchparty.me/screenshot4.png
3600
Serve static assets with an efficient cache policy — 10 resources found
Watchparty.me 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://js.stripe.com/v3
60000
100930
https://m.stripe.network/out-4.5.42.js
300000
14900
https://watchparty-273604.firebaseapp.com/__/auth/iframe.js
1800000
284415
https://www.google-analytics.com/analytics.js
7200000
20664
https://www.watchparty.me/screenshot14.png
14400000
994687
https://www.watchparty.me/screenshot4.png
14400000
729934
https://www.watchparty.me/screenshot18.png
14400000
672169
https://www.watchparty.me/static/js/main.ed47634f.js
14400000
386741
https://www.watchparty.me/static/css/main.40cbba6b.css
14400000
4780
https://cdn.jsdelivr.net/npm/hls.js@latest
604800000
100843
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/themes/default/assets/fonts/icons.woff2
21.305999951437
https://fonts.gstatic.com/s/lato/v23/S6u9w4BMUTPHh6UVSwiPGQ3q5d0.woff2
3.2789999386296
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/themes/default/assets/fonts/brand-icons.woff2
23.040000000037
https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.4.1/themes/default/assets/fonts/outline-icons.woff2
22.747000097297
Reduce the impact of third-party code — Third-party code blocked the main thread for 630 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)
120939
413.5
100843
125.184
190506
63.236
21279
25.98
41708
0.812
44333
0
16331
0
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://www.watchparty.me/screenshot14.png
https://www.watchparty.me/screenshot4.png
https://www.watchparty.me/screenshot18.png
First Contentful Paint (3G) — 9450 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
93

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of watchparty.me. 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 `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

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

ARIA

ARIA input fields do not 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.
Failing Elements

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

Links do not 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.

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 watchparty.me 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
Create React App
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://cdn.jsdelivr.net/npm/hls.js@latest
https://cdn.jsdelivr.net/npm/hls.min.js.map
https://www.watchparty.me/static/js/main.ed47634f.js
https://www.watchparty.me/static/js/main.ed47634f.js.map
https://js.stripe.com/v3/fingerprinted/js/m-outer-8cb24ab2d649fd36a488d04d8c457933.js
https://js.stripe.com/v3/sourcemaps/m-outer-cb35da7c5fc15bbeac1d5d83b92ec8a6.js.map
https://js.stripe.com/v3
https://js.stripe.com/v3/sourcemaps/stripe-81adcffd0022c9ea1a206a1f4e8ac487.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 — 1 insecure request 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://watchparty.me/
Allowed
97

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for watchparty.me. 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 watchparty.me on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px

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.

Mobile Friendly

Tap targets are not sized appropriately — 71% 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.
Tap Target Size Overlapping Target
36x28
36x28
36x28
36x28

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

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

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Sets 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
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 watchparty.me on mobile screens.
Provides 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.

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

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

Private Registration: Yes
Name: REDACTED FOR PRIVACY
Organization: Privacy service provided by Withheld for Privacy ehf
Country: IS
City: REDACTED FOR PRIVACY
State: Capital Region
Post Code: REDACTED FOR PRIVACY
Email:
Phone: REDACTED FOR PRIVACY
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
NameCheap, Inc. 104.16.99.56
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: watchparty.me
Issued By: WE1
Valid From: 12th October, 2024
Valid To: 10th January, 2025
Subject: CN = watchparty.me
Hash: 5baa16ae
Issuer: CN = WE1
O = Google Trust Services
S = US
Version: 2
Serial Number: 0xF05DFA8D764656D70D86C2BDB8F22E80
Serial Number (Hex): F05DFA8D764656D70D86C2BDB8F22E80
Valid From: 12th October, 2024
Valid To: 10th January, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:90:77:92:35:67:C4:FF:A8:CC:A9:E6:7B:D9:80:79:7B:CC:93:F9:38
Extended Key Usage: TLS Web Server Authentication
CRL Distribution Points:
Full Name:
URI:http://c.pki.goog/we1/iUnSZAxKPhw.crl

Certificate Policies: Policy: 2.23.140.1.2.1

Authority Information Access: OCSP - URI:http://o.pki.goog/s/we1/8F0
CA Issuers - URI:http://i.pki.goog/we1.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
Timestamp : Oct 12 11:11:44.957 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:AE:F2:AC:50:23:48:52:0F:BB:78:90:
C3:E9:78:BD:9C:0B:1D:7A:7B:A4:D5:42:7B:D2:27:55:
B5:48:FE:8C:EE:02:21:00:D9:23:8B:F9:39:65:33:1B:
0B:7C:BE:42:74:8F:01:3A:63:9E:C9:48:79:01:4C:C2:
9F:99:D7:60:64:D8:51:3E
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
Timestamp : Oct 12 11:11:44.991 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:9F:68:20:D4:FA:82:B4:95:4D:B1:7F:
E8:F1:FB:C2:4B:A3:4B:E8:14:06:D4:A9:04:FD:52:AD:
00:87:C2:02:3E:02:21:00:C9:E8:BD:EE:E8:EF:E6:79:
96:90:97:F7:FD:FC:A5:5B:DD:FC:99:5D:82:24:5D:EC:
29:FB:F2:2F:7A:F9:41:57
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.watchparty.me
DNS:watchparty.me
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/2 200
date: 16th November, 2024
content-type: text/html; charset=UTF-8
cache-control: public, max-age=0
server: cloudflare
x-powered-by: Express
access-control-allow-origin: *
accept-ranges: bytes
last-modified: 10th November, 2024
vary: Accept-Encoding
cf-cache-status: DYNAMIC
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=%2FW9CT%2F%2Fak13%2F2OrHnhkDwCa83tNIFu5k65QNDvgRIFkK52d1N8bRBx5jLM3JKZbqmF16fGR8UZNAGUMqZUd%2FB7CSlY3tPRLu5%2BQXgYzfRgi2%2FfVGK94jHxRuKUul5TR6QekVAw%3D%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
cf-ray: 8e33394d0b77c9bc-IAD
alt-svc: h3=":443"; ma=86400
server-timing: cfL4;desc="?proto=TCP&rtt=832&sent=5&recv=10&lost=0&retrans=0&sent_bytes=3397&recv_bytes=923&delivery_rate=3439429&cwnd=252&unsent_bytes=0&cid=df9548fc4401c3c3&ts=24&x=0"

Whois Lookup

Created: 9th April, 2020
Changed: 7th June, 2024
Expires: 9th April, 2026
Registrar: NameCheap, Inc.
Status: clientTransferProhibited
Nameservers: adi.ns.cloudflare.com
dave.ns.cloudflare.com
Owner Name: REDACTED FOR PRIVACY
Owner Organization: Privacy service provided by Withheld for Privacy ehf
Owner Street: REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner State: Capital Region
Owner Country: IS
Owner Phone: REDACTED FOR PRIVACY
Owner Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Full Whois: Domain Name: watchparty.me
Registry Domain ID: d3b7aa32c82342aa8fa8f2f0f0b891db-DONUTS
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: https://www.namecheap.com/
Updated Date: 2024-06-07T22:11:29Z
Creation Date: 2020-04-09T03:30:06Z
Registry Expiry Date: 2026-04-09T03:30:06Z
Registrar: NameCheap, Inc.
Registrar IANA ID: 1068
Registrar Abuse Contact Email: abuse@namecheap.com
Registrar Abuse Contact Phone: +1.9854014545
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Privacy service provided by Withheld for Privacy ehf
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: Capital Region
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: IS
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: dave.ns.cloudflare.com
Name Server: adi.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2024-11-16T00:04:30Z <<<

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

Terms of Use: Access to WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the registry database. The data in this record is provided by Identity Digital or the Registry Operator for informational purposes only, and accuracy is not guaranteed. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Identity Digital except as reasonably necessary to register domain names or modify existing registrations. When using the Whois service, please consider the following: The Whois service is not a replacement for standard EPP commands to the SRS service. Whois is not considered authoritative for registered domain objects. The Whois service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the Whois services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of Whois service access. Abuse of the Whois system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the Whois records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to this data provided by Identity Digital can be requested by submitting a request via the form found at https://www.identity.digital/about/policies/whois-layered-access/. The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Identity Digital Inc. and Registry Operator reserve the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

Nameservers

Name IP Address
adi.ns.cloudflare.com 108.162.192.56
dave.ns.cloudflare.com 108.162.193.109
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$10 USD

Sites hosted on the same IP address

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