strikeout.cc

strikeout.cc is SSL secured

Free website and domain report on strikeout.cc

Last Updated: 4th June, 2023 Update Now
Overview

Snoop Summary for strikeout.cc

This is a free and comprehensive report about strikeout.cc. The domain strikeout.cc is currently hosted on a server located in Colombia with the IP address 45.178.6.146, where the local currency is COP and Spanish is the local language. Our records indicate that strikeout.cc is privately registered by REDACTED FOR PRIVACY. Strikeout.cc is expected to earn an estimated $429 USD per day from advertising revenue. The sale of strikeout.cc would possibly be worth $313,072 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Strikeout.cc is insanely popular with an estimated 101,410 daily unique visitors. This report was last updated 4th June, 2023.

About strikeout.cc

Site Preview: strikeout.cc strikeout.cc
Title: StrikeOut - NFL, NBA, NHL, MLB, MMA Sports HD Streams | Strikeout
Description: StrikeOut – Watch HD NFL, NBA, NHL, MLB, MMA, UFC streams for free. Looking for quality HD sports streams? Visit strikeout stream now
Keywords and Tags: gambling, popular, sports
Related Terms: anime streams, bilasport nhl, mlb draft, mlb schedule, mlb streams, nhl steams, resultado nhl, sport streams, top periscope streams
Fav Icon:
Age: Over 6 years old
Domain Created: 31st January, 2018
Domain Updated: 25th June, 2022
Domain Expires: 31st January, 2024
Review

Snoop Score

3/5 (Great!)

Valuation

$313,072 USD
Note: All valuation figures are estimates.

Popularity

Very High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 13,032
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: 101,410
Monthly Visitors: 3,086,601
Yearly Visitors: 37,014,650
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $429 USD
Monthly Revenue: $13,053 USD
Yearly Revenue: $156,531 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: strikeout.cc 12
Domain Name: strikeout 9
Extension (TLD): cc 2
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 81
Performance 96
Accessibility 95
Best Practices 83
SEO 100
PWA 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://wp.strikeout.cc/
Updated: 28th November, 2022

2.03 seconds
First Contentful Paint (FCP)
70%
18%
12%

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

Simulate loading on desktop
96

Performance

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

Metrics

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

