Performance
· 15 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.
2.83 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
5.06 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
42 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.013
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.83 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.
5.67 s
Page Load Progression
FPage Weight BudgetAction6.7 MB transferred, 64 requestsFIX
Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
Image bandwidth is high — modern formats (WebP/AVIF) and resizing typically cut it 50%+.
Source: web.dev
Subset fonts to include only used characters, or switch to system font stacks.
Font payload is large — subset to used glyphs only, or fall back to system fonts (zero load time).
Source: web.dev font loading
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
DThird-Party ImpactAction100% third-party, 0 ms blockingFIX
DJS BundlesAction10 scripts, 460 KB unusedFIX
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://www.fbi.gov/++plone++production/++unique++2025-08-18T20:53:28.626929/default.js | 341 KB | 217 KB (65%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtag/js?id=G-CSLL4ZEK4L&cx=c>m=4e64h1 | 147 KB | 106 KB (72%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtag/js?id=G-CSLL4ZEK4L | 147 KB | 63 KB (43%) | ✓ | 3rd |
| https://www.fbi.gov/++plone++castle-advantage/libs/audioplayer/audioplayer.js | 60 KB | 39 KB (66%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtag/js?id=G-DBEM2FVVRF | 172 KB | 35 KB (38%) | ✓ | 3rd |
| https://www.fbi.gov/++theme++2025-05-16/new-frontpage/bootstrap/js/bootstrap.bundle.min.js | 24 KB | — | ✓ | 3rd |
| https://www.fbi.gov/++theme++2025-05-16/new-frontpage/frontpage.js | 1 KB | — | ✓ | 3rd |
| https://dap.digitalgov.gov/Universal-Federated-Analytics-Min.js?agency=DOJ&subagency=FBI | 9 KB | — | ✓ | 3rd |
| https://www.fbi.gov/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js? | 13 KB | — | ✓ | 3rd |
| https://dap.digitalgov.gov/web-vitals/dist/web-vitals.attribution.iife.js | 4 KB | — | ✓ | 3rd |
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
FPage Weight InventoryAction64 resources · 6.7 MB · 460 KB savings availableFIX
~460.2 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 64 resources | 6.7 MiB | ||||||
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
CImage OptimizationAction30 images, 0 KB saveableREVIEW
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
CJS Execution CostAction1017ms total JS executionREVIEW
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://www.fbi.gov/ | 245ms | 28ms | 2ms | 3rd |
| https://www.fbi.gov/++plone++production/++unique++2025-08-18T20:53:28.626929/default.js | 234ms | 166ms | 57ms | 3rd |
| Unattributable | 196ms | 3ms | 0ms | 3rd |
| https://www.googletagmanager.com/gtag/js?id=G-DBEM2FVVRF | 129ms | 103ms | 24ms | 3rd |
| https://www.fbi.gov/cdn-cgi/challenge-platform/scripts/jsd/main.js | 116ms | 110ms | 1ms | 3rd |
| https://www.googletagmanager.com/gtag/js?id=G-CSLL4ZEK4L | 97ms | 79ms | 17ms | 3rd |
A+Text CompressionAll text resources are compressedPASS
A+Font Loading6 fonts (2500 KB)PASS
Web fonts
6
2500 KB total
Render-blocking
0
of 6
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
- Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
- Convert to woff2 for ~30% smaller file size
- Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
- Convert to woff2 for ~30% smaller file size
- Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
- Convert to woff2 for ~30% smaller file size
- Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
- Convert to woff2 for ~30% smaller file size
- 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 ~1918 KB and ~3836 ms
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource HintsNo optimization neededPASS
A+Green HostingWhether the site is served from green-energy infrastructurePASS
Green Hosting
This site is hosted on green energy infrastructure
Provider: Cloudflare
Network Waterfall64 requests over 1532msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
www.fbi.gov www.fbi.gov | Other | 245ms | 11 KB | — | $3/mo | Costly |
www.fbi.gov www.fbi.gov | Other | 234ms | 341 KB | 65% | $3/mo | Costly |
Unattributable Unattributable | Other | 196ms | 0 KB | — | $3/mo | Optional |
Google Tag Manager www.googletagmanager.com | Tag Manager | 129ms | 172 KB | 38% | $2/mo | Optional |
www.fbi.gov www.fbi.gov | Other | 116ms | 0 KB | — | $2/mo | Optional |
Google Tag Manager www.googletagmanager.com | Tag Manager | 97ms | 147 KB | 43% | $1/mo | Optional |
These scripts may cost more than they're worth
- www.fbi.gov adds 245ms and costs ~$3/month
- www.fbi.gov adds 234ms and costs ~$3/month
100% of JavaScript execution time is spent on third-party scripts. Consider auditing which scripts are essential.
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
www.fbi.gov takes 245ms 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
www.fbi.gov takes 234ms 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
65% of www.fbi.gov'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