Technical Performance Audit
TrooPerformance Audit Report · www.vestwell.com
A combined TrooPerformance agent audit across desktop and mobile profiles, with prioritized opportunities and a recommended remediation plan.
Executive summary
vestwell.com is a well-built, modern site with perfect SEO and strong accessibility. The opportunity is squarely in performance: the page ships a heavy payload, carries a large amount of unused and un-minified JavaScript, and a mobile Largest Contentful Paint of 3.7s sits above Google's 2.5s "good" threshold. On the phones most savers use, that delay is the lived experience.
The good news: most of the headroom is in well-understood, fast wins (payload reduction, JavaScript trimming, image delivery, and caching), none of which require a redesign. Cumulative Layout Shift is already excellent.
~15.6 MB
Total page payload (desktop)
718 KiB
Unused JS (desktop)
3.7s
Mobile LCP vs 2.5s target
Performance scores
Desktop· custom throttling
Mobile· Moto G Power · Slow 4G
Core Web Vitals & key metrics
Metric
Desktop
Mobile
Google "good"
Largest Contentful Paint
1.6s
3.7s
≤2.5s
First Contentful Paint
1.1s
2.3s
≤1.8s
Total Blocking Time
610ms
170ms
≤200ms
Cumulative Layout Shift
0.017
0.005
≤0.1
Prioritized opportunities
Ranked by impact across both profiles. Estimated savings are agent-measured figures (desktop / mobile where both apply).
#
Opportunity
Est. saving
Priority
1
Reduce total page payload
Total transfer measured at ~15,630 KiB on desktop, very heavy for a marketing page. Audit and trim the largest assets.
~15.6 MB total
CRITICAL
2
Reduce unused JavaScript
Ship less JS up front via code-splitting and deferring non-critical bundles.
718 / 192 KiB
HIGH
3
Minimize main-thread work
Heavy scripting keeps the main thread busy and delays interactivity, especially on mobile.
4.4 / 4.7s
HIGH
4
Reduce JavaScript execution time
Parsing, compiling and executing JS is a top contributor to blocking time.
1.9 / 1.5s
HIGH
5
Use efficient cache lifetimes
Longer cache TTLs on static assets cut repeat-visit load and origin requests.
195 KiB
MEDIUM
6
Improve image delivery
Right-size, compress and serve next-gen formats for hero and content imagery.
80 KiB
MEDIUM
7
Minify JavaScript
Straightforward build-step win across bundles.
106 / 59 KiB
MEDIUM
8
Reduce long main-thread tasks
Break up long tasks (2 on desktop, 9 on mobile) to keep the page responsive.
2 / 9 tasks
MEDIUM
9
Remove legacy JavaScript
Drop transpiled polyfills not needed by modern browsers.
36 / 12 KiB
LOW
10
Forced reflow & non-composited animations
Avoid layout thrash and move animations onto the compositor.
1 element
LOW
Accessibility & best practices
Accessibility 93 / 93
- Some links lack a discernible name (screen-reader clarity)
- Image elements with alt text that duplicates nearby text
- Touch targets below recommended size / spacing
- Video
<track kind="captions"> present, good
- 10 items flagged for manual review
Best practices 54 / 100
- Deprecated API warning (1) on the desktop run
- 50 third-party cookies detected
- Browser errors logged to the console
- Trust & Safety items (CSP, HSTS, COOP, Trusted Types) to review
- Mobile run scored 100; see variance note below
Methodology & caveats
Read these numbers honestly
These are lab results from the TrooPerformance agent, not field data. The two runs use different conditions (desktop on custom throttling, mobile on a Moto G Power over Slow 4G), which is why the desktop performance score (59) and mobile (82) differ, and why Best Practices reads 54 on one run and 100 on the other.
Both runs flagged stored data (IndexedDB) that can affect loading scores, so a clean incognito capture is recommended for a reliable baseline.
Treat this as a directional first pass. The consistent, high-confidence signals (heavy payload, unused JS, and mobile LCP above threshold) are real and worth acting on. Pairing a clean baseline with CrUX / real-user field data would give the definitive picture.
Recommended plan
1
Clean baseline
Clean incognito crawl + CWV across key templates; pull field data.
2
Optimize
Payload, unused JS, images, caching, main-thread work.
3
QA
Manual checks; protect functionality and compliance.
4
Before / after
Speed comparison + third-party script impact ranking.
90+
Target performance score
≤2.5s
Mobile LCP into the green
2X
Typical load-speed gain