Audits

Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.9 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://strikeout.cc/
http/1.1
0
251.08300009742
243
0
301
text/html
https://wp.strikeout.cc/
http/1.1
251.38799985871
1176.5239997767
4745
15791
200
text/html
Document
https://fonts.googleapis.com/css2?family=Lato:ital,wght@0,400;0,700;1,400&display=swap
h2
1183.4660000168
1201.7529997975
1227
2170
200
text/css
Stylesheet
https://wp.strikeout.cc/darkly.css
http/1.1
1185.5629999191
2189.3489998765
23890
195794
200
text/css
Stylesheet
https://wp.strikeout.cc/font/strikeout.woff2
http/1.1
1186.0429998487
2080.941000022
12729
12372
200
font/woff2
Font
https://wp.strikeout.cc/home.min.css
http/1.1
1186.1319998279
2041.8759998865
848
2084
200
text/css
Stylesheet
https://www.googletagmanager.com/gtag/js?id=UA-147730155-3
h2
2083.3999998868
2101.9279998727
44438
111645
200
application/javascript
Script
https://wp.strikeout.cc/img/strikeout.svg
http/1.1
2111.7940000258
3054.4170001522
1242
2709
200
image/svg+xml
Image
https://wp.strikeout.cc/home.bun.min.js
http/1.1
2192.0039998367
2671.0789999925
48330
158333
200
application/javascript
Script
data
2203.1259997748
2203.2099999487
0
70
200
image/png
Image
https://uptimecdn.com/script/bootstrap.js
h2
2204.7089999542
2278.3419997431
35592
100584
200
application/javascript
Script
https://wp.strikeout.cc/img/home.png
http/1.1
2209.7390000708
2899.54699995
24864
24508
200
image/png
Image
https://wp.strikeout.cc/img/worldcup.svg
http/1.1
2210.8040000312
2735.53299997
1980
3725
200
image/svg+xml
Image
https://fonts.gstatic.com/s/lato/v23/S6uyw4BMUTPHjx4wXiWtFCc.woff2
h2
2212.241999805
2217.0069999993
14904
13976
200
font/woff2
Font
https://fonts.gstatic.com/s/lato/v23/S6u9w4BMUTPHh6UVSwiPGQ3q5d0.woff2
h2
2213.0020000041
2216.5179997683
15076
14148
200
font/woff2
Font
https://www.google-analytics.com/analytics.js
h2
2258.1059997901
2263.9219998382
20662
50230
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=171296643&t=pageview&_s=1&dl=https%3A%2F%2Fwp.strikeout.cc%2F&ul=en-us&de=UTF-8&dt=StrikeOut%20-%20NFL%2C%20NBA%2C%20NHL%2C%20MLB%2C%20MMA%20Sports%20HD%20Streams%20%7C%20Strikeout&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAACAAI~&jid=490035106&gjid=1611748845&cid=47034227.1669660977&tid=UA-147730155-3&_gid=1233693830.1669660977&_r=1&gtm=2oub90&z=649207737
h2
2292.9380000569
2296.9470000826
613
1
200
text/plain
XHR
https://uptimecdn.com/script/ut.js?cb=1669660976750
h2
2331.2479997985
2406.307999976
26400
71356
200
application/javascript
Script
https://youradexchange.com/script/suurl4.php?r=2370731&chua=%22Chromium%22;v=98,%20%22Google%20Chrome%22;v=98,%20%22Lighthouse%22;v=9.6.6&chmob=?0&chp=macOS&chpv=10.15.7&chuafv=98.0.4695.0&cbur=0.9213949138166806&cbiframe=0&cbWidth=1350&cbHeight=940&cbtitle=StrikeOut%20-%20NFL%2C%20NBA%2C%20NHL%2C%20MLB%2C%20MMA%20Sports%20HD%20Streams%20%7C%20Strikeout&cbpage=https%3A%2F%2Fwp.strikeout.cc%2F&cbref=&cbdescription=StrikeOut%20%E2%80%93%20Watch%20HD%20NFL%2C%20NBA%2C%20NHL%2C%20MLB%2C%20MMA%2C%20UFC%20streams%20for%20free.%20Looking%20for%20quality%20HD%20sports%20streams%3F%20Visit%20strikeout%20stream%20now&cbkeywords=&cbcdn=uptimecdn.com&aggr=0
h2
2336.2289997749
2394.77299992
176
0
204
Fetch
https://vip.jams.wiki/?pge=home&lang=en&dom=sd&ref=&h=1
h2
2709.5929998904
2791.7280001566
2178
4512
403
text/html
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1180.838
11.755
2191.154
10.56
2205.704
31.467
2237.257
9.06
2251.585
7.451
2271.084
23.282
2305.768
27.51
2413.758
17.052
2684.211
25.214
2737.402
6.535
3056.1
7.954
3702.32
5.46
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Strikeout.cc should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Strikeout.cc should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Strikeout.cc should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Strikeout.cc should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Strikeout.cc should consider minifying JS files.
Reduce unused CSS — Potential savings of 22 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Strikeout.cc 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://wp.strikeout.cc/darkly.css
23890
22522
Reduce unused JavaScript — Potential savings of 56 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://wp.strikeout.cc/home.bun.min.js
48330
35622
https://www.googletagmanager.com/gtag/js?id=UA-147730155-3
44438
22003
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Strikeout.cc should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://strikeout.cc/
190
https://wp.strikeout.cc/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Strikeout.cc 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 22 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://uptimecdn.com/script/bootstrap.js
12227
https://uptimecdn.com/script/ut.js?cb=1669660976750
10460
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 274 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://wp.strikeout.cc/home.bun.min.js
48330
https://www.googletagmanager.com/gtag/js?id=UA-147730155-3
44438
https://uptimecdn.com/script/bootstrap.js
35592
https://uptimecdn.com/script/ut.js?cb=1669660976750
26400
https://wp.strikeout.cc/img/home.png
24864
https://wp.strikeout.cc/darkly.css
23890
https://www.google-analytics.com/analytics.js
20662
https://fonts.gstatic.com/s/lato/v23/S6u9w4BMUTPHh6UVSwiPGQ3q5d0.woff2
15076
https://fonts.gstatic.com/s/lato/v23/S6uyw4BMUTPHjx4wXiWtFCc.woff2
14904
https://wp.strikeout.cc/font/strikeout.woff2
12729
Avoids an excessive DOM size — 187 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
187
Maximum DOM Depth
Go
9
Maximum Child Elements
24
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Strikeout.cc 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.0 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://wp.strikeout.cc/
65.406
5.535
1.755
Minimizes main-thread work — 0.3 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
119.479
Other
55.086
Style & Layout
36.822
Rendering
13.008
Script Parsing & Compilation
12.725
Parse HTML & CSS
11.937
Garbage Collection
1.631
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 19 requests • 274 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
19
280137
Script
5
175422
Font
3
42709
Image
4
30264
Stylesheet
3
25965
Document
1
4745
Other
3
1032
Media
0
0
Third-party
10
161266
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)
44438
0
31207
0
21275
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 4 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00028299842395587
6.9443459416864E-5
6.8978198056212E-5
1.2489493039138E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of strikeout.cc on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Metrics

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

