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.04 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
7.00 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
13 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.
3.90 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.19 s
Page Load Progression
FPage Weight BudgetAction19.8 MB transferred, 151 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
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
DThird-Party ImpactAction100% third-party, 0 ms blockingFIX
FJS BundlesAction66 scripts, 393 KB unusedFIX
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://assets.adobedtm.com/2d251f50426c/e52f833be42a/launch-EN26af1ee4ef084984926fd80d1cb93835.min.js | 277 KB | 85 KB (31%) | ✓ | 3rd |
| https://js-cdn.dynatrace.com/jstag/16294a69b33/ruxitagent_A2QSVfhqru_10223210811140219.js | 88 KB | 77 KB (88%) | ✓ | 3rd |
| https://www.esri.com/etc.clientlibs/esri-sites/clientlibs/clientlib-dependencies.js | 83 KB | 51 KB (62%) | ✗ | 3rd |
| https://cdn.mouseflow.com/projects/3eb3135f-f8a5-4a4a-b8bd-122bc5d300b0.js | 65 KB | 48 KB (74%) | ✓ | 3rd |
| https://connect.facebook.net/en_US/fbevents.js | 97 KB | 47 KB (49%) | ✓ | 3rd |
| https://webapps-cdn.esri.com/CDN/components/global-nav/js/gn.js | 114 KB | 45 KB (40%) | ✓ | 3rd |
| https://www.esri.com/etc.clientlibs/esri-sites/clientlibs/components.js | 52 KB | 38 KB (73%) | ✗ | 3rd |
| https://js.arcgis.com/calcite-components/1.8.0/p-349ad3f8.js | 1 KB | — | ✓ | 3rd |
| https://js.arcgis.com/calcite-components/1.8.0/p-b20009dc.js | 1 KB | — | ✓ | 3rd |
| https://webapps-cdn.esri.com/CDN/packages/instant.page/instantpage.min.js | 2 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
DPage Weight InventoryAction151 resources · 19.8 MB · 393 KB savings availableFIX
~392.9 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 151 resources | 19.8 MiB | ||||||
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
BImage Optimization38 images, 0 KB saveableREVIEW
BJS Execution Cost582ms total JS executionREVIEW
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| Unattributable | 192ms | 16ms | 0ms | 3rd |
| https://www.esri.com/en-us/home | 160ms | 5ms | 1ms | 3rd |
| https://assets.adobedtm.com/2d251f50426c/e52f833be42a/launch-EN26af1ee4ef084984926fd80d1cb93835.min.js | 133ms | 101ms | 25ms | 3rd |
| https://webapps-cdn.esri.com/CDN/components/global-nav/js/gn.js | 98ms | 77ms | 7ms | 3rd |
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
A+Text CompressionAll text resources are compressedPASS
A+Font Loading3 fonts (58 KB)PASS
Web fonts
3
58 KB total
Render-blocking
0
of 3
Dominant font-display
swap
Most common across fonts
Font loading timeline
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)
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource HintsNo optimization neededPASS
Network Waterfall151 requests over 3193msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
Unattributable Unattributable | Other | 192ms | 0 KB | — | $3/mo | Optional |
www.esri.com www.esri.com | Other | 160ms | 12 KB | — | $2/mo | Optional |
assets.adobedtm.com assets.adobedtm.com | Other | 133ms | 277 KB | 31% | $2/mo | Optional |
webapps-cdn.esri.com webapps-cdn.esri.com | Other | 98ms | 114 KB | 40% | $1/mo | Optional |
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