speedlify2

Lighthouse lab metrics, Axe, and Chrome UX Report field data for a list of sites recorded and compared over time.

Measurement runs Embed a score

typescriptlang.org

https://www.typescriptlang.org/

88 100 100 100 ✓AXE ✓CWV

Data from Aug 27, 2026, 7:02 PM UTC old

Overall #676 Developer Tooling #11 · 1 measurement · since Aug 27, 2026

Stack

Detected on the same page load as the accessibility pass — the generator from <meta name="generator"> or the shape of the page, the host from response headers.

Gatsby 5.16.1 Built with Gatsby 5.16.1
GitHub Pages Hosted by GitHub Pages

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-29 → 2026-08-25). This is what Google measures you on.

LCP 1.25 s good
INP 96 ms good
CLS 0.010 good

Scores

88
Performance
no change
100
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Filmstrip Lighthouse, mobile

How the page drew during the measured load, at 8 points across 3.00 s.

  1. 375 ms
  2. 750 ms
  3. 1.13 s
  4. 1.50 s
  5. 1.88 s
  6. 2.25 s
  7. 2.63 s
  8. 3.00 s

Without JavaScript

The same load, photographed twice at 412×823: once with scripts disabled, once as rendered.

Scripts disabled
As rendered

0% of pixels differ — they are identical. A shifted layout counts as difference, so a <noscript> banner alone can account for a large figure.

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.36 s — — 3.36 s 3.36 s
CLS Cumulative Layout Shift 0.002 — — 0.002 0.002
TBT Total Blocking Time 21 ms — — 21 ms 21 ms
FCP First Contentful Paint 2.71 s — — 2.71 s 2.71 s
Speed Index 2.71 s — — 2.71 s 2.71 s
TTFB Time to First Byte 603 ms — — 603 ms 603 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 3.36 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 74 ms
time to first byte 3 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-07-29 → 2026-08-25). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.25 s good 92.3% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 96 ms good 92.3% good
CLS CWV 0.010 good 88.2% good
FCP 1.19 s good 86.8% good
TTFB 745 ms good 77.5% good

Lab vs field LCP

Lab 3.36 s
Field p75 1.25 s

The lab LCP is 2.7× the field p75 — real users likely have above-average hardware or network connectivity.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-22 1.26 s 96 ms 0.010 1.21 s 765 ms
2026-08-15 1.25 s 95 ms 0.010 1.19 s 775 ms
2026-08-08 1.30 s 95 ms 0.010 1.24 s 837 ms
2026-08-01 1.30 s 95 ms 0.010 1.24 s 861 ms
2026-07-25 1.30 s 96 ms 0.010 1.23 s 862 ms
2026-07-18 1.31 s 97 ms 0.010 1.25 s 859 ms
2026-07-11 1.30 s 99 ms 0.010 1.24 s 808 ms
2026-07-04 1.31 s 104 ms 0.010 1.26 s 796 ms
2026-06-27 1.31 s 106 ms 0.010 1.26 s 778 ms
2026-06-20 1.36 s 111 ms 0.010 1.31 s 801 ms
2026-06-13 1.35 s 108 ms 0.010 1.29 s 823 ms
2026-06-06 1.32 s 108 ms 0.010 1.24 s 785 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 589 kB — — 589 kB 589 kB
Requests 23 — — 23 23
Third-party Weight 184 kB — — 184 kB 184 kB
Third-party CPU 2 ms — — 2 ms 2 ms
Unused JS 131 kB — — 131 kB 131 kB
Unused CSS 29.4 kB — — 29.4 kB 29.4 kB

By resource type

script 307 kB · 7 req
font 180 kB · 5 req
document 70.7 kB · 1 req
image 16.9 kB · 2 req
other 7.3 kB · 5 req
stylesheet 6.1 kB · 1 req
third party 184 kB · 5 req

Third parties 2 entities

184 kB transferred, 2 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

office.net 130 kB · 0 ms CPU
azurefd.net 53.5 kB · 2 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 627 ms — — 627 ms 627 ms
Long Tasks 4 — — 4 4
DOM Elements 1,414 — — 1,414 1,414
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 0 — — 0 0
A11y Failures 0 — — 0 0
A11y Failing Nodes 0 — — 0 0

Main thread work

script evaluation 218 ms
other 136 ms
style layout 135 ms
script parse compile 77 ms
parse HTML 35 ms
paint composite render 27 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 2024 passing. This is a standalone axe run, stricter than the subset Lighthouse folds into its score above — and it is the second tiebreaker in the ranking.

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

Measurement log

Every stored run for this URL, newest first. Failures are kept as records — "this site was down on Tuesday" is data too.

When PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 27, 2026, 7:02 PM UTC 88 3.36 s 0.002 21 ms 589 kB 3/3 ±12 2,990 23.2s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show typescriptlang.org's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site! 

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://www.typescriptlang.org/"></speedlify2-score>