Skip to content
https://t.me

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

93

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.

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.

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.

URLResource SizeEst Savings
div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image
telegram.org/file/400780400931/3/L6HFfelQm5E.394826.jpg/c82f3df5fb2bdde5f3385.6 KiB357.9 KiB
div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image
telegram.org/file/400780400115/5/Cv5ZyIIoOC0.324347.jpg/9b317921d13d7c6dda316.7 KiB288.8 KiB
Telegram for PC / Linux Telegram for macOS div.tl_main_download_desktop_section > div.tl_main_download_desktop_wrap1 > div.tl_main_download_desktop_wrap > div.tl_main_download_desktop
telegram.org/img/SiteDesktop.jpg?295.3 KiB42.6 KiB
telegram.org/file/464001828/11e9a/1yY7a721t4o.30567.png/e113973dae2bee508b29.9 KiB25.6 KiB
telegram.org/file/464001166/2/FzTl8_M5mQA.19325.png/b6c5dbc0e4f655380518.9 KiB14.7 KiB
telegram.org/file/464001132/3/-1qvqKPZsQQ.17975.png/7d57d7159cf4fbe9b217.6 KiB13.4 KiB
telegram.org/file/464001560/2/n7EACfx4FPY.16465.png/7318c11715aa2ec45b16.1 KiB11.9 KiB
telegram.org/file/464001453/3/mNzXWC3RX0c.15740.png/9ce5fa5f3fb74460b415.4 KiB11.2 KiB
div.tl_main_wrap > div.tl_main_download_mobile > a.tl_main_download_link > div.tl_main_download_image__ios div.tl_main_wrap > div.tl_main_download_mobile > a.tl_main_download_link > div.tl_main_download_image__ios
telegram.org/img/SiteiOS.jpg?230.6 KiB11.1 KiB
telegram.org/file/464001737/4/Fn57W9l3xI0.15286.png/d4b936ecc2c939f4fa14.9 KiB10.8 KiB
telegram.org/file/464001402/5/eOMSj3GzJXo.13579.png/f3cec6c451d023c10913.3 KiB9.1 KiB
telegram.org/file/464001880/3/xOpm7ohoHQ0.12690.png/feb1e161b1d360861312.4 KiB8.2 KiB
div.tl_main_wrap > div.tl_main_download_mobile > a.tl_main_download_link > div.tl_main_download_image__android div.tl_main_wrap > div.tl_main_download_mobile > a.tl_main_download_link > div.tl_main_download_image__android
telegram.org/img/SiteAndroid.jpg?220.6 KiB7.9 KiB
img img
telegram.org/file/464001897/3/f0Go0rLpEwk.11343.png/dd4eeb46cc5efc068811.1 KiB6.9 KiB

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-2-DIV
nodeLabel: Telegram for PC / Linux Telegram for macOS
path: 1,HTML,1,BODY,1,DIV,1,DIV,0,DIV,0,DIV,2,DIV,1,DIV,0,DIV,0,DIV
selector: div.tl_main_download_desktop_section > div.tl_main_download_desktop_wrap1 > div.tl_main_download_desktop_wrap > div.tl_main_download_desktop
snippet: <div class="tl_main_download_desktop clearfix">

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.

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
value: no origins were preconnected
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
value: No additional origins are good candidates for preconnecting

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.

RequestCache TTLTransfer Size
telegram.org/img/t_main_Android_demo.mp4345600.0 s245.4 KiB
telegram.org/img/t_main_iOS_demo.mp4345600.0 s239.5 KiB
telegram.org/img/SiteDesktop.jpg?2345600.0 s95.6 KiB
telegram.org/img/SiteiOS.jpg?2345600.0 s30.8 KiB
telegram.org/css/telegram.css?249345600.0 s30.3 KiB
telegram.org/img/SiteAndroid.jpg?2345600.0 s20.8 KiB
telegram.org/css/bootstrap.min.css?3345600.0 s10.1 KiB
telegram.org/img/t_logo_sprite.svg345600.0 s7.7 KiB
telegram.org/js/main.js?47345600.0 s6.9 KiB
telegram.org/js/tgsticker.js?31345600.0 s6.9 KiB
telegram.org/img/twitter.png345600.0 s1.4 KiB
telegram.org/img/SiteIconAndroid.svg345600.0 s1.2 KiB
telegram.org/img/SiteIconApple.svg345600.0 s647 B

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.

