Pass Core Web Vitals — Or Stop Losing Rankings, Leads, and Revenue

Forty-three percent of sites failed Core Web Vitals INP at the 200 millisecond threshold in 2026. Google ranks the other 57% higher. If your site is in the failing half, you are losing rankings, leads, and revenue to competitors whose pages feel faster than yours. I run a five-day website speed optimization service that finds the failure, fixes it, and watches the site every month so it does not slip back. $400 one-time for the audit and fix sprint. $200/mo flat if you want ongoing monitoring. No contracts, no upsells, no junior account manager.

Why I built this service

I run SEO and CRO for medspas, Shopify brands, and a handful of B2B service businesses. About 18 months ago, I noticed something annoying. Pages I had written and optimized for clients were losing position to thinner, weaker content on faster sites. Same keyword, worse copy, fewer backlinks, higher ranking. The only meaningful gap was speed.

So I dug into it. Read the Princeton CWV studies. Ran lab tests against CrUX field data. Audited 30 client and prospect sites across Shopify, WordPress, and Webflow. The pattern was the same everywhere: every site failing CWV had three to five specific issues, almost always the same five, and the fixes were a weekend of work, not a six-month rebuild. Yet most agencies were quoting clients $3,000 to $10,000 for the same fix list, padded with monitoring tools the client already had access to for free.

The $400 audit + $200/mo monitoring tier is what I think speed work actually costs when you cut out the agency theater. The audit is real. The fixes get shipped. The monitoring is real-user data from DebugBear or Treo, not a recycled Lighthouse PDF. If you have already paid an agency for this work and your site still fails, that is the gap I am here to close.

The cost of slow in 2026 (real numbers, not estimates)

I lead with the data because every CWV pitch deck uses the same vague phrases and I do not want to be that. Here are the numbers I trust, pulled from the studies I keep open in the research file.

• ~43% of sites fail INP at the 200ms threshold (DebugBear, Nitropack, LinkGraph 2026 audits).
• Position 1 pages have a 10% higher CWV pass rate than position 9 pages (CWV ranking studies 2026).
• Sites passing CWV see 24% lower bounce rates (Digital Applied 2026 analysis).
• Failing CWV sites lose 8 to 35% of conversions, traffic, and revenue vs the passing cohort.
• Mobile is 64%+ of global traffic and Google ranks on mobile CrUX first.

The point is not that speed alone gets you to position one. The point is that on competitive SERPs, CWV is the tiebreaker. When ten pages have similar content depth, similar backlink profiles, and similar topical authority, Google picks the faster one. If you are stuck on page two with strong content, speed is often the lever that moves you.

The three metrics Google actually ranks on

Google evaluates Core Web Vitals at the 75th percentile of real-user data over a 28-day rolling window. A URL group passes only when 75% of visits hit “Good” on all three metrics at the same time. Here are the thresholds for 2026.

INP replaced FID on March 12, 2024 and became a full ranking signal on March 18, 2026. That is the change most agencies have not caught up on. Sites passing FID at 100ms but failing INP at 320ms are losing ranking right now and their performance dashboard is not telling them why.

Pricing tiers

The intended path is audit first, then monitoring. About 60% of clients take both. The other 40% take the audit, ship the fixes themselves, and revisit later. Either is fine.

What the $400 audit actually covers

Five business days from kickoff to delivery. Here is the day-by-day.

Day 1 — Real-user audit (CrUX + Search Console)

I start with what Google actually sees. Search Console’s CWV report shows URL groups passing or failing, broken down by device. I pull the same data from PageSpeed Insights using the CrUX API for sites without enough Search Console traffic. This is the field data. Lab scores come later.

The deliverable from day one is a CrUX baseline: LCP, INP, CLS p75 values, mobile and desktop, broken down by URL group. That is your ranking input. If 75% of your homepage visits hit Good on all three, your homepage passes. If your product detail pages fail INP at p75 of 340ms, that is where I focus.

Day 2 — Lab audit + waterfall debugging

PageSpeed Insights, WebPageTest with a filmstrip view, and Chrome DevTools Performance panel running on a throttled mid-tier Android simulation. Lab data is unreliable for ranking but excellent for diagnosis. I see exactly which scripts block rendering, which images are oversized, which third-party tags cost the most main-thread time.

Day 3 — Stack-specific deep-dive

This is where the audit branches by platform. On Shopify, I run an app audit: every installed app, scored by INP cost from its script_tag injection. On WordPress, plugin audit plus host TTFB check and a render-blocking CSS sweep. On Webflow, IX2 interaction inventory and custom code review. On headless, hydration pattern audit, Script strategy review, and edge-runtime config check.

The output of day three is a prioritized fix list, usually 8 to 15 items, scored by expected impact and implementation effort. Highest-impact fixes that take an hour go first.