Other

Serve static assets with an efficient cache policy — 3 resources found
Strikeout.cc 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.google-analytics.com/analytics.js
7200000
20662
https://uptimecdn.com/script/bootstrap.js
14400000
35592
https://uptimecdn.com/script/ut.js?cb=1669660976750
14400000
26400

Other

Reduce initial server response time — Root document took 930 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://wp.strikeout.cc/
926.13
95

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of strikeout.cc. 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.
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 alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Strikeout.cc 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

Navigation

Heading elements are not 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.
Failing Elements

Manual Checks

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
5.2.1
jQuery
3.6.1
core-js
core-js-pure@3.22.3; core-js-pure@3.22.3
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.
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://strikeout.cc/
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 403 (Forbidden)
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for strikeout.cc. 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 strikeout.cc on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

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

PWA

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of strikeout.cc on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

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

PWA Optimized

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

Manual Checks

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

1.84 seconds
First Contentful Paint (FCP)
74%
16%
10%

0.01 seconds
First Input Delay (FID)
98%
1%
1%

Simulate loading on mobile
54

Performance

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

Metrics

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

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Strikeout.cc should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Strikeout.cc should consider serving more appropriate-sized images.
Defer offscreen images — Potential savings of 2 KiB
Time to Interactive can be slowed down by resources on the page. Strikeout.cc should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://vip.jams.wiki/?pge=home&lang=en&dom=sd&ref=&h=1
2179
2179
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Strikeout.cc should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Strikeout.cc should consider minifying JS files.
Reduce unused CSS — Potential savings of 22 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Strikeout.cc 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://wp.strikeout.cc/darkly.css
23890
22597
Reduce unused JavaScript — Potential savings of 56 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://wp.strikeout.cc/home.bun.min.js
48330
35622
https://www.googletagmanager.com/gtag/js?id=UA-147730155-3
44438
22003
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 4,470 ms
Redirects can cause additional delays before the page can begin loading. Strikeout.cc should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://strikeout.cc/
4470
https://wp.strikeout.cc/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Strikeout.cc should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 231 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://wp.strikeout.cc/home.bun.min.js
48330
https://www.googletagmanager.com/gtag/js?id=UA-147730155-3
44438
https://wp.strikeout.cc/img/home.png
24864
https://wp.strikeout.cc/darkly.css
23890
https://wp.strikeout.cc/
21724
https://www.google-analytics.com/analytics.js
20664
https://fonts.gstatic.com/s/lato/v23/S6u9w4BMUTPHh6UVSwiPGQ3q5d0.woff2
15076
https://fonts.gstatic.com/s/lato/v23/S6uyw4BMUTPHjx4wXiWtFCc.woff2
14904
https://wp.strikeout.cc/font/strikeout.woff2
12729
https://vip.jams.wiki/?pge=home&lang=en&dom=sd&ref=&h=1
2179
Uses efficient cache policy on static assets — 3 resources found
Strikeout.cc 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://booptuwa.net/5/5532940
0
135
https://thefacux.com/tag.min.js
0
133
https://www.google-analytics.com/analytics.js
7200000
20664
Avoids an excessive DOM size — 188 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
188
Maximum DOM Depth
Go
9
Maximum Child Elements
24
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Strikeout.cc 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.
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 21 requests • 231 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
21
236105
Script
5
113700
Font
3
42709
Image
4
30265
Stylesheet
3
25965
Document
1
21724
Other
5
1742
Media
0
0
Third-party
11
99956
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00020989439222548
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 — 20 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://wp.strikeout.cc/
2222
1426
https://wp.strikeout.cc/home.bun.min.js
4500
808
https://www.google-analytics.com/analytics.js
6440
385
https://wp.strikeout.cc/
1859
363
https://wp.strikeout.cc/
3819
291
https://www.googletagmanager.com/gtag/js?id=UA-147730155-3
4188
267
https://wp.strikeout.cc/
5566
251
https://www.googletagmanager.com/gtag/js?id=UA-147730155-3
5308
202
https://wp.strikeout.cc/darkly.css
3648
171
https://wp.strikeout.cc/
1224
164
https://wp.strikeout.cc/
636
157
Unattributable
850
151
https://wp.strikeout.cc/
1710
149
Unattributable
1487
143
Unattributable
1001
87
https://wp.strikeout.cc/
4110
78
Unattributable
1388
71
Unattributable
1630
67
Unattributable
1160
64
https://wp.strikeout.cc/
5863
63
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of strikeout.cc on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://strikeout.cc/
http/1.1
0
246.18300003931
258
0
301
text/html
https://wp.strikeout.cc/
http/1.1
246.6199999908
1236.9020000333
21724
74277
200
text/html
Document
https://fonts.googleapis.com/css2?family=Lato:ital,wght@0,400;0,700;1,400&display=swap
h2
1260.5570000596
1281.8320000079
1227
2170
200
text/css
Stylesheet
https://wp.strikeout.cc/darkly.css
http/1.1
1260.927000083
2322.077000048
23890
195794
200
text/css
Stylesheet
https://wp.strikeout.cc/font/strikeout.woff2
http/1.1
1261.0690000001
2169.4530000677
12729
12372
200
font/woff2
Font
https://wp.strikeout.cc/home.min.css
http/1.1
1261.1920000054
2129.316000035
848
2084
200
text/css
Stylesheet
https://www.googletagmanager.com/gtag/js?id=UA-147730155-3
h2
2174.8430000152
2192.9409999866
44438
111645
200
application/javascript
Script
https://wp.strikeout.cc/img/strikeout.svg
http/1.1
2231.4849999966
2786.291000084
1242
2709
200
image/svg+xml
Image
https://wp.strikeout.cc/home.bun.min.js
http/1.1
2326.8530000933
3097.9590000352
48330
158333
200
application/javascript
Script
https://wp.strikeout.cc/img/home.png
http/1.1
2415.4950000811
3393.4800000861
24864
24508
200
image/png
Image
https://wp.strikeout.cc/img/worldcup.svg
http/1.1
2420.2580000274
3180.159999989
1980
3725
200
image/svg+xml
Image
https://fonts.gstatic.com/s/lato/v23/S6uyw4BMUTPHjx4wXiWtFCc.woff2
h2
2426.5810000943
2435.3480000282
14904
13976
200
font/woff2
Font
data
2590.9000000684
2591.0520000616
0
70
200
image/png
Image
https://fonts.gstatic.com/s/lato/v23/S6u9w4BMUTPHh6UVSwiPGQ3q5d0.woff2
h2
2787.7840000438
2795.4690000042
15076
14148
200
font/woff2
Font
https://wp.strikeout.cc/
http/1.1
3249.616999994
3807.6570000267
284
0
200
application/octet-stream
XHR
https://thefacux.com/5/5532923/?oo=1&aab=1
3279.3130000355
4166.8910000008
0
0
-1
XHR
https://thefacux.com/tag.min.js
h2
3291.6260000784
3711.340000038
133
0
200
text/html
Script
https://vip.jams.wiki/?pge=home&lang=en&dom=sd&ref=&h=1
h2
3971.2240000954
4253.6570000229
2179
4512
403
text/html
Image
https://www.google-analytics.com/analytics.js
h2
4038.1530000595
4047.0710000955
20664
50230
200
text/javascript
Script
https://kluauvass.com/
h2
4321.6249999823
4448.0700000422
587
0
200
text/html
XHR
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=897355017&t=pageview&_s=1&dl=https%3A%2F%2Fwp.strikeout.cc%2F&ul=en-us&de=UTF-8&dt=StrikeOut%20-%20NFL%2C%20NBA%2C%20NHL%2C%20MLB%2C%20MMA%20Sports%20HD%20Streams%20%7C%20Strikeout&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUABAAAAACAAI~&jid=188155430&gjid=1259732970&cid=407095881.1669661010&tid=UA-147730155-3&_gid=699137712.1669661010&_r=1&gtm=2oub90&z=867059033
h2
4416.3089999929
4424.3509999942
613
1
200
text/plain
XHR
https://booptuwa.net/5/5532940
h2
4620.16400008
5039.1430000309
135
0
200
text/html
Script
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)
1249.954
37.306
1309.805
9.983
2326.961
42.701
2370.74
9.764
2380.519
181.55
2586.077
713.013
3299.162
39.234
3345.067
28.567
3373.651
37.683
3411.747
21.706
3433.569
13.677
3447.358
11.295
3458.688
145.68
3604.419
19.427
3623.957
66.668
3690.804
11.261
3704.247
15.957
3720.61
41.097
3761.82
17.64
3779.474
201.993
3982.381
50.453
4033.645
14.027
4055.35
125.505
4180.885
13.917
4195.994
11.387
4209.373
35.847
4257.291
16.687
4275.061
15.649
4291.105
13.958
4305.889
13.02
4318.928
8.635
4327.717
96.24
4430.069
9.153
4447.587
10.637
4535.067
6.974
5471.581
13.543
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 2.3 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 6.7 s
The time taken for the page to become fully interactive.
Speed Index — 5.8 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.8 s
The timing of the largest text or image that is painted.

