New format
How to speed up a WordPress site: hosting, theme, plugins
A slow WordPress is usually the sum of hosting, a do-everything theme, a dozen plugins, and unoptimized images. Changing the plan without cleaning the site helps little; cleaning without decent TTFB helps little too.
Below: diagnosis and speed-up order. We don’t copy other people’s Kinsta/Flywheel cases and “+N PageSpeed points” as a recipe. Measure your URL in current tools (PageSpeed Insights, Web Vitals) and fix the real bottlenecks.
Diagnosis: where it actually stalls
Pull a PageSpeed / Lighthouse report for the mobile version of key URLs. Watch TTFB, LCP, INP/CLS, and the “load less” list.
Separately check: how many plugins, which theme, hero image weight, whether the server sends compression and cache. Without measurement, fixes are blind.
Typical WordPress bottlenecks:
- slow server response (TTFB)
- a heavy theme with extra scripts
- duplicates and dead plugins
- large JPG/PNG without WebP
- blocking JS/CSS and extra fonts
Hosting and the server layer
If TTFB is 1–2+ seconds, start with hosting: current PHP, server cache, SSD, sensible geolocation. WordPress-oriented plans often include cache and CDN out of the box — check current terms, not a 2019 price list.
CDN cuts static latency for distant users. SSL and modern HTTP are baseline, not optional. Changing hosts without theme optimization gives a partial effect — that’s normal.
What to ask the host:
- is there page cache / object cache
- PHP version and limits
- CDN and HTTP/2–3
- backups and staging for tests
Theme, plugins, and media
A premium theme for every case pulls sliders, fonts, and builders you don’t use. Take a lighter template or hard-disable modules.
Plugins: remove unused ones; don’t keep two caches, two SEO plugins, or two sliders. Update what’s left. Images — compression, sensible sizes, lazy-load, WebP/AVIF where possible.
JS/CSS: defer non-critical work, don’t load Google Fonts in a pack “just in case,” prefer system or local fonts when possible. “Combine everything” plugins — test on staging: they sometimes break the site.
Work order:
- backup and staging
- measure before changes
- clean plugins and theme
- optimize images
- cache + CDN
- re-measure the same URLs
FAQ
Where should I start if everything is slow?
Measure TTFB and LCP on mobile. If TTFB is high — look at hosting and server cache. If TTFB is fine but LCP is bad — theme, images, JS.
Is a cache plugin enough?
Cache helps, but won’t save a heavy theme and 40 plugins. Remove the excess first, then cache and CDN.
Does Elementor speed up the site?
Builders are convenient, but they aren’t a speed-up by themselves. A light theme plus fewer widgets is usually faster than a heavy builder with piles of add-ons.
Do I need specialized WordPress hosting?
Often yes: HTTP/2 or HTTP/3, SSL, server cache, decent PHP. Cheap shared hosting without cache kills TTFB.
Does speed mean better rankings?
Speed affects UX and SEO indirectly. Rankings for the core are separate work: prep about a month; page-one share of the core is typically planned for two to six months after work starts.
WordPress crawls — and you’re chasing 100/100 while the cart breaks?
We’ll measure TTFB and LCP, clean theme and plugins on staging, then add cache/CDN without killing business flows.
Discuss the task
