Yo54.com Test Results

Yo54.com Mobile Performance: 93/100
Quick overview:
Max Potential First Input Delay
400 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.
Serve images in next-gen formats
Potential savings of 79 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.
Minimize main-thread work
2.9 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
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Eliminate render-blocking resources
Potential savings of 480 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.
Efficiently encode images
Potential savings of 13 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Avoid an excessive DOM size
1,452 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.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Properly size images
Potential savings of 41 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Serve static assets with an efficient cache policy
38 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
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().

Yo54.com Mobile SEO: 83/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Yo54.com Mobile Best Practices: 48/100
Quick overview:
General
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
User Experience
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 about legible font sizes. Text is illegible because there's no viewport meta tag optimized for mobile screens.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Trust and Safety
Does not use HTTPS
41 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.
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`
Yo54.com Mobile Accessibility: 35/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.
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.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
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.
Links rely on color to be distinguishable.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Similar sites
Similar tests
www.yo54.com
www.yo54.net
www.yo54.org
www.yo54.info
www.yo54.biz
www.yo54.us
www.yo54.mobi
www.o54.com
www.yo54.com
www.to54.com
www.yto54.com
www.tyo54.com
www.go54.com
www.ygo54.com
www.gyo54.com
www.ho54.com
www.yho54.com
www.hyo54.com
www.uo54.com
www.yuo54.com
www.uyo54.com
www.y54.com
www.yi54.com
www.yoi54.com
www.yio54.com
www.yk54.com
www.yok54.com
www.yko54.com
www.yl54.com
www.yol54.com
www.ylo54.com
www.yp54.com
www.yop54.com
www.ypo54.com
www.yo4.com
www.yo5.com
www.yo54.con
Last Tested: