watchwrestling.store

watchwrestling.store is SSL secured

Free website and domain report on watchwrestling.store

Last Updated: 30th May, 2021 Update Now
Overview

Snoop Summary for watchwrestling.store

This is a free and comprehensive report about watchwrestling.store. The domain watchwrestling.store is currently hosted on a server located in United States with the IP address 172.67.138.101, where USD is the local currency and the local language is English. Our records indicate that watchwrestling.store is owned/operated by Cloudflare, Inc.. Watchwrestling.store has the potential to be earning an estimated $4 USD per day from advertising revenue. If watchwrestling.store was to be sold it would possibly be worth $3,283 USD (based on the daily revenue potential of the website over a 24 month period). Watchwrestling.store is quite popular with an estimated 1,573 daily unique visitors. This report was last updated 30th May, 2021.

About watchwrestling.store

Site Preview: watchwrestling.store watchwrestling.store
Title: Watch Wrestling - WWE, Raw, Smackdown, UFC, TNA Live.
Description: watch wrestling, watchwrestling, watchwrestlinguno, watchwrestlingup, watchwrestlingonline, watchwrestling24, watchwrestling2k, wrestlingonlinematches, watchwrestlings, watchwrestling hd, watchprowrestling, watchwrestlingtoday, wrestlingnetwork, bollyrulezz
Keywords and Tags: bollyrulezz, potential illegal software, watch wrestling, watchprowrestling, watchwrestling, watchwrestling hd, watchwrestling24, watchwrestling2k, watchwrestlingonline, watchwrestlings, watchwrestlingtoday, watchwrestlinguno, watchwrestlingup, wrestlingnetwork, wrestlingonlinematches
Related Terms: smackdown, tna, watchwrestling in, wwe smackdown
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

1/5

Valuation

$3,283 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 510,579
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: 1,573
Monthly Visitors: 47,877
Yearly Visitors: 574,145
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $4 USD
Monthly Revenue: $136 USD
Yearly Revenue: $1,636 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: watchwrestling.store 20
Domain Name: watchwrestling 14
Extension (TLD): store 5

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 81
Performance 98
Accessibility 91
Best Practices 87
SEO 92
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://watchwrestling.store/
Updated: 30th May, 2021

1.71 seconds
First Contentful Paint (FCP)
49%
42%
9%

0.00 seconds
First Input Delay (FID)
99%
1%
0%

Simulate loading on desktop
98

Performance

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

Metrics

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

Other

