Slow website: how much revenue does it cost you?

A slow website does two things that directly hit revenue: visitors drop off and search engines get weaker signals for ranking. The result is fewer leads, lower conversion rates and higher cost-per-acquisition.

This article explains how to measure that impact. You get a straightforward calculation you can apply to your own numbers. And you get a practical priority list with indicative cost ranges to fix the biggest issues.

Why load time affects revenue

Speed affects both behaviour and visibility. Users abandon slow pages more often. Google measures speed and experience through Core Web Vitals, and those signals affect how often your pages appear in results. See the Core Web Vitals overview here: https://web.dev/articles/vitals.

In short:

• Traffic loss: lower rankings and higher bounce.
• Conversion loss: users leave before converting.
• Higher ad costs: campaigns become less efficient.

Note: speed is only one factor. Poor content, unclear CTAs or bad targeting will also hurt conversions.

How to measure the impact (practical)

Step 1 — Collect baseline data

• Sessions per page and pages with key conversions (Google Analytics/GA4).
• Conversion rate per page (requests or leads divided by sessions).
• Average order value or lead value.

Step 2 — Performance metrics

• Measure Largest Contentful Paint (LCP) and Interaction to Next Paint (INP) in field data (Real User Monitoring) and run lab tests. See LCP definition: https://web.dev/articles/lcp and Core Web Vitals: https://web.dev/articles/vitals.
• Compare field and lab results (Lighthouse, WebPageTest) to identify systemic issues.

Step 3 — Connect speed to conversion

• Split sessions into buckets (for example LCP < 2.5s, 2.5–4s, >4s).
• Compute conversion rate per bucket. That shows how many conversions you lose per bucket.

Sample calculation (apply your own numbers)

Assumptions (example):

• Page receives 10,000 sessions/month.
• Overall conversion rate 2% = 200 conversions.
• Average customer or lead value €500.
• Distribution by LCP: 60% <2.5s, 25% 2.5–4s, 15% >4s.

Assume conversion rates per bucket are 2.4% / 1.8% / 1.0% respectively (replace with your measurements).

If you move all sessions to <2.5s and conversion becomes 2.4%, you get 240 conversions = €120,000 revenue. That’s a potential increase of €18,000/month in this example.

Important: this is an illustrative example. Use your own sessions, conversions and customer value. The method is the point.

How much does fixing speed cost? (indicative ranges)

Costs vary widely depending on CMS, architecture and required changes. Below are ballpark figures. All amounts are indicative and vary per project.

Small wins (image compression, cache headers) often cost little and pay back quickly. Large projects (migrations, rebuilds) are more expensive but can fix systemic issues.

Priority list: what to do first

• Measure first: field data for LCP and INP.
• Optimise images and fonts; usually large wins for small cost.
• Reduce or defer blocking JavaScript. Do code-splitting.
• Configure caching and CDN properly.
• Automate asset optimisation in your build pipeline.

If you need help prioritising, start with a quick audit. For technical SEO implications and how performance ties into indexing, check Google’s Search Essentials: https://developers.google.com/search/docs/essentials.

Checklist (do these in order)

• Collect sessions, conversions and value per conversion.
• Collect Field Core Web Vitals (LCP, INP, CLS).
• Segment and compute conversion per LCP bucket.
• Prioritise image and script optimisation.
• Deploy changes gradually and measure impact.
• Set up monitoring and alerts (RUM/Lighthouse CI).
• Plan maintenance and ongoing support; see our maintenance and support page.

Measurement methods and tools

Use both field and lab data. Field data shows real-user experience; lab data helps reproduce and debug. Google documents how search sees your site and how long results take to show in Search Console — useful context when you tackle ranking issues: https://developers.google.com/search/docs/monitor-debug/search-console-start.

Tools: Lighthouse, WebPageTest, RUM via GA4 or dedicated providers.

Final notes

Speed improvements give measurable returns, but they are part of a broader optimisation effort. Combine performance work with better content and UX. If you want a practical plan or price estimate, DevCru is a senior-led web and app development team that builds custom sites and provides ongoing maintenance without overpromising. For a short quote or a contact, visit /quote or /contact.