WordPress is slow: performance checklist
- 20.02.2026 00:58
-
- hosting
- performance
- php
- wordpress
A slow WordPress website is usually caused by a combination of caching settings, heavy plugins, unoptimized images, and limited PHP/database resources.
GARMTECH hosting uses LiteSpeed Enterprise, which can significantly speed up WordPress when the LiteSpeed Cache (LSCache) plugin is configured correctly.
Step 0 – Confirm the problem
- Test your site in an incognito/private window (to avoid cached sessions).
- Test from at least two networks (for example, mobile data and Wi‑Fi).
- Check if the problem affects only the admin area (
/wp-admin) or the public site.
Step 1 – Enable page caching with LSCache (recommended)
- In WordPress, install and activate LiteSpeed Cache.
- Open LiteSpeed Cache → Cache and ensure caching is enabled.
- Purge cache after changes (Purge All).
If you already use another caching plugin, avoid running two page caches at the same time – it often makes the site slower or unstable.
Step 2 – Check PHP version and mode in Plesk
Modern WordPress versions perform best on recent PHP versions. In Plesk:
- Open the domain → PHP Settings.
- Select a newer supported PHP version (if your site and plugins support it).
- Enable PHP-FPM if available.
Step 3 – Identify slow plugins and themes
- Temporarily disable heavy plugins one by one (especially page builders, security suites, and statistics plugins).
- Check if performance improves on a default theme (for example, Twenty Twenty‑Four).
If you cannot access wp-admin, you can disable a plugin by renaming its folder in wp-content/plugins using Plesk File Manager.
Step 4 – Optimize images and static assets
- Compress large images and use modern formats (WebP if possible).
- Enable browser cache and minification in LSCache (test carefully).
- Remove unused fonts and third‑party scripts if possible.
Step 5 – Database and cron
- Clean up post revisions and transient options (many caching plugins can do this).
- Make sure WordPress scheduled tasks (WP‑Cron) are working properly. If WP‑Cron is disabled, set a real cron job in Plesk.
Step 6 – Check resource usage
If the site is slow only during peak traffic, it can be caused by hitting resource limits. Typical signs:
- Intermittent 503/508 errors,
- Slow admin actions,
- Long page generation times even without large images.
In this case, consider:
- Upgrading the hosting plan, or
- Moving heavy workloads (analytics, background jobs) to external services.
Step 7 – If you use Cloudflare (optional)
- Make sure Cloudflare is not caching dynamic pages like
/wp-admin. - Use “DNS only” for mail-related records (MX, mail hostnames).
- Use “Full (strict)” SSL when your origin has a valid certificate.
Good baseline checklist
- WordPress core + plugins updated.
- LSCache enabled (single page cache only).
- PHP version updated (compatible).
- Images optimized.
- Database cleaned occasionally.