scatboi.com

scatboi.com is SSL secured

Free website and domain report on scatboi.com

Last Updated: 19th November, 2024
Overview

Snoop Summary for scatboi.com

This is a free and comprehensive report about scatboi.com. The domain scatboi.com is currently hosted on a server located in Czechia with the IP address 89.185.228.31, where the local currency is CZK and Czech is the local language. Our records indicate that scatboi.com is owned/operated by Identity Protect Limited. Scatboi.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If scatboi.com was to be sold it would possibly be worth $1,015 USD (based on the daily revenue potential of the website over a 24 month period). Scatboi.com is somewhat popular with an estimated 483 daily unique visitors. This report was last updated 19th November, 2024.

About scatboi.com

Site Preview:
Title:
Description: sb - schwule Scat Bilder und Profile für Kerle und Jungs ab 18, die es dreckig mögen!
Keywords and Tags: adult content, merda cacata stronzo pisciare pisciata cacca cacasotto feticcio, popular, pornography
Related Terms: female scat, fucking in scat, nur jungs, scat blowjob, scat brazil, scat eating, scat lunch, scat pack, scat slave, scat solo
Fav Icon:
Age: Over 20 years old
Domain Created: 12th March, 2004
Domain Updated: 14th May, 2021
Domain Expires: 12th March, 2025
Review

Snoop Score

2/5

Valuation

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

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 1,377,200
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: 483
Monthly Visitors: 14,701
Yearly Visitors: 176,295
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $42 USD
Yearly Revenue: $502 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: scatboi.com 11
Domain Name: scatboi 7
Extension (TLD): com 3

Page Speed Analysis

Average Load Time: 1.54 seconds
Load Time Comparison: Faster than 58% of sites

PageSpeed Insights

Avg. (All Categories) 68
Performance 93
Accessibility 68
Best Practices 80
SEO 82
Progressive Web App 18
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://scatboi.com/
Updated: 10th October, 2021

3.43 seconds
First Contentful Paint (FCP)
22%
42%
36%

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

93

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for scatboi.com. 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.
Largest Contentful Paint — 1.0 s
The timing of the largest text or image that is painted.
Time to Interactive — 0.7 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.057
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.7 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://scatboi.com/
http/1.1
0
208.47899999353
403
0
301
text/html
https://scatboi.com/
http/1.1
208.99899999495
2452.0460000203
3584
9192
200
text/html
Document
https://scatboi.com/common/style.css?1590774025
http/1.1
2468.6100000108
3504.5200000168
2416
6757
200
text/css
Stylesheet
https://scatboi.com/common/style_sb.css?1612462834
http/1.1
2468.7580000027
3504.8410000163
928
1474
200
text/css
Stylesheet
https://scatboi.com/common/style_flags.css?1356122406
http/1.1
2469.2340000183
3088.9040000038
1994
13065
200
text/css
Stylesheet
https://scatboi.com/common/functions.js?1589229873
http/1.1
2469.4200000085
3511.9300000079
1053
1596
200
application/x-javascript
Script
https://scatboi.com/common/javascript/greybox/AJS.js?1332768890
http/1.1
2469.6720000065
3502.2420000168
4078
10396
200
application/x-javascript
Script
https://scatboi.com/common/javascript/greybox/AJS_fx.js?1332768891
http/1.1
2469.9689999979
3505.4740000051
1525
3192
200
application/x-javascript
Script
https://scatboi.com/common/javascript/greybox/gb_scripts.js?1332768891
http/1.1
2470.2700000198
3504.0190000145
3688
11907
200
application/x-javascript
Script
https://scatboi.com/common/javascript/greybox/gb_styles.css?1332768891
http/1.1
2470.5210000102
3506.2740000139
1028
2302
200
text/css
Stylesheet
https://scatboi.com/_scatboi/images/logo.gif
http/1.1
3510.5700000131
4144.8950000049
4394
4102
200
image/gif
Image
https://scatboi.com/_scatboi/images/home.jpg
http/1.1
3513.7709999981
4237.1980000171
15317
15023
200
image/jpeg
Image
https://scatboi.com/common/images/safeadlt.gif
http/1.1
3518.0850000179
4036.1730000004
1473
1182
200
image/gif
Image
https://scatboi.com/_scatboi/images/corner_t_l.gif
http/1.1
3520.4160000139
4148.772000015
343
55
200
image/gif
Image
https://scatboi.com/_scatboi/images/corner_t_r.gif
http/1.1
3520.629000006
4047.6229999913
343
55
200
image/gif
Image
https://www.scatboi.com/common/images/star.png
http/1.1
3545.0509999937
4577.4970000202
764
473
200
image/png
Image
https://scatboi.com/common/javascript/greybox/w_close.gif
http/1.1
4581.7019999959
5613.2380000199
363
74
200
image/gif
Image
https://scatboi.com/common/javascript/greybox/header_bg.gif
http/1.1
4581.8389999913
5616.360999993
1480
1188
200
image/gif
Image
https://scatboi.com/common/javascript/greybox/g_close.gif
http/1.1
4582.0490000187
5100.6430000125
831
541
200
image/gif
Image
https://scatboi.com/common/javascript/greybox/indicator.gif
http/1.1
4582.3600000003
5205.5530000071
8530
8238
200
image/gif
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)
2482.555
10.29
3540.447
5.726
3546.185
10.409
3556.917
16.153
3573.134
26.515
4066.791
5.099
4089.003
5.554
4176.911
7.524
5103.231
6.042
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.

