Utters.io Test Results

Utters.io Mobile Performance: 26/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused JavaScript. Potential savings of 479 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Remove unused CSS. Potential savings of 51 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Eliminate render-blocking resources. Potential savings of 330 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Serve images in next-gen formats. Potential savings of 61 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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce the impact of third-party code
Third-party code blocked the main thread for 3,920 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Some third-party resources can be lazy loaded with a facade
1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more.
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.
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.
Minimize main-thread work
10.9 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
7.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 enormous network payloads
Total size was 4,934 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Serve static assets with an efficient cache policy
13 resources found
A long cache lifetime can speed up repeat visits to your page. 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
20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Keep request counts low and transfer sizes small
79 requests • 4,934 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid non-composited animations
3 animated elements found
Animations which are not composited can be janky and increase CLS. Learn more
User Timing marks and measures
21 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
Avoid chaining critical requests
4 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.

Utters.io Mobile SEO: 67/100
Quick overview:
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Document doesn't use legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more. Text is illegible because there's no viewport meta tag optimized for mobile screens.
Tap targets are not sized appropriately
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more. Tap targets are too small because there's no viewport meta tag optimized for mobile screens
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more. No `<meta name="viewport">` tag found
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
22 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more.

Utters.io Mobile Best Practices: 87/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.
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
Utters.io Mobile Progressive Web App: 17/100
Quick overview:
PWA Optimized
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more. No `<meta name="viewport">` tag found
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Content is not sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more. The viewport size of 980px does not match the window size of 360px.
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. No manifest was fetched
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.
Installable
Web app manifest or service worker do not meet the installability requirements
1 reason
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. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.
Utters.io Mobile Accessibility: 91/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.
Similar tests
www.utters.com
www.utters.net
www.utters.org
www.utters.info
www.utters.biz
www.utters.us
www.utters.mobi
www.tters.io
www.utters.io
www.ytters.io
www.uytters.io
www.yutters.io
www.htters.io
www.uhtters.io
www.hutters.io
www.jtters.io
www.ujtters.io
www.jutters.io
www.itters.io
www.uitters.io
www.iutters.io
www.uters.io
www.urters.io
www.utrters.io
www.urtters.io
www.ufters.io
www.utfters.io
www.uftters.io
www.ugters.io
www.utgters.io
www.ugtters.io
www.uyters.io
www.utyters.io
www.utrers.io
www.uttrers.io
www.utfers.io
www.uttfers.io
www.utgers.io
www.uttgers.io
www.utyers.io
www.uttyers.io
www.uttrs.io
www.uttwrs.io
www.uttewrs.io
www.uttwers.io
www.uttsrs.io
www.uttesrs.io
www.uttsers.io
www.uttdrs.io
www.uttedrs.io
www.uttders.io
www.uttrrs.io
www.utterrs.io
www.uttes.io
www.uttees.io
www.utteres.io
www.utteers.io
www.utteds.io
www.utterds.io
www.uttefs.io
www.utterfs.io
www.uttefrs.io
www.uttets.io
www.utterts.io
www.uttetrs.io
www.utter.io
www.utterw.io
www.uttersw.io
www.utterws.io
www.uttere.io
www.utterse.io
www.utterd.io
www.uttersd.io
www.utterz.io
www.uttersz.io
www.utterzs.io
www.utterx.io
www.uttersx.io
www.utterxs.io
www.uttera.io
www.uttersa.io
www.utteras.io
Last Tested: