In this article
  1. Page load time calculator
  2. First, measure: what the numbers mean
  3. Why is my website slow? The 12-point checklist
  4. Worked example: from 4.3 seconds to 1.8
  5. When the problem is your hosting
  6. Frequently asked questions

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.

MetricWhat it measuresGood
Largest Contentful Paint (LCP)How fast the main content appears2.5 s or less
Interaction to Next Paint (INP)How fast the page reacts to taps and clicks200 ms or less
Cumulative Layout Shift (CLS)How much the page jumps while loading0.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
Thresholds from web.dev (Google). TTFB is not a Core Web Vital but strongly affects LCP.

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 InsightsLikely causeFix
1Slow TTFB or “reduce initial server response time”Cheap shared hosting, no page caching, slow databaseTurn on page caching; move to better hosting
2“Properly size images”, large LCP imagePhotos uploaded straight from a camera or phoneResize to display size; use WebP or AVIF
3“Defer offscreen images”All images load at onceLazy-load images below the first screen
4“Reduce unused JavaScript”Page builders, sliders and unused pluginsRemove what you do not use
5Long “third-party” listChat widgets, trackers, embedded videos and mapsRemove extras; load videos only on click
6“Eliminate render-blocking resources”CSS and scripts loaded before contentDefer non-critical scripts
7Several font filesMany weights and styles of web fontsUse one or two weights, or system fonts
8“Enable text compression”Server not compressing filesTurn on Brotli or gzip
9Fast nearby, slow abroadServer far from visitorsUse a CDN
10High CLSImages and ads without set sizesGive images width and height
11Slow on mobile onlyHeavy page on slower phones and networksCut page weight and JavaScript
12Suddenly slowA plugin update, traffic spike, malware or host issueCheck recent changes and your host’s status
World Elev checklist. Diagnostic labels as they appear in Lighthouse-based tools such as PageSpeed Insights.

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.

StepPage sizeServer responseEstimated load
Before4.0 MB0.8 s4.3 s
Compress and resize images (−1.5 MB)2.5 MB0.8 s3.1 s
Add page caching2.5 MB0.3 s2.6 s
Remove an unused slider and two plugins (−1 MB)1.5 MB0.3 s1.8 s
World Elev calculation on a 10 Mbps connection with 0.3 s of connection set-up (100 ms latency × 3 round trips).

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.

Sources

  1. HTTP Archive Web Almanac 2025: Page weight
  2. web.dev: Web Vitals
  3. web.dev: Time to First Byte (TTFB)
  4. Google Search Central: Core Web Vitals and Google search results
  5. web.dev: Image performance
  6. Google: PageSpeed Insights