Rg.ru Российская газета
Российская газета - издание Правительства Российской Федерации, официальный публикатор документов
rg.ru Desktop Performance
73/100
These metrics represent real-world Chrome users experience viewing rg.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
Largest Contentful Paint
Cumulative Layout Shift
First Input Delay
First Contentful Paint
Metrics
Speed Index29/100 2.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Time to Interactive52/100 4.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time77/100 210 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Largest Contentful Paint88/100 1.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
First Contentful Paint95/100 0.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Cumulative Layout Shift100/100 0.015
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (17)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused JavaScript
Potential savings of 526 KiB
930 ms
Reduce initial server response time
Root document took 1,450 ms
848 ms
Preload key requests
Potential savings of 370 ms
370 ms
Eliminate render-blocking resources
Potential savings of 330 ms
334 ms
Defer offscreen images
Potential savings of 159 KiB
100 ms
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
Does not use passive listeners to improve scrolling performance
Avoid `document.write()`
Serve static assets with an efficient cache policy
34 resources found
Avoid an excessive DOM size
1,787 elements
Minimize main-thread work
3.1 s
JavaScript execution time
1.3 s
Keep request counts low and transfer sizes small
183 requests • 2,277 KiB
Avoid long main-thread tasks
9 long tasks found
Largest Contentful Paint element
1 element found
Avoid chaining critical requests
11 chains found
Avoid large layout shifts
5 elements found
Passed Audits (12)
Minimize third-party usage
Third-party code blocked the main thread for 200 ms
Use video formats for animated content
Preconnect to required origins
Avoids enormous network payloads
Total size was 2,277 KiB
Minify CSS
Efficiently encode images
Potential savings of 11 KiB
Serve images in next-gen formats
Potential savings of 30 KiB
Remove unused CSS
Potential savings of 127 KiB
Avoid multiple page redirects
Potential savings of 190 ms
Properly size images
Potential savings of 42 KiB
Enable text compression
Potential savings of 12 KiB
Minify JavaScript
rg.ru Desktop SEO
92/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 (1)
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
Passed Audits (11)
Document has a valid `hreflang`
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Document has a `<title>` element
Document has a meta description
Links are crawlable
Document avoids plugins
Links have descriptive text
Page isn’t blocked from indexing
Document has a valid `rel=canonical`
robots.txt is valid
Page has successful HTTP status code
rg.ru Desktop Best Practices
62/100
These checks highlight opportunities to improve the overall code health of rg.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 (5)
Trust and Safety
Links to cross-origin destinations are unsafe
Does not use HTTPS
1 insecure request found
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
General
Browser errors were logged to the console
User Experience
Serves images with low resolution
Passed Audits (9)
Detected JavaScript libraries
Avoids requesting the geolocation permission on page load
Page has the HTML doctype
Avoids deprecated APIs
Avoids requesting the notification permission on page load
Properly defines charset
Allows users to paste into password fields
Displays images with correct aspect ratio
Avoids Application Cache
rg.ru Desktop Progressive Web App
41/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 (5)
PWA Optimized
Manifest doesn't have a maskable icon
Fast and reliable
Current page does not respond with a 200 when offline
`start_url` does not respond with a 200 when offline
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 19.5 s
Installable
Does not use HTTPS
1 insecure request found
Passed Audits (8)
Provides a valid `apple-touch-icon`
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Web app manifest meets the installability requirements
Redirects HTTP traffic to HTTPS
Registers a service worker that controls page and `start_url`
Contains some content when JavaScript is not available
Sets a theme color for the address bar.
Configured for a custom splash screen
rg.ru Desktop Accessibility
78/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 (7)
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.
Image elements do not have `[alt]` attributes
`<frame>` or `<iframe>` elements do not have a title
Buttons do not have an accessible name
Links do not have a discernible name
Tables and lists
These are opportunities to 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>`).
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Passed Audits (18)
Document has a `<title>` element
`[aria-hidden="true"]` elements do not contain focusable descendents
`[aria-*]` attributes match their roles
`<html>` element has a `[lang]` attribute
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
`[aria-*]` attributes are valid and not misspelled
ARIA IDs are unique
`[role]` values are valid
`[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.
`[role]`s are contained by their required parent element
`[aria-hidden="true"]` is not present on the document `<body>`
No element has a `[tabindex]` value greater than 0
`<html>` element has a valid value for its `[lang]` attribute
The page contains a heading, skip link, or landmark region
`[id]` attributes on active, focusable elements are unique
`[aria-*]` attributes have valid values
Desktop Speed
44/100
These checks analyze the performance of rg.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 (4)
Enable compression
Leverage browser caching
Optimize images
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Passed Audits (6)
Avoid landing page redirects
Reduce server response time
Minify CSS
Minify HTML
Minify JavaScript
Prioritize visible content
www.rg.com
www.rg.net
www.rg.org
www.rg.info
www.rg.biz
www.rg.us
www.rg.mobi
www.g.ru
www.rg.ru
www.eg.ru
www.reg.ru
www.erg.ru
www.dg.ru
www.rdg.ru
www.drg.ru
www.fg.ru
www.rfg.ru
www.frg.ru
www.tg.ru
www.rtg.ru
www.trg.ru
www.r.ru
www.rf.ru
www.rgf.ru
www.rv.ru
www.rgv.ru
www.rvg.ru
www.rt.ru
www.rgt.ru
www.rb.ru
www.rgb.ru
www.rbg.ru
www.ry.ru
www.rgy.ru
www.ryg.ru
www.rh.ru
www.rgh.ru
www.rhg.ru
www.rg.net
www.rg.org
www.rg.info
www.rg.biz
www.rg.us
www.rg.mobi
www.g.ru
www.rg.ru
www.eg.ru
www.reg.ru
www.erg.ru
www.dg.ru
www.rdg.ru
www.drg.ru
www.fg.ru
www.rfg.ru
www.frg.ru
www.tg.ru
www.rtg.ru
www.trg.ru
www.r.ru
www.rf.ru
www.rgf.ru
www.rv.ru
www.rgv.ru
www.rvg.ru
www.rt.ru
www.rgt.ru
www.rb.ru
www.rgb.ru
www.rbg.ru
www.ry.ru
www.rgy.ru
www.ryg.ru
www.rh.ru
www.rgh.ru
www.rhg.ru