Opportunities

Properly size images
Images can slow down the page's load time. Scatboi.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Scatboi.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Scatboi.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Scatboi.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Scatboi.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images — Potential savings of 9 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://scatboi.com/_scatboi/images/home.jpg
15023
8788
Serve images in next-gen formats — Potential savings of 11 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://scatboi.com/_scatboi/images/home.jpg
15023
11344.25
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. Scatboi.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://scatboi.com/
190
https://scatboi.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Scatboi.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
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.

Diagnostics

Avoids enormous network payloads — Total size was 53 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://scatboi.com/_scatboi/images/home.jpg
15317
https://scatboi.com/common/javascript/greybox/indicator.gif
8530
https://scatboi.com/_scatboi/images/logo.gif
4394
https://scatboi.com/common/javascript/greybox/AJS.js?1332768890
4078
https://scatboi.com/common/javascript/greybox/gb_scripts.js?1332768891
3688
https://scatboi.com/
3584
https://scatboi.com/common/style.css?1590774025
2416
https://scatboi.com/common/style_flags.css?1356122406
1994
https://scatboi.com/common/javascript/greybox/AJS_fx.js?1332768891
1525
https://scatboi.com/common/javascript/greybox/header_bg.gif
1480
Avoids an excessive DOM size — 103 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
103
Maximum DOM Depth
14
Maximum Child Elements
11
Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Scatboi.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.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://scatboi.com/
112.253
10.299
1.745
Minimizes main-thread work — 0.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
49.689
Style & Layout
39.067
Rendering
29.937
Script Evaluation
18.319
Parse HTML & CSS
12.099
Script Parsing & Compilation
2.79
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 — 20 requests • 53 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
20
54535
Image
10
33838
Script
4
10344
Stylesheet
4
6366
Document
1
3584
Other
1
403
Media
0
0
Font
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.024305972938905
0.014971577423752
0.0093052884186714
0.0061332045910277
 
0.0015762970531756
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.

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 550 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Scatboi.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://scatboi.com/common/style.css?1590774025
2416
70
https://scatboi.com/common/style_sb.css?1612462834
928
150
https://scatboi.com/common/style_flags.css?1356122406
1994
150
https://scatboi.com/common/javascript/greybox/gb_styles.css?1332768891
1028
150
https://scatboi.com/common/functions.js?1589229873
1053
150
https://scatboi.com/common/javascript/greybox/AJS.js?1332768890
4078
150
https://scatboi.com/common/javascript/greybox/AJS_fx.js?1332768891
1525
70
https://scatboi.com/common/javascript/greybox/gb_scripts.js?1332768891
3688
70

Diagnostics

Serve static assets with an efficient cache policy — 18 resources found
Scatboi.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://scatboi.com/_scatboi/images/home.jpg
0
15317
https://scatboi.com/common/javascript/greybox/indicator.gif
0
8530
https://scatboi.com/_scatboi/images/logo.gif
0
4394
https://scatboi.com/common/javascript/greybox/AJS.js?1332768890
0
4078
https://scatboi.com/common/javascript/greybox/gb_scripts.js?1332768891
0
3688
https://scatboi.com/common/style.css?1590774025
0
2416
https://scatboi.com/common/style_flags.css?1356122406
0
1994
https://scatboi.com/common/javascript/greybox/AJS_fx.js?1332768891
0
1525
https://scatboi.com/common/javascript/greybox/header_bg.gif
0
1480
https://scatboi.com/common/images/safeadlt.gif
0
1473
https://scatboi.com/common/functions.js?1589229873
0
1053
https://scatboi.com/common/javascript/greybox/gb_styles.css?1332768891
0
1028
https://scatboi.com/common/style_sb.css?1612462834
0
928
https://scatboi.com/common/javascript/greybox/g_close.gif
0
831
https://www.scatboi.com/common/images/star.png
0
764
https://scatboi.com/common/javascript/greybox/w_close.gif
0
363
https://scatboi.com/_scatboi/images/corner_t_l.gif
0
343
https://scatboi.com/_scatboi/images/corner_t_r.gif
0
343

