Eeo.one Test Results
Eeo.one Mobile Performance: 71/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Eliminate render-blocking resources
Est savings of 1,030 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.
Avoid multiple page redirects
Est savings of 2,250 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce unused CSS
Est savings of 191 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.
Largest Contentful Paint element
4,050 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Serve static assets with an efficient cache policy
8 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Enable text compression
Est savings of 8 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Document request latency
Est savings of 6 KiB
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Render blocking requests
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Time to Interactive
4.1 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.
Eeo.one Mobile SEO: 50/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Page is blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Eeo.one Mobile Best Practices: 79/100
Quick overview:
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.
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration. Document contains a `doctype` that triggers `limited-quirks-mode`
Eeo.one Mobile Accessibility: 87/100
Quick overview:
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Navigation
These are opportunities to improve keyboard navigation in your application.
Some elements have a `[tabindex]` value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.
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.eeo.com
www.eeo.net
www.eeo.org
www.eeo.info
www.eeo.biz
www.eeo.us
www.eeo.mobi
www.eo.one
www.eeo.one
www.weo.one
www.eweo.one
www.weeo.one
www.seo.one
www.eseo.one
www.seeo.one
www.deo.one
www.edeo.one
www.deeo.one
www.reo.one
www.ereo.one
www.reeo.one
www.ewo.one
www.eewo.one
www.eso.one
www.eeso.one
www.edo.one
www.eedo.one
www.ero.one
www.eero.one
www.ee.one
www.eei.one
www.eeoi.one
www.eeio.one
www.eek.one
www.eeok.one
www.eeko.one
www.eel.one
www.eeol.one
www.eelo.one
www.eep.one
www.eeop.one
www.eepo.one
www.eeo.net
www.eeo.org
www.eeo.info
www.eeo.biz
www.eeo.us
www.eeo.mobi
www.eo.one
www.eeo.one
www.weo.one
www.eweo.one
www.weeo.one
www.seo.one
www.eseo.one
www.seeo.one
www.deo.one
www.edeo.one
www.deeo.one
www.reo.one
www.ereo.one
www.reeo.one
www.ewo.one
www.eewo.one
www.eso.one
www.eeso.one
www.edo.one
www.eedo.one
www.ero.one
www.eero.one
www.ee.one
www.eei.one
www.eeoi.one
www.eeio.one
www.eek.one
www.eeok.one
www.eeko.one
www.eel.one
www.eeol.one
www.eelo.one
www.eep.one
www.eeop.one
www.eepo.one