Audits

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

Metrics

Total Blocking Time — 3,210 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).

Audits

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

Other

Reduce initial server response time — Root document took 990 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://wp.strikeout.cc/
991.273
Reduce JavaScript execution time — 5.0 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://wp.strikeout.cc/
5635.044
2686.012
487.032
Unattributable
1002.76
22.972
0
https://wp.strikeout.cc/home.bun.min.js
835.824
644.348
88.548
https://www.googletagmanager.com/gtag/js?id=UA-147730155-3
734.064
684.88
35.284
https://www.google-analytics.com/analytics.js
395.732
375.472
5.056
https://wp.strikeout.cc/darkly.css
170.804
0
0
Minimize main-thread work — 8.8 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
4414.712
Other
1427.328
Style & Layout
1179.96
Rendering
742.384
Script Parsing & Compilation
617.172
Parse HTML & CSS
299.836
Garbage Collection
142.992
Reduce the impact of third-party code — Third-party code blocked the main thread for 630 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
44438
327.432
21277
306.52
31207
0
First Contentful Paint (3G) — 4590 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
95

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of strikeout.cc. 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.
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 alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Strikeout.cc 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
Go

Navigation

Heading elements are not 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.
Failing Elements

Manual Checks

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
5.2.1
jQuery
3.6.1
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.
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://strikeout.cc/
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
Access to XMLHttpRequest at 'https://thefacux.com/5/5532923/?oo=1&aab=1' from origin 'https://wp.strikeout.cc' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: the server responded with a status of 403 (Forbidden)
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for strikeout.cc. 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 strikeout.cc on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

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