Metrics

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

Opportunities

Reduce initial server response time — Root document took 2,240 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://scatboi.com/
2244.04

Diagnostics

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://scatboi.com/_scatboi/images/home.jpg
https://scatboi.com/_scatboi/images/logo.gif
https://scatboi.com/common/images/safeadlt.gif
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of scatboi.com on mobile screens.
68

Accessibility

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

Navigation

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

ARIA

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

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
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.
`<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 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"]`
Scatboi.com 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

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that scatboi.com 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.
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

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 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.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 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://scatboi.com/
Allowed

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Audits

Registers an `unload` listener
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.
Source
82

SEO

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

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.

Mobile Friendly

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.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of scatboi.com on mobile screens.

Crawling and Indexing

robots.txt is not 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.
18

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 scatboi.com. 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.

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 have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of scatboi.com on mobile screens.
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) 63
Performance 87
Accessibility 68
Best Practices 73
SEO 69
Progressive Web App 17
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://scatboi.com/
Updated: 10th October, 2021

4.08 seconds
First Contentful Paint (FCP)
6%
37%
57%

0.24 seconds
First Input Delay (FID)
3%
93%
4%

87

Performance

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

Metrics

Largest Contentful Paint — 2.1 s
The timing of the largest text or image that is painted.
Time to Interactive — 2.1 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).

Other

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 2.1 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://scatboi.com/
http/1.1
0
211.5150000318
403
0
301
text/html
https://scatboi.com/
http/1.1
212.07000000868
2432.6829999918
3584
9192
200
text/html
Document
https://scatboi.com/common/style.css?1590774025
http/1.1
2447.296999977
3384.3200000119
2416
6757
200
text/css
Stylesheet
https://scatboi.com/common/style_sb.css?1612462834
http/1.1
2447.6259999792
2967.2150000115
927
1474
200
text/css
Stylesheet
https://scatboi.com/common/style_flags.css?1356122406
http/1.1
2447.8000000236
3278.7799999933
1995
13065
200
text/css
Stylesheet
https://scatboi.com/common/functions.js?1589229873
http/1.1
2448.3309999923
3379.4600000256
1053
1596
200
application/x-javascript
Script
https://scatboi.com/common/javascript/greybox/AJS.js?1332768890
http/1.1
2448.6400000169
3280.1370000234
4078
10396
200
application/x-javascript
Script
https://scatboi.com/common/javascript/greybox/AJS_fx.js?1332768891
http/1.1
2448.8400000264
3276.7239999957
1525
3192
200
application/x-javascript
Script
https://scatboi.com/common/javascript/greybox/gb_scripts.js?1332768891
http/1.1
2448.9869999816
3281.8979999865
3688
11907
200
application/x-javascript
Script
https://scatboi.com/common/javascript/greybox/gb_styles.css?1332768891
http/1.1
2449.2120000068
3380.616999988
1028
2302
200
text/css
Stylesheet
https://scatboi.com/_scatboi/images/logo.gif
http/1.1
3381.6680000164
4186.4610000048
4394
4102
200
image/gif
Image
https://scatboi.com/_scatboi/images/home.jpg
http/1.1
3385.3320000344
4185.3390000178
15317
15023
200
image/jpeg
Image
https://scatboi.com/common/images/safeadlt.gif
http/1.1
3390.3220000211
4082.3070000042
1473
1182
200
image/gif
Image
https://scatboi.com/_scatboi/images/corner_t_l.gif
http/1.1
3394.5149999927
4082.6620000298
343
55
200
image/gif
Image
https://scatboi.com/_scatboi/images/corner_t_r.gif
http/1.1
3394.6800000267
4083.1440000329
343
55
200
image/gif
Image
https://www.scatboi.com/common/images/star.png
http/1.1
3418.4109999915
4971.93900001
764
473
200
image/png
Image
https://scatboi.com/common/javascript/greybox/w_close.gif
http/1.1
4974.8890000046
5495.0299999909
362
74
200
image/gif
Image
https://scatboi.com/common/javascript/greybox/header_bg.gif
http/1.1
4975.0450000283
5496.3850000058
1479
1188
200
image/gif
Image
https://scatboi.com/common/javascript/greybox/g_close.gif
http/1.1
4975.259000028
5495.3930000192
831
541
200
image/gif
Image
https://scatboi.com/common/javascript/greybox/indicator.gif
http/1.1
4975.6209999905
5599.2689999985
8530
8238
200
image/gif
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)
2465.161
8.764
3415.72
5.774
3421.505
20.885
3442.648
7.775
3450.441
11.226
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.

