How to Check Your Website Speed (And What the Numbers Mean)

"Your website is slow."

You've probably heard this before. But what does "slow" actually mean? And how slow is too slow?

In 2026, Google's Core Web Vitals aren't just a nice-to-have — they're a confirmed ranking signal. If your site is slow, you're losing customers twice: once when Google ranks you lower, and again when visitors leave before the page loads.

This guide breaks down exactly how to measure your speed, what each number means, and what to fix first.

Why Speed Matters (In Real Numbers)

• 53% of mobile users leave if a page takes longer than 3 seconds to load
• Every additional second of load time reduces conversions by ~7%
• Google uses page speed as a direct ranking factor for both mobile and desktop
• Pages that meet all Core Web Vitals thresholds get a measurable ranking boost in search results

For a local business getting 500 visitors per month, shaving 2 seconds off your load time could mean 5-10 more leads per month. For an e-commerce site doing \$10,000/month, a 1-second improvement could translate to \$700+ in additional monthly revenue.

The 5 Metrics That Actually Matter

Google groups these into Core Web Vitals (the three that directly affect rankings) and supplementary metrics. Here's what each one measures and what "good" looks like:

1. Largest Contentful Paint (LCP) — Core Web Vital

What it measures: How long until the biggest visible element (usually a hero image or heading) finishes loading.

Good: Under 2.5 seconds | Needs work: 2.5 to 4 seconds | Poor: Over 4 seconds

Why it matters: LCP is the metric most closely tied to perceived load speed. If your hero image takes 6 seconds to appear, users think your entire site is broken — even if the text loaded in 1 second.

Common causes of poor LCP: Unoptimized images, slow server response, render-blocking JavaScript, and CSS that delays the main content.

2. Interaction to Next Paint (INP) — Core Web Vital

What it measures: How quickly your page responds when a user clicks a button, taps a link, or types in a form. INP replaced First Input Delay (FID) as a Core Web Vital in March 2024.

Good: Under 200ms | Needs work: 200 to 500ms | Poor: Over 500ms

Why it matters: A page that loads fast but feels sluggish when you interact with it is still a bad experience. INP captures responsiveness throughout the entire visit, not just the first click.

Common causes of poor INP: Heavy JavaScript execution, third-party scripts (chat widgets, analytics), and complex DOM updates.

3. Cumulative Layout Shift (CLS) — Core Web Vital

What it measures: How much the page content moves around while loading. Ever tried to click a button and the page shifted, making you click an ad instead? That's layout shift.

Good: Under 0.1 | Needs work: 0.1 to 0.25 | Poor: Over 0.25

Why it matters: Layout shifts are one of the most frustrating user experiences on the web. They cause accidental clicks, lost reading positions, and a general feeling that your site is janky.

Common causes of poor CLS: Images without width/height attributes, ads that load late, fonts that swap and resize text, and dynamically injected content.

4. First Contentful Paint (FCP)

What it measures: How long until the user sees anything on screen — even a loading spinner or background color.

Good: Under 1.8 seconds | Needs work: 1.8 to 3 seconds | Poor: Over 3 seconds

5. Total Blocking Time (TBT)

What it measures: The total time between FCP and when the page becomes fully interactive. It's a lab-based proxy for INP.

Good: Under 200ms | Needs work: 200 to 600ms | Poor: Over 600ms

How to Check Your Speed

Free Tools (Best to Use Together)

1. FreeSiteAudit Speed Snapshot — Our Speed Snapshot tool gives you an instant overview of your page load performance with clear pass/fail indicators for each Core Web Vital. Just enter your URL.

2. Google PageSpeed Insights — Provides both lab data (simulated test) and field data (real user measurements from the Chrome User Experience Report). Field data is what Google actually uses for rankings.

3. Google Search Console — Under "Core Web Vitals," you'll see which pages pass or fail based on real user data. This is the definitive source for how Google sees your speed.

4. WebPageTest.org — The most detailed free tool. Shows a waterfall chart of every resource your page loads, so you can pinpoint exactly what's slow.