PWA

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of strikeout.cc on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

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

PWA Optimized

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

Manual Checks

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

Server Location

Server IP Address: 45.178.6.146
Continent: South America
Country: Colombia
Colombia Flag
Region:
City:
Longitude: -74.0799
Latitude: 4.5981
Currencies: COP
Languages: Spanish

Web Hosting Provider

Registration

Domain Registrant

Private Registration: Yes
Name: REDACTED FOR PRIVACY
Organization: REDACTED FOR PRIVACY
Country: US
City: REDACTED FOR PRIVACY
State: NY
Post Code: REDACTED FOR PRIVACY
Email:
Phone: REDACTED FOR PRIVACY
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Sarek 95.215.19.224
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 80/100
WOT Child Safety: 10/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: strikeout.cc
Issued By: R3
Valid From: 23rd November, 2022
Valid To: 21st February, 2023
Subject: CN = strikeout.cc
Hash: dee78694
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03349F9B9AACB08B6DDCEEF02CEA982D42DB
Serial Number (Hex): 03349F9B9AACB08B6DDCEEF02CEA982D42DB
Valid From: 23rd November, 2024
Valid To: 21st February, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Nov 23 18:40:53.348 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:57:3A:54:36:7A:73:50:71:D4:06:B3:52:
43:4B:E5:DF:2D:37:D0:2A:B8:0F:4B:46:15:84:B8:0A:
CB:03:DD:A6:02:21:00:AB:20:4F:DD:FF:01:F4:91:5B:
1F:1E:DF:7A:CF:7A:8D:EA:5C:84:F9:D4:BA:0D:54:67:
A4:DB:92:AA:DA:65:F1
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
Timestamp : Nov 23 18:40:53.882 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:97:D7:2A:75:5F:BA:F0:90:85:10:10:
ED:B5:55:93:FB:F7:92:6D:1D:B9:67:C2:FC:47:81:7B:
E5:5D:B6:66:DA:02:20:2B:89:EA:E1:B3:F6:F1:F6:22:
80:1B:53:CD:2B:D8:5C:B5:73:FA:A7:08:A3:08:2A:8D:
BC:4D:48:6F:39:4E:C4
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:strikeout.cc
DNS:wp.strikeout.cc
DNS:www.strikeout.cc
DNS:ko.strikeout.cc
Technical

