Awful.systems Site Title
awful.systems - the jank is a feature
Awful.systems Meta Description
Lemmy
Awful.systems Test Results
Awful.systems Mobile Performance: 36/100
Quick overview:
Max Potential First Input Delay
2,470 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
First Meaningful Paint
11.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Time to Interactive
22.3 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce unused JavaScript
Potential savings of 867 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Avoid an excessive DOM size
2,628 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Reduce unused CSS
Potential savings of 325 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Minify CSS
Potential savings of 44 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Reduce JavaScript execution time
2.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Enable text compression
Potential savings of 2,737 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Minimize main-thread work
3.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Avoid serving legacy JavaScript to modern browsers
Potential savings of 34 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Eliminate render-blocking resources
Potential savings of 1,700 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Largest Contentful Paint element
22,260 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid enormous network payloads
Total size was 3,783 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Serve static assets with an efficient cache policy
11 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Awful.systems Mobile SEO: 100/100
Quick overview:
Awful.systems Mobile Best Practices: 83/100
Quick overview:
General
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Awful.systems Mobile Accessibility: 93/100
Quick overview:
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Similar sites
Similar tests
www.awful.com
www.awful.net
www.awful.org
www.awful.info
www.awful.biz
www.awful.us
www.awful.mobi
www.wful.systems
www.awful.systems
www.qwful.systems
www.aqwful.systems
www.qawful.systems
www.wwful.systems
www.awwful.systems
www.wawful.systems
www.swful.systems
www.aswful.systems
www.sawful.systems
www.zwful.systems
www.azwful.systems
www.zawful.systems
www.aful.systems
www.aqful.systems
www.awqful.systems
www.aaful.systems
www.awaful.systems
www.aawful.systems
www.asful.systems
www.awsful.systems
www.aeful.systems
www.aweful.systems
www.aewful.systems
www.awul.systems
www.awcul.systems
www.awfcul.systems
www.awcful.systems
www.awdul.systems
www.awfdul.systems
www.awdful.systems
www.awrul.systems
www.awfrul.systems
www.awrful.systems
www.awtul.systems
www.awftul.systems
www.awtful.systems
www.awgul.systems
www.awfgul.systems
www.awgful.systems
www.awvul.systems
www.awfvul.systems
www.awvful.systems
www.awfl.systems
www.awfyl.systems
www.awfuyl.systems
www.awfyul.systems
www.awfhl.systems
www.awfuhl.systems
www.awfhul.systems
www.awfjl.systems
www.awfujl.systems
www.awfjul.systems
www.awfil.systems
www.awfuil.systems
www.awfiul.systems
www.awfu.systems
www.awfup.systems
www.awfulp.systems
www.awfupl.systems
www.awfuo.systems
www.awfulo.systems
www.awfuol.systems
www.awfuk.systems
www.awfulk.systems
www.awfukl.systems
www.awful.net
www.awful.org
www.awful.info
www.awful.biz
www.awful.us
www.awful.mobi
www.wful.systems
www.awful.systems
www.qwful.systems
www.aqwful.systems
www.qawful.systems
www.wwful.systems
www.awwful.systems
www.wawful.systems
www.swful.systems
www.aswful.systems
www.sawful.systems
www.zwful.systems
www.azwful.systems
www.zawful.systems
www.aful.systems
www.aqful.systems
www.awqful.systems
www.aaful.systems
www.awaful.systems
www.aawful.systems
www.asful.systems
www.awsful.systems
www.aeful.systems
www.aweful.systems
www.aewful.systems
www.awul.systems
www.awcul.systems
www.awfcul.systems
www.awcful.systems
www.awdul.systems
www.awfdul.systems
www.awdful.systems
www.awrul.systems
www.awfrul.systems
www.awrful.systems
www.awtul.systems
www.awftul.systems
www.awtful.systems
www.awgul.systems
www.awfgul.systems
www.awgful.systems
www.awvul.systems
www.awfvul.systems
www.awvful.systems
www.awfl.systems
www.awfyl.systems
www.awfuyl.systems
www.awfyul.systems
www.awfhl.systems
www.awfuhl.systems
www.awfhul.systems
www.awfjl.systems
www.awfujl.systems
www.awfjul.systems
www.awfil.systems
www.awfuil.systems
www.awfiul.systems
www.awfu.systems
www.awfup.systems
www.awfulp.systems
www.awfupl.systems
www.awfuo.systems
www.awfulo.systems
www.awfuol.systems
www.awfuk.systems
www.awfulk.systems
www.awfukl.systems