Skip to content
https://wordpress.org

Performance

· 16 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.
SCORE
88
GRADE
B
FIX
2
REVIEW
5
PASS
7
INFO
2

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

Mobile Desktop
67
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.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
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.

1.63 s

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

7.78 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

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

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

7.79 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
16
7 PASS 5 REVIEW 2 FIX
D
Third-Party Impact
Action
77% third-party, 0 ms blocking
FIX
77% third-party, 0 ms blocking
Warning::
Third-party code accounts for 77% of page weight (1.2 MiB of 1.5 MiB)
Info::
Third-party blocking time is low (0 ms)
23%
77%
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.

B
Page Weight Budget
1.5 MB transferred, 48 requests
REVIEW
1.5 MB transferred, 48 requests
Info::
Page weighs 2.5 MB (1.5 MB transferred)
Info::
48 HTTP requests
Info::
Estimated 0.32 g CO2 per page load
1.5 MB / 2.4 MB budget
1.5 MB transferred
48 requests
0.32 g CO2 per page load
Images 884.7 KiB 57%
JavaScript 319.8 KiB 21%
Fonts 184.6 KiB 12%
CSS 117.2 KiB 8%
HTML 31.2 KiB 2%
Other 1.7 KiB 0%
Other 1.2 KiB 0%
0 2.4 MB 4.9 MB
Approaching limit
B
Image Optimization
19 images, 0 KB saveable
REVIEW
19 images, 0 KB saveable
Info::
All images are well-optimized
19 images 885 KB
0 oversized -0 KB
6 legacy format
0 missing dimensions CLS risk
B
JS Execution Cost
884ms total JS execution
REVIEW
884ms total JS execution
Warning::
https://www.googletagmanager.com/gtm.js?id=GTM-P24...: 279ms CPU time
Warning::
https://www.googletagmanager.com/gtag/js?id=G-CG6G...: 268ms CPU time
Info::
Unattributable: 230ms CPU time
Info::
https://wordpress.org/: 107ms CPU time
Warning::
Third-party scripts: 777ms (88% of total)

Main Thread Breakdown

Script Evaluation 40% Other 28% Style & Layout 13% Parse HTML & CSS 9% Script Parsing & Compilation 8%
ScriptTotalScriptingParse/CompileParty
https://www.googletagmanager.com/gtm.js?id=GTM-P24PF4B279ms139ms30ms3rd
https://www.googletagmanager.com/gtag/js?id=G-CG6GJ50G8J&cx=c&gtm=4e6431268ms210ms45ms3rd
Unattributable230ms6ms0ms3rd
https://wordpress.org/107ms6ms3ms1st
B
JS Bundles
10 scripts, 131 KB unused
REVIEW
10 scripts, 131 KB unused
Warning::
https://www.googletagmanager.com/gtag/js?id=G-CG6G...: 67 KB unused (39%)
Consider code splitting or tree shaking to reduce unused code.
Warning::
https://www.googletagmanager.com/gtm.js?id=GTM-P24...: 64 KB unused (49%)
Consider code splitting or tree shaking to reduce unused code.
Info::
Total unused JavaScript: 131 KB
131 KB unused JavaScript

Downloaded but never executed on this page.

ScriptSizeUnusedMinifiedParty
https://www.googletagmanager.com/gtag/js?id=G-CG6GJ50G8J&cx=c&gtm=4e6431171 KB67 KB (39%)✓3rd
https://www.googletagmanager.com/gtm.js?id=GTM-P24PF4B131 KB64 KB (49%)✓3rd
https://wordpress.org/wp-content/mu-plugins/pub-sync/blocks/language-suggest/build/front.js?ver=6f71d5ef610256d46dec1 KB—✓1st
https://wordpress.org/wp-content/plugins/gutenberg/build/modules/interactivity/index.min.js?ver=4d2a3a72c7410d54888115 KB—✓1st
https://wordpress.org/wp-content/plugins/gutenberg/build/modules/block-library/navigation/view.min.js?ver=96a846e1d7b789c39ab9-202403080 KB—✓1st
https://wordpress.org/wp-content/mu-plugins/pub-sync/blocks/time/build/view.js?ver=385bfe9134bf98c52dda0 KB—✓1st
https://stats.wp.com/e-202615.js2 KB—✓3rd
https://wordpress.org/wp-content/mu-plugins/pub-sync/blocks/global-header-footer/js/view.js?ver=17513359060 KB—✓1st
blob:https://wordpress.org/9e34d963-73c1-407f-8b85-103bb6b97b09-0 KB—✓3rd
https://wordpress.org/wp-includes/js/wp-emoji-release.min.js?ver=7.1-alpha-622130 KB—✓1st