First CPU Idle — 0.8 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive watchwrestling.store as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://watchwrestling.store/
http/1.1
0
121.90399999963
856
0
301
text/html
https://watchwrestling.store/
h2
122.38000001526
276.95299999323
9754
65235
200
text/html
Document
https://watchwrestling.store/wp-content/cache/min/1/e1e58e9ae40cd1e91f9be54a849b63af.css
h2
291.81700001936
373.29999997746
38147
247232
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Arimo%3A400%2C700%7CDroid+Serif%3A400%2C700%7COpen+Sans%3A600%2C700&ver=5.7.2
h2
292.02699998859
306.76700000186
1600
9504
200
text/css
Stylesheet
https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
h2
293.41400001431
312.00999999419
4951
12332
200
application/javascript
Script
data
297.47599997791
297.52899997402
0
64
200
image/svg+xml
Image
https://watchwrestling.store/wp-content/cache/min/1/6c39208c311672bc2132dfeb4c6ca335.js
h2
318.36899998598
417.1530000167
67323
224187
200
application/javascript
Script
https://watchwrestling.store/wp-content/plugins/wp-rocket/assets/js/lazyload/12.0/lazyload.min.js
h2
318.58199997805
345.50599998329
2899
5585
200
application/javascript
Script
https://watchwrestling.store/wp-content/cache/busting/1/gtm-8fa11fdbfca3b49af5b8396a1dd45deb.js
h2
319.03299997794
349.90500001004
34600
90806
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-WV3FDJD
h2
383.87700001476
475.48399999505
1966
0
404
text/html
Script
https://watchwrestling.store/wp-content/themes/watchwrestling_store/images/s.png
h2
390.59000002453
415.69900000468
9718
8804
200
image/png
Image
https://watchwrestling.store/wp-content/themes/watchwrestling_store/images/bg-pattern-nav.png
h2
390.97100001527
445.87499997579
3872
2962
200
image/png
Image
https://watchwrestling.store/wp-content/themes/watchwrestling_store/images/nav-sep.png
h2
391.13000000361
435.80899998778
3735
2827
200
image/png
Image
https://watchwrestling.store/wp-content/themes/watchwrestling_store/images/bg-pattern-black.png
h2
391.57999999588
417.69400000339
8591
7675
200
image/png
Image
https://watchwrestling.store/wp-content/themes/watchwrestling_store/images/bg-grad.png
h2
392.14200002607
470.83100001328
3734
2822
200
image/png
Image
https://watchwrestling.store/wp-content/themes/watchwrestling_store/images/icon-plus-32.png
h2
392.63800001936
471.47599997697
4434
3528
200
image/png
Image
https://watchwrestling.store/wp-content/themes/watchwrestling_store/images/stats.png
h2
394.87299998291
419.9179999996
5066
4156
200
image/png
Image
https://fonts.gstatic.com/s/opensans/v20/mem5YaGs126MiZpBA-UN7rgOUuhpKKSTjw.woff2
h2
405.01400001813
408.09799998533
9733
9128
200
font/woff2
Font
https://watchwrestling.store/wp-content/themes/watchwrestling_store/images/s2.png
h2
405.22199997213
443.59199999599
5218
4308
200
image/png
Image
https://watchwrestling.store/wp-content/cache/busting/google-tracking/ga-6df1787c4be82d1bb24f8bffa10c7738.js
h2
470.01099999761
502.8090000269
19848
49153
200
application/javascript
Script
https://watchwrestling.store/wp-content/uploads/2020/03/watchwrestling.png
h2
471.3960000081
521.78100001765
4748
3838
200
image/png
Image
https://watchwrestling.store/wp-content/uploads/2021/05/Watch-AEW-Double-Or-Nothing-2021-PPV-53021-320x180.jpg
h2
471.79300000425
495.28299999656
23605
22700
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2020/01/AEW-Wrestling-Dynamite-1-320x180.jpg
h2
472.06599998754
521.27799997106
20332
19410
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2019/12/Watch-WWE-Smackdown-11819-3-2-1-320x180.jpg
h2
472.28400001768
501.85900001088
16685
15773
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2021/05/Watch-Haney-vs-Linares-52921-320x180.jpg
h2
472.70400001435
496.27100001089
19301
18381
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2021/05/PBC-premier-boxing-champions-320x180.jpg
h2
472.81800000928
497.66300001647
15060
14144
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2020/08/WWE-Talking-Smack-320x180.jpg
h2
473.11399999307
496.84600002365
12944
12034
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2020/08/NJPW-Watch-NJPW-Strong-New-Japan-Cup-2020-USA-320x180.jpg
h2
473.24600000866
565.61599997804
22910
22000
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2020/01/205-live-320x180.jpg
h2
473.43399998499
495.88000000222
14260
13346
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2019/12/MainEvent-320x180.jpg
h2
473.7239999813
503.14899999648
15477
14565
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2020/01/this-week-in-wwe-1-320x180.jpeg
h2
473.87699998217
503.43799998518
7810
6898
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2019/12/impactwrestling-3-2-1-320x180.jpg
h2
474.0350000211
502.50100000994
13259
12348
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2020/01/NXT-UK-3-2-1-320x180.jpg
h2
474.47600000305
502.19500000821
15488
14573
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2021/05/Watch-NJPW-Road-to-Wrestle-Grand-Slam-52421-320x180.jpg
h2
474.65499996906
523.89200002654
12292
11381
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2019/12/NXT-Logo-1-320x180.jpg
h2
474.78200000478
507.91099999333
19013
18101
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2020/01/aew-dark-320x180.jpg
h2
476.53899999568
503.66400001803
17846
16927
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2020/01/NWA-Powerrr-2020-320x180.jpg
h2
477.69199998584
526.95700002369
11827
10915
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2019/12/Wwe-Raw-monday-night-2-320x180.jpg
h2
477.85099997418
503.91899998067
9469
8562
200
image/jpeg
Image
https://www.supercounters.com/fc.php?id=1588376&w=1&v=2&ua=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_14_6)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F90.0.4420.0%20Safari%2F537.36%20Chrome-Lighthouse&ref=&url=https%3A%2F%2Fwatchwrestling.store%2F&sw=800&sh=600&rand=63
http/1.1
598.04499999154
765.43099997798
279
28
200
application/x-javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j90&aip=1&a=790139880&t=pageview&_s=1&dl=https%3A%2F%2Fwatchwrestling.store%2F&ul=en-us&de=UTF-8&dt=Watch%20Wrestling%20-%20WWE%2C%20Raw%2C%20Smackdown%2C%20UFC%2C%20TNA%20Live.&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAAC~&jid=491837315&gjid=960060182&cid=576359261.1622381765&tid=UA-70441024-4&_gid=2032914315.1622381765&_r=1&gtm=2ou5q1&did=dZTNiMT&z=143009905
h2
706.13700000104
711.99500001967
623
1
200
text/plain
XHR
https://widget.supercounters.com/images/online/dddddd.png
h2
767.74600002682
836.22900000773
1366
503
200
image/png
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)
306.09
6.954
317.178
7.419
339.43
13.191
400.874
6.889
407.814
43.503
451.332
10.732
462.08
8.439
484.122
9.768
494.069
7.365
502.366
67.822
572.209
61.508
643.137
13.469
658.87
13.774
674.476
11.256
688.991
9.206
699.082
9.35
708.756
23.96
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images — Potential savings of 158 KiB
Images can slow down the page's load time. Watchwrestling.store should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://watchwrestling.store/wp-content/uploads/2021/05/Watch-AEW-Double-Or-Nothing-2021-PPV-53021-320x180.jpg
22700
14528
https://watchwrestling.store/wp-content/uploads/2020/08/NJPW-Watch-NJPW-Strong-New-Japan-Cup-2020-USA-320x180.jpg
22000
14080
https://watchwrestling.store/wp-content/uploads/2020/01/AEW-Wrestling-Dynamite-1-320x180.jpg
19410
12422
https://watchwrestling.store/wp-content/uploads/2021/05/Watch-Haney-vs-Linares-52921-320x180.jpg
18381
11764
https://watchwrestling.store/wp-content/uploads/2019/12/NXT-Logo-1-320x180.jpg
18101
11585
https://watchwrestling.store/wp-content/uploads/2020/01/aew-dark-320x180.jpg
16927
10833
https://watchwrestling.store/wp-content/uploads/2019/12/Watch-WWE-Smackdown-11819-3-2-1-320x180.jpg
15773
10095
https://watchwrestling.store/wp-content/uploads/2020/01/NXT-UK-3-2-1-320x180.jpg
14573
9327
https://watchwrestling.store/wp-content/uploads/2019/12/MainEvent-320x180.jpg
14565
9322
https://watchwrestling.store/wp-content/uploads/2021/05/PBC-premier-boxing-champions-320x180.jpg
14144
9052
https://watchwrestling.store/wp-content/uploads/2020/01/205-live-320x180.jpg
13346
8541
https://watchwrestling.store/wp-content/uploads/2019/12/impactwrestling-3-2-1-320x180.jpg
12348
7903
https://watchwrestling.store/wp-content/uploads/2020/08/WWE-Talking-Smack-320x180.jpg
12034
7702
https://watchwrestling.store/wp-content/uploads/2021/05/Watch-NJPW-Road-to-Wrestle-Grand-Slam-52421-320x180.jpg
11381
7284
https://watchwrestling.store/wp-content/uploads/2020/01/NWA-Powerrr-2020-320x180.jpg
10915
6986
https://watchwrestling.store/wp-content/uploads/2019/12/Wwe-Raw-monday-night-2-320x180.jpg
8562
5480
https://watchwrestling.store/wp-content/uploads/2020/01/this-week-in-wwe-1-320x180.jpeg
6898
4415
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Watchwrestling.store should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Watchwrestling.store should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Watchwrestling.store should consider minifying JS files.
Remove unused CSS — Potential savings of 36 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Watchwrestling.store 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://watchwrestling.store/wp-content/cache/min/1/e1e58e9ae40cd1e91f9be54a849b63af.css
38147
36723
Remove unused JavaScript — Potential savings of 35 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://watchwrestling.store/wp-content/cache/min/1/6c39208c311672bc2132dfeb4c6ca335.js
67323
36177
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
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 160 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://watchwrestling.store/
155.57
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Watchwrestling.store should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://watchwrestling.store/
190
https://watchwrestling.store/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Watchwrestling.store 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 6 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://watchwrestling.store/wp-content/cache/min/1/6c39208c311672bc2132dfeb4c6ca335.js
6092
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 499 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://watchwrestling.store/wp-content/cache/min/1/6c39208c311672bc2132dfeb4c6ca335.js
67323
https://watchwrestling.store/wp-content/cache/min/1/e1e58e9ae40cd1e91f9be54a849b63af.css
38147
https://watchwrestling.store/wp-content/cache/busting/1/gtm-8fa11fdbfca3b49af5b8396a1dd45deb.js
34600
https://watchwrestling.store/wp-content/uploads/2021/05/Watch-AEW-Double-Or-Nothing-2021-PPV-53021-320x180.jpg
23605
https://watchwrestling.store/wp-content/uploads/2020/08/NJPW-Watch-NJPW-Strong-New-Japan-Cup-2020-USA-320x180.jpg
22910
https://watchwrestling.store/wp-content/uploads/2020/01/AEW-Wrestling-Dynamite-1-320x180.jpg
20332
https://watchwrestling.store/wp-content/cache/busting/google-tracking/ga-6df1787c4be82d1bb24f8bffa10c7738.js
19848
https://watchwrestling.store/wp-content/uploads/2021/05/Watch-Haney-vs-Linares-52921-320x180.jpg
19301
https://watchwrestling.store/wp-content/uploads/2019/12/NXT-Logo-1-320x180.jpg
19013
https://watchwrestling.store/wp-content/uploads/2020/01/aew-dark-320x180.jpg
17846
Uses efficient cache policy on static assets — 3 resources found
Watchwrestling.store 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://www.supercounters.com/fc.php?id=1588376&w=1&v=2&ua=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_14_6)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F90.0.4420.0%20Safari%2F537.36%20Chrome-Lighthouse&ref=&url=https%3A%2F%2Fwatchwrestling.store%2F&sw=800&sh=600&rand=63
0
279
https://widget.supercounters.com/images/online/dddddd.png
14400000
1366
https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
172800000
4951
Avoids an excessive DOM size — 641 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
641
Maximum DOM Depth
12
Maximum Child Elements
45
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Watchwrestling.store 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://watchwrestling.store/
183.982
4.273
0.91
https://watchwrestling.store/wp-content/cache/min/1/6c39208c311672bc2132dfeb4c6ca335.js
58.656
36.646
4.387
https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
56.979
38.993
1.688
Minimizes main-thread work — 0.4 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
127.227
Other
113.131
Style & Layout
92.899
Rendering
36.24
Parse HTML & CSS
12.587
Script Parsing & Compilation
11.963
Keep request counts low and transfer sizes small — 40 requests • 499 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
40
510639
Image
27
318060
Script
7
131866
Stylesheet
2
39747
Document
1
9754
Font
1
9733
Other
2
1479
Media
0
0
Third-party
7
20518
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
11333
0
4951
0
1966
0
623
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.074698073836996
0.0072061671230984
0.0013498381342779
0.0013498381342779
0.0013498381342779
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations — 133 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element
AEW
MMA
NWA
UFC
WWE
AEW
GCW
New
nwa
nxt
raw
ROH
ufc
wwe

