NEWIntroducing Client Dashboard — sign up, order services and manage everything in one place. Get started free
WordPress Speed Optimization · Sub-1s Load Times

From 6-second WordPress to sub-1s,. Core Web Vitals all green

Slow WordPress kills conversions, rankings, and AdSense RPMs. We diagnose the actual bottleneck (usually not what the plugin sellers told you), clean the database, optimise images, fix caching, tune the server, and get your site into the top 10% of WordPress performance. Before-and-after Lighthouse reports included in every engagement.

Sub-1s
Target load time
All green
Core Web Vitals
95+
Target Lighthouse
-75%
Avg load-time drop
WordPress speed optimization service by Aapta — performance analyst auditing Core Web Vitals, analytics dashboards and search performance to deliver sub-1 second load times
Why your WordPress is slow

Most WordPress slowness isn't mysterious - it's accumulated

A page builder you installed two years ago is loading 400 KB of CSS you don't use. An SEO plugin is running a database query on every request to check schema. Forty-two plugins are firing on every single page load because nobody deactivates anything. The database has ten years of post revisions, orphaned options, and spam transients that never got cleaned up.

Then there's the host. 'Managed WordPress hosting' from mass-market providers is usually shared infrastructure with a WordPress sticker on it. Object cache disabled, OPcache too small, PHP-FPM pool sized for 20 concurrent connections even though your site has 500. Your site is waiting for its turn on a shared server that's also running 300 other sites — and losing.

Speed optimisation is mostly undoing the damage — removing what shouldn't be there — and then caching what's left aggressively. We find the bottleneck with real profiling (not guessing), fix the cause (not the symptom), and ship a site that stays fast because it's architected to. Not a site that looks fast on a lucky benchmark run and wheezes under real load.

01

Bloated themes & page builders

Elementor Pro, Divi, Flatsome commonly ship 400 KB+ of CSS/JS per page. Most of it unused.

02

Unoptimised images

JPGs at 3000×2000 px scaled down by the browser, no WebP / AVIF, no lazy loading below the fold.

03

No real caching layer

Every page hitting PHP and MySQL from scratch on every request. Object cache disabled by default on most hosts.

04

Shared hosting bottlenecks

300 sites on one server. PHP-FPM pool starved for worker processes. OPcache too small to matter.

05

Database bloat

Post revisions going back 10 years, orphaned options, expired transients, spam from 2018 — all loaded on every request.

What WordPress speed optimisation covers

Real profiling, real fixes

Not 'install WP Rocket and hope'. The actual engineering work that takes a slow WordPress site to sub-1s and keeps it there.

Real performance profile

New Relic or Query Monitor against your actual site — not a best-case local setup. We find the slowest query, the heaviest asset, the longest-running request.

Plugin audit & reduction

Identify plugins you don't need, plugins doing too much, and plugins with known performance issues. We typically cut plugin count by 30–50%.

Database optimisation

Clean post revisions, orphaned meta, expired transients, spam comments. Rebuild indexes. Clean wp_options autoload. Free 20–80% of DB size on most sites.

Image optimisation

Convert JPG / PNG to WebP or AVIF with fallbacks. Lazy-load below the fold. Resize oversized uploads. Typical page weight drops 40–60%.

Caching stack setup

LiteSpeed Cache (or WP Rocket / W3 Total Cache) with Redis or Memcached object caching — correctly configured for your site, not copy-pasted defaults.

CDN integration

Cloudflare or BunnyCDN at the edge. Static assets served from 300+ global POPs instead of your single origin server.

Critical CSS & defer

Generate critical CSS for above-the-fold render. Defer non-essential JS. Preconnect fonts. Eliminate render-blocking resources.

Server-level tuning

PHP-FPM pool sizing, OPcache tuning, MySQL / MariaDB config, Nginx or LiteSpeed config — sized for your real traffic, not a default template.

Theme cleanup

Remove unused CSS, unused JS, dead code. If you're on a page builder, we evaluate whether moving to a custom theme pays back within 6 months.

Before / after reports

Full Lighthouse + PageSpeed Insights + WebPageTest runs before and after. You see exactly what changed, on which pages, by how much.

How we make WordPress fast (and keep it fast)

From baseline to green Core Web Vitals

The speed-optimisation process we've refined over hundreds of WordPress performance projects.

01
3–5 days

Audit & baseline

Full performance profile on all critical pages. Lighthouse, PageSpeed, WebPageTest, Query Monitor, New Relic. Baseline metrics recorded — so we can prove the improvement at the end.

02
Week 1

Quick wins

The 20% of work that gives 80% of the improvement: image optimisation, critical CSS, caching setup, database cleanup, plugin trim. Usually visible speed improvement by end of week 1.

03
Week 2–4

Deep fixes

Plugin reduction, theme cleanup, query optimisation, server tuning. The work that makes sure the site stays fast under real load, not just on a single benchmark run.

04
Week 4

Load testing

Simulate traffic 5× your peak with Loader.io or k6. Identify remaining bottlenecks under real concurrency. Fix or flag. Crucial for WooCommerce stores and publishers.

05
Ongoing

Handover & monitoring

