Skip to content
https://t.me/+7CNbkKxrQEJkMmI1

Performance

· 24 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.
SCORE
88
GRADE
B
FIX
3
REVIEW
4
PASS
13
INFO
4

Performance-focused optimization plan with CWV assessment, top offenders, and time estimates

Mobile Desktop
97
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
50
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
82
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

532 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.31 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

569 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.31 s

Page Load Progression

1.6 s
3.1 s
4.7 s
6.2 s
7.8 s
9.3 s
10.9 s
12.5 s
Checks
24
13 PASS 4 REVIEW 3 FIX
D
Third-Party Impact
Action
98% third-party, 0 ms blocking
FIX
98% third-party, 0 ms blocking
Warning::
Third-party code accounts for 98% of page weight (203.1 KiB of 207.7 KiB)
Info::
Third-party blocking time is low (0 ms)
98%
First-party Third-party
D
JS Execution Cost
Action
2004ms total JS execution
FIX
2004ms total JS execution
Warning::
https://telegram.org/js/tgwallpaper.min.js?3: 1221ms CPU time
Warning::
https://t.me/+7CNbkKxrQEJkMmI1: 546ms CPU time
Info::
Unattributable: 237ms CPU time
Warning::
Third-party scripts: 1221ms (61% of total)

Main Thread Breakdown

Other 52% Rendering 16% Script Evaluation 16% Style & Layout 15%
ScriptTotalScriptingParse/CompileParty
https://telegram.org/js/tgwallpaper.min.js?31221ms318ms0ms3rd
https://t.me/+7CNbkKxrQEJkMmI1546ms5ms0ms1st
Unattributable237ms0ms0ms1st
D
HTTP Caching
Action
no-store (uncacheable)
FIX
no-store (uncacheable)
Info::
Cache-Control: no-store prevents all caching
Intentional for dynamic content, but increases server load for every page view.
Got: no-store
Info::
No ETag or Last-Modified header
Conditional requests (304 Not Modified) are not possible without validators.
Cache-Control

no-store

DirectiveValueMeaning
no-store—Never cache this response
B
HTTP/3 (QUIC)
HTTP/3 not advertised
REVIEW
HTTP/3 not advertised
Info::
HTTP/3 (QUIC) is not advertised
HTTP/3 isn't advertised via Alt-Svc and the worker didn't negotiate h3. HTTP/3 reduces handshake latency (1-RTT instead of 2-3 RTTs) and is more resilient on lossy connections. Most modern CDNs (Cloudflare, Fastly, AWS CloudFront, Google Cloud CDN) support HTTP/3 with a single config switch -- consider enabling for mobile-heavy workloads.
B
Document Compression
Document response uses gzip; brotli would be ~20% smaller
REVIEW
Document response uses gzip; brotli would be ~20% smaller
Info::
Main HTML response uses gzip (brotli would be ~20% smaller)
All current browsers support brotli. Most CDNs (Cloudflare, Fastly, AWS CloudFront, Vercel, Netlify) can switch from gzip to brotli with a single config flag. Origin servers (nginx, Apache) need a brotli module compiled in -- nginx-brotli or Apache mod_brotli.
B
Server-Timing Observability
No Server-Timing header found
REVIEW
No Server-Timing header found
Info::
No Server-Timing header found
Server-Timing exposes backend timing breakdowns to browser DevTools (e.g., `db: 45ms; render: 120ms; cache: 2ms`). Useful for diagnosing slow pages without backend log access. Most modern frameworks (Next.js, Cloudflare Workers, Fastly) emit it automatically; absence on a managed platform usually means telemetry headers are stripped at the edge.
C
Green Hosting
Action
Whether the site is served from green-energy infrastructure
REVIEW

Green Hosting

No green hosting detected

A+
Page Weight Budget
208 KB transferred, 10 requests
PASS
208 KB transferred, 10 requests
Info::
Page weighs 485 KB (208 KB transferred)
Info::
10 HTTP requests
Info::
Estimated 0.04 g CO2 per page load
208 KB / 2.4 MB budget
208 KB transferred
10 requests
0.04 g CO2 per page load
Images 137.9 KiB 66%
CSS 41.5 KiB 20%
Fonts 22.0 KiB 11%
HTML 4.6 KiB 2%
JavaScript 1.7 KiB 1%
0 2.4 MB 4.9 MB
Under budget
A+
Text Compression
All text resources are compressed
PASS
All text resources are compressed
Info::
All text resources are compressed
All text resources are properly compressed.
A
Image Optimization
2 images, 0 KB saveable
PASS
2 images, 0 KB saveable
Info::
All images are well-optimized
2 images 138 KB
0 oversized -0 KB
2 legacy format
0 missing dimensions CLS risk
A+
Font Loading
2 fonts (22 KB)
PASS
2 fonts (22 KB)
Info::
2 font(s) use font-display: swap (FOUT risk but functional)

Web fonts

2

22 KB total

Render-blocking

0