DNS Lookup

A Records

Host IP Address Class TTL
strikeout.cc. 45.178.6.104 IN 900
strikeout.cc. 45.178.6.146 IN 900

NS Records

Host Nameserver Class TTL
strikeout.cc. dns1.cloudns.net. IN 900
strikeout.cc. dns2.cloudns.net. IN 900
strikeout.cc. dns5.cloudns.net. IN 900
strikeout.cc. dns6.cloudns.net. IN 900

SOA Records

Domain Name Primary NS Responsible Email TTL
strikeout.cc. dns1.cloudns.net. support.cloudns.net. 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 28th November, 2022
Content-Type: application/octet-stream
Content-Length: 2
Connection: keep-alive
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Xss-Protection: 1; mode=block

Whois Lookup

Created: 31st January, 2018
Changed: 25th June, 2022
Expires: 31st January, 2024
Registrar: Sarek
Status: ok
Nameservers: dns1.cloudns.net
dns2.cloudns.net
dns5.cloudns.net
dns6.cloudns.net
Owner Name: REDACTED FOR PRIVACY
Owner Organization: REDACTED FOR PRIVACY
Owner Street: REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner State: REDACTED FOR PRIVACY
Owner Country: REDACTED FOR PRIVACY
Owner Phone: REDACTED FOR PRIVACY
Owner Email: https://sarek.fi/contact/strikeout.cc/registrant
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: REDACTED FOR PRIVACY
Full Whois: Domain Name: strikeout.cc
Updated Date: 2022-06-25T17:45:37.000Z
Creation Date: 2018-01-31T16:14:46.000Z
Expiration Date: 2024-01-31T16:14:46.000Z
Registrar: Sarek
Registrar URL: https://sarek.fi
Registrar Abuse Contact Email: abuse@sarek.fi
Registrar Abuse Contact Phone:
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: REDACTED FOR PRIVACY
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: REDACTED FOR PRIVACY
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext:
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext:
Registrant Email: https://sarek.fi/contact/strikeout.cc/registrant
Domain Status: ok https://www.icann.org/epp#ok
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext:
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext:
Admin Email: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext:
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext:
Tech Email: REDACTED FOR PRIVACY
Name Server: dns1.cloudns.net
Name Server: dns2.cloudns.net
Name Server: dns5.cloudns.net
Name Server: dns6.cloudns.net
DNSSEC: unsigned

Nameservers

Name IP Address
dns1.cloudns.net 185.136.96.77
dns2.cloudns.net 185.136.97.77
dns5.cloudns.net 185.136.98.77
dns6.cloudns.net 185.136.99.77
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

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

Sites hosted on the same IP address

Domain Valuation Snoop Score
$4,225 USD 2/5