Short answer
Common causes include unoptimised images, too many render-blocking scripts or third-party embeds, slow or distant hosting, and a bloated theme or plugin stack. Each has a different fix, so it's worth identifying which applies before making changes.
Before diagnosing specific causes, it helps to confirm there's actually a broad problem rather than one slow page. site audit crawls your entire site and flags pages with slow load times as part of its health check, giving you a page-by-page starting point rather than a single site-wide guess.
Oversized, uncompressed images are consistently one of the biggest contributors to slow page loads — a single unresized photo can outweigh every other optimisation on a page combined. Compressing images and serving appropriately-sized versions (not a 4000px photo displayed at 400px wide) is often the single highest-impact fix available.
Chat widgets, analytics scripts, embedded videos, and ad tags each add their own loading delay, and a page with several stacked on top of each other can feel sluggish even with otherwise clean code. Loading non-essential scripts asynchronously, or removing ones that aren't earning their keep, is worth auditing directly.
A slow or geographically distant server adds delay before a page even starts rendering, regardless of how optimised the page itself is — this is invisible in the page's own code and only shows up as a slow "time to first byte". Cheap shared hosting is a common, often-overlooked culprit worth ruling out separately from front-end fixes.
On CMS platforms especially, an accumulation of plugins, addons, or a heavy theme framework can slow every page site-wide, sometimes without any single culprit standing out — it's the cumulative weight of many small additions. Auditing for and removing genuinely unused plugins or extensions is worth doing periodically, not just when troubleshooting.
Page speed is a confirmed part of Google's page experience signals, generally considered a smaller factor than content relevance and quality — but a genuinely slow site still creates a worse experience for visitors regardless of the exact ranking impact, which is reason enough to fix it.
No — Illumae's site audit uses a simpler load-time check (a fetch timer), not the full Core Web Vitals metrics Google itself measures. For genuine LCP, INP, and CLS figures, Google's own PageSpeed Insights or Search Console are the accurate source.
Image optimisation is very commonly the highest-impact, lowest-effort fix — compressing and correctly sizing images alone often produces a noticeably faster page before touching anything else.
Yes — server response time happens before any front-end optimisation even has a chance to matter, so a slow host can undermine an otherwise well-built, well-optimised page. It's worth checking time-to-first-byte specifically if everything else checks out.
Yes. The free plan includes 3 AI article generations, keyword research, a content calendar, and a basic dashboard — no card required.
No credit card required. See real output for your own business before you pay anything.