Exo.ru Test Results

Exo.ru Mobile Performance: 18/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Preload key requests. Potential savings of 6,630 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.
Remove unused JavaScript. Potential savings of 554 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Avoid multiple page redirects. Potential savings of 1,440 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Reduce initial server response time. Root document took 910 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Eliminate render-blocking resources. Potential savings of 460 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.
Defer offscreen images. Potential savings of 31 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Serve images in next-gen formats. Potential savings of 23 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.
Remove unused CSS. Potential savings of 44 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.
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.
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.
Reduce the impact of third-party code
Third-party code blocked the main thread for 3,930 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.
Minimize main-thread work
19.8 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
13.7 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
21 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoid an excessive DOM size
1,574 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. 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
173 requests • 1,827 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid large layout shifts
1 element found
These DOM elements contribute most to the CLS of the page.

Exo.ru Mobile SEO: 92/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.
Tap targets are not sized appropriately
91% appropriately sized tap targets
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.
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.

Exo.ru Mobile Best Practices: 71/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
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more.
Registers an `unload` listener
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the `pagehide` or `visibilitychange` events instead. Learn More
Trust and Safety
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.
Does not use HTTPS
5 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 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.
Exo.ru Mobile Progressive Web App: 54/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.
Does not redirect HTTP traffic to HTTPS
If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Does not provide fallback content when JavaScript is not available
Your app should display some content when JavaScript is disabled, even if it's just a warning to the user that JavaScript is required to use the app. Learn more. The page body should render some content if its scripts are not available.
Fast and reliable
Page load is not fast enough on mobile networks
Interactive at 19.7 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.
Installable
Does not use HTTPS
5 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 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.
Exo.ru Mobile Accessibility: 70/100
Quick overview:
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
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.
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.
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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
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.
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.
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.
Similar tests
www.exo.com
www.exo.net
www.exo.org
www.exo.info
www.exo.biz
www.exo.us
www.exo.mobi
www.xo.ru
www.exo.ru
www.wxo.ru
www.ewxo.ru
www.wexo.ru
www.sxo.ru
www.esxo.ru
www.dxo.ru
www.edxo.ru
www.dexo.ru
www.rxo.ru
www.erxo.ru
www.rexo.ru
www.eo.ru
www.ezo.ru
www.exzo.ru
www.ezxo.ru
www.eso.ru
www.exso.ru
www.edo.ru
www.exdo.ru
www.eco.ru
www.exco.ru
www.ecxo.ru
www.ex.ru
www.exi.ru
www.exoi.ru
www.exio.ru
www.exk.ru
www.exok.ru
www.exko.ru
www.exl.ru
www.exol.ru
www.exlo.ru
www.exp.ru
www.exop.ru
www.expo.ru
Last Tested: