Skip to content
// Core Web Vitals · PageSpeed · LCP · CLS · FID

Your site is
slow. That
costs money.

Every second of load time costs you conversions, rankings, and revenue. I audit your site, find exactly what's slow, and fix it — with a before/after PageSpeed score you can see with your own eyes.

Get a Free Audit WhatsApp See Projects →
✓ Top Rated Upwork
✓ 100% Job Success
✓ 17+ Years
7%
Conversion drop per 1s delay
70%
WP sites score under 50 on mobile
90+
Target score after optimization
12+
Years of performance work
Business Impact

Speed is a Revenue Problem

These aren't abstract technical metrics — they translate directly to lost sales, lower rankings, and customers who leave before your page even loads.

−7%
Conversion rate lost
per 1 second of delay
Source: Google Research
53%
Mobile users abandon
a page that takes over 3s
Source: Google / SOASTA
Top 3
Core Web Vitals are a
direct Google ranking signal
Since Page Experience Update 2021
Services

What I Fix and How

Every slow site has specific bottlenecks — I find them, fix them, and show you the score improvement.

WordPress speed optimization and performance audit

WordPress Speed Optimization

Plugin audit, image optimization, caching layer (WP Rocket / Redis), database cleanup, theme-level render-blocking fixes, and server configuration for measurable score improvement.

WordPressWP RocketRedis
Core Web Vitals LCP CLS FID optimization

Core Web Vitals Fix

Targeted LCP, CLS, and FID/INP fixes — image preloading, layout shift elimination, JavaScript deferral, and font optimization to pass Google's green thresholds on all three.

LCPCLSFID/INP
WooCommerce performance optimization for online stores

WooCommerce Performance

Cart fragment loading fix, product archive page optimization, checkout speed, database query reduction, and object caching for stores with large product catalogues.

WooCommerceQuery CacheCart
Laravel database query and Redis cache optimization

Laravel / PHP Optimization

N+1 query elimination with eager loading, Redis caching for expensive queries, queue workers for async jobs, and database indexing for pages slow under real traffic.

LaravelRedisN+1 Queries
React Next.js bundle size optimization and code splitting

React / Next.js Optimization

Bundle size reduction, code splitting, dynamic imports, image optimization with next/image, prefetching strategies, and eliminating render-blocking third-party scripts.

ReactNext.jsBundle Split
CDN setup server configuration and hosting optimization

Server & CDN Optimization

CDN setup and configuration (Cloudflare, BunnyCDN), server-side caching (Nginx, Varnish), GZIP/Brotli compression, HTTP/2 push, and server response time (TTFB) reduction.

CloudflareNginxTTFB
What's Actually Slow

The 8 Problems I Find Every Time

After dozens of speed audits, the same culprits show up again and again. Here's what kills most WordPress and WooCommerce scores.

Unoptimized Images

5MB hero images served as PNG. No WebP conversion, no lazy loading, no size attributes causing layout shift.

Kills LCP + CLS

Too Many Plugins

Each plugin adds HTTP requests, JavaScript, and CSS on every page — including pages where the plugin does nothing.

Kills TBT + LCP

No Caching Layer

WordPress rebuilding every page from database queries on every visitor request with no object or page cache in place.

Kills TTFB

Render-Blocking JS & CSS

Scripts in the <head> blocking the browser from rendering the page — the visitor sees a blank screen while scripts load.

Kills FCP + LCP

Slow Shared Hosting

Server taking 2–4 seconds just to respond before any content is sent — no amount of caching fixes a slow server.

Kills TTFB

No CDN for Static Assets

Images, CSS, and JS served from a single server location — visitors far from that server wait for every asset.

Kills LCP globally

WooCommerce Cart Fragments

WooCommerce's cart fragment AJAX call fires on every page load — disabling page caching across the entire store.

Kills WooCommerce cache

Database Query Bloat

Plugins making 100+ database queries per page, N+1 query patterns in custom code, and missing indexes on large tables.

Kills TTFB + TBT
Is your site scoring under 50 on mobile?
WhatsApp Now Get Free Audit
Process

Audit, Fix, Prove It

Every engagement follows the same rigorous process — no guessing, no generic fixes, no vague "optimization."

Website speed audit using PageSpeed Insights and Lighthouse
Step 1 — Audit

Find exactly what's slow before touching anything.

Most speed "optimizations" are generic — install a cache plugin and hope. I start with a full diagnostic: PageSpeed Insights, GTmetrix waterfall analysis, Lighthouse detailed report, and real-device testing on mobile.

  • PageSpeed Insights scores — mobile and desktop, all metrics
  • GTmetrix waterfall — every HTTP request, every blocking resource
  • Database query profiling — slow queries, N+1 patterns, missing indexes
  • Written audit report with prioritized fixes and expected impact per fix
Implementing speed fixes caching CDN and image optimization
Step 2 — Fix

Implement the fixes in the right order.

