Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
mf.b37mrtl.ru/files/2026.04/69e5ebe885f54058780f73e8.mp4	14400.0 s	1.4 MiB
mf.b37mrtl.ru/files/2026.04/69e7a63285f54076f72f8f16.mp4	14400.0 s	671.6 KiB
mc.yandex.ru/metrika/tag.js	3600.0 s	85.4 KiB
mf.b37mrtl.ru/files/2026.04/l/69e78a5585f54076f72f8f0d.jpg	14400.0 s	61.1 KiB
/wrapper/js/common-engine.js?v=s-dc1af2de-5f10-4ef6-a4db-...	345600.0 s	152.2 KiB
cdn.jsdelivr.net/npm/@farcaster/miniapp-sdk/dist/index.min.js	604800.0 s	162.3 KiB
mf.b37mrtl.ru/files/2026.04/xs/69e75fa485f540054421eb90.jpg	14400.0 s	18.5 KiB
en.russiatoday.com/static/css/template.css/template.4aa2d5aa.css	345600.0 s	65.9 KiB
mf.b37mrtl.ru/files/2026.04/xs/69e788e32030272d9c58067f.jpg	14400.0 s	16.5 KiB
mf.b37mrtl.ru/files/2026.04/xs/69e79c542030273bb01e3018.jpg	14400.0 s	11.9 KiB
en.russiatoday.com/static/js/common.min.js?v=16464124494475130342	345600.0 s	40.1 KiB
abt.s3.yandex.net/expjs/latest/exp.js	0.0 ms	6.4 KiB
en.russiatoday.com/static/libs/jquery-1.11.2.min.js?v=2	345600.0 s	33.2 KiB
en.russiatoday.com/static/js/services.sharing.js?v=10	345600.0 s	28.9 KiB
en.russiatoday.com/static/js/services.sharing.js?v=13	345600.0 s	28.8 KiB
mf.b37mrtl.ru/files/2026.04/xs/69e7b4e820302768c023a8df.jpg	14400.0 s	5.1 KiB
mf.b37mrtl.ru/files/2026.04/69e7a63285f54076f72f8f16.mp4	14400.0 s	4.1 KiB
cdn.dmtgvn.com/wrapper/js/manager.js?pid=880ca144-da2d-42d5-918a-bc6aa4fbd9c3	600.0 s	1.6 KiB
en.russiatoday.com/static/libs/qrcode.min.js?v=2	345600.0 s	6.9 KiB
en.russiatoday.com/static/js/libs/lazyall.js	345600.0 s	6.3 KiB
en.russiatoday.com/static/js/libs/lazysizes.min.js	345600.0 s	3.8 KiB
mc.yandex.com/metrika/advert.gif?t=gdpr(14)ti(4)	3600.0 s	327 B
/sync_cookie_image_decide?cid=32550500&scid=a19f91d9-14c9...	0.0 ms	255 B
en.russiatoday.com/static/js/pushes/notification.js?v=5	345600.0 s	1.2 KiB
en.russiatoday.com/static/js/libs/counters.js?b=7	345600.0 s	646 B
/sync_cookie_image_decide_secondary?cid=32550500&scid=d09...	0.0 ms	79 B
mf.b37mrtl.ru/files/2026.04/69e7a63285f54076f72f8f16.mp4	14400.0 s	0 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
fonts.gstatic.com/s/archivo/v3/k3kVo8UDI-1M0wlSdSrLO0bhLA.woff2	45 ms
fonts.gstatic.com/s/archivo/v3/k3kVo8UDI-1M0wlSdWLNO0bhLA.woff2	45 ms
fonts.gstatic.com/s/archivo/v3/k3kQo8UDI-1M0wlSfdnoLg.woff2	40 ms

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:0.068 source:map[column:3520 line:27 type:source-location url:https://en.russiatoday.com/static/js/libs/lazysizes.min.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:4.217 source:map[column:19 line:139 type:source-location url:https://www.rt.com/ urlProvider:network]] map[reflowTime:80.768 source:map[type:text value:[unattributed]]] map[reflowTime:0.745 source:map[column:70 line:14 type:source-location url:https://mc.yandex.ru/metrika/tag.js urlProvider:network]] map[reflowTime:6.643 source:map[column:38014 line:1 type:source-location url:https://yandex.ru/ads/system/context.js urlProvider:network]] map[reflowTime:1.259 source:map[column:22604 line:1 type:source-location url:https://yandex.ru/ads/system/context.js urlProvider:network]] map[reflowTime:0.843 source:map[column:37548 line:1 type:source-location url:https://yandex.ru/ads/system/context.js urlProvider:network]] map[reflowTime:0.068 source:map[column:3037 line:26 type:source-location url:https://en.russiatoday.com/static/js/libs/lazysizes.min.js urlProvider:network]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:306.839 label:Time to first byte subpart:timeToFirstByte] map[duration:612.194 label:Resource load delay subpart:resourceLoadDelay] map[duration:317.236 label:Resource load duration subpart:resourceLoadDuration] map[duration:1559.412 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: US-Iran talks in limbo as ceasefire deadline looms (PHOTOS, VIDEOS)

path: 1,HTML,1,BODY,6,DIV,2,DIV,4,DIV,0,DIV,0,SECTION,0,DIV,1,DIV,0,DIV,0,DIV,0,UL,0,LI,0,DIV,0,DIV,0,DIV,0,A,0,PICTURE,4,IMG

selector: div.media__image > a.link > picture > img.media__item

snippet: <img alt="US-Iran talks in limbo as ceasefire deadline looms (PHOTOS, VIDEOS)" src="https://mf.b37mrtl.ru/files/2026.04/l/69e78a5585f54076f72f8f0d.jpg" data-sizes="auto" data-src="https://mf.b37mrtl.ru/files/2026.04/xxs/69e78a5385f54076f72f8f0a.jpg" class="media__item media__item_ratio lazyautosizes lazyloaded" sizes="372px">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: US-Iran talks in limbo as ceasefire deadline looms (PHOTOS, VIDEOS)

path: 1,HTML,1,BODY,6,DIV,2,DIV,4,DIV,0,DIV,0,SECTION,0,DIV,1,DIV,0,DIV,0,DIV,0,UL,0,LI,0,DIV,0,DIV,0,DIV,0,A,0,PICTURE,4,IMG

selector: div.media__image > a.link > picture > img.media__item

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
en.russiatoday.com/static/libs/qrcode.min.js?v=2	6.9 KiB
en.russiatoday.com/static/libs/jquery-1.11.2.min.js?v=2	33.2 KiB	426 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
US-Iran talks in limbo as ceasefire deadline looms (PHOTOS, VIDEOS) `div.media__image > a.link > picture > img.media__item`	mf.b37mrtl.ru/files/2026.04/l/69e78a5585f54076f72f8f0d.jpg	60.8 KiB	22.0 KiB
‘War crime’: Russian envoy denounces US-Israeli war on Iran from Tehran rubble `div.media__image > a.link > picture > img.media__item`	mf.b37mrtl.ru/files/2026.04/xs/69e75fa485f540054421eb90.jpg	18.3 KiB	8.9 KiB
UK special forces resigning en masse over war crimes probe – media `div.media__image > a.link > picture > img.media__item`	mf.b37mrtl.ru/files/2026.04/xs/69e788e32030272d9c58067f.jpg	16.3 KiB	6.9 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 888 ms

URL	Time Spent
rt.com/	888 ms
www.rt.com/	0.0 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 430 ms 59.3 KiB

URL	Transfer Size	Est Savings
en.russiatoday.com/static/css/template.css/template.4aa2d5aa.css	65.5 KiB	59.3 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.0 s 358.7 KiB

URL	Transfer Size	Est Savings
yastatic.net/partner-code-bundles/1304651/00cc0164cd639ddf.js	129.7 KiB	104.7 KiB
/wrapper/js/common-engine.js?v=s-dc1af2de-5f10-4ef6-a4db-...	152.0 KiB	99.5 KiB
yandex.ru/ads/system/context.js	103.8 KiB	57.3 KiB
mc.yandex.ru/metrika/tag.js	84.7 KiB	44.2 KiB
en.russiatoday.com/static/js/common.min.js?v=16464124494475130342	40.0 KiB	27.9 KiB
yastatic.net/partner-code-bundles/1304651/22d10f9d8e892aab.js	31.8 KiB	25.2 KiB

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	883 ms	61 ms	0.0 ms
www.rt.com/	671 ms	37 ms	9.4 ms
abt.s3.yandex.net/expjs/latest/exp.js	622 ms	565 ms	2.0 ms
yandex.ru/ads/system/context.js	532 ms	434 ms	48 ms
mc.yandex.ru/metrika/tag.js	310 ms	232 ms	63 ms
/wrapper/js/common-engine.js?v=s-dc1af2de-5f10-4ef6-a4db-...	296 ms	202 ms	59 ms
en.russiatoday.com/static/js/libs/lazysizes.min.js	201 ms	56 ms	1.0 ms
yastatic.net/partner-code-bundles/1304651/00cc0164cd639ddf.js	175 ms	104 ms	70 ms
en.russiatoday.com/static/js/common.min.js?v=16464124494475130342	114 ms	66 ms	13 ms
en.russiatoday.com/static/libs/jquery-1.11.2.min.js?v=2	83 ms	54 ms	6.5 ms
yastatic.net/partner-code-bundles/1304651/22d10f9d8e892aab.js	69 ms	36 ms	33 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	2.0 s
Other	996 ms
Style & Layout	542 ms
Script Parsing & Compilation	332 ms
Parse HTML & CSS	130 ms
Garbage Collection	94 ms
Rendering	86 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
The page was evicted from the cache because an active network connection received too much data. Chrome limits the amount of data that a page may receive while cached.	Not actionable

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
mf.b37mrtl.ru/files/2026.04/69e5ebe885f54058780f73e8.mp4	1.4 MiB
odysee.com/$/api/content/v2/get	677.1 KiB
mf.b37mrtl.ru/files/2026.04/69e7a63285f54076f72f8f16.mp4	671.6 KiB
odysee.com/public/assets/app-BvKe1kfu.js	216.4 KiB
api.odysee.com/geo/blocked_list	195.2 KiB
cdn.jsdelivr.net/npm/@farcaster/miniapp-sdk/dist/index.min.js	162.3 KiB
/wrapper/js/common-engine.js?v=s-dc1af2de-5f10-4ef6-a4db-...	152.2 KiB
www.googletagmanager.com/gtag/js?id=G-BB8DNPB73F	151.8 KiB
yastatic.net/partner-code-bundles/1304651/00cc0164cd639ddf.js	130.3 KiB
odysee.com/public/assets/index-BcGw2l9Q.css	127.4 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Optimize DOM size

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoid long main-thread tasks 10 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 150 ms

●Server Backend Latencies 140 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 150 ms

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
LIVE `div.header__main-wrapper > div.header__line > div.header__live > a.live-button`
EXCLUSIVE `li.main-promobox__item > a.main-promobox__heading > div.main-promobox__wrapper > span.category-tag`
EXCLUSIVE `div.Section-block > div.article-card > div.article-card__title > span.category-tag`
© Autonomous Nonprofit Organization “TV-Novosti”, 2005–2026. All rights reserve… `div.footer__copiright__BlockWrapper > div.footer__copyright_block > div.copyright__text > p`

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.Section-container > div.Section-block > div#mainnews_2 > iframe#odysee-iframe `div.Section-container > div.Section-block > div#mainnews_2 > iframe#odysee-iframe`
div.Section-container > div.Section-block > div#mainnews_3 > iframe#odysee-iframe `div.Section-container > div.Section-block > div#mainnews_3 > iframe#odysee-iframe`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > a.visually-hidden `body > a.visually-hidden`
div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.layout__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.main-promobox__cover > div.media > div.media__image > a.link `div.main-promobox__cover > div.media > div.media__image > a.link`
div.article-card__cover > div.media > div.media__image > a.link `div.article-card__cover > div.media > div.media__image > a.link`
div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link `div.footer__social > div.main-socials > div.main-socials__item > a.main-socials__link`
div.footer__copiright__BlockWrapper > div.footer__copyright_block > div.copyright__logo > a `div.footer__copiright__BlockWrapper > div.footer__copyright_block > div.copyright__logo > a`

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

Trust and Safety

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source
www.gstatic.com/firebasejs/11.0.1/firebase-messaging-compat.js

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
en.russiatoday.com/static/js/pushes/notification.js?v=5 line 87, col 20	`[fcm] failed to get token FirebaseError: Messaging: The notification permission was not granted and blocked instead. (messaging/permission-blocked). at Ze (https://www.gstatic.com/firebasejs/11.0.1/firebase-messaging-compat.js:1:21924)`
invalid/	`Failed to load resource: net::ERR_FAILED`
/hit;RTNEWS?t44.6;r;s41282324;uhttps%3A//www.rt.com/;hR...	`Failed to load resource: net::ERR_TIMED_OUT`
counter.yadro.ru/hit?r;s41282324;uhttps%3A//www.rt.com/;0.8936874778175482	`Failed to load resource: net::ERR_TIMED_OUT`

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
div.header__line > ul.mobile-nav > li.mobile-nav__item > a.js-mobile-element-nav `div.header__line > ul.mobile-nav > li.mobile-nav__item > a.js-mobile-element-nav`
div.header__line > ul.mobile-nav > li.mobile-nav__item > a.js-mobile-element-nav `div.header__line > ul.mobile-nav > li.mobile-nav__item > a.js-mobile-element-nav`
Accept cookies `div.layout__footer > div.cookies__banner > div.cookies__banner-wrapper > a.cookies__banner-button`

To appear in search results, crawlers need access to your app.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`