Technical Performance Audit · Mobile
TrooPerformance Audit Report · getsmylo.com
A mobile-only PageSpeed Insights audit across the product page and best-sellers collection page, with prioritized opportunities and a recommended remediation plan.
Executive summary
Real-user (CrUX) field data shows Core Web Vitals passing on both pages, LCP around 2.1s, INP under 200ms, CLS well inside the "good" range. That reflects returning visitors on cached pages. A fresh, cold mobile load, the exact experience for new visitors from Shark Tank coverage and paid traffic, tells a different story: the PDP scores 50/100 and the collection page 44/100 on Lighthouse, with Largest Contentful Paint as high as 16.9 seconds on the PDP.
The gap is explained by page weight and script load: both pages ship 5.2-6.5 MB per load, with up to 1 MB of unused JavaScript and inefficient image delivery and caching. None of this requires a redesign, it's a well-understood optimization pass.
44-50
Mobile performance score (lab)
16.9s
PDP Largest Contentful Paint (lab)
6.4 MB
PDP total page weight
Passed
Core Web Vitals, real-user field data
Performance scores
Product page· combo-pack-adult-1
Collection page· value-pack (best sellers)
Core Web Vitals & key metrics (lab, cold mobile load)
Metric
Product page
Collection page
Google "good"
Largest Contentful Paint
16.9s
13.7s
≤2.5s
First Contentful Paint
2.9s
5.8s
≤1.8s
Total Blocking Time
470ms
360ms
≤200ms
Cumulative Layout Shift
0.012
0.146
≤0.1
Field data (real users, CrUX, 28-day)
Metric
Product page
Collection page
Google "good"
Largest Contentful Paint
2.1s
2.1s
≤2.5s
Interaction to Next Paint
183ms
185ms
≤200ms
Cumulative Layout Shift
0.09
0.06
≤0.1
Prioritized opportunities
Ranked by impact across both pages. Estimated savings are PageSpeed Insights-measured figures (product page / collection page where both apply).
#
Opportunity
Est. saving
Priority
1
Reduce total page weight
Total transfer measured at 6,580 KiB (PDP) and 5,325 KiB (collection), very heavy for a mobile load. Audit and trim the largest assets.
6.4 / 5.2 MB
CRITICAL
2
Improve image delivery
Right-size, compress and serve next-gen formats across PDP gallery and collection grid images.
1,442 / 173 KiB
HIGH
3
Reduce unused JavaScript
Ship less JS up front via code-splitting and deferring non-critical bundles and apps.
952 / 1,039 KiB
HIGH
4
Use efficient cache lifetimes
Longer cache TTLs on static assets cut repeat-visit load and origin requests.
818 KiB (both)
HIGH
5
Render-blocking requests
Defer or inline critical CSS/JS so the page can start painting sooner.
450 / 300 ms
MEDIUM
6
Minimize main-thread work
Heavy scripting keeps the main thread busy and delays interactivity.
5.6 / 4.3s
MEDIUM
7
Reduce JavaScript execution time
Parsing, compiling and executing JS is a top contributor to blocking time.
2.9 / 2.2s
MEDIUM
8
Reduce unused CSS
Trim unused stylesheet rules shipped on every load.
56 / 45 KiB
LOW
9
Legacy & duplicated JavaScript
Drop transpiled polyfills and duplicate bundles not needed by modern browsers.
47 / 12-30 KiB
LOW
10
Layout shift culprits & forced reflow
Address the collection page's 0.146 CLS and clean up forced reflow on both pages.
Collection CLS 0.146
LOW
Accessibility & best practices
Accessibility 79 / 90 (PDP/Collection)
- PDP: buttons and links without a discernible name
- PDP: touch targets below recommended size / spacing
- PDP: ARIA roles missing required child roles
- Both pages: background/foreground contrast ratio insufficient
- Collection scores 90, PDP 79, gap is concentrated on the PDP
Best practices 54 / 54 (PDP/Collection)
- Deprecated API warning on both pages
- Third-party cookies detected on both pages
- Browser errors logged to the console
- Trust & Safety items (CSP, HSTS, COOP, Trusted Types) to review
- Identical 54/100 score on both pages, a site-wide pattern, not one-off
Methodology & caveats
Read these numbers honestly
These are lab results from Google PageSpeed Insights (Lighthouse 13.4.1, mobile, Moto G Power emulation, Slow 4G throttling), captured Aug 12, 2026. This is a deliberately harsh, cold-load simulation, not what most real visitors experience.
The same reports include field data from the Chrome UX Report (real users, 28-day rolling window): Core Web Vitals pass on both pages there, LCP around 2.1s. That's returning traffic on cached pages. The lab numbers above are what a brand-new visitor, someone clicking a paid ad or arriving fresh off Shark Tank coverage, actually experiences on a cold load with an empty cache.
Treat the lab numbers as a directional first pass on new-visitor experience specifically. The consistent, high-confidence signals (heavy page weight, unused JS, and image delivery) are real and worth acting on regardless of which number you look at.
Recommended plan
1
Confirm scope
Extend this baseline across the homepage and other key templates.
2
Optimize
Fix page weight, unused JS, images, caching, and render-blocking.
3
QA
Manual checks to protect functionality and compliance.
4
Before / after
Re-run lab and field data to confirm the actual gain.
75+
Target performance score
≤2.5s
Mobile LCP into the green
2X
Typical load-speed gain
Scope note
A separate app/plugin audit will be shared covering third-party apps and integrations in more detail.
Some fixes depend on third-party apps and platforms that are outside our direct control. Where that's the case, we'll do everything possible to optimise within those constraints, and recommend lighter-weight alternatives where the app itself is the bottleneck.