Website Speed Test vs PageSpeed vs Core Web Vitals

People use these terms like they all mean the same thing:

• website speed test
• PageSpeed
• Lighthouse
• Core Web Vitals

They do not.

They overlap, but each one answers a different question.

A website speed test is the broadest term

A website speed test usually means:

“Tell me how fast this site responds and loads from the outside.”

That can include things like:

• response time
• TTFB
• redirect count
• HTML size
• asset weight
• basic delivery-path context

It is a general outside-in check.

That is the job Website Performance is trying to do here.

PageSpeed Insights is a specific Google tool

PageSpeed Insights is not just a synonym for “fast website check.”

It is Google’s own interface that combines:

• Lighthouse-style lab data
• field data from the Chrome UX Report when available

So when people say “check PageSpeed,” they usually mean “show me what Google’s PageSpeed Insights sees.”

Lighthouse is the lab-style audit engine

Lighthouse is the controlled audit.

It helps answer:

• what is likely slowing this page down?
• which resources block rendering?
• what did this one run look like under a fixed test setup?

It is good for debugging. It is not the same thing as real user experience across the world.

Core Web Vitals are user-experience metrics

Core Web Vitals focus on the quality of the experience users actually have.

That usually centers on:

• LCP
• CLS
• INP

These are not “one more score.” They are specific experience signals that matter because users feel them.

Why these get mixed up

Because people want one clean answer to “is the site fast?”

There usually is not one.

A site can:

• respond quickly but still feel bad in the browser
• score well in one lab run but struggle in field data
• have decent Core Web Vitals but still carry unnecessary backend delay

That is why a useful performance workflow needs more than one lens.

Which one should you use?

Use a website speed test when:

• you want a fast outside-in check
• you want to know whether the document is slow or the site is flat-out failing
• you want TTFB, redirects, and delivery-path clues

Use PageSpeed Insights when:

• you want Google’s lab and field framing
• you need a familiar performance benchmark
• you want a broader optimisation view

Use Core Web Vitals when:

• you care about real user experience
• you want to know whether loading, stability, and responsiveness are acceptable
• you want a stronger SEO-facing quality signal

The mistake to avoid

Do not ask a website speed test to be a full replacement for PageSpeed.

Do not ask PageSpeed to explain every backend delay.

Do not ask Core Web Vitals to explain every outage.

Each tool sees a different slice of the problem.

A better way to think about it

If you want the quick mental model:

• website speed test = “what happened on this request?”
• PageSpeed = “what does Google’s test setup think, and do we have field data?”
• Core Web Vitals = “how are users likely experiencing this over time?”

Once you separate those, performance work becomes much less confusing.

Where to go next

If you are trying to make sense of the metrics:

• Core Web Vitals & Site Performance
• PageSpeed Insights: Lab Data vs Field Data
• What Is TTFB and Why Is It High?

Those three together usually clear up most of the terminology confusion.