Website Performance: Speed Optimization for SEO and Conversions in 2025

Technical web performance optimization guide. Core Web Vitals, optimization techniques, testing tools, and impact on SEO and conversions.

Why Site Speed Matters

Users have increasingly high expectations. A 1-second delay can cost thousands of euros in lost conversions. Google uses speed as a ranking factor. Performance is no longer optional - it's critical.

Speed Impact Statistics

  • 1 second delay = 7% conversion loss
  • 53% abandon if site takes >3 seconds
  • Bounce rate increases 32% when load time goes from 1 to 3 seconds
  • Fast sites have 2x higher conversions
  • Amazon: 100ms delay = 1% revenue lost
  • Google: Speed has been a ranking factor since 2018
  • Core Web Vitals

    Google measures three main metrics:

    LCP (Largest Contentful Paint)

  • What it measures: When the largest visible element loads
  • Target: < 2.5 seconds
  • Impact: User perception of load
  • FID (First Input Delay) / INP (Interaction to Next Paint)

  • What it measures: Time until site responds to first interaction
  • Target: < 100ms (FID) / < 200ms (INP)
  • Impact: Interactivity
  • CLS (Cumulative Layout Shift)

  • What it measures: How much the page "shifts" during loading
  • Target: < 0.1
  • Impact: Visual stability
  • Performance Diagnosis

    Testing Tools

    Google PageSpeed Insights:

  • URL: pagespeed.web.dev
  • Core Web Vitals
  • Specific recommendations
  • Lab and Field data
  • GTmetrix:

  • Waterfall analysis
  • Multiple locations
  • Historical data
  • WebPageTest:

  • Deep analysis
  • Multiple runs
  • Visual comparison
  • Chrome DevTools:

  • Network tab (waterfall)
  • Performance tab (profiling)
  • Lighthouse audit
  • Google Search Console:

  • Core Web Vitals report
  • URLs with issues
  • Real user data
  • What to Analyze

    1. Waterfall Chart

  • What's loading?
  • In what order?
  • What's blocking?
  • 2. Largest Resources

  • What are the biggest files?
  • Can they be compressed/optimized?
  • 3. Third-Party Scripts

  • Analytics, ads, widgets
  • Impact on performance
  • 4. Time to First Byte (TTFB)

  • Server response time
  • <200ms ideal
  • Image Optimization

    Why It Matters

    Images are usually 50%+ of page weight.

    Image Formats

    WebP:

  • 30% smaller than JPEG/PNG
  • Nearly universal support
  • Ideal for most cases
  • AVIF:

  • 50% smaller than JPEG
  • Growing support
  • Next-gen format
  • JPEG:

  • Photographs
  • Fallback for older browsers
  • PNG:

  • When transparency needed
  • Graphics with solid colors
  • SVG:

  • Icons and logos
  • Infinitely scalable
  • Very small
  • Optimization Techniques

    1. Compression

  • Tools: TinyPNG, ImageOptim, Squoosh
  • Quality: 80-85% for JPEG
  • Savings: 50-80%
  • 2. Responsive Images

  • Use srcset for different screen sizes
  • Specify sizes to tell browser what size to choose
  • Browser automatically picks the right image
  • 3. Lazy Loading

  • Add loading="lazy" attribute on images
  • Load images when approaching viewport
  • Native HTML attribute
  • Reduces initial load
  • 4. Specified Dimensions

  • Always specify width and height on images
  • Prevents CLS (Cumulative Layout Shift)
  • Browser reserves space before loading
  • 5. CDN for Images

  • Cloudflare Images
  • Imgix
  • Cloudinary
  • Auto-optimization and resize
  • CSS Optimization

    Critical CSS

    What it is:

    CSS needed for above-the-fold, inline in HTML.

    Implementation:

    1. Identify critical CSS

    2. Inline in

    3. Load rest async

    Tools:

  • Critical (npm package)
  • CriticalCSS
  • Penthouse
  • Minification

    Eliminates:

  • Whitespace
  • Comments
  • Redundant characters
  • Tools:

  • cssnano
  • clean-css
  • PostCSS
  • Remove Unused CSS

    Problem:

    CSS frameworks include everything, you use 10%.

    Solutions:

  • PurgeCSS
  • UnCSS
  • Tailwind's purge
  • Avoid @import in CSS

  • Don't use @import to load other CSS files
  • @import blocks parallel loading
  • Better to use separate link tags or concatenation
  • JavaScript Optimization

    Minimize and Bundle

    Minification:

  • Terser
  • UglifyJS
  • esbuild
  • Bundling:

  • Webpack
  • Rollup
  • Vite
  • Code Splitting

    What it is:

    Splitting the bundle into chunks loaded on-demand.

    Benefits:

  • Smaller initial load
  • Load only what's needed
  • Defer and Async for Scripts

    Defer:

  • Add defer attribute on scripts
  • Doesn't block HTML parsing
  • Executes after DOM is ready
  • Maintains script order
  • Async:

  • Add async attribute for independent scripts
  • Doesn't block HTML parsing
  • Executes immediately when loaded
  • Doesn't guarantee execution order
  • Ideal for analytics and tracking
  • Remove Unused JavaScript

    Tools:

  • Chrome Coverage tool
  • Bundlephobia (check package sizes)
  • Import cost (VS Code extension)
  • Third-Party Scripts

    Problems:

  • Analytics
  • Chat widgets
  • Ads
  • Social widgets
  • Solutions:

  • Lazy load where possible
  • Facades (placeholders)
  • Self-host critical ones
  • Regular audit
  • Server-Side Optimization

    Hosting and Server

    Upgrade hosting:

  • Shared -> VPS -> Dedicated
  • Traditional -> Cloud
  • CDN (Content Delivery Network):

  • Cloudflare
  • AWS CloudFront
  • Fastly
  • Bunny CDN
  • CDN Benefits:

  • Servers close to users
  • Reduces latency
  • Aggressive caching
  • DDoS protection
  • Caching

    Browser Caching:

  • Configure Cache-Control header on server
  • Static assets (CSS, JS, images): cache for 1 year
  • HTML: short cache or no-cache
  • Use cache busting (versioning) for updates
  • Server Caching:

  • Redis
  • Memcached
  • Page caching
  • CDN Caching:

  • Edge caching
  • TTL configuration
  • Compression

    Gzip:

  • Universal support
  • 70-80% size reduction
  • Brotli:

  • 15-20% better than Gzip
  • Modern browser support
  • Preferred when possible
  • HTTP/2 and HTTP/3

    HTTP/2:

  • Multiplexing
  • Header compression
  • Server push
  • Requires HTTPS
  • HTTP/3:

  • QUIC protocol
  • Faster connections
  • Better for mobile
  • Database Optimization

    Indexing:

  • Frequent queries
  • Columns in WHERE/JOIN
  • Query Optimization:

  • Avoid N+1
  • Limit data retrieved
  • Caching layer
  • Specific Optimizations

    WordPress

    Essentials:

  • Caching plugin (WP Rocket, W3 Total Cache)
  • Image optimization (ShortPixel, Imagify)
  • CDN integration
  • Database cleanup
  • Avoid:

  • Too many plugins
  • Heavy themes
  • Excessive post revisions
  • Large media files
  • E-commerce

    Product Pages:

  • Optimized product images
  • Lazy load reviews
  • Defer non-critical JS
  • Checkout:

  • Minimal distractions
  • Fast payment processing
  • No blocking scripts
  • SPA (Single Page Applications)

    Initial Load:

  • Aggressive code splitting
  • Server-side rendering (SSR)
  • Static generation where possible
  • Runtime:

  • Virtual scrolling for long lists
  • Memoization
  • Efficient state management
  • Continuous Monitoring

    Real User Monitoring (RUM)

    What it is:

    Data from real users, not lab tests.

    Metrics:

  • Page load times
  • Time to interactive
  • Core Web Vitals
  • Tools:

  • Google Analytics 4
  • SpeedCurve
  • New Relic Browser
  • Datadog RUM
  • Synthetic Monitoring

    What it is:

    Regular automated tests.

    Tools:

  • Calibre
  • SpeedCurve
  • Pingdom
  • Alerting

    Setup alerts for:

  • LCP > 3s
  • CLS > 0.1
  • TTFB > 500ms
  • Error rates
  • Optimization Checklist

    Quick Wins

  • [ ] Enable compression (Gzip/Brotli)
  • [ ] Enable browser caching
  • [ ] Use CDN
  • [ ] Optimize images (format, size, lazy load)
  • [ ] Minify CSS/JS
  • [ ] Defer non-critical JS
  • Medium Effort

  • [ ] Critical CSS inline
  • [ ] Remove unused CSS/JS
  • [ ] Code splitting
  • [ ] Preconnect to important origins
  • [ ] Optimize web fonts
  • Advanced

  • [ ] Server-side rendering
  • [ ] Service workers
  • [ ] HTTP/2 or HTTP/3
  • [ ] Database optimization
  • [ ] Edge computing
  • ROI of Optimization

    Impact Calculation

    Example:

  • 100,000 visitors/month
  • 2% conversion
  • $100 average order
  • Revenue: $200,000/month
  • After optimization (load time 4s -> 2s):

  • Bounce rate drops 20%
  • Conversion increases to 2.5%
  • Revenue: $250,000/month
  • Increase: $50,000/month
  • Investment vs Return

    Optimization cost: $5,000-20,000 (one-time) Return: $50,000+/month (ongoing) ROI: 250%+ in first month

    Conclusion

    Web performance is a continuous discipline, not a one-time project. The business impact is direct and measurable.

    Principles:

  • Measure before optimizing
  • Focus on critical path
  • User experience > metrics
  • Continuous, not periodic

Getting started:

1. Audit with PageSpeed Insights

2. Identify biggest issues

3. Prioritize by impact

4. Implement and measure

5. Setup continuous monitoring

---

The DGI team offers web performance audit and optimization services. Contact us for a free analysis of your site.

Share article:
Back to Blog