Server-level fixes first (TTFB), then caching, then asset optimization, then code-level changes. Doing it out of order wastes effort — fixing images doesn't help if the server takes 3 seconds to respond.

  • Server response time (TTFB) and hosting issues addressed first
  • Caching layer installed and configured correctly for your stack
  • Images converted to WebP, lazy-loaded, sized correctly
  • Render-blocking scripts deferred and consolidated
Before and after PageSpeed score comparison showing improvement
Step 3 — Prove

Before and after scores you can verify yourself.

Every engagement ends with a documented comparison — before scores, after scores, and a breakdown of which fix contributed what improvement. You can run PageSpeed Insights yourself to verify every number.

  • Before/after PageSpeed Insights screenshots — mobile and desktop
  • Core Web Vitals field data improvement (when applicable)
  • GTmetrix waterfall comparison — requests reduced, total size reduced
  • Written summary of every change made and why
Related Work

Sites I've Built Fast From the Start

Speed optimization isn't just about fixing slow sites — it's built into every project I deliver. These are examples of performance-conscious builds.

WordPress site built for performance and speed

WordPress Builds

Every WordPress site I build ships with Redis object caching, WebP images, deferred scripts, and a CDN config in place — performance is architecture, not an afterthought.

WordPressRedisCDN90+ Score
 React Next.js fast loading web application

React / Next.js Apps

Next.js SSR/SSG with automatic code splitting, optimized image loading, and prefetching — Core Web Vitals green from day one, not retrofitted after complaints.

Next.jsSSRCode SplitLCP <2.5s
 Laravel application with Redis caching and query optimization

Laravel Applications

Including a platform handling 100M+ records — proper indexing, eager loading, Redis caching, and queue workers keep response times fast regardless of dataset size.

LaravelRedis100M+ RecordsQuery Opt.
View All 32 Projects →
Why Mehdi

Speed Optimization Done by a Full-Stack Developer

Most "speed optimization" services are plugin installers. I'm a full-stack developer — which means I can fix the actual code, not just configure surface-level tools.

🔍

Root cause, not symptoms

I find WHY your site is slow — specific queries, specific scripts, specific server configurations — not generic advice about "enabling compression."

🏗️

Code-level fixes available

I can fix a slow database query, rewrite a render-blocking theme function, or refactor how images are loaded — not just install a plugin and hope.

📊

Before/after proof

Every engagement is documented with actual PageSpeed scores before and after — numbers you can verify yourself with a free Google tool, not vague claims.

🌐

Any stack — WordPress, Laravel, React

I optimize across all the platforms I build on — WordPress/WooCommerce, Laravel, React/Next.js. Speed fixes look different on each one.

⭐

Top Rated on Upwork, 100% JSS

Public, verifiable track record across 50+ projects — every client's actual rating, not selected testimonials.

🌍

US, UK & AU time zones

Available for calls and reviews during your business hours — 10+ countries served without communication friction.

FAQ

Questions About Speed Optimization

Google uses Core Web Vitals (LCP, CLS, FID/INP) as direct ranking signals since the 2021 Page Experience update. A poor LCP score signals a slow page that Google will rank lower than faster competitors. Beyond ranking, Google's own research shows that a 1-second delay in mobile page load reduces conversions by up to 20%. Speed is both an SEO and a revenue problem — fixing it improves both simultaneously.
Google considers 90–100 Good, 50–89 Needs Improvement, and 0–49 Poor. For most business websites, achieving 85+ on mobile and 90+ on desktop is a realistic and impactful target. The mobile score matters most for SEO since Google uses mobile-first indexing. Most WordPress sites with unoptimized images and too many plugins score in the 20–50 range on mobile before optimization — well into the Poor zone.
A full speed audit with written report takes 2–3 days. Implementing the fixes on a typical WordPress site takes 1–2 weeks. For WooCommerce stores or Laravel applications with complex query issues, 2–4 weeks. The timeline depends on the depth of the problems found — some sites need only caching and image optimization (fast), others need theme-level rewrites or server configuration changes (slower but much higher impact).
Done correctly, no — but done carelessly, yes. I always test every change in a staging environment before applying it to the live site. Caching misconfigurations, aggressive minification, and poorly implemented CDN rules are common causes of broken sites after "speed optimization." I keep a rollback plan for every change and test across browsers and devices before marking anything as done.
Yes — most speed optimization work is on existing sites. I start with a full audit to understand the current codebase, then implement fixes systematically. I've optimized sites built on various themes, page builders (Elementor, Divi, Beaver Builder), and custom PHP/Laravel applications. The audit phase always happens first so I understand what I'm working with before making any changes.
PageSpeed Insights gives you a lab score (0–100) based on simulated testing in a controlled environment. Core Web Vitals (LCP, CLS, FID/INP) are field data metrics — real measurements from actual visitors to your site, collected via Chrome User Experience Report. Both matter: the lab score is useful for identifying and fixing issues, while field data Core Web Vitals are what Google actually uses as a ranking signal. I optimize for both.
Let's Fix Your Speed

From red to green — with numbers to prove it.

Share your URL and I'll run a free preliminary audit, then come back with a clear plan and honest quote for the full fix.

Share My URL Get Free Audit Hire on Upwork
Available for new projects · Free audit · Replies within 24 hours