Budgets

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

Opportunities

Eliminate render-blocking resources — Potential savings of 460 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Watchwrestling.store 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://watchwrestling.store/wp-content/cache/min/1/e1e58e9ae40cd1e91f9be54a849b63af.css
38147
80
https://fonts.googleapis.com/css?family=Arimo%3A400%2C700%7CDroid+Serif%3A400%2C700%7COpen+Sans%3A600%2C700&ver=5.7.2
1600
230

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/opensans/v20/mem5YaGs126MiZpBA-UN7rgOUuhpKKSTjw.woff2
3.0839999672025
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 Failing Elements
https://watchwrestling.store/wp-content/uploads/2021/05/Watch-AEW-Double-Or-Nothing-2021-PPV-53021-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2020/08/NJPW-Watch-NJPW-Strong-New-Japan-Cup-2020-USA-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2020/01/AEW-Wrestling-Dynamite-1-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2021/05/Watch-Haney-vs-Linares-52921-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2019/12/NXT-Logo-1-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2020/01/aew-dark-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2019/12/Watch-WWE-Smackdown-11819-3-2-1-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2020/01/NXT-UK-3-2-1-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2019/12/MainEvent-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2021/05/PBC-premier-boxing-champions-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2020/01/205-live-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2019/12/impactwrestling-3-2-1-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2020/08/WWE-Talking-Smack-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2021/05/Watch-NJPW-Road-to-Wrestle-Grand-Slam-52421-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2021/05/Watch-NJPW-Road-to-Wrestle-Grand-Slam-52421-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2020/01/NWA-Powerrr-2020-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2019/12/Wwe-Raw-monday-night-2-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2020/01/this-week-in-wwe-1-320x180.jpeg
https://watchwrestling.store/wp-content/uploads/2020/03/watchwrestling.png
91