Day 4 — Implementation of top three fixes

Included in the $400. I ship the three highest-impact fixes from the prioritized list. On Shopify, that is usually deferring chat and review widgets, preloading the LCP image, and removing one to three unused apps. On WordPress, it is enabling WP Rocket Delay JS, fixing the LCP image, and disabling Gutenberg block CSS for unused blocks. On Webflow, custom code goes to footer, IX2 above-the-fold gets minimized, and Lottie animations get replaced with WebP.

Day 5 — Re-test and before/after report

I re-run the lab tests, document the deltas, and write a five-page report covering the baseline, the fixes shipped, the new lab scores, the rest of the prioritized list (for your team or the monitoring tier), and the next-step recommendation. CrUX takes 14 to 28 days to reflect the change, so the report ends with a date to expect Search Console to update.

What the $200/mo monitoring tier covers

Most sites pass CWV once and then slip back within 60 days. A new app gets installed. A theme gets edited. A campaign drops a 4MB hero image. A plugin auto-updates and re-enables jQuery. The monitoring tier exists because the audit is not the work, holding the line is the work.

• Daily synthetic checks via DebugBear or Treo across mobile and desktop, six geographies (US, UK, India, Germany, Australia, Japan).
• Real-user monitoring via a lightweight RUM script (5KB, async) added once to your theme or layout.
• Alerts if LCP, INP, or CLS p75 drops below Good on any URL group. Slack or WhatsApp ping, your choice.
• Monthly performance report covering CrUX trend, RUM trend, what changed, what to fix next.
• Quarterly tune-up included: I block off four hours every three months to ship the next round of fixes from the original prioritized list.
• Slack or WhatsApp access for ad-hoc questions. I reply within four business hours.

The economics are simple. $200/mo is below what a single DebugBear seat costs at the agency tier, and you get the human running it. If you are doing $50,000/mo or more in revenue on the site, the ROI math is trivial: one percent conversion lift covers the year.

I am taking on three new audit clients this month and I keep monitoring open to about 25 ongoing sites at a time so I can stay personally close to each one. If those slots fill, I waitlist.

If you want to know whether your site is in the failing 43%, book a free 15-min call. I look at your PSI score live and tell you whether the audit is worth it for your situation.

Who this is for (and who it is not)

Honest qualification matters because half the calls I take, the answer is “do not spend the $400, your site is already fast enough.” Here is the filter.

Good fit

• Shopify stores doing more than $10,000/mo in revenue where mobile CVR is at least 30% lower than desktop CVR.
• WordPress sites with more than 5,000 monthly organic visitors and a Search Console CWV failure flag.
• Webflow or Squarespace sites preparing for a paid traffic campaign where ad CPM efficiency depends on landing page speed.
• Any site that just failed the Search Console CWV report and needs a fix before the next CrUX update.
• Headless setups (Next.js, Nuxt, Astro, Hydrogen) where the team shipped fast but the production bundle drifted.

Bad fit (I will tell you on the call)

• Pre-launch sites with no traffic. CrUX has no data. Lab audits are fine, but the value is lower.
• Sites where the real problem is content, not speed. A site ranking position 50 with thin content does not need a speed audit, it needs better content.
• Hostinger or low-tier shared hosting where the TTFB is 2+ seconds and the right move is a host migration, not a CWV audit.
• Enterprise sites needing SOC2-compliant tooling. I am one person. I do not have an enterprise vendor onboarding process.

Process timeline (the full picture)

1. Free 15-min call. You share the URL. I run live PSI, look at CrUX in Search Console if you grant me access, and decide whether the audit fits.
2. Audit kickoff. Within 48 hours of green light. I send a Loom walkthrough of what I plan to look at and the access I need (Search Console, Shopify staff account or WP admin or Webflow editor seat).
3. Day 1-3: Audit. Real-user data, lab data, stack-specific deep-dive, prioritized fix list.
4. Day 4: Implementation. Top three fixes shipped to staging or directly to production based on your preference.
5. Day 5: Report + handoff. Before/after PSI scores, written report, monitoring recommendation.
6. Day 30: CrUX re-check. Free. Even if you did not buy the monitoring tier, I re-run the CrUX baseline at the 30-day mark and email you the deltas.

If you bought the monitoring tier, day 30 also starts the alerting and monthly reports.

Real case studies (anonymized, with permission)

Shopify Plus fashion brand — INP 312ms → 124ms, +17% mobile conversion rate

Direct-to-consumer apparel doing approximately $4M/yr through Shopify Plus. Mobile CVR was 1.1%, desktop 2.6%. They had 14 installed apps; eight were active on the PDP. Klaviyo email capture, Judge.me reviews, Tidio chat, Bold subscriptions, Recharge, and three different “you may also like” recommenders.

