Mail.ru Mail.ru: почта, поиск в интернете, новости, игры
Почта Mail.ru — крупнейшая бесплатная почта, быстрый и удобный интерфейс, неограниченный объем ящика, надежная защита от спама и вирусов, мобильная ве...
mail.ru Desktop Performance
60/100
These metrics represent real-world Chrome users experience viewing mail.ru web page. Reports are focused on loading performance and other critical factors that most affect user experience. Follow our guide to track, optimize, and improve the quality of your web pages.
User Loading Experience
First Input Delay
Largest Contentful Paint
Cumulative Layout Shift
First Contentful Paint
Metrics
Speed Index4/100 4.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Time to Interactive21/100 6.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Largest Contentful Paint52/100 2.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
First Contentful Paint96/100 0.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Total Blocking Time96/100 110 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Cumulative Layout Shift99/100 0.052
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (18)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused JavaScript
Potential savings of 498 KiB
1,050 ms
Reduce initial server response time
Root document took 1,260 ms
657 ms
Enable text compression
Potential savings of 192 KiB
380 ms
Serve images in next-gen formats
Potential savings of 174 KiB
360 ms
Remove unused CSS
Potential savings of 29 KiB
70 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid `document.write()`
Does not use passive listeners to improve scrolling performance
Serve static assets with an efficient cache policy
69 resources found
Minimize main-thread work
3.8 s
Avoid enormous network payloads
Total size was 3,110 KiB
Reduce JavaScript execution time
1.8 s
Avoids an excessive DOM size
765 elements
User Timing marks and measures
16 user timings
Avoid chaining critical requests
11 chains found
Avoid long main-thread tasks
4 long tasks found
Keep request counts low and transfer sizes small
397 requests • 3,110 KiB
Largest Contentful Paint element
1 element found
Avoid large layout shifts
5 elements found
Passed Audits (12)
Eliminate render-blocking resources
Potential savings of 60 ms
Minimize third-party usage
Third-party code blocked the main thread for 20 ms
Avoid multiple page redirects
Potential savings of 190 ms
Properly size images
Potential savings of 21 KiB
Efficiently encode images
Defer offscreen images
Potential savings of 17 KiB
Minify JavaScript
Potential savings of 9 KiB
Preconnect to required origins
All text remains visible during webfont loads
Use video formats for animated content
Minify CSS
Preload key requests
mail.ru Desktop SEO
82/100
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more. Run these additional validators on your site to check additional SEO best practices.
Should Fix (2)
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
1 link found
Image elements do not have `[alt]` attributes
Passed Audits (9)
Page has successful HTTP status code
Document avoids plugins
Document has a valid `hreflang`
robots.txt is valid
Document has a meta description
Document has a `<title>` element
Page isn’t blocked from indexing
Links are crawlable
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
mail.ru Desktop Best Practices
77/100
These checks highlight opportunities to improve the overall code health of mail.ru page. Current recommendations will help to make your page fast and secure, to create a good user experience and to avoid deprecated technologies.
Should Fix (3)
General
Browser errors were logged to the console
Trust and Safety
Does not use HTTPS
1 insecure request found
Links to cross-origin destinations are unsafe
Passed Audits (11)
Avoids requesting the notification permission on page load
Avoids deprecated APIs
Detected JavaScript libraries
Properly defines charset
Displays images with correct aspect ratio
Allows users to paste into password fields
Avoids front-end JavaScript libraries with known security vulnerabilities
Avoids requesting the geolocation permission on page load
Avoids Application Cache
Serves images with appropriate resolution
Page has the HTML doctype
mail.ru Desktop Progressive Web App
22/100
These checks validate the aspects of a Progressive Web App. Learn more. These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Should Fix (9)
Fast and reliable
Current page does not respond with a 200 when offline
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 29.6 s
`start_url` does not respond with a 200 when offline
PWA Optimized
Is not configured for a custom splash screen
Manifest doesn't have a maskable icon
Does not set a theme color for the address bar.
Installable
Does not use HTTPS
1 insecure request found
Web app manifest does not meet the installability requirements
Does not register a service worker that controls page and `start_url`
Passed Audits (4)
Redirects HTTP traffic to HTTPS
Contains some content when JavaScript is not available
Provides a valid `apple-touch-icon`
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
mail.ru Desktop Accessibility
0/100
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged. These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Should Fix (6)
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.
`<frame>` or `<iframe>` elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
Image elements do not have `[alt]` attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
Some elements have a `[tabindex]` value greater than 0
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors have a sufficient contrast ratio
Passed Audits (19)
`[role]`s have all required `[aria-*]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
The page contains a heading, skip link, or landmark region
`[id]` attributes on active, focusable elements are unique
`[aria-hidden="true"]` elements do not contain focusable descendents
`[role]` values are valid
Heading elements appear in a sequentially-descending order
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`[role]`s are contained by their required parent element
Buttons have an accessible name
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
`<html>` element has a valid value for its `[lang]` attribute
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
`[aria-hidden="true"]` is not present on the document `<body>`
`<html>` element has a `[lang]` attribute
ARIA IDs are unique
Document has a `<title>` element
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Desktop Speed
80/100
These checks analyze the performance of mail.ru on desktop devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (5)
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Optimize images
Leverage browser caching
Prioritize visible content
Enable compression
Passed Audits (5)
Avoid landing page redirects
Reduce server response time
Minify CSS
Minify HTML
Minify JavaScript
www.mail.com
www.mail.net
www.mail.org
www.mail.info
www.mail.biz
www.mail.us
www.mail.mobi
www.ail.ru
www.mail.ru
www.nail.ru
www.mnail.ru
www.nmail.ru
www.jail.ru
www.mjail.ru
www.jmail.ru
www.kail.ru
www.mkail.ru
www.kmail.ru
www.mil.ru
www.mqil.ru
www.maqil.ru
www.mqail.ru
www.mwil.ru
www.mawil.ru
www.mwail.ru
www.msil.ru
www.masil.ru
www.msail.ru
www.mzil.ru
www.mazil.ru
www.mzail.ru
www.mal.ru
www.maul.ru
www.maiul.ru
www.mauil.ru
www.majl.ru
www.maijl.ru
www.majil.ru
www.makl.ru
www.maikl.ru
www.makil.ru
www.maol.ru
www.maiol.ru
www.maoil.ru
www.mai.ru
www.maip.ru
www.mailp.ru
www.maipl.ru
www.maio.ru
www.mailo.ru
www.maik.ru
www.mailk.ru
www.mail.net
www.mail.org
www.mail.info
www.mail.biz
www.mail.us
www.mail.mobi
www.ail.ru
www.mail.ru
www.nail.ru
www.mnail.ru
www.nmail.ru
www.jail.ru
www.mjail.ru
www.jmail.ru
www.kail.ru
www.mkail.ru
www.kmail.ru
www.mil.ru
www.mqil.ru
www.maqil.ru
www.mqail.ru
www.mwil.ru
www.mawil.ru
www.mwail.ru
www.msil.ru
www.masil.ru
www.msail.ru
www.mzil.ru
www.mazil.ru
www.mzail.ru
www.mal.ru
www.maul.ru
www.maiul.ru
www.mauil.ru
www.majl.ru
www.maijl.ru
www.majil.ru
www.makl.ru
www.maikl.ru
www.makil.ru
www.maol.ru
www.maiol.ru
www.maoil.ru
www.mai.ru
www.maip.ru
www.mailp.ru
www.maipl.ru
www.maio.ru
www.mailo.ru
www.maik.ru
www.mailk.ru