Test Results Mobile Performance: 67/100
Quick overview:
More information about the performance of your application. These numbers don't directly affect the Performance score.
Serve images in next-gen formats
Potential savings of 927 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Reduce unused JavaScript
Potential savings of 45 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.
Largest Contentful Paint element
18,290 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid multiple page redirects
Potential savings of 2,510 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Use video formats for animated content
Potential savings of 1,207 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formats
Properly size images
Potential savings of 1,611 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
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.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn how to avoid document.write().
Avoid enormous network payloads
Total size was 5,536 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Minimize main-thread work
3.6 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
Minify CSS
Potential savings of 7 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.
Serve static assets with an efficient cache policy
30 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
First Meaningful Paint
3.2 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
3.2 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. Mobile SEO: 66/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. Mobile Best Practices: 76/100
Quick overview:
Trust and Safety
Does not use HTTPS
17 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.
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
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 must contain a doctype Mobile Accessibility: 79/100
Quick overview:
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 about heading order.
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.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Similar tests
Last Tested: