Manifest position 72 · CrUX rank bucket 1000
https://t.me
Coverage complete
The requested URL redirects to https://telegram.org/. Audit covers the destination public-site templates. Atomic coverage complete: 58/58 checks judged.
Attempts
1 / 3
Judged checks
58 / 58
Blocked
0
Not run
0
This report has no published overall score. Blocked and not-run checks are not passes. A coverage-complete report means every check has a judged outcome; it does not mean every check passed.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Dark emulation matches true, but home-dark.png is visually identical to the light capture; computed body remains rgb(255,255,255) and color-scheme is normal. F-001 medium: Add system-driven dark mode |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, getAnimations() still reports the non-essential 500ms t-logo-play animation. F-002 medium: Stop decorative logo motion when reduced motion is requested |
respect-user-preferencesrespects-contrast | issues | high | The prefers-contrast: more screenshot is unchanged, while axe measures the main #0088cc links at only 3.89:1 on white. F-003 medium: Adapt to higher contrast and fix low-contrast links |
implement-natural-interactionsview-transitions | issues | high | The navigation video records a direct cross-document swap from Home to FAQ; DOM/CSS has no view-transition declarations. F-004 low: Route changes swap abruptly |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation exists on the representative pages, so there is no implementation to place on a scroll timeline. |
implement-natural-interactionsphysical-gestures | pass | high | DOM/CSS inspection found ordinary links and native scrolling, with no custom pointermove, swipe, pull-to-refresh, or gesture interception fighting platform behaviour. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Long FAQ (about 53,068px mobile content height) and Safety pages retain static header chrome with no progress, shrinking, or scroll-state response. F-005 low: Long documents provide no scroll-state guidance |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or floating menu is exposed on the audited public pages. |
provide-guided-navigationdirects-attention | pass | high | Screenshots show an active blue underline in the global navigation; FAQ in-page links use real fragment targets, preserving location and orientation. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Desktop and mobile load screenshots show content immediately with no modal, consent wall, interstitial, or obscuring banner. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No overlay, modal flow, disclosure widget, or rich picker is present on these static public pages. |
maximize-content-reduce-noisereduced-chrome | pass | high | Across home, FAQ, Apps, Safety, and API screenshots, a single compact header leaves the viewport primarily to content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a requested 360px viewport, Safety reports a 450px layout viewport and 90px horizontal overflow, forcing browser scale-down rather than true 360px reflow. F-006 high: Safety uses a 450px minimum layout on a 360px device |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | medium | Mobile and desktop screenshots show the reused global header and content columns adapting via responsive CSS; no component is reused in conflicting container sizes that requires a container query. |
adapt-to-the-form-factorinput-modality-aware | pass | high | Lighthouse target-size passed, viewport scaling is allowed, the theme button retains a browser focus outline, and primary header links occupy the 48px header hit area. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first viewport names Telegram, presents platform download choices, and uses direct labels such as “Telegram for Android” and “Telegram for iPhone / iPad”. |
support-core-task-successprimary-flow-completion | pass | high | The home and Apps paths expose direct platform-specific download links without account walls, modals, or hidden prerequisites. |
support-core-task-successclear-system-state-and-recovery | pass | high | The static download and documentation journeys use normal links and browser history, with no loading shell or partial state on the exercised successful paths. |
be-fast-and-stablegood-core-web-vitals | issues | high | Cold Lighthouse reports LCP 4.7s (score 0.33), outside the good <=2.5s Core Web Vitals threshold, although CLS is 0. F-007 high: Cold-load LCP is 4.7 seconds |
be-fast-and-stablevisual-stability | pass | high | Layout observers reported CLS 0 on Home, FAQ, and Safety, with no observed shifts during the capture windows. |
be-fast-and-stableefficient-main-thread | issues | high | The DevTools trace records one 194.12ms main-thread task and 144.12ms total blocking time on the simple landing page. F-008 medium: A 194ms main-thread task blocks initial responsiveness |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR confirms three parser-inserted render-blocking stylesheets and three classic scripts without async/defer; Lighthouse also estimates 26 KiB unused CSS and cold LCP is 4.7s. F-009 medium: Blocking resources and unused CSS delay a simple page |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR confirms three parser-inserted render-blocking stylesheets and three classic scripts without async/defer; Lighthouse also estimates 26 KiB unused CSS and cold LCP is 4.7s. F-009 medium: Blocking resources and unused CSS delay a simple page |
be-inclusivenames-roles-labels | issues | high | axe reports two images without alt text, the logo home link without an accessible name, and the Images primitive confirms two missing alt attributes. F-010 high: Images and the logo link lack accessible alternatives |
be-inclusivesufficient-contrast | issues | high | axe reports serious color-contrast failures: the shared #0088cc link color is 3.89:1 on white across navigation and news links. F-011 high: Shared blue links fail WCAG AA contrast |
be-inclusivestructure-and-focus | issues | high | axe reports no main landmark, no H1 on Home, invalid heading order, broad content outside landmarks, and an empty heading. F-012 high: Home lacks basic heading and landmark structure |
be-inclusivelegible-text | pass | high | Visual review across four templates found readable line lengths, clear heading/body hierarchy, and no clipping in ordinary desktop and mobile states. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At a requested 360px viewport, Safety reports a 450px layout viewport and 90px horizontal overflow, forcing browser scale-down rather than true 360px reflow. F-006 high: Safety uses a 450px minimum layout on a 360px device |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console passed and no uncaught runtime exception appeared during CDP evidence collection. |
follow-best-practicessound-document-and-assets | issues | high | Images primitive reports both sampled below-fold news images omit width and height attributes (and loading/srcset). F-013 low: Below-fold images omit intrinsic dimensions |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse best-practices scored 1.00, BFCache passed, and no permission prompt, paste prevention, or deprecation surfaced during recon. |
be-discoverabletitle-and-description | issues | high | Metadata probe finds a descriptive title but no meta description on Home, FAQ, Apps, Safety, or API; Lighthouse meta-description fails. F-014 medium: Every sampled page lacks a meta description |
be-discoverablecrawlable-and-mobile-friendly | pass | high | All sampled navigation/content links have real href values, viewport metadata is present, raw HTML contains the content, and no robots noindex directive blocks crawling. |
be-discoverablecanonical-and-indexing-signals | issues | high | robots.txt and sitemap.xml return 404, sampled pages have no canonical, and an invented URL returns HTTP 200 with the homepage, creating a soft-404 indexing signal. F-015 high: Soft 404s and missing canonical crawl signals confuse indexing |
be-discoverablestructured-and-shareable-metadata | pass | high | All five sampled templates include Open Graph metadata matching their visible Telegram content; none is a product, event, or article detail requiring richer schema for the audited task. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers primitive finds HTTPS and HSTS, but no Content-Security-Policy and no X-Content-Type-Options; the short-lived cookie is Secure and HttpOnly. F-016 high: Core XSS and MIME-sniffing defenses are absent |
be-private-and-securedata-minimisation-and-third-parties | pass | high | Tracker capture found no known trackers, cookies found no third-party cookie, secrets found no exposed credential, and the HAR contains only the t.me to telegram.org first-party organisational redirect. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | The audited public information and download pages request no browser permissions and expose no authentication flow. |
be-private-and-securedefensive-browser-policies | issues | high | Headers primitive finds no Referrer-Policy or Permissions-Policy; X-Frame-Options and HSTS are present. F-017 medium: Privacy-oriented browser policies are incomplete |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 100% raw-HTML content coverage with no JS shell; browser and crawler views both contain the core page. |
be-resilientresilient-runtime-behaviour | pass | high | The sampled static routes use native links and no overlays; no clipped menu, async shell, or unstable reactive state appeared in screenshots or DOM evidence. |
be-resilientoffline-and-installable | not-applicable | high | The audited surface is a brochure/documentation site linking to native and web apps, not an installable app itself; offline installability is not required for this surface. |
be-resilientnetwork-and-http-failure-states | issues | high | A clearly nonexistent path returns HTTP 200 and silently renders the homepage instead of an explicit not-found state with recovery guidance. F-018 medium: Unknown routes silently become the homepage |
be-internationalisedlang-dir-and-logical-properties | issues | high | All five sampled documents omit html lang (axe serious), and the root computed direction metadata is also undeclared despite offering 19 languages. F-019 high: Localized pages omit language and direction metadata |
be-internationalisedlocale-aware-data | pass | medium | The language selector exposes 19 locales; a German cookie response localised navigation and the visible date from “Jul 14” to “14. Jul”. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative pages do not coordinate events, appointments, deadlines, or user-entered times across time zones. |
be-trustworthyno-dark-patterns | pass | high | No consent wall, forced continuity, disguised ad, nagging prompt, pricing, or destructive action appears on any sampled public page. |
be-trustworthyhumane-error-handling | not-applicable | high | No form is present on the audited public pages. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No editable input or account/payment form is present on the audited public pages. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, consent, sign-in, or account-management flow is exposed on the audited pages. |
be-sustainableoptimised-assets | issues | high | HAR transfers 666,179 image bytes; the two 600px news images lack lazy loading and srcset, including one 324,389-byte below-fold image. F-020 medium: Below-fold images are heavy and not responsive or lazy |
be-sustainableno-wasteful-work | pass | high | HAR and trace show a bounded initial load with no analytics beacons, recurring background fetches, or continuous idle processing. |
be-sustainablethird-party-and-media-budget | issues | high | The simple landing page initiates six media requests plus 20 image requests and transfers 798,160 bytes before interaction; demo MP4 requests begin without user intent. F-021 low: Demo media starts loading before user intent |
be-agent-readystructured-agent-capabilities | not-applicable | high | This public marketing/documentation surface does not declare an agent-facing intent; emerging WebMCP capability is an opportunity, not an obligation. |
be-agent-readyon-device-inference | not-applicable | high | The pages contain no summarisation or generation workflow where on-device inference would improve the task. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | Ten repeated theme toggles left DOM nodes unchanged at 306 and reduced measured used JS heap by 701,845 bytes after settling. |
be-memory-efficientbounded-footprint | pass | high | The heap baseline is about 29.0 MB self size with 68,857 nodes in the snapshot graph, proportionate to the image-rich static landing page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | After ten theme toggles, live DOM node count remained 306; the second heap summary showed only modest cross-process variance and no direct evidence of unbounded retention. |
Provenance
Canonical report: results/atomic/reports/0072-t_me.json
Report SHA-256: a2fbeeb5ac9492a1f666187756f9f56e7e69ae2c59a7b47180ed2637ca935f49
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/t_me/2026-07-18T05-21-10-852Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/t_me/2026-07-18T05-21-10-852Z
Catalog SHA-256: sha256:78ccfdb2d483f4c57d9dafed80fd86c6265585a56457c8dcfddc254b80fb44d7
Raw screenshots, HARs, traces, heaps, and other browser artifacts are retained at the local evidence root and intentionally are not committed. Artifact paths in the canonical report are relative to that root.