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.
1.71 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.51 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
34 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.
1.71 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.
2.51 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.
CImage OptimizationAction4 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
CJS BundlesAction8 scripts, 278 KB unusedREVIEW
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://www.googletagmanager.com/gtag/js?id=G-2C0WZ1JHG0&cx=c>m=4e64k0h1 | 158 KB | 67 KB (42%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtag/js?id=G-HXP006LBGY&cx=c>m=4e64k0h1 | 156 KB | 67 KB (43%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtm.js?id=GTM-KHBDBW7 | 134 KB | 62 KB (47%) | ✓ | 3rd |
| https://www.shinyapps.io/admin/components/jquery/dist/jquery.min.js | 88 KB | 53 KB (60%) | ✓ | 3rd |
| https://www.shinyapps.io/admin/components/bootstrap/dist/js/bootstrap.min.js | 39 KB | 29 KB (75%) | ✓ | 3rd |
| https://cdn.jsdelivr.net/npm/search-insights@2.2.1 | 3 KB | — | ✓ | 3rd |
| https://www.shinyapps.io/scripts/lib/smooth-scroll.js | 1 KB | — | ✓ | 3rd |
| https://www.shinyapps.io/scripts/main.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
BPage Weight Inventory25 resources · 1.0 MB · 278 KB savings availableREVIEW
~277.9 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 25 resources | 1.0 MiB | ||||||
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
APage Weight Budget1.0 MB transferred, 25 requestsPASS
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
A+Text CompressionAll text resources are compressedPASS
A+JS Execution Cost222ms total JS executionPASS
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://www.googletagmanager.com/gtag/js?id=G-2C0WZ1JHG0&cx=c>m=4e64k0h1 | 81ms | 67ms | 9ms | 3rd |
| https://www.googletagmanager.com/gtag/js?id=G-HXP006LBGY&cx=c>m=4e64k0h1 | 78ms | 52ms | 10ms | 3rd |
| https://www.shinyapps.io/ | 63ms | 2ms | 1ms | 3rd |
A+Font Loading2 fonts (106 KB)PASS
Web fonts
2
106 KB total
Render-blocking
0
of 2
Dominant font-display
swap
Most common across fonts
Font loading timeline
- Convert to woff2 for ~30% smaller file size
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 ~19 KB and ~38 ms
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource HintsNo optimization neededPASS
Network Waterfall25 requests over 1181msINFO
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 | 81ms | 158 KB | 42% | $1/mo | Optional |
Google Tag Manager www.googletagmanager.com | Tag Manager | 78ms | 156 KB | 43% | $1/mo | Optional |
www.shinyapps.io www.shinyapps.io | Other | 63ms | 27 KB | — | $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