jekyllrb.com

Data from Aug 23, 2026, 1:15 AM UTC 21h old

Site Generators #11 · 3 measurements · 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 Jekyll 4.4.1

Hosted by GitHub Pages

Core Web Vitals field data, url-level

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

LCP 1.11 s good

INP 75 ms good

CLS 0 good

Scores

Performance

↑ +1 (+1%)

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.

375 ms
750 ms
1.13 s
1.50 s
1.88 s
2.25 s
2.63 s
3.00 s

Lab metrics Lighthouse, mobile

Metric	Current	Previous	Change	Best	Worst
LCP Largest Contentful Paint	2.04 s	2.14 s	↓ -100 ms (-4.7%)	1.96 s	2.14 s
CLS Cumulative Layout Shift	0	0	→ no change	0	0
TBT Total Blocking Time	53 ms	73 ms	↓ -20 ms (-27.4%)	53 ms	73 ms
FCP First Contentful Paint	919 ms	905 ms	↑ +14 ms (+1.5%)	902 ms	919 ms
Speed Index	919 ms	905 ms	↑ +14 ms (+1.5%)	902 ms	919 ms
TTFB Time to First Byte	619 ms	605 ms	↑ +14 ms (+2.3%)	602 ms	619 ms

Metric

Current

Change

Best

Worst

Trend

LCP Largest Contentful Paint

2.04 s

2.14 s

↓ -100 ms (-4.7%)

1.96 s

2.14 s

CLS Cumulative Layout Shift

→ no change

TBT Total Blocking Time

53 ms

73 ms

↓ -20 ms (-27.4%)

53 ms

73 ms

FCP First Contentful Paint

919 ms

905 ms

↑ +14 ms (+1.5%)

902 ms

919 ms

Speed Index

919 ms

905 ms

↑ +14 ms (+1.5%)

902 ms

919 ms

TTFB Time to First Byte

619 ms

605 ms

↑ +14 ms (+2.3%)

602 ms

619 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 2.04 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 76 ms

time to first byte 20 ms

Field data Chrome UX Report, url-level

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

Metric	p75	Rating	Distribution (good / needs work / poor)
LCP CWV	1.11 s	good	95.9% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run	75 ms	good	97.5% good
CLS CWV	0	good	99.4% good
FCP	1.13 s	good	91% good
TTFB	578 ms	good	83.9% good

Metric

p75

Rating

Distribution (good / needs work / poor)

LCP CWV

1.11 s

good

95.9% good

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

75 ms

good

97.5% good

CLS CWV

good

99.4% good

FCP

1.13 s

good

91% good

TTFB

578 ms

good

83.9% good

Lab vs field

Lab LCP 2.04 s · field p75 1.11 s · real users are 0.54× 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.08 s	76 ms	1.09 s	595 ms
2026-08-08	1.06 s	75 ms	1.07 s	548 ms
2026-08-01	1.03 s	76 ms	1.05 s	559 ms
2026-07-25	1.06 s	74 ms	1.08 s	609 ms
2026-07-18	1.08 s	73 ms	1.09 s	604 ms
2026-07-11	1.13 s	76 ms	1.15 s	638 ms
2026-07-04	1.16 s	73 ms	1.17 s	639 ms
2026-06-27	1.14 s	75 ms	1.14 s	622 ms
2026-06-20	1.14 s	74 ms	1.14 s	621 ms
2026-06-13	1.07 s	73 ms	1.07 s	609 ms
2026-06-06	1.05 s	72 ms	1.07 s	585 ms
2026-05-30	1.04 s	73 ms	1.05 s	585 ms

Week ending

LCP

INP

CLS

FCP

TTFB

2026-08-15

1.08 s

76 ms

1.09 s

595 ms

2026-08-08

1.06 s

75 ms

1.07 s

548 ms

2026-08-01

1.03 s

76 ms

1.05 s

559 ms

2026-07-25

1.06 s

74 ms

1.08 s

609 ms

2026-07-18

1.08 s

73 ms

1.09 s

604 ms

2026-07-11

1.13 s

76 ms

1.15 s

638 ms