For a complete picture beyond speed, run a full website audit. It checks speed alongside 50+ other factors including meta titles, meta descriptions, schema markup, and trust signals — with prioritized recommendations.

Lab Data vs. Field Data

This trips up a lot of people:

• Lab data (from PageSpeed Insights' Lighthouse test) runs on a simulated mid-tier phone with a throttled connection. It's useful for debugging but doesn't affect rankings.
• Field data (from Chrome UX Report) shows how real users experience your site. This is what Google uses for ranking decisions.

Your lab score might be 45 while your field data passes all Core Web Vitals. Or vice versa. Always check both.

The 5 Most Common Speed Killers

1. Uncompressed Images

The #1 culprit. A single unoptimized hero image can be 3-5MB. Compress images to WebP format and aim for under 200KB per image. Use the element to serve modern formats with a JPEG fallback:

`html

`

Always include width and height attributes on images — this prevents layout shift (CLS) by reserving space before the image loads.

2. Too Many Scripts

Every plugin, widget, and analytics tracker adds JavaScript that blocks page rendering. Common offenders:

• Live chat widgets: 200-500KB of JavaScript, often loaded on every page
• Social media embeds: Each embed loads its own framework
• Analytics stacks: Google Analytics + Hotjar + Facebook Pixel + more = significant overhead
• Unused WordPress plugins: Plugins load JavaScript even on pages where they aren't needed

If you're not actively using something, remove it. For essential scripts, defer or async-load them.

3. No Browser Caching

Without caching headers, every visit downloads everything from scratch — HTML, CSS, JavaScript, images, fonts. Enable caching so returning visitors load your site almost instantly.

For most sites, add these headers:

• Static assets (images, CSS, JS): Cache for 1 year
• HTML pages: Cache for a few minutes or use stale-while-revalidate

4. Cheap Shared Hosting

Budget hosting puts hundreds of sites on one server. When any of those sites gets a traffic spike, everyone suffers. Signs you've outgrown shared hosting:

• Time to First Byte (TTFB) over 800ms
• Random slowdowns at peak hours
• Your host's "unlimited bandwidth" comes with CPU throttling

Consider managed hosting (SiteGround, Cloudways, Kinsta) or add a free CDN like Cloudflare to serve static assets from edge servers worldwide.

5. Render-Blocking CSS and Fonts

CSS files that load before any content can appear. Custom fonts that cause text to flash or become invisible while loading. Solutions:

• Inline critical CSS (the CSS needed for above-the-fold content) directly in your HTML
• Defer non-critical CSS with media="print" and swap on load
• Use font-display: swap so text appears immediately in a fallback font while custom fonts load

Speed by Industry: What We See

After auditing thousands of small business websites, here's how different industries typically stack up:

The pattern is clear: images and third-party scripts are the universal speed killers across every industry. The businesses that fix these two things first see the biggest improvements.

What to Fix First (Priority Order)

Here's your action plan, ranked by impact and difficulty:

Run a speed check to see exactly where your site stands. Most sites can cut their load time in half with just the first two items on this list.

Monitoring: Don't Set and Forget

Speed isn't a one-time fix. Every new image, plugin, or content update can regress your performance. Set up ongoing monitoring:

• Google Search Console — Check Core Web Vitals report monthly
• FreeSiteAudit — Run a full audit quarterly to catch regressions
• PageSpeed Insights — Test after any major site change

Your website speed is the foundation everything else is built on. Your meta titles can be perfect, your schema markup can be flawless, your trust signals can be dialed in — but if the page takes 6 seconds to load, none of it matters.

Sources

This article references best practices and data from authoritative sources including:

1. Google Web.dev — Core Web Vitals - Official metrics definitions and thresholds
2. Google PageSpeed Insights - Free page speed measurement tool with lab and field data
3. Chrome Developers — INP - Interaction to Next Paint methodology and thresholds
4. Google Search Central — Page Experience - How Core Web Vitals affect search ranking
5. HTTP Archive — State of the Web - Web performance statistics and trends
6. MDN Web Docs — Image Performance - Responsive images and modern formats

Last updated: March 8, 2026