Opportunities

Properly size images
Images can slow down the page's load time. Scatboi.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Scatboi.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Scatboi.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Scatboi.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Scatboi.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
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 630 ms
Redirects can cause additional delays before the page can begin loading. Scatboi.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://scatboi.com/
630
https://scatboi.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Scatboi.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
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.

Diagnostics

Avoids enormous network payloads — Total size was 53 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://scatboi.com/_scatboi/images/home.jpg
15317
https://scatboi.com/common/javascript/greybox/indicator.gif
8530
https://scatboi.com/_scatboi/images/logo.gif
4394
https://scatboi.com/common/javascript/greybox/AJS.js?1332768890
4078
https://scatboi.com/common/javascript/greybox/gb_scripts.js?1332768891
3688
https://scatboi.com/
3584
https://scatboi.com/common/style.css?1590774025
2416
https://scatboi.com/common/style_flags.css?1356122406
1995
https://scatboi.com/common/javascript/greybox/AJS_fx.js?1332768891
1525
https://scatboi.com/common/javascript/greybox/header_bg.gif
1479
Avoids an excessive DOM size — 103 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
103
Maximum DOM Depth
14
Maximum Child Elements
11
Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Scatboi.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.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://scatboi.com/
289.44
24.648
6.312
Unattributable
83.272
9.792
0.536
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)
Other
140.6
Style & Layout
110.744
Rendering
68.744
Script Evaluation
51.812
Parse HTML & CSS
32.68
Script Parsing & Compilation
10.388
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 — 20 requests • 53 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
20
54533
Image
10
33836
Script
4
10344
Stylesheet
4
6366
Document
1
3584
Other
1
403
Media
0
0
Font
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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 — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.052443008303217
0.043045131770851
0.029870712653105
0.022804108821155
 
0.014783176567767
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.

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.1 s
The time taken for the first image or text on the page to be rendered.
Cumulative Layout Shift — 0.172
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Opportunities

Efficiently encode images — Potential savings of 9 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://scatboi.com/_scatboi/images/home.jpg
15023
8788
Serve images in next-gen formats — Potential savings of 11 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://scatboi.com/_scatboi/images/home.jpg
15023
11344.25

Diagnostics

Serve static assets with an efficient cache policy — 18 resources found
Scatboi.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://scatboi.com/_scatboi/images/home.jpg
0
15317
https://scatboi.com/common/javascript/greybox/indicator.gif
0
8530
https://scatboi.com/_scatboi/images/logo.gif
0
4394
https://scatboi.com/common/javascript/greybox/AJS.js?1332768890
0
4078
https://scatboi.com/common/javascript/greybox/gb_scripts.js?1332768891
0
3688
https://scatboi.com/common/style.css?1590774025
0
2416
https://scatboi.com/common/style_flags.css?1356122406
0
1995
https://scatboi.com/common/javascript/greybox/AJS_fx.js?1332768891
0
1525
https://scatboi.com/common/javascript/greybox/header_bg.gif
0
1479
https://scatboi.com/common/images/safeadlt.gif
0
1473
https://scatboi.com/common/functions.js?1589229873
0
1053
https://scatboi.com/common/javascript/greybox/gb_styles.css?1332768891
0
1028
https://scatboi.com/common/style_sb.css?1612462834
0
927
https://scatboi.com/common/javascript/greybox/g_close.gif
0
831
https://www.scatboi.com/common/images/star.png
0
764
https://scatboi.com/common/javascript/greybox/w_close.gif
0
362
https://scatboi.com/_scatboi/images/corner_t_l.gif
0
343
https://scatboi.com/_scatboi/images/corner_t_r.gif
0
343

Other

First Contentful Paint (3G) — 4125 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Metrics

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

Opportunities

Eliminate render-blocking resources — Potential savings of 1,390 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Scatboi.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://scatboi.com/common/style.css?1590774025
2416
180
https://scatboi.com/common/style_sb.css?1612462834
927
480
https://scatboi.com/common/style_flags.css?1356122406
1995
480
https://scatboi.com/common/javascript/greybox/gb_styles.css?1332768891
1028
480
https://scatboi.com/common/functions.js?1589229873
1053
480
https://scatboi.com/common/javascript/greybox/AJS.js?1332768890
4078
480
https://scatboi.com/common/javascript/greybox/AJS_fx.js?1332768891
1525
180
https://scatboi.com/common/javascript/greybox/gb_scripts.js?1332768891
3688
180
Reduce initial server response time — Root document took 2,220 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://scatboi.com/
2221.608

