SEO and performance
How Website Speed Affects SEO Without a Fake Formula
Google uses Core Web Vitals in its broader ranking systems and recommends good page experience. It also says good scores do not guarantee top rankings and relevance remains fundamental. There is no universal “100 milliseconds equals one percent” rule.
Reviewed July 24, 2026 against current Google Search, PageSpeed and web.dev guidance.
Hassan Jamal·March 9, 2026·11 min read
The defensible answer
- ✓Core Web Vitals contribute to Google's broader ranking systems; they are not the whole ranking algorithm.
- ✓Google publishes no Lighthouse score that guarantees a position or triggers a fixed penalty.
- ✓Mobile-first indexing concerns the mobile version's content; a mobile lab score is not an indexing grade.
- ✓Performance can affect whether a visitor can use a page, but commercial impact depends on the route, audience and funnel.
- ✓Use Search Console, field performance, analytics and a release log to test a property-specific hypothesis.
Search
Pages, queries, impressions, clicks, positions, indexing and SERP context.
Experience
Field LCP, INP and CLS plus repeated lab diagnostics.
Business
Journey, traffic source, device, conversion, value and confounders.
What Google confirms about Core Web Vitals
Google's current guidance defines Core Web Vitals as real-user metrics for loading, responsiveness and visual stability. At the 75th percentile, the published “good” thresholds are LCP within 2.5 seconds, INP within 200 milliseconds and CLS at or below 0.1. Google says its ranking systems use these metrics, while also stating that strong page experience does not override relevance and good report scores do not guarantee top rank.
There is no single “most important SEO speed metric” disclosed by Google for every query. LCP, INP and CLS cover different parts of experience. A technically relevant issue is the one that affects the visitor journey and fails the measured distribution.
PageSpeed score is not a ranking cutoff
PageSpeed Insights can show eligible field data and a Lighthouse lab result. The 0-to-100 Lighthouse performance score is a weighted diagnostic generated under a synthetic profile. It changes with page state, test conditions and tool versions. Google does not publish 70, 90 or 100 as a direct ranking requirement. Our repeatable process for improving a Lighthouse score explains how to record the test profile so the number means something.
Search Console Core Web Vitals, CrUX field data and a mobile Lighthouse score are related performance tools, not interchangeable values. Label the source, population, period and conditions every time.
Mobile-first indexing does not mean “mobile score decides rank”
Google primarily uses the mobile version of content for indexing and ranking. Its guidance focuses on keeping mobile content, metadata, structured data, images and crawl access equivalent and usable. This does not turn one mobile Lighthouse run into a ranking score.
Why speed and search results can move together
Several mechanisms can produce that pattern, and they are worth separating before deciding what to fix. The technical side is covered in why a website loads slowly, and the search side in our competitor ranking gap analysis.
- ✓Core Web Vitals are one part of Google's broader systems.
- ✓Server failure, blocked resources or broken rendering can affect crawl and usable content as well as performance.
- ✓A redesign or migration often changes content, internal links, metadata, layout, tracking and platform behavior at the same time.
- ✓Demand, competition, SERP presentation, links, seasonality and Google updates can move while performance changes.
The presence of a correlation does not identify the mechanism or prove a fixed effect. Claims that bounce rate automatically lowers rank, every 100 milliseconds creates the same revenue change, or speed alone moves a page a fixed number of positions exceed Google's guidance.
How to measure a search effect
- ✓Annotate the exact release and list all material content, link, design, tracking, URL and technical changes.
- ✓Compare Search Console pages and queries by country, device and search type across sensible periods.
- ✓Check indexing, crawl, statuses, robots, canonicals, rendered content, sitemaps and server errors.
- ✓Compare URL or template field Core Web Vitals where eligible data exists and retain lab traces for diagnosis.
- ✓Use unaffected pages or staged rollouts as a comparison where the site and risk permit it.
- ✓Report uncertainty and competing explanations instead of assigning the full change to speed.
If the timing lines up with a Google rollout rather than one of your releases, check the dates against the record of the March 2026 core update before acting. Where the site runs on WordPress and the change followed a speed regression, the WordPress traffic drop walkthrough covers the same evidence in platform terms.
How to measure business impact
- ✓Define the affected journey and event, including test, refund and attribution treatment.
- ✓Segment by route, device, traffic source, market, new or returning visitor and experiment state.
- ✓Track usability and failure signals such as interaction delay, form error, abandonment and support contacts.
- ✓Control or document offer, price, campaign, creative, inventory, seasonality and other releases.
- ✓Use a range and confidence level; do not linearly extrapolate another company's case study.
How to read performance case studies
A web.dev case study can show that a named company changed particular metrics and observed particular outcomes during a stated period. It does not establish the same multiplier for another industry, traffic mix, implementation or experiment. Use it to generate hypotheses and study methods, then measure your own property.
Our own rebuild, and what it does not prove
Panda Patches is owned by a PandaCodeGen co-founder, so this is founder-affiliated evidence rather than an independent client result. It ran on WordPress and WooCommerce for three years at roughly 64 mobile PageSpeed with an LCP near 5.8 seconds. We rebuilt it on Next.js, Sanity, Supabase and Square, and the mobile lab scores moved into the 90s.
The paragraph above is exactly the kind of evidence the previous section warns about, so hold it to the same standard. It is a lab measurement on one property, taken before and after a rebuild that changed the platform, the hosting, the templates and the images all at once. It does not isolate which change produced the result, it does not establish a multiplier for your site, and it is not a search-ranking claim. We publish it because it is our own property and we can state the conditions, not because it proves what a rebuild will do for you.
Framework and platform choice
WordPress, Shopify, Webflow, Wix, Squarespace and Next.js do not have universal score or ranking ceilings. Compare representative routes, content, integrations, field data, editor needs, security, ownership, operating cost and available controls. Optimize the current platform first when it can meet the requirement; migrate when residual constraints and total cost justify it.
Where the platform is the suspected constraint, start from the route-level diagnostic for that stack: fixing a slow WordPress site, testing a slow Wix site, testing a slow Squarespace site or diagnosing a Shopify Dawn theme.
Migration protects controls, not outcomes
These are the controls a migration plan should name, and what a migration does to search visibility explains how each one is tested. Scoping and delivery sit under our WordPress migration service and custom engineering.
- ✓Keep valuable URLs stable where practical and map every approved change to a relevant destination.
- ✓Preserve content, metadata, canonicals, internal links, media and structured data.
- ✓Crawl staging and production, test redirects and errors, submit sitemaps and keep rollback.
- ✓Record representative performance acceptance and monitor Search Console after launch.
These practices reduce avoidable technical risk. They do not guarantee ranking retention, recovery, traffic growth or a timeline because search engines control those outcomes. What a scoped engagement covers is set out on our pricing page.
Primary sources
- Google Search Central: Core Web Vitals
- Google Search Central: page experience
- Google Search Central: debugging Search traffic drops
- PageSpeed Insights documentation
- Google Search Central: mobile-first indexing
- web.dev case study: Swappie
Get your SEO-safe performance plan
We will connect route-level field and lab evidence to search and funnel data, then scope optimization or migration without inventing a ranking or revenue result.
Frequently Asked Questions
Related Articles
AEO & Web Performance Glossary: 23 Terms Defined (2026)
A source-linked map of 23 AI-search, rendering, structured-data, and web-performance terms, including what each term does and does not prove.
Lovable Site Not Showing on Google? A 2026 Diagnostic
Current Lovable apps support SSR or crawler pre-rendering. Diagnose publishing, indexing, canonicals, metadata, content and Search Console before proposing a rebuild.
Lighthouse Agentic Browsing Checks Explained (2026)
A dated review of the Agentic Browsing checks shown in the audit snapshot, what was scored, what was marked not applicable, and why no technical score guarantees AI inclusion or sales.