Accessibility

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

Navigation

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

ARIA

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

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<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.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

Contrast

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

Best practices

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

Manual Checks

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

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

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

Audits

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

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
Modernizr
2.6.2
yepnope
WordPress
5.7.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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://watchwrestling.store/wp-content/plugins/wp-rocket/assets/js/lazyload/12.0/lazyload.min.js
https://watchwrestling.store/wp-content/plugins/wp-rocket/assets/js/lazyload/12.0/lazyload.min.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://watchwrestling.store/
Allowed

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: the server responded with a status of 404 (Not Found)
ReferenceError: jQuery is not defined at <anonymous>:67:4 at t.activateScript (https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js:1:11855) at https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js:1:11052 at t.run (https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js:1:11259) at https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js:1:2907 at https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js:1:8117
92

SEO

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

Content Best Practices

Document does not have a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.

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

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of watchwrestling.store. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 watchwrestling.store 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) 78
Performance 90
Accessibility 91
Best Practices 80
SEO 88
Progressive Web App 42
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://watchwrestling.store/
Updated: 30th May, 2021

1.88 seconds
First Contentful Paint (FCP)
46%
45%
9%

0.02 seconds
First Input Delay (FID)
97%
2%
1%

Simulate loading on mobile
90

Performance

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

Metrics

Speed Index — 2.7 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 3.3 s
The time taken for the page to become fully interactive.
Total Blocking Time — 60 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).

Other

