Why a WordPress site is slow

Updated · 31 Aug 2026

Short answer.

“The site is slow” may mean a long server response, a heavy page, blocking JavaScript, a slow database, background jobs, or a problem visible only to some users. Record one concrete journey and time, then separate network, backend, and browser. Cache is useful after a cause is known—not instead of finding it.

Check first

Evidence before change.

• The exact page, action, device, and login state that reproduce the delay.
• DNS/TLS/TTFB plus the page’s resource count and weight.
• PHP workers, memory, CPU, I/O, and slow/error logs at the same time.
• Slow database queries, autoloaded options, and temporary-data volume.
• Cron, Action Scheduler, external APIs, and repeating background failures.
• Images, fonts, JavaScript, CSS, and cache behavior for logged-in/anonymous users.

Safe sequence

Move in small verifiable steps.

• Record a baseline. One URL, one journey, several repeats, and a meaningful metric.
• Separate layers. Compare the raw server response, HTML, and final render.
• Look for correlation. Find errors, load, or a slow external request at the same time.
• Change one cause at a time. Otherwise an improvement cannot be explained or a regression reversed.
• Repeat the same journey. Compare the worst repeatable values as well as the average.

Common mistakes

What usually increases risk.

• Installing multiple cache plugins together.
• Removing required functionality only to improve a synthetic score.
• Optimizing the home page when checkout or wp-admin is actually slow.
• Treating one remote test as a universal description of the site.

320px Site Audit

What can be checked automatically.

Site Audit shows observable configuration signals, resources, errors, and selected final-DOM evidence. It does not replace long-running server tracing, but helps separate concrete findings from generic “speed up the site” advice.

When help is useful

A concrete next step.

320px investigates performance within technical support, using a baseline, one hypothesis at a time, and repeated verification.