Final Lighthouse / PageSpeed report showing every metric before and after. Core Web Vitals monitoring set up in Search Console. On a care plan? We watch it forever — no silent regressions.

Real speed-optimisation project

From 6.4s WordPress to 0.9s - organic traffic +210% in 9 months

SaaS marketing site · Speed optimisationSan Francisco, USA

Series A SaaS marketing site stuck on a bloated theme, flat organic for 6 months. Three weeks of work, 9 months of compounding results.

A Series A SaaS had been sitting on a stalled WordPress marketing site for 18 months. Page load averaged 6.4 seconds, Core Web Vitals were all red, and organic traffic had been flat for two quarters despite the content team publishing weekly. Their marketing lead suspected the platform was the problem; their previous agency kept telling them it wasn't.

We audited the site in three days. Found: a bought multi-purpose theme shipping 420 KB of CSS and 380 KB of JS on every page, 14 plugins that didn't need to be there, no object caching, images uploaded at 3000×2000 px, no CDN, and a hosting plan with 2 PHP workers handling all traffic for a site doing 80k monthly pageviews.

Three weeks of work: replaced the theme with a hand-coded custom theme, 14 plugins down to 4, full image conversion to WebP, Cloudflare CDN, LiteSpeed + Redis object caching, and migration to better hosting with 8 PHP workers. Page load dropped 6.4s → 0.9s. All three Core Web Vitals green. Over the next 9 months organic traffic climbed 210% — the content team had been producing good work; the platform had been strangling it.

Stack used
Custom themeLiteSpeed + RedisCloudflare CDNWebP/AVIFRankMath schema
Results
0.9s
Page load (from 6.4s)
+210%
Organic traffic in 9 months
All green
Core Web Vitals
WordPress speed FAQ

Questions we get on every speed call

On modern hosting with proper caching, a WordPress marketing site loads in 0.5–1.2 seconds on 4G, with all three Core Web Vitals green. WooCommerce stores are slightly slower because of cart/checkout dynamics but should still hit 1–1.5s for product pages. Anything over 2.5s means something is wrong — usually bloat, not WordPress itself.

The audit itself is ₹9,999 ($119) for a single-site audit with full profiling, Lighthouse / PageSpeed / WebPageTest runs, and a prioritised fix list. If you engage us for the full optimisation within 14 days, the audit fee is credited against the project. Audit-only is also fine — you can take the report to another agency if you prefer.

A standard marketing site is 1–2 weeks. A WooCommerce store with complex product queries is 2–4 weeks. Large publisher sites or enterprise multi-sites can take 6–8 weeks because load testing and incremental rollout need more care. Fixed-price, dated timeline sent with the audit report.

Sometimes yes, usually no. 'Upgrade to our Business Plan' is the default host response because upsells drive their revenue. Most speed issues are plugin, theme, and configuration — not server capacity. We diagnose the actual bottleneck first. If it is genuinely the host, we'll tell you, and we'll tell you which host to move to (and we don't take commissions from hosts).

All speed work happens on a staging copy first. Every change is tested on staging, reviewed by you, and only pushed to production when confirmed working. For larger sites we deploy improvements in phases so regressions (if any) are easy to pinpoint. Complete snapshot of the original site is kept as a rollback for 60 days.

Yes, these are what we target. LCP (Largest Contentful Paint) is usually fixed with image optimisation, critical CSS, and hosting tuning. INP (Interaction to Next Paint, which replaced FID) and CLS (Cumulative Layout Shift) are theme and JS issues — we reduce JS, defer what's non-essential, and fix layout shifts caused by lazy-loaded elements without reserved space. Most sites go from 2+ red metrics to all 3 green in the optimisation.

Maybe — we only recommend it when the host is genuinely the bottleneck and no amount of config will fix it (shared hosts with hard resource limits, mass-market 'managed WordPress' with crippled tuning). Our default recommendation is LiteSpeed-based hosting for WordPress. We also run our own managed WordPress hosting with the stack we use on client work — see our cloud hosting page for details.

Page builders are the #1 cause of slow WordPress sites we see. We can optimise them — reduce widgets, trim global CSS, fix lazy-loading — but they come with a ceiling. If your site is a page-builder site and speed is mission-critical (publisher, ecommerce, high-traffic marketing), we'll recommend moving to a custom theme and give you the 6-month payback math. For smaller sites, optimising the page-builder setup is often enough.

A lot, and growing. Core Web Vitals are a confirmed Google ranking factor. Sites with all-green CWV typically outrank slower competitors in the same content quality tier. More importantly, fast sites have better dwell time, lower bounce rate, and higher conversion — which Google uses as engagement signals. Our case study here saw organic traffic +210% over 9 months; speed was the main change.

Without ongoing maintenance, most WordPress sites slow down 10–15% a year from accumulating plugins, content bloat, and updates. On our care plan we include quarterly performance re-checks — we catch regressions before they're visible to users. If you're not on a care plan, we give you a maintenance checklist and you can run it yourself every few months.

Site loading slow?

Find out what's actually slowing it down - and fix it.

Most WordPress speed audits cost next to nothing. We'll run a real performance profile on your site, tell you the actual bottleneck, and scope the fix. If it's cheap, we do it. If it's expensive, we tell you what you'd pay for and why — before anything happens.