Elo.health Site Title
Elo Health
Elo.health Meta Description
Elo - Nutrition with precision
Elo.health Test Results
Elo.health Mobile Performance: 31/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Serve images in next-gen formats. Potential savings of 383 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Avoid multiple page redirects. Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Remove unused JavaScript. Potential savings of 106 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Efficiently encode images. Potential savings of 88 KiB
Optimized images load faster and consume less cellular data. Learn more.
Avoid serving legacy JavaScript to modern browsers. Potential savings of 25 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 More
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
Minimize main-thread work
5.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
3.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid chaining critical requests
2 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Keep request counts low and transfer sizes small
20 requests • 1,211 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid long main-thread tasks
12 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Elo.health Mobile SEO: 92/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
9 links found
Descriptive link text helps search engines understand your content. Learn more.
Elo.health Mobile Best Practices: 93/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 servedover 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.
Elo.health Mobile Progressive Web App: 64/100
Quick overview:
Installable
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
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 servedover 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.
PWA Optimized
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more.
Fast and reliable
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. The start_url did respond, but not via a service worker.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
Elo.health Mobile Accessibility: 80/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.
`[aria-hidden="true"]` elements contain focusable descendents
Focusable descendents within an `aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn more.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more.
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 more.
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 more.
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 more.
Similar sites
Similar tests
www.elo.com
www.elo.net
www.elo.org
www.elo.info
www.elo.biz
www.elo.us
www.elo.mobi
www.lo.health
www.elo.health
www.wlo.health
www.ewlo.health
www.welo.health
www.slo.health
www.eslo.health
www.selo.health
www.dlo.health
www.edlo.health
www.delo.health
www.rlo.health
www.erlo.health
www.relo.health
www.eo.health
www.epo.health
www.elpo.health
www.eplo.health
www.eoo.health
www.eloo.health
www.eolo.health
www.eko.health
www.elko.health
www.eklo.health
www.el.health
www.eli.health
www.eloi.health
www.elio.health
www.elk.health
www.elok.health
www.ell.health
www.elol.health
www.ello.health
www.elp.health
www.elop.health
www.elo.net
www.elo.org
www.elo.info
www.elo.biz
www.elo.us
www.elo.mobi
www.lo.health
www.elo.health
www.wlo.health
www.ewlo.health
www.welo.health
www.slo.health
www.eslo.health
www.selo.health
www.dlo.health
www.edlo.health
www.delo.health
www.rlo.health
www.erlo.health
www.relo.health
www.eo.health
www.epo.health
www.elpo.health
www.eplo.health
www.eoo.health
www.eloo.health
www.eolo.health
www.eko.health
www.elko.health
www.eklo.health
www.el.health
www.eli.health
www.eloi.health
www.elio.health
www.elk.health
www.elok.health
www.ell.health
www.elol.health
www.ello.health
www.elp.health
www.elop.health