First CPU Idle — 3.3 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 130 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive watchwrestling.store as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://watchwrestling.store/
http/1.1
0
86.914000101388
845
0
301
text/html
https://watchwrestling.store/
h2
87.540999986231
172.41099942476
9758
65235
200
text/html
Document
https://watchwrestling.store/wp-content/cache/min/1/e1e58e9ae40cd1e91f9be54a849b63af.css
h2
187.43699975312
236.41199991107
38149
247232
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Arimo%3A400%2C700%7CDroid+Serif%3A400%2C700%7COpen+Sans%3A600%2C700&ver=5.7.2
h2
187.63299938291
202.79200002551
1600
9504
200
text/css
Stylesheet
https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
h2
188.70399985462
208.77599995583
4949
12332
200
application/javascript
Script
data
193.07599961758
193.14699992537
0
64
200
image/svg+xml
Image
https://watchwrestling.store/wp-content/cache/min/1/6c39208c311672bc2132dfeb4c6ca335.js
h2
215.76099935919
271.12299948931
67317
224187
200
application/javascript
Script
https://watchwrestling.store/wp-content/plugins/wp-rocket/assets/js/lazyload/12.0/lazyload.min.js
h2
216.15199930966
237.08700016141
2907
5585
200
application/javascript
Script
https://watchwrestling.store/wp-content/cache/busting/1/gtm-8fa11fdbfca3b49af5b8396a1dd45deb.js
h2
216.57699998468
249.68999996781
34608
90806
200
application/javascript
Script
https://watchwrestling.store/wp-content/themes/watchwrestling_store/images/s.png
h2
251.26999989152
283.05399976671
9710
8804
200
image/png
Image
https://watchwrestling.store/wp-content/themes/watchwrestling_store/images/bg-pattern-nav.png
h2
251.51900015771
274.45999998599
3880
2962
200
image/png
Image
https://watchwrestling.store/wp-content/themes/watchwrestling_store/images/nav-sep.png
h2
251.77699979395
271.74900006503
3735
2827
200
image/png
Image
https://watchwrestling.store/wp-content/themes/watchwrestling_store/images/bg-grad.png
h2
252.1369997412
276.3049993664
3728
2822
200
image/png
Image
https://watchwrestling.store/wp-content/themes/watchwrestling_store/images/icon-plus-32.png
h2
252.81600002199
275.54999943823
4434
3528
200
image/png
Image
https://watchwrestling.store/wp-content/themes/watchwrestling_store/images/stats.png
h2
253.8899993524
275.04199929535
5064
4156
200
image/png
Image
https://fonts.gstatic.com/s/opensans/v20/mem5YaGs126MiZpBA-UN7rgOUuhpKKSTjw.woff2
h2
265.59199951589
269.38799954951
9734
9128
200
font/woff2
Font
https://watchwrestling.store/wp-content/themes/watchwrestling_store/images/s2.png
h2
265.86999930441
312.92300019413
5212
4308
200
image/png
Image
https://www.googletagmanager.com/gtm.js?id=GTM-WV3FDJD
h2
321.67899981141
463.27799931169
1966
0
404
text/html
Script
https://www.supercounters.com/fc.php?id=1588376&w=1&v=2&ua=Mozilla%2F5.0%20(Linux%3B%20Android%207.0%3B%20Moto%20G%20(4))%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F90.0.4420.0%20Mobile%20Safari%2F537.36%20Chrome-Lighthouse&ref=&url=https%3A%2F%2Fwatchwrestling.store%2F&sw=360&sh=640&rand=52
http/1.1
452.26799976081
609.25199929625
279
28
200
application/x-javascript
Script
https://watchwrestling.store/wp-content/cache/busting/google-tracking/ga-6df1787c4be82d1bb24f8bffa10c7738.js
h2
481.3120001927
507.50099960715
19847
49153
200
application/javascript
Script
https://watchwrestling.store/wp-content/uploads/2020/03/watchwrestling.png
h2
512.02300004661
534.75399967283
4758
3838
200
image/png
Image
https://watchwrestling.store/wp-content/uploads/2021/05/Watch-AEW-Double-Or-Nothing-2021-PPV-53021-320x180.jpg
h2
512.17899937183
539.84299954027
23613
22700
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2020/01/AEW-Wrestling-Dynamite-1-320x180.jpg
h2
512.69799936563
533.76599960029
20324
19410
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2019/12/Watch-WWE-Smackdown-11819-3-2-1-320x180.jpg
h2
512.82699964941
534.25799962133
16683
15773
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2021/05/Watch-Haney-vs-Linares-52921-320x180.jpg
h2
512.94799987227
536.01399995387
19301
18381
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2021/05/PBC-premier-boxing-champions-320x180.jpg
h2
513.05999979377
540.50299990922
15052
14144
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2020/08/WWE-Talking-Smack-320x180.jpg
h2
513.35399970412
535.59099975973
12946
12034
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2020/08/NJPW-Watch-NJPW-Strong-New-Japan-Cup-2020-USA-320x180.jpg
h2
513.53899948299
544.38799992204
22914
22000
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2020/01/205-live-320x180.jpg
h2
513.70000001043
538.9809999615
14256
13346
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2019/12/MainEvent-320x180.jpg
h2
513.96899949759
540.15999939293
15475
14565
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2020/01/this-week-in-wwe-1-320x180.jpeg
h2
515.30800014734
539.44199997932
7808
6898
200
image/jpeg
Image
https://watchwrestling.store/wp-content/themes/watchwrestling_store/images/select-arrow.png
h2
516.20600000024
576.90099999309
4194
3286
200
image/png
Image
https://www.google-analytics.com/j/collect?v=1&_v=j90&aip=1&a=765991405&t=pageview&_s=1&dl=https%3A%2F%2Fwatchwrestling.store%2F&ul=en-us&de=UTF-8&dt=Watch%20Wrestling%20-%20WWE%2C%20Raw%2C%20Smackdown%2C%20UFC%2C%20TNA%20Live.&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUABAAAAAC~&jid=282130414&gjid=459886156&cid=271548123.1622381783&tid=UA-70441024-4&_gid=1260360378.1622381783&_r=1&gtm=2ou5q1&did=dZTNiMT&z=1068163559
h2
570.54099999368
573.67900013924
623
1
200
text/plain
XHR
https://watchwrestling.store/wp-content/uploads/2019/12/impactwrestling-3-2-1-320x180.jpg
h2
586.97099983692
638.94099928439
13253
12348
200
image/jpeg
Image
https://watchwrestling.store/wp-content/uploads/2020/01/NXT-UK-3-2-1-320x180.jpg
h2
587.407999672
614.84799999744
15482
14573
200
image/jpeg
Image
https://widget.supercounters.com/images/online/dddddd.png
h2
611.56199965626
673.32199960947
1364
503
200
image/png
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)
205.503
7.123
216.249
7.732
239.949
13.73
267.582
7.378
275.228
54.559
338.674
7.77
346.842
6.769
353.847
7.985
362.217
61.865
426.643
65.683
493.412
7.858
501.287
9.808
512.395
12.584
526.919
10.971
543.918
13.015
558.699
7.999
578.882
21.895
600.796
9.766
617
5.749
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Watchwrestling.store should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Watchwrestling.store should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Watchwrestling.store should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Watchwrestling.store should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
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)
https://watchwrestling.store/
85.865
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Watchwrestling.store should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://watchwrestling.store/
630
https://watchwrestling.store/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Watchwrestling.store 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 6 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://watchwrestling.store/wp-content/cache/min/1/6c39208c311672bc2132dfeb4c6ca335.js
6091
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 426 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://watchwrestling.store/wp-content/cache/min/1/6c39208c311672bc2132dfeb4c6ca335.js
67317
https://watchwrestling.store/wp-content/cache/min/1/e1e58e9ae40cd1e91f9be54a849b63af.css
38149
https://watchwrestling.store/wp-content/cache/busting/1/gtm-8fa11fdbfca3b49af5b8396a1dd45deb.js
34608
https://watchwrestling.store/wp-content/uploads/2021/05/Watch-AEW-Double-Or-Nothing-2021-PPV-53021-320x180.jpg
23613
https://watchwrestling.store/wp-content/uploads/2020/08/NJPW-Watch-NJPW-Strong-New-Japan-Cup-2020-USA-320x180.jpg
22914
https://watchwrestling.store/wp-content/uploads/2020/01/AEW-Wrestling-Dynamite-1-320x180.jpg
20324
https://watchwrestling.store/wp-content/cache/busting/google-tracking/ga-6df1787c4be82d1bb24f8bffa10c7738.js
19847
https://watchwrestling.store/wp-content/uploads/2021/05/Watch-Haney-vs-Linares-52921-320x180.jpg
19301
https://watchwrestling.store/wp-content/uploads/2019/12/Watch-WWE-Smackdown-11819-3-2-1-320x180.jpg
16683
https://watchwrestling.store/wp-content/uploads/2020/01/NXT-UK-3-2-1-320x180.jpg
15482
Uses efficient cache policy on static assets — 3 resources found
Watchwrestling.store 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://www.supercounters.com/fc.php?id=1588376&w=1&v=2&ua=Mozilla%2F5.0%20(Linux%3B%20Android%207.0%3B%20Moto%20G%20(4))%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F90.0.4420.0%20Mobile%20Safari%2F537.36%20Chrome-Lighthouse&ref=&url=https%3A%2F%2Fwatchwrestling.store%2F&sw=360&sh=640&rand=52
0
279
https://widget.supercounters.com/images/online/dddddd.png
14400000
1364
https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
172800000
4949
Avoids an excessive DOM size — 641 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
641
Maximum DOM Depth
12
Maximum Child Elements
45
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Watchwrestling.store 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.5 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://watchwrestling.store/
810.536
17.488
3.812
https://watchwrestling.store/wp-content/cache/min/1/6c39208c311672bc2132dfeb4c6ca335.js
253.172
173.456
15.56
https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
222.196
155.808
7.584
Unattributable
133.128
4.216
0.816
https://watchwrestling.store/wp-content/cache/busting/google-tracking/ga-6df1787c4be82d1bb24f8bffa10c7738.js
92.84
71.38
5.072
https://watchwrestling.store/wp-content/cache/busting/1/gtm-8fa11fdbfca3b49af5b8396a1dd45deb.js
72.832
59.148
10.42
Minimizes main-thread work — 1.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
511.26
Other
460.816
Style & Layout
390.412
Rendering
193.328
Parse HTML & CSS
52.688
Script Parsing & Compilation
46.204
Keep request counts low and transfer sizes small — 35 requests • 426 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
35
435768
Image
22
243186
Script
7
131873
Stylesheet
2
39749
Document
1
9758
Font
1
9734
Other
2
1468
Media
0
0
Third-party
7
20515
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
11334
0
4949
0
1966
0
623
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.15507374661028
0.02981340392562
div
0.01749053030303
0.016218491735537
0.0072347193526171
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://watchwrestling.store/wp-content/cache/min/1/6c39208c311672bc2132dfeb4c6ca335.js
3210
131
https://watchwrestling.store/
1234
124
https://watchwrestling.store/
1125
109
https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
1905
55
Avoid non-composited animations — 130 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element
AEW
MMA
NWA
UFC
WWE
AEW
GCW
New
nwa
nxt
raw
ROH
ufc
wwe

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 — 2.7 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 2.7 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.228
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First Meaningful Paint — 2.7 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 5220 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Remove unused CSS — Potential savings of 36 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Watchwrestling.store 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://watchwrestling.store/wp-content/cache/min/1/e1e58e9ae40cd1e91f9be54a849b63af.css
38149
36584
Remove unused JavaScript — Potential savings of 35 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://watchwrestling.store/wp-content/cache/min/1/6c39208c311672bc2132dfeb4c6ca335.js
67317
36174