2026-07-04

1.16 s

73 ms

1.17 s

639 ms

2026-06-27

1.14 s

75 ms

1.14 s

622 ms

2026-06-20

1.14 s

74 ms

1.14 s

621 ms

2026-06-13

1.07 s

73 ms

1.07 s

609 ms

2026-06-06

1.05 s

72 ms

1.07 s

585 ms

2026-05-30

1.04 s

73 ms

1.05 s

585 ms

Page weight

Metric	Current	Previous	Change	Best	Worst
Page Weight	368 kB	368 kB	↓ -369 B (-0.1%)	368 kB	368 kB
Requests	12	12	→ no change	12	12
Third-party Weight	229 kB	229 kB	↓ -252 B (-0.1%)	229 kB	229 kB
Third-party CPU	64 ms	69 ms	↓ -5 ms (-7.1%)	63 ms	69 ms
Unused JS	98.1 kB	98.0 kB	↑ +42 B	98.0 kB	98.1 kB
Unused CSS	12.1 kB	12.1 kB	→ no change	12.1 kB	12.1 kB

Metric

Current

Change

Best

Worst

Trend

Page Weight

368 kB

↓ -369 B (-0.1%)

368 kB

Requests

→ no change

Third-party Weight

229 kB

↓ -252 B (-0.1%)

229 kB

Third-party CPU

64 ms

69 ms

↓ -5 ms (-7.1%)

63 ms

69 ms

Unused JS

98.1 kB

98.0 kB

↑ +42 B

98.0 kB

98.1 kB

Unused CSS

12.1 kB

→ no change

12.1 kB

By resource type

script 229 kB · 3 req

image 72.7 kB · 3 req

font 46.5 kB · 2 req

stylesheet 14.1 kB · 1 req

document 3.7 kB · 1 req

other 38 B · 1 req

third party 229 kB · 4 req

Third parties 3 entities

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

Google Tag Manager 160 kB · 40 ms CPU

JSDelivr CDN 48.2 kB · 13 ms CPU

Google Analytics 20.9 kB · 12 ms CPU

Page health

Metric	Current	Previous	Change	Best	Worst
Main Thread Work	522 ms	568 ms	↓ -46 ms (-8.1%) significant	522 ms	568 ms
Long Tasks	2	2	→ no change	1	2
DOM Elements	143	143	→ no change	143	143
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset	13	13	→ no change	13	13
A11y Failures	2	2	→ no change	2	2
A11y Failing Nodes	8	8	→ no change	8	8

Main thread work

script evaluation 269 ms

other 93 ms

script parse compile 74 ms

style layout 68 ms

parse HTML 12 ms

paint composite render 6 ms

Axe violations axe-core 4.13.0, full rule set

13 violating nodes across 4 rules, 232 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 link-in-text-block — Links must be distinguishable without relying on color 7 nodes
moderate region — All page content should be contained by landmarks 4 nodes
serious color-contrast — Elements must meet minimum color contrast ratio thresholds 1 node
moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 2 of 20 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.

link-in-text-block — Links rely on color to be distinguishable. 7 nodes
landmark-one-main — Document does not have a main landmark. 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	TBT	Weight	Runs	Spread	Bench	Took
Aug 23, 2026, 1:15 AM UTC	99	2.04 s	53 ms	368 kB	3/3	±27	2,473	29s
Aug 22, 2026, 1:09 AM UTC	98	2.14 s	73 ms	368 kB	3/3	±27	2,320	27s
Aug 20, 2026, 11:32 PM UTC	99	1.96 s	56 ms	368 kB	3/3	±5	2,499	21.3s

When

Perf

LCP

CLS

TBT

Weight

Runs

Spread

Bench

Took

Aug 23, 2026, 1:15 AM UTC

2.04 s

53 ms

368 kB

3/3

±27

2,473

29s

Aug 22, 2026, 1:09 AM UTC

2.14 s

73 ms

368 kB

3/3

±27

2,320

27s

Aug 20, 2026, 11:32 PM UTC

1.96 s

56 ms

368 kB

3/3

±5

2,499

21.3s

Embed this score

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