Ozon.ru Test Results

Ozon.ru Mobile Performance: 17/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 313 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Avoid multiple page redirects. Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Eliminate render-blocking resources. Potential savings of 1,110 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.
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 960 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.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
Minimize main-thread work
10.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
6.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Serve static assets with an efficient cache policy
16 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoid an excessive DOM size
905 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Keep request counts low and transfer sizes small
181 requests • 1,681 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid chaining critical requests
16 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.
User Timing marks and measures
1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. 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
Avoid large layout shifts
1 element found
These DOM elements contribute most to the CLS of the page.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More

Ozon.ru Mobile SEO: 93/100
Quick overview:
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.

Ozon.ru Mobile Best Practices: 69/100
Quick overview:
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
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.
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
Ozon.ru Mobile Progressive Web App: 29/100
Quick overview:
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.
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: Manifest does not have a PNG icon of at least 512px, Manifest does not have `background_color`, Manifest does not have `theme_color`.
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: Manifest does not have `theme_color`, No `<meta name="theme-color">` tag found.
Installable
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: Manifest does not have a PNG icon of at least 144px, Manifest icon failed to be fetched.
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.
Fast and reliable
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.
Page load is not fast enough on mobile networks
Interactive at 16.8 s
A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.
`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.
Ozon.ru Mobile Accessibility: 72/100
Quick overview:
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.
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.
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.
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.
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.ozon.com
www.ozon.net
www.ozon.org
www.ozon.info
www.ozon.biz
www.ozon.us
www.ozon.mobi
www.zon.ru
www.ozon.ru
www.izon.ru
www.oizon.ru
www.iozon.ru
www.kzon.ru
www.okzon.ru
www.kozon.ru
www.lzon.ru
www.olzon.ru
www.lozon.ru
www.pzon.ru
www.opzon.ru
www.pozon.ru
www.oon.ru
www.oxon.ru
www.ozxon.ru
www.oxzon.ru
www.oson.ru
www.ozson.ru
www.oszon.ru
www.oaon.ru
www.ozaon.ru
www.oazon.ru
www.ozn.ru
www.ozin.ru
www.ozoin.ru
www.ozion.ru
www.ozkn.ru
www.ozokn.ru
www.ozkon.ru
www.ozln.ru
www.ozoln.ru
www.ozlon.ru
www.ozpn.ru
www.ozopn.ru
www.ozpon.ru
www.ozo.ru
www.ozob.ru
www.ozonb.ru
www.ozobn.ru
www.ozoh.ru
www.ozonh.ru
www.ozohn.ru
www.ozoj.ru
www.ozonj.ru
www.ozojn.ru
www.ozom.ru
www.ozonm.ru
www.ozomn.ru
Last Tested:

This website uses cookies to ensure you get the best experience on our website. Learn more. Got it.