Opportunities

Eliminate render-blocking resources — Potential savings of 1,440 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Watchwrestling.store 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://watchwrestling.store/wp-content/cache/min/1/e1e58e9ae40cd1e91f9be54a849b63af.css
38149
450
https://fonts.googleapis.com/css?family=Arimo%3A400%2C700%7CDroid+Serif%3A400%2C700%7COpen+Sans%3A600%2C700&ver=5.7.2
1600
780

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/opensans/v20/mem5YaGs126MiZpBA-UN7rgOUuhpKKSTjw.woff2
3.796000033617
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 Failing Elements
https://watchwrestling.store/wp-content/uploads/2021/05/Watch-AEW-Double-Or-Nothing-2021-PPV-53021-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2020/08/NJPW-Watch-NJPW-Strong-New-Japan-Cup-2020-USA-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2020/01/AEW-Wrestling-Dynamite-1-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2021/05/Watch-Haney-vs-Linares-52921-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2019/12/Watch-WWE-Smackdown-11819-3-2-1-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2020/01/NXT-UK-3-2-1-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2019/12/MainEvent-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2021/05/PBC-premier-boxing-champions-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2020/01/205-live-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2019/12/impactwrestling-3-2-1-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2020/08/WWE-Talking-Smack-320x180.jpg
https://watchwrestling.store/wp-content/uploads/2020/01/this-week-in-wwe-1-320x180.jpeg
https://watchwrestling.store/wp-content/uploads/2020/03/watchwrestling.png
91

