speedlify2

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

Measurement runs · Embed a score · Field data from the Chrome UX Report ·

globe.church

https://www.globe.church/

96 100 100 100 CWV 2AXE

Data from Aug 21, 2026, 11:46 AM UTC — 7h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 7h

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.

Eleventy 4.0.0 Built with Eleventy 4.0.0
Netlify Hosted by Netlify

Core Web Vitals field data, origin-level

Real Chrome users, 28-day window (2026-07-19 → 2026-08-15). From the backfilled CrUX history rather than this measurement, which predates the API key. This is what Google measures you on.

LCP no data
INP no data
CLS no data

Scores

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

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.96 s 1.96 s 1.96 s
CLS Cumulative Layout Shift 0.075 0.075 0.075
TBT Total Blocking Time 131 ms 131 ms 131 ms
FCP First Contentful Paint 1.81 s 1.81 s 1.81 s
Speed Index 1.81 s 1.81 s 1.81 s
TTFB Time to First Byte 605 ms 605 ms 605 ms

What LCP is made of

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

element render delay 49 ms
resource load duration 10 ms
resource load delay 9 ms
time to first byte 5 ms

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-15
2026-08-08
2026-08-01
2026-07-25 0 1.27 s
2026-07-18
2026-07-11 1.50 s 0 1.25 s
2026-07-04 1.44 s 0 1.18 s
2026-06-27 1.36 s 0 1.13 s
2026-06-20 0 1.18 s
2026-06-13 1.52 s 71 ms 0 1.24 s 722 ms
2026-06-06 1.41 s 70 ms 0 1.13 s 710 ms
2026-05-30 1.49 s 72 ms 0 1.18 s 727 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 855.9 kB 855.9 kB 855.9 kB
Requests 30 30 30
Third-party Weight 374.3 kB 374.3 kB 374.3 kB
Third-party CPU 100 ms 100 ms 100 ms
Unused JS 142.0 kB 142.0 kB 142.0 kB
Unused CSS 0 B 0 B 0 B

By resource type

image 424.2 kB · 7 req
script 341.7 kB · 4 req
font 49.1 kB · 2 req
other 19.2 kB · 4 req
stylesheet 14.9 kB · 11 req
document 4.3 kB · 1 req
third party 374.3 kB · 6 req

Third parties 3 entities

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

Google Tag Manager 304.3 kB · 86 ms CPU
Adobe TypeKit 49.1 kB · 0 ms CPU
Google Analytics 20.9 kB · 14 ms CPU

Page health

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

Main thread work

script evaluation 417 ms
other 209 ms
script parse compile 96 ms
style layout 77 ms
parse HTML 22 ms
paint composite render 15 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 1 rule, 410 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.

  • moderate region — All page content should be contained by landmarks 2 nodes

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 21, 2026, 11:46 AM UTC 96 1.96 s 0.075 131 ms 855.9 kB 3/3 ±33 2,492 29s

Embed this score

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

<speedlify-score speedlify-url="https://zachleat.github.io/speedlify2/" url="https://www.globe.church/"></speedlify-score>