In this article
Why is my website slow? For most small business sites the cause is one of four things: images that are far too big, too much JavaScript, a server that is slow to respond, or third-party add-ons such as chat widgets and trackers. The fix starts with measuring. Run your page through Google’s free PageSpeed Insights, then use the checklist below to match the results to a cause.
Key facts
- 2.6 MB: the median mobile home page in July 2025, up from 845 KB in 2015 (HTTP Archive Web Almanac).
- 911 KB of images and 632 KB of JavaScript on that median mobile home page.
- 2.5 seconds: Google’s “good” target for Largest Contentful Paint, the time to show the main content.
- 0.8 seconds: a good server response time (TTFB); over 1.8 seconds is poor.
Page load time calculator
Estimate how page size, your visitors’ connection and your server affect load time. The defaults are the worked example below: a 4 MB page on a 10 Mbps mobile connection with a 0.8-second server response.
Estimate how long a page takes to load from its size, the visitor’s connection and your server’s response time.
A simplified model: connection set-up (latency × round trips) + server response + download time (size × 8 ÷ speed). Real browsers download files in parallel and show content before everything arrives, so measure your own pages with PageSpeed Insights. The 2.5-second target is Google’s “good” threshold for Largest Contentful Paint.
Want to come back to it later? Bookmark our standalone page load time calculator, or browse all our free calculators.
First, measure: what the numbers mean
Google’s Core Web Vitals are the three numbers that matter most. A page passes when 75% of real visits meet all three targets.
| Metric | What it measures | Good |
|---|---|---|
| Largest Contentful Paint (LCP) | How fast the main content appears | 2.5 s or less |
| Interaction to Next Paint (INP) | How fast the page reacts to taps and clicks | 200 ms or less |
| Cumulative Layout Shift (CLS) | How much the page jumps while loading | 0.1 or less |
| Time to First Byte (TTFB) | How fast the server starts responding (supporting metric) | 0.8 s or less; over 1.8 s is poor |
Google says good Core Web Vitals align with what its core ranking systems seek to reward, so speed matters for search as well as for customers. For a local business, a slow mobile page also means callers give up before they find your phone number.
Why is my website slow? The 12-point checklist
| # | Symptom in PageSpeed Insights | Likely cause | Fix |
|---|---|---|---|
| 1 | Slow TTFB or “reduce initial server response time” | Cheap shared hosting, no page caching, slow database | Turn on page caching; move to better hosting |
| 2 | “Properly size images”, large LCP image | Photos uploaded straight from a camera or phone | Resize to display size; use WebP or AVIF |
| 3 | “Defer offscreen images” | All images load at once | Lazy-load images below the first screen |
| 4 | “Reduce unused JavaScript” | Page builders, sliders and unused plugins | Remove what you do not use |
| 5 | Long “third-party” list | Chat widgets, trackers, embedded videos and maps | Remove extras; load videos only on click |
| 6 | “Eliminate render-blocking resources” | CSS and scripts loaded before content | Defer non-critical scripts |
| 7 | Several font files | Many weights and styles of web fonts | Use one or two weights, or system fonts |
| 8 | “Enable text compression” | Server not compressing files | Turn on Brotli or gzip |
| 9 | Fast nearby, slow abroad | Server far from visitors | Use a CDN |
| 10 | High CLS | Images and ads without set sizes | Give images width and height |
| 11 | Slow on mobile only | Heavy page on slower phones and networks | Cut page weight and JavaScript |
| 12 | Suddenly slow | A plugin update, traffic spike, malware or host issue | Check recent changes and your host’s status |
Images are usually the quickest win. Google’s image performance guide explains modern formats and responsive sizes. On WordPress, a common cause is installing a plugin for every small job; each one can add scripts to every page.
Worked example: from 4.3 seconds to 1.8
Here is the same page fixed in three steps, using the calculator above. It is a simplified model, but it shows where the time goes.
| Step | Page size | Server response | Estimated load |
|---|---|---|---|
| Before | 4.0 MB | 0.8 s | 4.3 s |
| Compress and resize images (−1.5 MB) | 2.5 MB | 0.8 s | 3.1 s |
| Add page caching | 2.5 MB | 0.3 s | 2.6 s |
| Remove an unused slider and two plugins (−1 MB) | 1.5 MB | 0.3 s | 1.8 s |
The median mobile home page is 2.6 MB, according to the 2025 Web Almanac, so many small business sites start well above the size that fits comfortably in 2.5 seconds on a typical phone connection.
When the problem is your hosting
If TTFB stays above 0.8 seconds even with caching on, the server is the bottleneck. Budget shared hosting packs many sites onto one machine. Our guide to what a website costs in 2026 shows typical hosting prices, and what happens when you type a web address explains the connection steps that add delay before a byte arrives.
Speed is one part of on-page SEO; see which on-page and off-page fixes moved rankings for the rest.
Frequently asked questions
Why is my website slow to load?
Usually heavy images, too much JavaScript, a slow server response or third-party scripts. PageSpeed Insights shows which applies to your page.
Why is my website slow on mobile?
Phones have slower processors and often slower connections, so heavy pages and JavaScript hurt more. Google measures mobile and desktop separately.
Why is my WordPress website slow?
Common causes are too many plugins, page builders that add code to every page, uncompressed images and hosting without page caching.
Why is my website suddenly slow?
Look at what changed: a plugin or theme update, a traffic spike, a problem at your host, or malware. Check your host’s status page and recent updates first.
Read more in our Web Hosting section.



