Yandex.ru Site Title

Ой!

Yandex.ru Test Results

Yandex.ru Mobile Performance: 30/100
Quick overview:
Time to Interactive
28.8 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.
Max Potential First Input Delay
2,520 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.
Properly size images
Potential savings of 969 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Avoid an excessive DOM size
1,817 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.
Serve images in next-gen formats
Potential savings of 1,162 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.
Avoid multiple page redirects
Potential savings of 3,090 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Minimize main-thread work
19.1 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
Largest Contentful Paint element
11,210 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce JavaScript execution time
11.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Reduce unused JavaScript
Potential savings of 1,124 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.
Reduce the impact of third-party code
Third-party code blocked the main thread for 6,160 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 how to minimize third-party impact.
Reduce unused CSS
Potential savings of 429 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Efficiently encode images
Potential savings of 266 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode 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.
Serve static assets with an efficient cache policy
36 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 19 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Preload Largest Contentful Paint image
Potential savings of -7,350 ms
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.
Avoid enormous network payloads
Total size was 4,944 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Defer offscreen images
Potential savings of 219 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.

Yandex.ru Mobile SEO: 92/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 about the `alt` attribute.

Yandex.ru Mobile Best Practices: 59/100
Quick overview:
General
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Uses deprecated APIs
2 warnings found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
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
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 about HTTPS.
Yandex.ru Mobile Accessibility: 59/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 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Some elements have a `[tabindex]` value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.
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 about proper list structure.
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.
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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`[aria-*]` attributes do not have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
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.
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.yandex.com
www.yandex.net
www.yandex.org
www.yandex.info
www.yandex.biz
www.yandex.us
www.yandex.mobi
www.andex.ru
www.yandex.ru
www.tandex.ru
www.ytandex.ru
www.tyandex.ru
www.gandex.ru
www.ygandex.ru
www.gyandex.ru
www.handex.ru
www.yhandex.ru
www.hyandex.ru
www.uandex.ru
www.yuandex.ru
www.uyandex.ru
www.yndex.ru
www.yqndex.ru
www.yaqndex.ru
www.yqandex.ru
www.ywndex.ru
www.yawndex.ru
www.ywandex.ru
www.ysndex.ru
www.yasndex.ru
www.ysandex.ru
www.yzndex.ru
www.yazndex.ru
www.yzandex.ru
www.yadex.ru
www.yabdex.ru
www.yanbdex.ru
www.yabndex.ru
www.yahdex.ru
www.yanhdex.ru
www.yahndex.ru
www.yajdex.ru
www.yanjdex.ru
www.yajndex.ru
www.yamdex.ru
www.yanmdex.ru
www.yamndex.ru
www.yanex.ru
www.yanxex.ru
www.yandxex.ru
www.yanxdex.ru
www.yansdex.ru
www.yaneex.ru
www.yandeex.ru
www.yanedex.ru
www.yanrex.ru
www.yandrex.ru
www.yanrdex.ru
www.yanfex.ru
www.yandfex.ru
www.yanfdex.ru
www.yancex.ru
www.yandcex.ru
www.yancdex.ru
www.yandx.ru
www.yandwx.ru
www.yandewx.ru
www.yandwex.ru
www.yandsx.ru
www.yandesx.ru
www.yanddx.ru
www.yandedx.ru
www.yanddex.ru
www.yandrx.ru
www.yanderx.ru
www.yande.ru
www.yandez.ru
www.yandexz.ru
www.yandezx.ru
www.yandes.ru
www.yandexs.ru
www.yanded.ru
www.yandexd.ru
www.yandec.ru
www.yandexc.ru
www.yandecx.ru
Last Tested: