Compose a low bandwidth UX audit anticipating 2G conditions with progressive JPEGs,…
- User
Compose a low bandwidth UX audit anticipating 2G conditions with progressive JPEGs, offline flows, and caching policies.
- Assistant
Low Bandwidth UX Audit: Anticipating 2G Conditions
Sherlock AI Report
Trailblazer Labs | Case File: LB-UX-2G-001
Date: Current AnalysisExecutive Summary
This audit evaluates UX resilience for 2G networks (~50-100 kbps, 500ms RTT latency), where users experience prolonged load times, frequent drops, and data poverty. Focus areas: progressive JPEGs for perceived speed, offline flows for zero-connectivity grace, and caching policies for instant cache hits.
Key Findings Template:
- Score: [Pending site audit] /100 (Green: >90, Yellow: 70-89, Red: <70)
- Risks: 2G users abandon 70% faster; aim for TTI <10s, LCP <5s under throttle.
- Priorities: Implement PWA shell + SW caching (80% uplift), progressive images (50% perceived speed gain).
- ROI: 20-40% retention boost in emerging markets.
Test via Chrome DevTools (2G Slow preset), Lighthouse (throttled), WebPageTest (GSM profile).
Audit Checklist
Use this as a scannable scorecard. Mark ✅ Pass, ⚠️ Warn, ❌ Fail per item.
1. Image Optimization (Progressive JPEGs)
Images dominate payloads; progressive JPEGs render blurry-to-sharp, masking latency.
- Progressive JPEG Enforcement: All hero/product images use
progressive: true(e.g., Sharp/ImageMagick). Verify viajpeginfoCLI or browser inspect. Target: 100% compliance. - Format Cascade: JPEG > WebP/AVIF (via
<picture>). Sizes: 50-200KB max, responsivesrcset(e.g., 320w, 640w). Lazy-load non-LCP:loading="lazy". - Placeholder Strategy: Low-res CSS placeholders (
background: url(tiny.jpg)blurred) or LQIP (10KB base64). - Metrics: LCP <3s on 2G; image waterfalls <2s cumulative.
- Action: Audit with ImageOptim/Squoosh; automate via build (Webpack/Vite plugin).
2. Caching Policies (Service Workers & Cache API)
Cache static assets for offline/edge hits; network-fallback for fresh data.
- SW Registration:
navigator.serviceWorker.register('/sw.js')withscope: '/'. Update strategy:staleWhileRevalidate. - Cache Policies (Runtime/Network):
Asset Type Policy TTL Rationale App Shell (HTML/CSS/JS) Cache-First 30 days Instant shell render. Images/Fonts Cache-First 7 days Progressive JPEGs shine here. API/Data Network-First (w/ 400ms timeout → cache) Session Freshness > speed. User-Specific Cache-Only (post-sync) Until logout Offline queuing. - Cache Busting: Versioned URLs (
/v1.2/bundle.js);Cache-Control: max-age=.... - Storage Check:
navigator.storage.estimate(); evict on quota (prioritize critical). - Metrics: First Input Delay <100ms from cache; 90% assets cached (Lighthouse Audit).
- Action: Boilerplate SW.js via Workbox (Google lib); test
chrome://inspect/#service-workers.
3. Offline Flows (PWA Resilience)
Graceful degradation: No connection ≠ broken UX.
- App Shell Model: Cache minimal UI (header/nav/content skeleton); populate async.
- Offline Detection:
navigator.onLine+fetchheartbeat; customevent: offline/online. - Fallback UI:
- Manifest.json:
display: standalone, offline icons. - Custom offline.html: "You're offline. Shell cached. Actions queued."
- Error boundaries: Skeleton loaders + retry btn (
fetchw/ exponential backoff).
- Manifest.json:
- Background Sync: Queue mutations (
idbIndexedDB);syncevent for reconnect (e.g., unsaved cart). - Optimistic UX: UI updates pre-fetch; rollback on fail (e.g., add-to-cart).
- Metrics: Offline Lighthouse score >90; zero CLS on reconnect.
- Action: PWA Builder (pwabuilder.com); test Airplane Mode + 2G toggle.
4. Broader Low-Bandwidth Optimizations
Holistic throttles for 2G hell.
- Payload Reduction: Gzip/Brotli (90% shrink); minify (Terser/Uglify); tree-shake (ESBuild).
- Critical Path:
<link rel="preload">fonts/scripts;<link rel="preconnect">CDNs. - Loading States: Skeleton screens + progress bars (e.g.,
networkInformation.downlinkfor ETA). - No-JS Fallback:
<noscript>critical content. - CDN + Edge: Cloudflare/akamai; geo-cache for latency.
- Metrics (2G Throttle):
Metric Target FCP <2s LCP <5s TTI <10s FID <50ms Cumulative Layout Shift <0.1
Testing Methodology
- Simulate: DevTools > Network > 2G; CPU 4x slow.
- Real-World: WebPageTest.org (select GSM); field test (rural SIM).
- Tools Stack: Lighthouse CI, PageSpeed Insights (Slow 4G proxy for 2G approx), SpeedCurve.
- A/B: Compare pre/post impl (e.g., cache miss vs hit waterfalls).
Recommendations & Next Steps
- Week 1: Audit images → progressive JPEG migration (script batch convert).
- Week 2: Deploy SW + caching (start w/ Workbox precache).
- Week 3: Offline flows + sync; Lighthouse audit loop.
- Monitor: RUM (Real User Metrics) via
web-vitalslib; alert on 2G regression. - Edge Cases: Data Saver mode (Chrome), low battery (throttle JS).
Verdict: Implement these, and your UX withstands 2G apocalypse. Questions? Provide URL for full site scan.
Elementary, my dear user.
Sherlock | Trailblazer Labs
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.