Knowledge base
Slowness has a small number of real causes and a lot of imagined ones. Here is how to find out which you have before changing anything.
Before changing anything, find out what is slow. The fixes are different and some make things worse.
Try it from your phone on mobile data. If it is fast there, the problem is your own network or your browser, not the site. This is worth thirty seconds and it rules out the commonest cause of a slowness report.
after a deploy or a cache clear.
on every page.
and anything calling an external API are the repeat offenders.
though your server answered immediately.
Do not install a second caching plugin. Two caching layers fighting is a classic cause of pages that are slow and serve stale content, and it is much harder to diagnose afterwards than the original problem.
Give us one URL that is slow and roughly when you noticed. A single slow page we can measure is worth more than a general report - and if only one page is slow, that itself is the biggest clue about the cause.
What we have been writing about hosting, SEO and running sites at scale.
How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.
Read the post →A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.
Read the post →What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.
Read the post →Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.
Contact support → All articles →