Why is my website so slow?
A slow website is almost never one problem - it is usually two or three stacking up. Here are the nine causes behind most slow sites, in the order worth checking them.
Oversized images are the most common culprit
Most slow pages are slow because they ship photos straight off a camera or stock library - 3 to 10 MB each - when the browser only needs a few hundred kilobytes. Check any hero or banner image first: if it is more than about 300 KB, compress it and serve a modern format such as WebP or AVIF. This single fix often halves load time.
Too much JavaScript before anything paints
Themes, page builders, chat widgets, popups, and tracking snippets each add script the browser must download and run before the page becomes usable. Google measures this as Largest Contentful Paint (LCP) and Interaction to Next Paint (INP). If your page is blank for a second or more before content appears, script weight is usually why.
Cheap or distant hosting
Shared hosting on an overloaded server, or a server on the other side of the world from your visitors, adds delay to every single request. Time to First Byte (TTFB) above roughly 800 ms points at the server rather than the page. A content delivery network (CDN) or a host in your visitors’ region fixes the distance half of the problem.
No caching
Without caching, your server rebuilds the same page for every visitor and browsers re-download files they already have. Page caching on the server plus long cache lifetimes for images, CSS, and scripts means repeat views load almost instantly. Most platforms have this available - it is often just switched off.
Third-party embeds you forgot about
Booking widgets, social feeds, map embeds, review carousels, and A/B testing tools all call other companies’ servers while your page loads. Each one is a delay you do not control. Audit what is actually embedded and remove anything that is not earning its keep.
How to find YOUR cause in about a minute
Guessing is the slow way. Run a scan that measures real Core Web Vitals (AuditHQ pulls them from Google PageSpeed Insights, the same data Google ranks with) and it will tell you whether images, script, server response, or third parties are the bottleneck - with the specific offenders named. The free AuditHQ quick scan takes about 60 seconds and needs no signup.
Frequently asked questions
What is a good page load time?
Aim for the main content to appear within 2.5 seconds - that is the threshold Google uses for a good Largest Contentful Paint. Under 4 seconds needs improvement; over 4 seconds is rated poor and measurably costs conversions.
Does a slow website affect Google rankings?
Yes. Core Web Vitals (LCP, CLS, INP) are a confirmed ranking signal, and slow pages also increase bounce rate, which compounds the problem. Speed is rarely the biggest ranking factor, but poor vitals are a handbrake.
Can I fix a slow website without a developer?
Often, yes. Image compression, enabling caching, and removing unused plugins or embeds are owner-level fixes on most platforms. Server and code-level fixes may need a developer, but a good diagnosis first means you only pay for the right fix.