Performance
· 26 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.Performance-focused optimization plan with CWV assessment, top offenders, and time estimates
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
5.63 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
10.06 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
374 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.068
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
7.98 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.
10.16 s
Page Load Progression
FJS Execution CostAction6176ms total JS executionFIX
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://elmwoodlaw.com/wp-content/litespeed/js/ab742891b172cd995ec50e535fca166b.js?ver=a166b | 2043ms | 741ms | 18ms | 1st |
| https://elmwoodlaw.com/wp-includes/js/jquery/jquery.min.js | 1137ms | 496ms | 6ms | 1st |
| https://elmwoodlaw.com/wp-content/litespeed/js/906e3c2d74f8ac5ab882f82705b83cb7.js?ver=83cb7 | 725ms | 443ms | 43ms | 1st |
| https://elmwoodlaw.com/wp-content/litespeed/js/e3084f8196924fd9296551fdd225e9d6.js?ver=5e9d6 | 640ms | 68ms | 7ms | 1st |
| https://elmwoodlaw.com/ | 630ms | 82ms | 19ms | 1st |
| Unattributable | 515ms | 95ms | 0ms | 1st |
| https://www.googletagmanager.com/gtag/js?id=G-DV0E215XBV&cx=c>m=4e66f1 | 205ms | 155ms | 44ms | 3rd |
| https://www.googletagmanager.com/gtm.js?id=GTM-5H9VQ47J | 109ms | 86ms | 22ms | 3rd |
| https://elmwoodlaw.com/wp-content/litespeed/js/855f6ffc224d0462ed42531083a8a10f.js?ver=8a10f | 106ms | 62ms | 20ms | 1st |
| https://elmwoodlaw.com/wp-content/litespeed/js/83cd2238782b6a2ffe185a4902c89a9c.js?ver=89a9c | 66ms | 63ms | 3ms | 1st |
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
CPage Weight BudgetAction1.8 MB transferred, 110 requestsREVIEW
Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
JavaScript bundle is large — code-split routes and lazy-load off-screen components to defer.
Source: web.dev
Remove unused CSS rules with tools like PurgeCSS to reduce stylesheet size.
CSS bundle is large — purge unused styles (PurgeCSS, Tailwind JIT) to reduce CSS payload.
Source: web.dev
Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.
Source: web.dev
BImage Optimization23 images, 0 KB saveableREVIEW
CJS BundlesAction27 scripts, 298 KB unusedREVIEW
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://www.googletagmanager.com/gtag/js?id=G-DV0E215XBV&cx=c>m=4e66f1 | 160 KB | 65 KB (41%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtm.js?id=GTM-5H9VQ47J | 120 KB | 65 KB (54%) | ✓ | 3rd |
| https://elmwoodlaw.com/wp-content/litespeed/js/855f6ffc224d0462ed42531083a8a10f.js?ver=8a10f | 71 KB | 48 KB (67%) | ✓ | 1st |
| https://elmwoodlaw.com/wp-content/litespeed/js/906e3c2d74f8ac5ab882f82705b83cb7.js?ver=83cb7 | 102 KB | 40 KB (39%) | ✓ | 1st |
| https://elmwoodlaw.com/wp-content/litespeed/js/ab742891b172cd995ec50e535fca166b.js?ver=a166b | 59 KB | 30 KB (51%) | ✓ | 1st |
| https://elmwoodlaw.com/wp-content/litespeed/js/f36107bedec90cece1df61c5ed5a4521.js?ver=a4521 | 36 KB | 29 KB (82%) | ✓ | 1st |
| https://elmwoodlaw.com/wp-content/litespeed/js/6d1a2624583a0711970e4c959f6df5af.js?ver=df5af | 37 KB | 22 KB (58%) | ✓ | 1st |
| https://elmwoodlaw.com/wp-content/litespeed/js/efbc07ee19df0cea3ccbb9f8f0975fcd.js?ver=75fcd | 2 KB | — | ✓ | 1st |
| https://elmwoodlaw.com/wp-content/litespeed/js/83cd2238782b6a2ffe185a4902c89a9c.js?ver=89a9c | 13 KB | — | ✓ | 1st |
| https://elmwoodlaw.com/wp-content/litespeed/js/4f81231bf27105975e5da148824de27a.js?ver=de27a | 0 KB | — | ✓ | 1st |
Consider code splitting or tree shaking to reduce unused code.
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.
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.
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.
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.
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
BCompression AlgorithmMain response uses gzip; brotli would be ~20% smallerREVIEW
BMain HTML Cache-ControlNo Cache-Control header on main HTML responseREVIEW
CPage Weight InventoryAction110 resources · 1.8 MB · 298 KB savings availableREVIEW
~298.0 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 110 resources | 1.8 MiB | ||||||
A+Third-Party Impact16% third-party, 0 ms blockingPASS
A+Text CompressionAll text resources are compressedPASS
A+Font Loading4 fonts (176 KB)PASS
Web fonts
4
176 KB total
Render-blocking
0
of 4
Dominant font-display
swap
Most common across fonts
Font loading timeline
- Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
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 ~57 KB and ~114 ms
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource HintsNo optimization neededPASS
A+HTTP/3 (QUIC)HTTP/3 advertised via Alt-SvcPASS
A+LCP Image PreloadLCP preload audit not availablePASS
A+Server-Timing Observability1 Server-Timing entries advertisedPASS
A+Server Response Intelligence2 server-response signal(s) detectedPASS
A+Render-Blocking ResourcesNo render-blocking resources detectedPASS
A+Third-Party ResourcesNo third-party resources detectedPASS
AJavaScript Blocking1 JS blocking issue(s) detectedPASS
A+CSS Performance DepthNo CSS performance depth issues detectedPASS
A+Green HostingWhether the site is served from green-energy infrastructurePASS
Green Hosting
This site is hosted on green energy infrastructure
Provider: Kualo
Network Waterfall110 requests over 2505msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
Google Tag Manager www.googletagmanager.com | Tag Manager | 205ms | 160 KB | 41% | £2/mo | Costly |
Google Tag Manager www.googletagmanager.com | Tag Manager | 109ms | 120 KB | 54% | £1/mo | Optional |
These scripts may cost more than they're worth
- Google Tag Manager adds 205ms and costs ~£2/month
Google Tag Manager takes 205ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
54% of Google Tag Manager's code is unused. The script may be loading features you don't use.
Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.
Source: web.dev
Real-User Performance (CrUX)Field metrics from the Chrome User Experience ReportINFO
Chrome User Experience (CrUX)
Real-user metrics from the Chrome UX Report (2026-05-19 — 2026-06-15)
LCP (p75)
4523 ms
46% good
INP (p75)
129 ms
86% good
CLS (p75)
0.140
59% good
FCP (p75)
1892 ms
TTFB (p75)
1465 ms