of 2

Dominant font-display

swap

Most common across fonts

Font loading timeline
Transfer FOIT (block) FOUT (swap)
0 ms 500 ms 1.0 s FCP 532 ms LCP 1.3 shttps://telegram.org/fonts/Roboto/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2KFOlCnqEu92Fr1MmWUlfBBc... https://telegram.org/fonts/Roboto/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2 — 11.0 KiB — 100 ms — font-display: swaphttps://telegram.org/fonts/Roboto/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2KFOmCnqEu92Fr1Mu4mxKKTU... https://telegram.org/fonts/Roboto/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2 — 11.0 KiB — 128 ms — font-display: swap
KFOlCnqEu92Fr1MmWUlfBBc... woff2 swap
Size 11 KB
Load time 100 ms
Start 294 ms
Risk FOUT — text flashes from fallback to web font
KFOmCnqEu92Fr1Mu4mxKKTU... woff2 swap
Size 11 KB
Load time 128 ms
Start 295 ms
Risk FOUT — text flashes from fallback to web font
Optimization checklist
  • Preload critical fonts (priority=high)
  • Use woff2 format for all fonts
  • Set font-display to swap, optional, or fallback
  • Subset large fonts (≤100 KB each)
A+
JS Bundles
1 scripts, 0 KB unused
PASS
1 scripts, 0 KB unused
0 KB unused JavaScript

Downloaded but never executed on this page.

ScriptSizeUnusedMinifiedParty
https://telegram.org/js/tgwallpaper.min.js?32 KB—✓3rd
A+
Resource Caching
All resources properly cached
PASS
All resources properly cached
Info::
No caching issues found
All static resources have appropriate caching headers.
A+
Critical Rendering Path
No render-blocking resources
PASS
No render-blocking resources
Info::
No render-blocking resources detected
A+
Resource Hints
No optimization needed
PASS
No optimization needed
Info::
No resource hint issues
A
Asset Compression
1 of 1 asset host still on gzip
PASS
1 of 1 asset host still on gzip
Info::
telegram.org serves assets with gzip; brotli would be ~20% smaller (assets: 11)
Every current browser accepts brotli. On a CDN this is a per-pull-zone toggle (Cloudflare, Fastly, CloudFront, CDN77, Bunny all expose it); on an origin it needs the brotli module (nginx-brotli, Apache mod_brotli). The saving lands on the assets this host serves, not on the HTML document -- the document's own encoding is reported separately.
Got: telegram.org (text/css)
A+
LCP Image Preload
LCP preload audit not available
PASS
LCP preload audit not available
Info::
LCP image preload audit not available for this scan
A+
Main HTML Cache-Control
Main HTML uses no-store -- correct for sensitive/dynamic content
PASS
Main HTML uses no-store -- correct for sensitive/dynamic content
Info::
Main HTML uses no-store -- correct for sensitive/dynamic content
Got: no-store
A
Server Response Intelligence
2 server-response signal(s) detected
PASS
2 server-response signal(s) detected
Warning::
Compressed response missing `Vary` header
The page is served with `Content-Encoding: gzip` but has no `Vary` header. Without `Vary: Accept-Encoding`, intermediary caches (corporate proxies, ISP caches) may serve the compressed variant to clients that didn't send the matching `Accept-Encoding` -- the client sees garbled bytes. Add `Vary: Accept-Encoding` whenever the response is conditionally compressed.
Info::
No `ETag` or `Last-Modified` -- conditional GET not supported
Without either header, browsers can't issue conditional GETs and refresh always re-downloads the full response body even when nothing changed. Add `ETag: "<hash>"` (or `Last-Modified: <date>`) on cacheable responses; the server returns 304 Not Modified when the client's cached copy is still valid, saving bandwidth.
A
Page Weight Inventory
10 resources · 208 KB · 0 KB savings available
PASS
10 resources · 208 KB · 0 KB savings available
Info::
Within 1MB page-weight target
Got: 208 KB
Warning::
9 third-party resources (98% of weight)
10 resources · 207.7 KiB · 9 third-party Within 1MB page-weight target
Image 66% · 137.9 KiB
CSS 20% · 41.5 KiB
Font 11% · 22.0 KiB
Document 2% · 4.6 KiB
JavaScript 1% · 1.7 KiB
Network Waterfall
10 requests over 949ms
INFO
0 ms 500 ms 1.0 s FCP 532 ms LCP 1.3 shttps://t.me/+7CNbkKxrQEJkMmI1/+7CNbkKxrQEJkMmI1 https://t.me/+7CNbkKxrQEJkMmI1 — 200 — 4.6 KiB — 126 ms — h2https://telegram.org/css/font-roboto.css?1telegram.org/css/font-roboto.css?1 https://telegram.org/css/font-roboto.css?1 — 200 — 893 B — 135 ms — h2https://telegram.org/css/bootstrap.min.css?3telegram.org/css/bootstrap.min.css?... https://telegram.org/css/bootstrap.min.css?3 — 200 — 10.1 KiB — 106 ms — h2https://telegram.org/css/telegram.css?256telegram.org/css/telegram.css?256 https://telegram.org/css/telegram.css?256 — 200 — 30.5 KiB — 134 ms — h2https://cdn5.telesco.pe/file/SKoatizU8B93ao-vWQpDu6ZuQC8mPGSW010W7z1OOfOAyEXFbXI-JyH9u6NE_sFJ8TeCJk0ojHUJI3UU91OY6dgV7EEVBRWXeyrpebO7HIFtsFd0RM2Dp4cOfsrnkyxlnmC0sPtynmIF71hzI6AfHt4zeTa_Bkfmz-a9ly2z_6hFnNVYQ2IvaZy8zkUbyEiFdBZPpQpbKm6eUGPrUjGhTDtrOQUU4iGl_lS6sScmTEupSMG1XJh4HvrypCwmOs8XFgQpeamRp06Pp49WMG4YcM-YXA1phSh8ijLUGs9wHsg-fNSO9yIPvvfI5BYbV6fv2_gp3kIoIRqD5FjKP7JP-w.jpgcdn5.telesco.pe/file/SKoatizU8B93ao... https://cdn5.telesco.pe/file/SKoatizU8B93ao-vWQpDu6ZuQC8mPGSW010W7z1OOfOAyEXFbXI-JyH9u6NE_sFJ8TeCJk0ojHUJI3UU91OY6dgV7EEVBRWXeyrpebO7HIFtsFd0RM2Dp4cOfsrnkyxlnmC0sPtynmIF71hzI6AfHt4zeTa_Bkfmz-a9ly2z_6hFnNVYQ2IvaZy8zkUbyEiFdBZPpQpbKm6eUGPrUjGhTDtrOQUU4iGl_lS6sScmTEupSMG1XJh4HvrypCwmOs8XFgQpeamRp06Pp49WMG4YcM-YXA1phSh8ijLUGs9wHsg-fNSO9yIPvvfI5BYbV6fv2_gp3kIoIRqD5FjKP7JP-w.jpg — 200 — 57.2 KiB — 812 ms — h2https://telegram.org/js/tgwallpaper.min.js?3telegram.org/js/tgwallpaper.min.js?... https://telegram.org/js/tgwallpaper.min.js?3 — 200 — 1.7 KiB — 133 ms — h2https://telegram.org/img/tgme/pattern.svg?1telegram.org/img/tgme/pattern.svg?1 https://telegram.org/img/tgme/pattern.svg?1 — 200 — 80.7 KiB — 62 ms — h2https://telegram.org/fonts/Roboto/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2telegram.org/fonts/Roboto/KFOlCnqEu... https://telegram.org/fonts/Roboto/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2 — 200 — 11.0 KiB — 100 ms — h2https://telegram.org/fonts/Roboto/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2telegram.org/fonts/Roboto/KFOmCnqEu... https://telegram.org/fonts/Roboto/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2 — 200 — 11.0 KiB — 128 ms — h2tg://join?invite=7CNbkKxrQEJkMmI1join?invite=7CNbkKxrQEJkMmI1 tg://join?invite=7CNbkKxrQEJkMmI1 — -1 — 0 B — 8 ms —
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
61% of JavaScript execution is third-party
First-party Third-party 1221ms · 2KB · $16/mo
telegram.org
Other
Costly
Execution 1221ms
Transfer 2 KB
Monthly Cost $16/mo

