storeallpurpose.com — Prepared Feb 19, 2026
Hi team,
We've completed a full site speed analysis across storeallpurpose.com — the homepage and all 81 facility/location pages. The results show a critical mobile performance problem that's directly impacting our ability to convert visitors into renters.
Full detailed report with per-page data is attached as PDF. Here's the summary.
63% of our website traffic comes from mobile devices. The average mobile performance score is 38 out of 100. Zero facility pages pass Google's Core Web Vitals. Our facility pages take an average of 9 seconds to load main content on mobile — Google's research shows this causes a 123% increase in bounce probability vs a 1-second load.
When a customer searches "storage units near me" on their phone and clicks through to one of our location pages, they wait 9 seconds before the main content appears and 23 seconds before they can actually interact with the page (tap buttons, fill out forms, etc.).
Most of them leave before the page finishes loading. Google's data from 11 million mobile page loads shows:
| Load Time | Bounce Increase | What It Means |
|---|---|---|
| 1 → 3 seconds | +32% | Losing 1 in 3 extra visitors |
| 1 → 5 seconds | +90% | Nearly double the bounces |
| 1 → 7 seconds | +113% | More than double |
| 1 → 9 seconds | +123% | APS is here |
| Metric | Mobile | Desktop | Target | Status |
|---|---|---|---|---|
| Performance Score | 42 | 63 | 90+ | POOR |
| Largest Contentful Paint | 5.9s | 1.4s | <2.5s | FAIL |
| Time to Interactive | 24.1s | 5.2s | <7.3s | FAIL |
| Total Blocking Time | 1,631ms | 1,374ms | <200ms | FAIL |
| Layout Shift (CLS) | 0.001 | 0.004 | <0.1 | PASS |
| Server Response (TTFB) | 178ms | 174ms | <800ms | PASS |
Key insight: The server responds fast (178ms TTFB). This is not a hosting or server problem. The bottleneck is client-side — heavy JavaScript, unoptimized images, and render-blocking resources. Desktop is significantly better because desktop devices have more processing power to handle the bloated page.
These are the location pages getting the most customer traffic. Their mobile speed matters most:
| Facility | Sessions (90d) | Mobile Score | LCP | Bounce Rate |
|---|---|---|---|---|
| Westmoreland, NH | 1,205 | 40 | 14.0s | 55.9% |
| Tilton, NH | 1,116 | 37 | 8.5s | 54.8% |
| S Burlington, VT | 992 | 36 | 6.8s | 33.0% |
| Lincolnville, ME | 978 | 41 | 7.5s | 57.5% |
| Poland, ME | 816 | 40 | 7.6s | 33.8% |
| Belmont, ME | 793 | 43 | 7.3s | 41.2% |
| Swannanoa, NC | 792 | 41 | 7.1s | 49.3% |
| Waterboro, ME | 756 | 36 | 11.3s | 28.3% |
| Hinsdale, NH | 734 | 39 | 8.3s | 30.2% |
| Warwick, RI | 694 | 42 | 7.0s | 51.8% |
Full data for all 81 pages in the attached PDF report.
We estimate fixing mobile speed from 9s to under 3s could recover $140,000 - $280,000/year in additional lifetime revenue from visitors who currently bounce before the page loads.
The math: Google shows ~32% bounce increase at 3s vs ~123% at 9s. At 555 sessions/day, 63% mobile, recovering even 10-20% of excess mobile bounces at our current 2.64% conversion rate and $1,314 average customer lifetime value gets us to that range.
Please action the P1 items first (LCP, TBT, TTI) — these are the highest impact. Specifically:
1. Image optimization — Convert to WebP/AVIF, implement lazy loading, serve responsive sizes. This should be quick.
2. JavaScript audit — Defer or remove non-critical scripts. Provide a breakdown of all third-party scripts on facility pages so we can decide what stays.
3. Render-blocking resources — Inline critical CSS, async/defer JS bundles.
4. Timeline — Let us know your timeline for the P1 fixes. We'll re-run the PageSpeed tests after to measure improvement.
Full report for all 81 pages is attached.
Thanks,
JC
All Purpose Storage