Decodex.io Test Results

Decodex.io Mobile Performance: 82/100
Quick overview:
Time to Interactive
4.0 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.
Max Potential First Input Delay
130 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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Largest Contentful Paint element
3,820 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce unused CSS
Potential savings of 20 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.
Avoid an excessive DOM size
867 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 JavaScript
Potential savings of 43 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.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more about adopting passive event listeners.
Serve static assets with an efficient cache policy
1 resource found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Eliminate render-blocking resources
Potential savings of 0 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.

Decodex.io Mobile SEO: 100/100
Quick overview:

Decodex.io Mobile Best Practices: 76/100
Quick overview:
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Trust and Safety
Does not use HTTPS
2 insecure requests 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.
Does not redirect HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Decodex.io Mobile Accessibility: 83/100
Quick overview:
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
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.
Similar tests
www.decodex.com
www.decodex.net
www.decodex.org
www.decodex.info
www.decodex.biz
www.decodex.us
www.decodex.mobi
www.ecodex.io
www.decodex.io
www.xecodex.io
www.dxecodex.io
www.xdecodex.io
www.secodex.io
www.dsecodex.io
www.sdecodex.io
www.eecodex.io
www.deecodex.io
www.edecodex.io
www.recodex.io
www.drecodex.io
www.rdecodex.io
www.fecodex.io
www.dfecodex.io
www.fdecodex.io
www.cecodex.io
www.dcecodex.io
www.cdecodex.io
www.dcodex.io
www.dwcodex.io
www.dewcodex.io
www.dwecodex.io
www.dscodex.io
www.descodex.io
www.ddcodex.io
www.dedcodex.io
www.ddecodex.io
www.drcodex.io
www.dercodex.io
www.deodex.io
www.dexodex.io
www.decxodex.io
www.dexcodex.io
www.dedodex.io
www.decdodex.io
www.defodex.io
www.decfodex.io
www.defcodex.io
www.devodex.io
www.decvodex.io
www.devcodex.io
www.decdex.io
www.decidex.io
www.decoidex.io
www.deciodex.io
www.deckdex.io
www.decokdex.io
www.deckodex.io
www.decldex.io
www.decoldex.io
www.declodex.io
www.decpdex.io
www.decopdex.io
www.decpodex.io
www.decoex.io
www.decoxex.io
www.decodxex.io
www.decoxdex.io
www.decosdex.io
www.decoeex.io
www.decodeex.io
www.decoedex.io
www.decorex.io
www.decodrex.io
www.decordex.io
www.decofex.io
www.decodfex.io
www.decofdex.io
www.decocex.io
www.decodcex.io
www.decocdex.io
www.decodx.io
www.decodwx.io
www.decodewx.io
www.decodwex.io
www.decodsx.io
www.decodesx.io
www.decoddx.io
www.decodedx.io
www.decoddex.io
www.decodrx.io
www.decoderx.io
www.decode.io
www.decodez.io
www.decodexz.io
www.decodezx.io
www.decodes.io
www.decodexs.io
www.decoded.io
www.decodexd.io
www.decodec.io
www.decodexc.io
www.decodecx.io
Last Tested: