blog.glitch.com

https://blog.glitch.com/

Data from Aug 20, 2026, 7:09 PM UTC 3d old

Built Awesome #459 · 1 measurement · since Aug 20, 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.

Built with Eleventy 3.0.0

Core Web Vitals field data, url-level

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

LCP 996 ms good

INP 104 ms good

CLS 0 good

Scores

100

Performance

no change

Accessibility

no change

100

Best Practices

no change

100

SEO

no change

Lab metrics Lighthouse, mobile

Metric	Current	Previous	Change	Best	Worst
LCP Largest Contentful Paint	1.01 s	—	—	1.01 s	1.01 s
CLS Cumulative Layout Shift	0.024	—	—	0.024	0.024
TBT Total Blocking Time	0 ms	—	—	0 ms	0 ms
FCP First Contentful Paint	1.01 s	—	—	1.01 s	1.01 s
Speed Index	1.01 s	—	—	1.01 s	1.01 s
TTFB Time to First Byte	665 ms	—	—	665 ms	665 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 1.01 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.

resource load duration 69 ms

time to first byte 54 ms

element render delay 16 ms

resource load delay 9 ms

Field data Chrome UX Report, url-level

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

Metric	p75	Rating	Distribution (good / needs work / poor)
LCP CWV	996 ms	good	93.6% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run	104 ms	good	89.2% good
CLS CWV	0	good	88.4% good
FCP	920 ms	good	90% good
TTFB	688 ms	good	78.4% good

Metric

p75

Rating

Distribution (good / needs work / poor)

LCP CWV

996 ms

good

93.6% good

INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run

104 ms

good

89.2% good

CLS CWV

good

88.4% good

FCP

920 ms

good

90% good

TTFB

688 ms

good

78.4% good

Lab vs field

Lab LCP 1.01 s · field p75 996 ms · real users are 0.99× faster than the lab.

Field history 25 weeks

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

Week ending	LCP	INP	FCP	TTFB
2026-08-15	1.01 s	105 ms	939 ms	697 ms
2026-08-08	999 ms	105 ms	933 ms	689 ms
2026-08-01	1.02 s	106 ms	949 ms	693 ms
2026-07-25	1.04 s	105 ms	966 ms	706 ms
2026-07-18	1.07 s	103 ms	998 ms	733 ms
2026-07-11	1.10 s	102 ms	1.02 s	763 ms
2026-07-04	1.10 s	101 ms	1.02 s	773 ms
2026-06-27	1.11 s	102 ms	1.03 s	789 ms
2026-06-20	1.09 s	105 ms	1.00 s	773 ms
2026-06-13	1.07 s	105 ms	990 ms	765 ms
2026-06-06	1.08 s	106 ms	992 ms	773 ms
2026-05-30	1.07 s	106 ms	984 ms	759 ms

Week ending

LCP

INP

CLS

FCP

TTFB

2026-08-15

1.01 s

105 ms

939 ms

697 ms

2026-08-08

999 ms

105 ms

933 ms

689 ms

2026-08-01

1.02 s

106 ms

949 ms

693 ms

2026-07-25

1.04 s

105 ms

966 ms

706 ms

2026-07-18

1.07 s

103 ms

998 ms

733 ms

2026-07-11

1.10 s

102 ms

1.02 s

763 ms

2026-07-04

1.10 s

101 ms

1.02 s

773 ms

2026-06-27

1.11 s

102 ms

1.03 s

789 ms

2026-06-20

1.09 s

105 ms

1.00 s

773 ms

2026-06-13

1.07 s

105 ms

990 ms

765 ms

2026-06-06

1.08 s

106 ms

992 ms

773 ms

2026-05-30

1.07 s

106 ms

984 ms

759 ms

Page weight

Metric	Current	Previous	Change	Best	Worst
Page Weight	539 kB	—	—	539 kB	539 kB
Requests	13	—	—	13	13
Third-party Weight	0 B	—	—	0 B	0 B
Third-party CPU	0 ms	—	—	0 ms	0 ms
Unused JS	0 B	—	—	0 B	0 B
Unused CSS	0 B	—	—	0 B	0 B

By resource type

font 346 kB · 1 req

image 162 kB · 10 req

document 15.6 kB · 1 req

Page health

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

Main thread work

other 106 ms

style layout 72 ms

script evaluation 27 ms

paint composite render 18 ms

parse HTML 14 ms

script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 332 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.

serious color-contrast — Elements must meet minimum color contrast ratio thresholds 1 node
moderate page-has-heading-one — Page should contain a level-one heading 1 node

Accessibility failures 1 of 19 audits

Tracked as a count, not just the score — the weighted score is coarse enough that you can ship a broken component and barely move it.

color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 1 node

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	Perf	LCP	CLS	TBT	Weight	Runs	Spread	Bench	Took
Aug 20, 2026, 7:09 PM UTC	100	1.01 s	0.024	0 ms	539 kB	3/3	±4	2,446	21.3s

When

Perf

LCP

CLS

TBT

Weight

Runs

Spread

Bench

Took

Aug 20, 2026, 7:09 PM UTC

100

1.01 s

0.024

0 ms

539 kB

3/3

±4

2,446

21.3s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show blog.glitch.com'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://blog.glitch.com/"></speedlify2-score>