Consider code splitting or tree shaking to reduce unused code.

Why this matters

This bundle has high unused code — code-split or tree-shake to ship only what executes.

Source: web.dev / Lighthouse coverage

Consider code splitting or tree shaking to reduce unused code.

Why this matters

This bundle has high unused code — code-split or tree-shake to ship only what executes.

Source: web.dev / Lighthouse coverage

C
Green Hosting
Action
Whether the site is served from green-energy infrastructure
REVIEW

Green Hosting

No green hosting detected

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+
Font Loading
3 fonts (185 KB)
PASS
3 fonts (185 KB)
Info::
3 font(s) use font-display: swap (FOUT risk but functional)

Web fonts

3

185 KB total

Render-blocking

0

of 3

Dominant font-display

swap

Most common across fonts

Font loading timeline
Transfer FOIT (block) FOUT (swap)
0 ms 1.0 s 2.0 s 3.0 s 4.0 s 5.0 s 6.0 s 7.0 s 8.0 s FCP 1.6 s LCP 7.8 shttps://wordpress.org/wp-content/mu-plugins/pub-sync/global-fonts/Inter/Inter-latin.woff2Inter-latin.woff2 https://wordpress.org/wp-content/mu-plugins/pub-sync/global-fonts/Inter/Inter-latin.woff2 — 76.0 KiB — 0 ms — font-display: swaphttps://wordpress.org/wp-content/mu-plugins/pub-sync/global-fonts/EB-Garamond/EBGaramond-latin.woff2EBGaramond-latin.woff2 https://wordpress.org/wp-content/mu-plugins/pub-sync/global-fonts/EB-Garamond/EBGaramond-latin.woff2 — 108.5 KiB — 0 ms — font-display: swaphttps://wordpress.org/wp-content/mu-plugins/pub-sync/global-fonts/Inter/Inter-arrows.woff2Inter-arrows.woff2 https://wordpress.org/wp-content/mu-plugins/pub-sync/global-fonts/Inter/Inter-arrows.woff2 — 70 B — 0 ms — font-display: swap
Inter-latin.woff2 woff2 swap
Size 76 KB
Load time 0 ms
Start 0 ms
Risk FOUT — text flashes from fallback to web font
EBGaramond-latin.woff2 woff2 swap
Size 108 KB
Load time 0 ms
Start 0 ms
Risk FOUT — text flashes from fallback to web font
  • Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
Inter-arrows.woff2 woff2 swap
Size 0 KB
Load time 0 ms
Start 0 ms
Risk FOUT — text flashes from fallback to web font
Optimization checklist
  • Preload critical fonts (priority=high)
  • Use woff2 format for all fonts
  • Set font-display to swap, optional, or fallback
  • Subset large fonts (≤100 KB each)

Fixing the unchecked items could save ~54 KB and ~108 ms

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
8 hints, 0 missing preconnects
PASS
8 hints, 0 missing preconnects
Info::
Page uses 8 resource hint(s)

Current Resource Hints

preconnect
3
preload
2
dns-prefetch
3
prefetch
—

8 resource hints configured

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
Network Waterfall
48 requests over 0ms
INFO

Performance analysis not available for this result.

Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
88% of JavaScript execution is third-party
First-party Third-party 777ms · 302KB · $10/mo
Google Tag Manager
Tag Manager
Costly
Execution 279ms
Transfer 131 KB
Unused 49%
Monthly Cost $4/mo
Google Tag Manager
Tag Manager
Costly
Execution 268ms
Transfer 171 KB
Unused 39%
Monthly Cost $4/mo
Unattributable
Other
Costly
Execution 230ms
Transfer 0 KB
Monthly Cost $3/mo

These scripts may cost more than they're worth

  • Google Tag Manager adds 279ms and costs ~$4/month
  • Google Tag Manager adds 268ms and costs ~$4/month
  • Unattributable adds 230ms and costs ~$3/month

88% 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

Google Tag Manager takes 279ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.

Why this matters

This script has high main-thread execution time — optimize hot paths or defer.

Source: web.dev

Google Tag Manager takes 268ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.

Why this matters

This script has high main-thread execution time — optimize hot paths or defer.

Source: web.dev

Unattributable takes 230ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.

Why this matters

This script has high main-thread execution time — optimize hot paths or defer.

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