What is Page Speed?
Page Speed is the time a website takes to load and become interactive. It is measured in metrics like: Largest Contentful Paint (LCP - seconds until main content loads), First Input Delay (FID - delay when user interacts), and Cumulative Layout Shift (CLS - visual stability during load).
A modern expectation: websites should load in under 3 seconds. Anything over 5 seconds is bad. Google has made page speed a ranking factor - faster websites rank better than slow ones.
But for B2B, speed matters even more than ranking positions: every second of load time costs you 5-10% conversions. If your landing page takes 5 seconds instead of 2 seconds to load, you lose massive leads.
Page Speed in B2B Context
In B2B, speed is particularly valuable for several reasons:
1. Users are impatient. A busy executive opens your landing page, sees "Loading..." after 2 seconds. Bounce. That is done.
2. Mobile users are especially affected. 70% of B2B traffic is desktop, but growing share is tablet and mobile. Mobile networks are slower - if desktop takes 2 seconds, mobile could take 8 seconds.
3. Conversion sensitivity. B2B conversions (demo booking, whitepaper download) are highly dependent on speed. A 1-second delay can cost 10% conversions.
4. SEO consequences. Google penalizes slow websites in rankings. Plus, if Google crawls a page slowly, it crawls fewer pages on your website per crawl budget. This means new pages are indexed later.
5. Brand perception. A slow website signals: "this company is not technically advanced." A SaaS with slow website? Suspicious.
Metrics for Page Speed
Google uses multiple metrics that together make up "core web vitals":
| Metric | What is measured | Target value |
|---|---|---|
| LCP (Largest Contentful Paint) | Seconds until main content loads (image, text, etc.) | Under 2.5 seconds = good, 2.5-4 = must improve, over 4 = bad |
| FID (First Input Delay) | Delay when clicking button/link until page responds | Under 100ms = good, 100-300ms = okay, over 300ms = bad |
| CLS (Cumulative Layout Shift) | How much content bounces around while loading | Under 0.1 = good, 0.1-0.25 = okay, over 0.25 = bad |
| TTFB (Time To First Byte) | Seconds until server sends first data | Under 600ms = good |
| Total Page Load Time | Seconds until entire page loads and is interactive | Under 3 seconds = good, under 2 = very good |
You can check your page speed for free with: Google PageSpeed Insights (free), Google Lighthouse (free), GTmetrix or WebPageTest.
Main Reasons for Slow Websites
1. Large unoptimized images - the most common problem. A 5MB image takes 10+ seconds on 3G. Images should be under 100KB. Use compressed formats (WebP instead of JPEG).
2. Too many HTTP requests - each JavaScript, CSS, image, font is a separate request. 100+ requests = slow. Reduce through code-splitting and lazy loading.
3. Render-blocking JavaScript - JavaScript that must load before the page renders blocks everything. Defer or async JavaScript loading helps.
4. Poor hosting/server - shared hosting with hundreds of sites is slow. Better hosting (cloud, CDN) helps dramatically.
5. 3rd-party scripts (analytics, ads, chat) - Google Analytics, Facebook pixel, live chat tools - all these external scripts slow things down. Load them async or defer.
6. Too much CSS/JavaScript - if your CSS is 500KB and you use only 20% of it, that slows things. Modern tools (CSS-in-JS, tree shaking) remove unused code.
7. Missing browser caching - when users visit your page, the browser should cache CSS, images, JavaScript. On next visit those are cached and the page is much faster.
Optimize Page Speed: Practical Guide
Step 1: Check with PageSpeed Insights
Google PageSpeed Insights (free) shows your problems and suggestions. Prioritize the biggest issues.
Step 2: Optimize images
- Compress with tools like TinyPNG, ImageOptim
- Use modern formats: WebP instead of JPEG (30% smaller)
- Use responsive images: different sizes for mobile vs desktop
- Lazy load images: images load only when user scrolls down
Step 3: Reduce JavaScript and CSS
- Minify: pack code into one line to reduce size (tools: Terser, cssnano)
- Code splitting: load only JavaScript this page needs, not all
- Async/Defer: don't load JavaScript render-blocking
Step 4: Enable caching
- Browser caching: set headers like "Cache-Control: max-age=31536000" for static assets
- Server-side caching: cache HTML pages after first render (e.g., Cloudflare, Redis)
Step 5: Use a CDN
A content delivery network (CDN) like Cloudflare or AWS CloudFront stores your page on hundreds of servers worldwide. Users load from servers closer to them = faster.
Step 6: Optimize server response time
- Upgrade hosting (better: cloud > VPS > shared hosting)
- Optimize database queries (too many queries = slow)
- Use server-side rendering or static generation when possible
Step 7: Monitoring and continuous testing
Page speed changes. With new content, new scripts, new visitor numbers - speed can degrade. Continuously monitor with Google Lighthouse, GTmetrix or Speedcurve.
Page Speed and Conversion Rate
There is a direct relationship between speed and conversions:
| Page Load Time | Conversions (Index 100 = 2 second baseline) |
|---|---|
| 1 second | 107 (+7%) |
| 2 seconds | 100 (baseline) |
| 3 seconds | 93 (-7%) |
| 4 seconds | 82 (-18%) |
| 5 seconds | 74 (-26%) |
| 6 seconds | 68 (-32%) |
This has been tested empirically in dozens of A/B tests. A page that improves from 2 to 4 seconds faster typically gets 15-20% more conversions. For many B2B companies this can mean thousands of additional leads per month.
Page Speed and Ranking
Google made page speed a ranking factor (2021 Core Web Vitals update). But consider: page speed is not as important as content or links. If you rank in the top 20 but are slow, speed could move you to 25. But if you are already at position 1 with good links/content, speed won't move you to 2.
Still: for B2B keywords (where competition is high), a speed advantage can make the difference between position 5 and 8.
Common Page Speed Mistakes
Mistake 1: Large images without compression. The #1 speed problem. Fix: compress images under 100KB.
Mistake 2: Forget to optimize 3rd-party scripts. Google Analytics, heat maps, live chat - all slow things down. Lazy load them.
Mistake 3: Do not use CDN. CDN costs often just a few euros/month. Enable Cloudflare or similar immediately.
Mistake 4: Load too many fonts. Use max 2 font families and 2-3 weights. 10 fonts = 500KB JavaScript.
Mistake 5: Don't set browser caching. Easy to fix (1-2 lines of code), huge impact.
At Leadanic we optimize website performance as a critical part of SEO and conversion strategy. With the right optimizations we typically bring page speed from 4-5 seconds to under 2 seconds within 2-3 weeks.