An inquiry that “the WordPress site is slow” almost never has a single cause. But before reaching blindly for a speed-up plugin, simply isolating where it’s slow greatly improves the precision of your countermeasures. This article explains an isolation procedure you can do without specialist tools.
First, look at “what’s slow” in numbers
Enter a URL into Google’s PageSpeed Insights and two important numbers appear.
- TTFB (server response time) — The time until the first byte is returned. If this exceeds 0.8 seconds, the cause is on the server side (server performance, PHP processing, the DB)
- LCP (Largest Contentful Paint) — The time until the main part of the page displays. If TTFB is fast but LCP exceeds 2.5 seconds, the cause is on the front-end side (images, CSS/JS, the theme)
These two first split the problem into “server side or front-end side.”
Isolating a slow server side
- Check whether caching is in place — If page caching is working, the second and subsequent TTFBs should be around 0.2 seconds. If they aren’t, caching is unset or not taking effect
- Suspect the plugins — If the admin screen is also slow, a plugin or the DB is the likely culprit. The Query Monitor plugin lets you identify which plugin is issuing slow queries
- Suspect server performance — On the lower plans of shared hosting, PHP processing itself can be slow. Placing the same site in a staging environment and comparing lets you tell them apart
Isolating a slow front-end side
- Images — The most common cause. Cases where a phone photo is uploaded as-is at 3 MB still happen frequently. WebP conversion and lazy loading improve things dramatically
- Unused CSS/JS — Page builders and multi-function themes tend to load the files of features you’re not using on every page
- External scripts — Chat widgets, social embeds, ad tags. Removing them one at a time and measuring reveals their impact
Speed-up measures, in order of impact
| Measure | Impact | Difficulty |
|---|---|---|
| Introduce page caching / review its settings | Large | Low–Medium |
| WebP-convert and size-optimize images | Large | Low |
| Remove or replace unneeded plugins | Medium–Large | Medium |
| Upgrade PHP/DB versions | Medium | Medium |
| Switch servers | Large | Medium–High |
| Rebuild the theme | Large | High |
Cautions before installing a speed-up plugin
Caching plugins have a large effect, but they also commonly cause incidents—display breakage, form malfunctions, and mistakenly cached member pages. When introducing one, always check “logged-in state,” “form submission,” and “cart and member pages.” Avoid running multiple caching plugins together, as it causes conflicts.
Summary | In the order of measure → isolate → act
Speed-up work is decided by “the accuracy of the isolation” rather than “the breadth of your bag of measures.” In SHANNON’s WordPress speed-up service, we present a measurement and root-cause report first and start with the highest-impact measures. We report the before-and-after numbers as a set, so the cost-effectiveness is clear. Please start with our free speed assessment.