These scripts may cost more than they're worth

  • telegram.org adds 1221ms and costs ~$16/month

61% of JavaScript execution time comes from third-party scripts.

Why this matters

Third-party scripts (analytics, ads, social, A/B testing) often dominate execution time — every one is a perf-and-privacy tax.

Learn more ▾

Each third-party script is a black box: you don't control when it loads, what it executes, or how much it grows. They often account for a major share of total blocking time on average sites (HTTP Archive's Web Almanac documents the trend). Audit which ones you actually need, defer the rest, and use facade patterns (lite-youtube, lite-vimeo) for embedded media.

Source: web.dev / HTTP Archive Web Almanac

telegram.org takes 1221ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.

Why this matters

This script has high main-thread execution time — optimize hot paths or defer.

Source: web.dev

How third-party costs are calculated

Real-User Performance (CrUX)
Field metrics from the Chrome User Experience Report
INFO

Chrome User Experience (CrUX)

Real-user metrics from the Chrome UX Report (2026-10-14 — 2026-11-10)

LCP (p75)

2258 ms

79% good

INP (p75)

128 ms

86% good

CLS (p75)

0.000

97% good

FCP (p75)

1920 ms

TTFB (p75)

1032 ms

This origin passes Core Web Vitals assessment
Image Optimization
1 images, 0 KB total, 0 KB wasted
INFO

Image Optimization Audit

Total Images

1

Total Size

0 KB

Oversized

1

1 missing alt text 1 missing dimensions
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback