Knowledge Base
Why is my WordPress website slow?
First check whether the problem affects one page, the whole website or just your device. Then review cPanel → Resource Usage for the affected time and WordPress → Tools → Site Health for website warnings. Large images, plugins, external services, uncached pages and resource limits can all contribute. A slow page does not automatically mean you need a bigger hosting plan.
Narrow down the problem
- Note an affected page, the time and what feels slow: the first page opening, images appearing, sign-in, search or checkout. Test the same page in a private browser window and on another network or device if you can.
- Compare a simple page with the affected page. If one image-heavy page is slow, its content may need attention. If the dashboard, forms and all pages are slow, check resource use and website changes next.
- If only your browser shows old or broken content, follow cache clearing before changing the server. If visitors see an error code, keep a screenshot and the exact code.
Check the hosting account
- Sign in to your account, choose Services, find the hosting service and choose Log in to cPanel.
- Open Resource Usage → Current usage and set Timeframe to cover the problem. Check for limits being reached, not just the current reading. Use our resource guide to understand the labels.
- On cPanel Tools, check Disk Usage too. Full storage can affect writes, logs and updates. Do not delete website files, mail or backups just because a folder looks large.
Check WordPress without disrupting visitors
- In the website's WordPress dashboard, open Tools → Site Health and read Status. Under Info, expand Server to check the PHP version and Active Plugins to see what is running.
- Look for recent changes: a new plugin, large image upload, import, backup job, external tracking service or design change. Share these details with your developer rather than changing several things together.
- Resize oversized images before uploading them and use appropriately compressed copies. Keep originals separately. Avoid adding several plugins that all provide the same caching or optimisation function.
- Back up the site, then test software updates, plugin changes and PHP changes on a separate copy first. On a shop, check sign-in, cart and checkout after any performance change.
- Cached pages are saved copies that can be served faster. Logged-in pages, carts and checkout need different handling. Do not force private or changing pages into a public cache to improve a speed score.
When to ask us
- Open Support → New Ticket, select Tech/Server and include the affected pages, time, device/network comparison, recent changes and resource readings. Explain whether the issue affects all visitors or only a particular action.
- We can check hosting-side evidence and help you decide the next step. We will not assume that buying a larger plan is the answer before checking the problem.