URLTransfer Size
telegram.org/css/telegram.css?24930.3 KiB
telegram.org/css/bootstrap.min.css?310.1 KiB

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

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: 40 ms 25.5 KiB
URLTransfer SizeEst Savings
telegram.org/css/telegram.css?24930.1 KiB25.5 KiB

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 4.9 KiB
URLTransfer SizeEst Savings
telegram.org/css/telegram.css?24930.3 KiB4.9 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image
telegram.org/file/400780400115/5/Cv5ZyIIoOC0.324347.jpg/9b317921d13d7c6dda
div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image
telegram.org/file/400780400931/3/L6HFfelQm5E.394826.jpg/c82f3df5fb2bdde5f3

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

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: 410 ms
URLTime Spent
t.me/410 ms
telegram.org/0.0 ms
●Time to Interactive 1.4 s
●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 20 ms
●Minify JavaScript
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 1,859 KiB
●JavaScript execution time 0.1 s
●Minimizes main-thread work 0.4 s
●Avoid non-composited animations 1 animated element found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 160 ms
●Server Backend Latencies 210 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 170 ms
○INP breakdown
○User Timing marks and measures
○Avoid long main-thread tasks
○Avoid large layout shifts
52

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
EN div.container > ul.nav > li.dropdown > a.dropdown-toggle
Twitter div.container > ul.nav > li.navbar-twitter > a
Home div.container > ul.nav > li.active > a
FAQ div.container > ul.nav > li > a
Apps div.container > ul.nav > li > a
API div.container > ul.nav > li.hidden-xs > a
Moderation div.container > ul.nav > li.hidden-xs > a
Recent News div.tl_main_side_blog > div.side_blog_wrap > div.side_blog > a.side_blog_header
AI Editor, Mighty Polls, Live Photos, Bots Managed by Bots, and More div.side_blog > div.side_blog_entries > a.side_blog_entry > div.side_blog_title
Member Tags, Login with Telegram, Disable Sharing, GIF Editing, Date Formatting… div.side_blog > div.side_blog_entries > a.side_blog_entry > div.side_blog_title
Android Redesign, Group Ownership Transfer, Gift Crafting, Colored Bot Buttons div.side_blog > div.side_blog_entries > a.side_blog_entry > div.side_blog_title
a new era of messaging div.tl_main_wrap > div.tl_main_head > div.tl_main_logo_wrap > p.tl_main_logo_lead
Telegram for Android div.tl_page > div.tl_main_wrap > div.tl_main_download_mobile > a.tl_main_download_link
Android div.tl_main_wrap > div.tl_main_download_mobile > a.tl_main_download_link > b
Telegram for iPhone / iPad div.tl_page > div.tl_main_wrap > div.tl_main_download_mobile > a.tl_main_download_link
iPhone div.tl_main_wrap > div.tl_main_download_mobile > a.tl_main_download_link > b
iPad div.tl_main_wrap > div.tl_main_download_mobile > a.tl_main_download_link > b
Recent News div.tl_main_wrap > div.tl_main_recent_news_wrap > h3.tl_main_recent_news_header > a
AI Editor, Mighty Polls, Live Photos, Bots Managed by Bots, and More a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > div.dev_blog_card_alltext_wrap > h4.dev_blog_card_title
Mar 31, 2026 div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > div.dev_blog_card_date
Member Tags, Login with Telegram, Disable Sharing, GIF Editing, Date Formatting… a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > div.dev_blog_card_alltext_wrap > h4.dev_blog_card_title
Mar 1, 2026 div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > div.dev_blog_card_date
API div.tl_main_card_cell > div.tl_main_card_wrap > div.tl_main_card_lead > a
FAQ div.footer_column > ul > li > a
Privacy div.footer_column > ul > li > a
Press div.footer_column > ul > li > a
iPhone/iPad div.footer_column > ul > li > a
Android div.footer_column > ul > li > a
Mobile Web div.footer_column > ul > li > a
PC/Mac/Linux div.footer_column > ul > li > a
macOS div.footer_column > ul > li > a
Web-browser div.footer_column > ul > li > a
API div.footer_column > ul > li > a
Translations div.footer_column > ul > li > a
Instant View div.footer_column > ul > li > a

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Telegram div.footer_wrap > div.footer_columns_wrap > div.footer_column > h5

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image
div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image

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
Telegram div.tl_main_wrap > div.tl_main_head > div.tl_main_logo_wrap > a.tl_main_logo

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Privacy div.footer_column > ul > li > a
Press div.footer_column > ul > li > a
Translations div.footer_column > ul > li > a
Instant View div.footer_column > ul > li > a

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-hidden="true"]` is not present on the document `<body>`
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Document has a `<title>` element
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●All heading elements contain content.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○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
○Elements use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has a valid value for its `[lang]` attribute
○`<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>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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.
100

Best Practices

●Uses HTTPS
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No browser errors logged to the console
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
82

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.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image
div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image div.tl_main_recent_news_cards > a.dev_blog_card_link_wrap > div.dev_blog_card_wrap > img.dev_blog_card_image

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●Document has a valid `hreflang`
○robots.txt is valid
○Document has a valid `rel=canonical`

Send Feedback