Accessibility

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

Navigation

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

ARIA

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

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<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.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

Contrast

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

Best practices

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

Manual Checks

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

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

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

Audits

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

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
Modernizr
2.6.2
yepnope
WordPress
5.7.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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://watchwrestling.store/wp-content/plugins/wp-rocket/assets/js/lazyload/12.0/lazyload.min.js
https://watchwrestling.store/wp-content/plugins/wp-rocket/assets/js/lazyload/12.0/lazyload.min.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://watchwrestling.store/
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://watchwrestling.store/wp-content/uploads/2020/03/watchwrestling.png
220 x 22
220 x 22
440 x 44

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: the server responded with a status of 404 (Not Found)
ReferenceError: jQuery is not defined at <anonymous>:67:4 at t.activateScript (https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js:1:11855) at https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js:1:11052 at t.run (https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js:1:11259) at https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js:1:2907 at https://ajax.cloudflare.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js:1:8117
88

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for watchwrestling.store. 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 watchwrestling.store on mobile screens.
Document uses legible font sizes — 60.58% 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
#copyright, #credits
6.79%
11px
.item .entry-meta, .item .stats
2.02%
11px
1.75%
11px
1.27%
11px
1.17%
11px
1.11%
11px
1.11%
11px
1.06%
11px
1.06%
11px
1.06%
11px
1.06%
11px
1.01%
11px
1.01%
11px
0.95%
11px
0.95%
11px
0.95%
11px
0.95%
11px
0.80%
11px
0.74%
11px
0.74%
11px
0.74%
11px
0.69%
11px
0.64%
11px
0.58%
11px
0.48%
11px
0.48%
11px
0.48%
11px
0.37%
11px
0.37%
11px
0.37%
11px
0.32%
11px
0.32%
11px
0.32%
11px
0.27%
11px
0.27%
11px
0.21%
11px
0.21%
11px
0.21%
11px
4.51%
< 12px
60.58%
≥ 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 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.

