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.
3.51 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
9.19 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
620 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.009
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.89 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.
9.19 s
Page Load Progression
DThird-Party ImpactAction100% third-party, 0 ms blockingFIX
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
BPage Weight Budget1.3 MB transferred, 31 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
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
CJS Execution CostAction1720ms total JS executionREVIEW
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://www.googletagmanager.com/gtag/js?id=G-BVVHFNW0ZT&cx=c>m=4e64h1 | 349ms | 284ms | 60ms | 3rd |
| https://www.texas.gov/ | 320ms | 11ms | 4ms | 3rd |
| https://www.texas.gov/framework-073c72e9d2e4c2490fcd.js | 270ms | 249ms | 18ms | 3rd |
| https://texas-gov.my.connect.aws/connectwidget/static/amazon-connect-chat-interface-client.js | 268ms | 166ms | 94ms | 3rd |
| https://www.googletagmanager.com/gtm.js?id=GTM-P3H2928 | 223ms | 166ms | 52ms | 3rd |
| Unattributable | 219ms | 7ms | 0ms | 3rd |
| https://www.google-analytics.com/analytics.js | 72ms | 61ms | 7ms | 3rd |
CJS BundlesAction13 scripts, 230 KB unusedREVIEW
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://texas-gov.my.connect.aws/connectwidget/static/amazon-connect-chat-interface-client.js | 196 KB | 105 KB (55%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtm.js?id=GTM-P3H2928 | 133 KB | 63 KB (48%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtag/js?id=G-BVVHFNW0ZT&cx=c>m=4e64h1 | 156 KB | 62 KB (40%) | ✓ | 3rd |
| https://www.texas.gov/app-f5aec5e54b493b7ac22a.js | 20 KB | — | ✓ | 3rd |
| https://www.texas.gov/styles-e9d24b1846c7d6eb9685.js | 0 KB | — | ✓ | 3rd |
| https://www.texas.gov/commons-25640115e8492352ba47.js | 26 KB | — | ✓ | 3rd |
| https://www.texas.gov/59086a9db22de0ac210aab17cb779fac9cb6e82f-ce919624506ba6e37093.js | 4 KB | — | ✓ | 3rd |
| https://www.texas.gov/2f4c15a58114e40d8f92c1442039dd265e3a3596-77b73c17bbeced749c6c.js | 20 KB | — | ✓ | 3rd |
| https://www.texas.gov/component---src-pages-index-tsx-ce6ef84e21c36c755464.js | 1 KB | — | ✓ | 3rd |
| https://cdnjs.cloudflare.com/polyfill/v3/polyfill.min.js?features=Promise%2CNodeList.prototype.forEach%2CElement.prototype.closest | 1 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
CPage Weight InventoryAction31 resources · 1.3 MB · 230 KB savings availableREVIEW
~230.3 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 31 resources | 1.3 MiB | ||||||
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
A+Text CompressionAll text resources are compressedPASS
AImage Optimization3 images, 0 KB saveablePASS
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
A+Font Loading4 fonts (430 KB)PASS
Web fonts
4
430 KB total
Render-blocking
0
of 4
Dominant font-display
swap
Most common across fonts
Font loading timeline
- 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 ~344 KB and ~688 ms
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource Hints14 hints, 0 missing preconnectsPASS
Current Resource Hints
14 resource hints configured
A+Render-Blocking ResourcesNo render-blocking resources detectedPASS
A+Third-Party ResourcesNo third-party resources detectedPASS
Network Waterfall31 requests over 2312msINFO
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 | 349ms | 156 KB | 40% | $1/mo | Costly |
www.texas.gov www.texas.gov | Other | 320ms | 36 KB | — | $1/mo | Costly |
www.texas.gov www.texas.gov | Other | 270ms | 40 KB | — | $1/mo | Costly |
texas-gov.my.connect.aws texas-gov.my.connect.aws | Other | 268ms | 196 KB | 55% | $1/mo | Costly |
Google Tag Manager www.googletagmanager.com | Tag Manager | 223ms | 133 KB | 48% | $1/mo | Costly |
Unattributable Unattributable | Other | 219ms | 0 KB | — | $1/mo | Costly |
Google Analytics www.google-analytics.com | Analytics | 72ms | 21 KB | — | $0/mo | Optional |
These scripts may cost more than they're worth
- Google Tag Manager adds 349ms and costs ~$1/month
- www.texas.gov adds 320ms and costs ~$1/month
- www.texas.gov adds 270ms and costs ~$1/month
- texas-gov.my.connect.aws adds 268ms and costs ~$1/month
- Google Tag Manager adds 223ms and costs ~$1/month
- Unattributable adds 219ms and costs ~$1/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
Google Tag Manager takes 349ms 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.texas.gov takes 320ms 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.texas.gov takes 270ms 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
texas-gov.my.connect.aws takes 268ms 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
55% of texas-gov.my.connect.aws'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
Google Tag Manager takes 223ms 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
Unattributable takes 219ms 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