Diagnostics

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://scatboi.com/_scatboi/images/home.jpg
https://scatboi.com/_scatboi/images/logo.gif
https://scatboi.com/common/images/safeadlt.gif
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of scatboi.com on mobile screens.
68

Accessibility

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

Navigation

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

ARIA

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

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
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.
`<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 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"]`
Scatboi.com 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

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that scatboi.com 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.
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.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

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 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.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 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://scatboi.com/
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://scatboi.com/_scatboi/images/home.jpg
153 x 240
153 x 240
306 x 480
https://scatboi.com/_scatboi/images/logo.gif
200 x 40
200 x 40
400 x 80

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Audits

Registers an `unload` listener
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.
Source
69

SEO

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

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.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of scatboi.com on mobile screens.
Document doesn't use 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 not sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Crawling and Indexing

robots.txt is not 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.
17

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 scatboi.com. 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.

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
Content is not 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.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of scatboi.com on mobile screens.
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: 89.185.228.31
Continent: Europe
Country: Czechia
Czechia Flag
Region:
City:
Longitude: 14.4112
Latitude: 50.0848
Currencies: CZK
Languages: Czech
Slovak

Web Hosting Provider

Registration

Domain Registrant

Private Registration: No
Name: Identity Protection Service
Organization: Identity Protect Limited
Country: GB
City: Hayes
State: Middlesex
Post Code: UB3 9TR
Email: d04ad7c9-4646-40cb-9680-a8a2d59f879e@identity-protect.org
Phone: +44.1483307527
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
MESH DIGITAL LIMITED 92.204.80.8
Security

Visitor Safety

Mature Content: Yes
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness: 62/100
WOT Child Safety: 10/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: scatboi.com
Issued By: R3
Valid From: 4th October, 2021
Valid To: 2nd January, 2022
Subject: CN = scatboi.com
Hash: 18aa475c
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x048A30C2810ABC05A791093AFEE4D04B791A
Serial Number (Hex): 048A30C2810ABC05A791093AFEE4D04B791A
Valid From: 4th October, 2024
Valid To: 2nd January, 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 : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
Timestamp : Oct 4 23:33:14.897 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:EE:3D:27:29:74:37:91:29:F7:03:FE:
71:33:72:6C:A3:BC:60:78:11:4D:EA:6C:F7:E9:E4:E4:
9A:20:00:8B:5D:02:21:00:98:F6:88:AE:B6:1E:ED:D4:
C9:1D:3B:CD:A2:07:CA:B4:7F:03:14:81:ED:7C:F2:4C:
13:A8:22:61:14:3A:5F:E4
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
Timestamp : Oct 4 23:33:15.121 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:7D:15:F5:E6:B4:62:9F:5E:6B:DD:A4:71:
FF:07:3C:E2:8A:0C:24:92:3A:72:7F:74:EC:77:DA:1E:
02:BD:BB:11:02:20:18:D9:EE:E1:4F:27:73:4E:C6:25:
1A:8A:3A:7F:F7:38:D6:73:0F:FE:96:BF:89:47:74:54:
6D:64:37:EC:A9:23
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.scatboi.com
DNS:scatboi.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
scatboi.com. 89.185.228.31 IN 21600

NS Records

Host Nameserver Class TTL
scatboi.com. ns2.exmasters.com. IN 21600
scatboi.com. ns1.exmasters.com. IN 21600

MX Records

Priority Host Server Class TTL
10 scatboi.com. mail.scatboi.com. IN 21600

SOA Records

Domain Name Primary NS Responsible Email TTL
scatboi.com. ns1.exmasters.com. hostmaster.exmasters.com. 3600

TXT Records

Host Value Class TTL
scatboi.com. v=spf1 IN 21600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 10th October, 2021
Server: Apache/2.2.22 (Unix)
Expires: 19th November, 1981
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Content-Type: text/html; charset=utf-8
X-Powered-By: PHP/5.2.17
Set-Cookie: *
Pragma: no-cache
Vary: Accept-Encoding

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: ns1.exmasters.com
ns2.exmasters.com
Full Whois: Rate limit exceeded. Try again after: 24h0m0s

Nameservers

Name IP Address
ns1.exmasters.com 81.31.38.10
ns2.exmasters.com 89.185.228.193
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address