Performance
· 17 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.
4.92 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
65.68 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
285 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.138
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
10.24 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.
71.17 s
Page Load Progression
FPage Weight BudgetAction28.1 MB transferred, 119 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
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
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
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
DJS Execution CostAction3374ms total JS executionFIX
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| Unattributable | 1468ms | 26ms | 0ms | 3rd |
| https://illinois.edu/ | 821ms | 38ms | 8ms | 1st |
| https://www.googletagmanager.com/gtag/js?id=GT-KTPV7C3 | 450ms | 349ms | 86ms | 3rd |
| https://www.googletagmanager.com/gtm.js?id=GTM-5SX53NV7 | 212ms | 171ms | 40ms | 3rd |
| https://cdn.toolkit.illinois.edu/3.7.0/toolkit.js | 205ms | 36ms | 25ms | 3rd |
| https://illinois.edu/wp-content/themes/illinois/js/search.js | 80ms | 54ms | 25ms | 1st |
| https://onetrust.techservices.illinois.edu/scripttemplates/otSDKStub.js | 78ms | 10ms | 2ms | 3rd |
| https://illinois.edu/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 | 60ms | 48ms | 10ms | 1st |
CImage OptimizationAction63 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
CJS BundlesAction18 scripts, 258 KB unusedREVIEW
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://www.googletagmanager.com/gtm.js?id=GTM-5SX53NV7 | 125 KB | 65 KB (52%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtag/js?id=GT-KTPV7C3 | 157 KB | 65 KB (41%) | ✓ | 3rd |
| https://illinois.edu/wp-content/themes/illinois/js/search.js | 72 KB | 45 KB (63%) | ✓ | 1st |
| https://cdn.disability.illinois.edu/skipto.min.js | 95 KB | 36 KB (38%) | ✓ | 3rd |
| https://cdn.toolkit.illinois.edu/3.7.0/toolkit.js | 55 KB | 24 KB (44%) | ✓ | 3rd |
| https://illinois.edu/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 | 35 KB | 23 KB (67%) | ✓ | 1st |
| https://illinois.edu/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1 | 6 KB | — | ✓ | 1st |
| https://illinois.edu/wp-content/themes/illinois/js/skiptoconf.js?ver=6.8.3 | 1 KB | — | ✓ | 1st |
| https://cdn.brand.illinois.edu/components/il-footer.mjs | 9 KB | — | ✓ | 3rd |
| https://onetrust.techservices.illinois.edu/scripttemplates/otSDKStub.js | 6 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
CPage Weight InventoryAction119 resources · 28.1 MB · 258 KB savings availableREVIEW
~257.9 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 119 resources | 28.1 MiB | ||||||
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
BHTTP Cachingno-cache, privateREVIEW
no-cache, private
| Directive | Value | Meaning |
|---|---|---|
| no-cache | — | Cache but always revalidate first |
| private | — | Only browser cache, not CDN/proxy |
A+Third-Party Impact4% third-party, 0 ms blockingPASS
A+Text CompressionAll text resources are compressedPASS
A+Font Loading2 fonts (217 KB)PASS
Web fonts
2
217 KB total
Render-blocking
0
of 2
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 ~67 KB and ~134 ms
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource Hints6 hints, 0 missing preconnectsPASS
Current Resource Hints
6 resource hints configured
A+Render-Blocking ResourcesNo render-blocking resources detectedPASS
A+Third-Party ResourcesNo third-party resources detectedPASS
Network Waterfall119 requests over 6004msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
Unattributable Unattributable | Other | 1468ms | 0 KB | — | $25/mo | Costly |
Google Tag Manager www.googletagmanager.com | Tag Manager | 450ms | 157 KB | 41% | $8/mo | Costly |
Google Tag Manager www.googletagmanager.com | Tag Manager | 212ms | 125 KB | 52% | $4/mo | Costly |
cdn.toolkit.illinois.edu cdn.toolkit.illinois.edu | Other | 205ms | 55 KB | 44% | $4/mo | Costly |
onetrust.techservices.illinois.edu onetrust.techservices.illinois.edu | Other | 78ms | 6 KB | — | $1/mo | Optional |
These scripts may cost more than they're worth
- Unattributable adds 1468ms and costs ~$25/month
- Google Tag Manager adds 450ms and costs ~$8/month
- Google Tag Manager adds 212ms and costs ~$4/month
- cdn.toolkit.illinois.edu adds 205ms and costs ~$4/month
72% 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
Unattributable takes 1468ms 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
Google Tag Manager takes 450ms 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
Google Tag Manager takes 212ms 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
52% 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
cdn.toolkit.illinois.edu 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