Content Best Practices

Document does not have a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.

Mobile Friendly

Tap targets are not sized appropriately — 30% 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
277x14
277x14
277x14
194x14
214x14
214x14
214x14
180x14
270x14
270x14
270x14
199x14
183x14
183x14
183x14
163x14
174x14
174x14
174x14
189x14
178x14
178x14
178x14
159x14
126x14
166x14
139x14
225x14
139x14
139x14
140x14
126x14
126x14
126x14
159x14
159x14
50x27
163x14
163x14
250x29
250x29
166x14
166x14
360x33
360x33
180x14
180x14
194x14
54x30
54x30
nxt
34x19
ufc
34x19
199x14
raw
37x19
189x14
189x14
nxt
34x19
36x19
36x19
raw
37x19
New
42x19
AEW
45x19
GCW
46x19
46x19
ufc
34x19
52x19
53x19
51x19
61x19
61x19
121x19
115x19
132x19
96x19
95x19
191x19
109x19
112x19
109x19
123x19
130x19
147x19
117x19
148x19
62x19
106x19
ROH
44x19
194x14
194x14
48x19
New
42x19
nwa
40x19
ROH
nwa
40x19
68x19
UFC
26x29
UFC
26x29
115x19
NWA
29x29
WWE
33x29
GCW
46x19
199x14
199x14
36x29
36x29
44x29
52x19
NWA
29x29
MMA
74x29
67x29
93x29
62x29
62x29
62x29
62x29

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

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of watchwrestling.store. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 watchwrestling.store 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: 172.67.138.101
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: No
Name:
Organization: Cloudflare, Inc.
Country: GB
City: wafangdian
State: Arizona
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 28th July, 2020
Valid To: 28th July, 2021
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: 4d04c09a
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 18044257597978116307915638571950637896
Serial Number (Hex): 0D9332961FE0297B15C87665072F8348
Valid From: 28th July, 2024
Valid To: 28th July, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.crl

Certificate Policies: Policy: 2.16.840.1.114412.1.1
CPS: https://www.digicert.com/CPS
Policy: 2.23.140.1.2.2

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/CloudflareIncECCCA-3.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
Timestamp : Jul 28 21:14:32.554 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:88:43:6B:81:A1:95:0E:08:79:79:E8:
43:A1:B4:98:87:50:DA:F1:BC:19:C8:2C:28:65:22:AA:
A1:77:00:EE:BC:02:21:00:A3:39:C7:61:0D:84:C3:28:
5C:D0:37:B9:0C:01:56:50:27:6D:55:4B:96:5A:D1:AA:
F8:2F:01:08:54:CA:CC:01
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
Timestamp : Jul 28 21:14:32.603 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:DD:73:34:23:F9:62:3A:33:50:E4:44:
24:12:98:BA:75:B2:38:94:8D:98:A4:AA:7B:24:0B:39:
A4:20:7A:5B:F1:02:20:40:21:23:5F:8D:4E:C9:5F:CE:
3A:2F:3C:DC:95:BE:88:4E:E2:6C:8A:3B:DF:7C:EC:34:
56:9A:1E:D9:59:11:F1
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:sni.cloudflaressl.com
DNS:watchwrestling.store
DNS:*.watchwrestling.store
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 30th May, 2021
Content-Type: text/html; charset=UTF-8
Cache-Control: max-age=0
Expires: 30th May, 2021
Server: cloudflare
Connection: keep-alive
Vary: X-Forwarded-Proto,Accept-Encoding,User-Agent
Last-Modified: 30th May, 2021
CF-Cache-Status: DYNAMIC
cf-request-id: 0a5f1627080000191b9d306000000001
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v2?s=yxBO7rj6upJGxPL63N4YPupDO8XXWMZ7nTki45cnOAAKWD1VaORKsUrmWJTN7GHrkkGOqIciGX82Q6IVqfXEYpoukbGur%2FrIiF1MfoK%2BcievAdM3BbI41FMkPI8LMvCGumM%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"report_to":"cf-nel","max_age":604800}
CF-RAY: 65785951ad96191b-EWR
alt-svc: h3-27=":443"; ma=86400, h3-28=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers:
Full Whois: watchwrestling.store domain is not supported

Nameservers

Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$516 USD
0/5
$164 USD 1/5
0/5

Sites hosted on the same IP address