PF-01
CWV Audits
Field data from CrUX and Search Console, lab data from Lighthouse and WebPageTest. Prioritized list of fixes with expected impact.
CWVCrUXGSC
Sheet · Performance
Service · Performance Optimization
Sites that load fast — and stay fast.
Core Web Vitals tuning, Lighthouse audits, third-party script reduction, image optimization, and caching strategy. We tune to field data, not synthetic scores.
Sheet 01 · Overview
Performance is a feature — and a ranking signal.
Core Web Vitals are the closest thing we have to a hard floor for site quality. LCP under 2.5 seconds. INP under 200 milliseconds. CLS under 0.1. Sites that pass these consistently rank better, convert better, and feel better.
We tune to field data from the CrUX dataset and Search Console — not synthetic Lighthouse scores in isolation. Synthetic scores are a sanity check; real-user metrics are the target.
Most engagements start with an audit identifying the top 3-5 levers (usually some combination of images, render-blocking JS, third-party scripts, and missing caching). Quick wins land in the first sprint; structural work follows.
Sheet 02 · Schedule of Capabilities
Capabilities delivered.
6 core areas
Scoped per brief
Scoped per brief
PF-02
LCP Optimization
Image strategy, font loading, server response times, and critical resource preloading — the levers that actually move LCP.
LCPImagesFonts
PF-03
INP & Responsiveness
JavaScript reduction, hydration strategy, event handler tuning, and long-task detection.
INPJSHydration
PF-04
CLS Stabilization
Reserved space for images, fonts, embeds, and dynamic content. Layout stability across breakpoints and load states.
CLSLayout
PF-05
Third-Party Audit
Inventory every third-party script. Defer, async, or remove the bloat. Tag managers, chat widgets, analytics — all on a performance leash.
Third-PartyGTM
PF-06
Caching Strategy
CDN headers, browser cache, edge caching, and application caching tuned per resource type.
CDNCacheHeaders
Sheet 03 · Process
How we tune.
- Phase 01
Measure
Field data from CrUX and Search Console, lab data from Lighthouse and WebPageTest. Output: a written CWV report with prioritized fixes.
- Phase 02
Quick wins
Image optimization, render-blocking removal, font tuning, and third-party deferral — usually a 20-40 point Lighthouse improvement in 1-2 weeks.
- Phase 03
Structural work
Caching strategy, hydration changes, route-level code splitting, and image strategy at scale. Each change verified against the budget.
- Phase 04
Monitor
Performance budget alarms, CWV regression alerts, and quarterly reviews against the field data trend.
Sheet 04 · Stack
Tools we reach for.
LighthouseWebPageTestChrome DevToolsCrUXSearch ConsoleCloudflareVercelNuxt ImageSharpCritical CSS toolingPerformanceObserverPageSpeed Insights
Sheet 05 · FAQ
Questions, answered.
What is Core Web Vitals and why does it matter?
Google's LCP, INP, and CLS metrics — a signal in search ranking and a strong proxy for real user experience. Sites with poor CWV lose rankings and conversions. Tuning is rarely optional in 2026.
What tools do you use?
Lighthouse, WebPageTest, Chrome DevTools, the CrUX dataset, and field data from Search Console. We tune to field data, not synthetic scores — synthetic is a sanity check, not the goal.
Can you fix a slow site without rewriting it?
Usually. Most performance gains come from images, third-party scripts, render-blocking resources, and missing caching. Architectural rewrites are the last resort, not the first.
What about Shopify Liquid themes?
CWV-tunable. We have moved Liquid themes from 40-60 Lighthouse to 90+ without going headless. App injections and image strategy are usually the biggest levers.
How long does a performance engagement take?
2-6 weeks typical. Quick wins land in the first sprint; structural work (architecture, caching strategy, third-party reduction) takes longer.
Sheet 07 · Start a brief
Faster site, better rankings.
Send us your URL. We'll come back with a CWV audit, a prioritized fix list, and an honest estimate of what each fix will move.