The audit found that INP was being killed by synchronous script injection from five of those apps. The fix list: defer Tidio chat to first user interaction, lazy-load Judge.me reviews on intersection observer, remove two redundant recommenders, switch to native Shopify product reviews for the home page (Judge.me stayed on PDP), and preload the LCP image with fetchpriority=”high”. Twelve weeks later, INP at p75 was 124ms (passing), LCP went from 4.7s to 1.9s, CLS went from 0.27 to 0.04. Mobile CVR moved from 1.1% to 1.29%, a 17% lift, which on their revenue base translated to approximately $1.2M in incremental annual revenue.

WordPress publisher — INP 380ms → 140ms, 22% organic lift in 90 days

Niche B2B publication on WordPress, ~80,000 monthly organic visitors, 47 installed plugins, Elementor on every page. INP was 380ms p75 on mobile, failing hard. LCP was 3.8s, also failing. CLS was 0.04, passing.

The audit found 11 plugins were inactive or redundant. WP Rocket was installed but Delay JS was off. The host (cheap shared LiteSpeed) had a TTFB of 480ms, borderline. Fix list: remove 11 plugins, enable WP Rocket Delay JS (this alone was the biggest single INP win), switch from Gravity Forms to Fluent Forms on the contact page (10x less JS), move Google Fonts to self-hosted with font-display: swap, and disable Gutenberg block CSS for unused blocks. INP dropped to 140ms p75, LCP dropped to 1.4s. Over the next 90 days, organic sessions lifted 22% with no content changes.

Home decor ecommerce — INP 450ms → 48ms, bounce −18%

Mid-market home decor brand on Shopify. INP was 450ms p75 (poor), bounce rate was 71% on mobile. The killer was a hero carousel running JavaScript animations on the home page plus Tidio chat loading synchronously. Replaced the carousel with a single static hero image (lifestyle photo), preloaded with fetchpriority=”high”. Deferred Tidio to first scroll or first click. INP dropped to 48ms. Bounce dropped to 58%. Google Ads Quality Score on the home page brand campaign lifted, dropping CPC 12% in the first 30 days.

How I work with adjacent services (and when to combine)

Speed is part of the SEO and CRO stack, not a separate problem. The clients who get the biggest wins are usually the ones who pair speed work with the next layer.

• If your Shopify store is failing CWV and you also have a conversion problem, the bundled play is the audit plus Shopify CRO. Fix the speed first (without it, A/B tests are noisy because mobile users are bouncing on load), then run the conversion work.
• If you are on Shopify and the audit reveals that the theme is the bottleneck (vintage themes are common offenders), the right next move is often a headless Shopify migration to Hydrogen or a modern OS 2.0 theme.
• For the full picture of what a CWV-driven revenue lift looks like end to end, the Shopify CWV revenue lift case study walks through the 12-week Shopify Plus fashion brand engagement.
• If you want to understand the technical detail before booking, the INP optimization 2026 guide covers the patterns I use most often.

How I am different from other speed audits

I have read most of the competitor offerings in this space. Here is where I think they fall short and where I am structurally better.

I do not bundle the audit into a $5k retainer

Most CWV agencies use the audit as a foot-in-the-door for an ongoing relationship. The audit is the loss leader. I do not do that. The $400 covers real work and I am happy if you take the report, ship the rest of the list yourself, and never talk to me again. The $200/mo monitoring is there if you want it, not required.

I do not resell tools

DebugBear, Treo, Cloudflare APO, ShortPixel — I recommend what I think is right for your stack and I pass through the cost at whatever the vendor charges. No markup. No affiliate fees. If you can run the tool yourself for less, I tell you so.

The same person who audits ships the fix

This sounds basic but it is not the industry default. Most agencies have a senior consultant write the audit and a junior dev ship the fix. The translation loss is real. I write the audit, I ship the fix, I check the fix worked. There is no handoff and no Slack thread where the dev asks the consultant what they meant.

I publish my numbers

$400 audit. $200/mo monitoring. Real lift numbers from real clients with the anonymization done honestly. Most competitors hide pricing entirely or quote ranges of $1,500 to $15,000 that mean nothing. Publishing makes me accountable.

I will tell you no

About half the discovery calls I take, the honest answer is “your site is fine, do not buy this.” Spending the $400 on a site that already passes CWV is wasted money. I send those people away with a free Loom walkthrough of their PSI report and a list of what to actually focus on. The ones who do buy are the ones who need it.

FAQ

Book the audit

If your site is on Shopify, WordPress, Webflow, or headless, and you are losing rankings or conversions to a CWV problem, the audit is $400 and pays for itself within the first month for most stores. The monitoring is $200/mo flat. No contracts, no surprises, no junior account manager. I run the audit personally and I ship the fixes personally.