Skip to content
https://pcre.org

Performance

· 17 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.
SCORE
95
GRADE
A
FIX
2
REVIEW
0
PASS
13
INFO
2

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

Mobile Desktop
94
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
96
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
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.

2.40 s

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

2.40 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.

2.87 s

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

2.40 s

Page Load Progression

375 ms
750 ms
1.1 s
1.5 s
1.9 s
2.2 s
2.6 s
3.0 s
Checks
17
13 PASS 2 FIX
D
Third-Party Impact
Action
96% third-party, 0 ms blocking
FIX
96% third-party, 0 ms blocking
Warning::
Third-party code accounts for 96% of page weight (3.8 KiB of 4.0 KiB)
Info::
Third-party blocking time is low (0 ms)
96%
First-party Third-party
F
HTTP Caching
Action
No cache headers
FIX
No cache headers
Warning::
No Cache-Control header found
Browsers will use heuristic caching, which can be unpredictable. Set explicit cache headers.

No Cache-Control header

Adding a Cache-Control header can significantly improve repeat-visit performance.

A+
Page Weight Budget
4 KB transferred, 4 requests
PASS
4 KB transferred, 4 requests
Info::
Page weighs 9 KB (4 KB transferred)
Info::
4 HTTP requests
Info::
Estimated 0.00 g CO2 per page load
4 KB / 2.4 MB budget
4 KB transferred
4 requests
0.00 g CO2 per page load
HTML 2.8 KiB 71%
Other 720 B 18%
CSS 456 B 11%
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
No images on this page
PASS
No images on this page
Info::
No images on this page
0 images 0 KB
0 oversized -0 KB
0 legacy format
0 missing dimensions CLS risk
A+
JS Execution Cost
189ms total JS execution
PASS
189ms total JS execution
Info::
Unattributable: 103ms CPU time
Info::
https://www.pcre.org/: 85ms CPU time
Warning::
Third-party scripts: 189ms (100% of total)

Main Thread Breakdown

Other 57% Style & Layout 26% Script Evaluation 7% Rendering 7% Parse HTML & CSS 3%
ScriptTotalScriptingParse/CompileParty
Unattributable103ms6ms0ms3rd
https://www.pcre.org/85ms5ms1ms3rd
A+
Font Loading
No web fonts (system fonts)
PASS
No web fonts (system fonts)
Info::
No web fonts loaded — system fonts are fastest
No web fonts loaded — system fonts are optimal.
A+
JS Bundles
No JavaScript
PASS
No JavaScript
Info::
No JavaScript bundles
No JavaScript files loaded.
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
Page Weight Inventory
4 resources · 4 KB · 0 KB savings available
PASS
4 resources · 4 KB · 0 KB savings available
Info::
Within 1MB page-weight target
Got: 4 KB
Warning::
3 third-party resources (96% of weight)
4 resources · 4.0 KiB · 3 third-party Within 1MB page-weight target
Document 75% · 3.0 KiB
Image 13% · 548 B
CSS 11% · 456 B
A+
Render-Blocking Resources
No render-blocking resources detected
PASS
No render-blocking resources detected
Info::
No render-blocking resources detected in <head>
A+
Third-Party Resources
No third-party resources detected
PASS
No third-party resources detected
A+
Green Hosting
Whether the site is served from green-energy infrastructure
PASS

Green Hosting

This site is hosted on green energy infrastructure

Provider: Google Cloud

Network Waterfall
4 requests over 1543ms
INFO
0 ms 500 ms 1.0 s 1.5 s 2.0 s 2.5 s FCP 2.4 s LCP 2.4 shttps://pcre.org// https://pcre.org/ — 301 — 172 B — 871 ms — h2https://www.pcre.org/www.pcre.org/ https://www.pcre.org/ — 200 — 2.8 KiB — 215 ms — h2https://www.pcre.org/style.csswww.pcre.org/style.css https://www.pcre.org/style.css — 200 — 456 B — 208 ms — h2https://www.pcre.org/favicon.icowww.pcre.org/favicon.ico https://www.pcre.org/favicon.ico — 200 — 548 B — 208 ms — h2
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
100% of JavaScript execution is third-party
First-party Third-party 189ms · 3KB · $2/mo
Unattributable
Other
Optional
Execution 103ms
Transfer 0 KB
Monthly Cost $1/mo
www.pcre.org
Other
Optional
Execution 85ms
Transfer 3 KB
Monthly Cost $1/mo

100% of JavaScript execution time is spent on third-party scripts. Consider auditing which scripts are essential.

Why this matters

When third-party JS execution time exceeds your own, performance gains from frontend work are capped by code you don't own.

Learn more ▾

Every millisecond of third-party JS competes with your own for main-thread time. If their share is bigger than yours, optimization on your code base barely moves the needle. Audit, defer, or remove third-parties before further frontend optimization. Use Lighthouse's third-party audit to identify the worst offenders.

Source: web.dev

How third-party costs are calculated

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

Send Feedback