NEW

✨ Say goodbye to lost search rankings. Introducing Gobiya AI Citation Engine. Learn more

Site Speed, UX and Conversion: The Complete Glossary

Site speed, UX and conversion are one chain, not three subjects. Google measures the first with Core Web Vitals, visitors experience it as the second, and the business feels it as the third. The twelve terms below run that chain from the metric a browser reports to the revenue a slow page costs.

What Google measures

Three field metrics, reported from real visits rather than a lab.

Core Web Vitals

Core Web Vitals are Google's three official measurements of real-world page experience: how fast the main content loads, how quickly the page responds to input, and how much it visually shifts around while loading.

The three metrics are Largest Contentful Paint (loading speed), Interaction to Next Paint (responsiveness), and Cumulative Layout Shift (visual stability). Google uses these as a ranking signal, and a slow, jumpy page also frustrates both human visitors and the crawlers trying to read it within a limited time budget.

Largest Contentful Paint (LCP)

LCP measures how long it takes for the largest, main piece of content on a page — usually a hero image or headline — to fully load and appear on screen.

Google considers an LCP under 2.5 seconds good. Common fixes include compressing hero images, removing render-blocking scripts, and using a content delivery network so the file has less distance to travel to the visitor.

Cumulative Layout Shift (CLS)

CLS measures how much visible content unexpectedly jumps around while a page is loading — like a button moving right as you're about to tap it because an ad above it just loaded in.

A low CLS score usually comes down to reserving space for images and ads before they load, and avoiding inserting new content above things a visitor is already reading. It's one of the three Core Web Vitals.

Interaction to Next Paint (INP)

INP measures how quickly a page visibly responds after someone clicks, taps, or types — a slow INP feels like the page is "lagging" behind the visitor's actions.

INP replaced an older metric called First Input Delay as one of the three Core Web Vitals. Heavy, poorly optimized JavaScript is the most common cause of a slow INP score.

What makes a page slow

Where the time actually goes before anyone sees anything.

Time to First Byte (TTFB)

TTFB measures how long a browser waits after requesting a page before the server sends back the very first byte of the response.

A slow TTFB — often caused by weak hosting, an unoptimized database, or no caching — delays every other metric downstream of it, since nothing else on the page can start loading until that first byte arrives.

Page Speed

Page speed is how quickly a webpage loads and becomes usable for a visitor, measured through metrics like Largest Contentful Paint and Time to First Byte.

Beyond its direct effect on Core Web Vitals rankings, page speed strongly affects bounce rate — visitors, and bots working within a crawl budget, both tend to abandon a page that takes too long to load.

Above the Fold

Above the fold refers to whatever content is visible on a page before a visitor scrolls — the first thing anyone sees when the page loads.

What sits above the fold heavily influences both first impressions and Cumulative Layout Shift, since ads or images that load late in this area are the ones visitors are most likely to notice jumping.

How you make it fast

The three levers that move the metrics above.

Server-Side Rendering (SSR)

Server-side rendering means a web page's full HTML content is built on the server and sent to the browser (or bot) already complete, rather than assembled afterward by JavaScript running in the browser.

This matters enormously for both SEO and GEO: a search or AI crawler that doesn't fully execute JavaScript will see an empty page on a client-rendered site, but a fully populated one on an SSR site. It's one of the first things to verify when a site isn't getting indexed or cited despite good content.

Content Delivery Network (CDN)

A CDN is a network of servers spread across many physical locations that stores copies of your site's files, so visitors load them from a server near them instead of one far away.

Using a CDN typically improves both Time to First Byte and Largest Contentful Paint, since the physical distance data has to travel is one of the biggest factors in how fast a page feels.

Responsive Design

Responsive design means a website automatically adjusts its layout to fit whatever screen it's viewed on, from a phone to a desktop monitor, without a separate mobile version.

Google indexes and ranks the mobile version of a site by default (mobile-first indexing), so a layout that breaks or hides content on small screens directly hurts both rankings and the experience for the majority of visitors, who are on mobile.

What speed is worth

Why any of this is a business problem and not a developer problem.

User Experience (UX)

UX is how easy, clear, and pleasant a website is to actually use — covering navigation, layout, speed, and how easily a visitor can find what they came for.

Good UX and good SEO overlap more than people expect: a site that's confusing for a human to navigate is often also harder for a search engine to crawl and understand cleanly.

Conversion Rate Optimization (CRO)

CRO is the practice of improving a website so a higher percentage of visitors take the action you want — booking a call, filling out a form, or making a purchase.

CRO usually involves testing changes to page layout, calls-to-action, and messaging, then measuring the effect on how many visitors actually convert, rather than just how many show up.

Common questions

Do Core Web Vitals actually affect rankings?

They are a real but small ranking factor, and they matter most as a tiebreaker between pages of comparable relevance. The larger effect is commercial rather than algorithmic: a page that loads slowly loses visitors before it gets the chance to rank badly.

My PageSpeed score is 95 but the site feels slow. Why?

Because that score is a lab simulation and Core Web Vitals are graded on field data — real visits, on real devices and connections. Search Console reports the field numbers. When the two disagree, the field data is the one Google uses.

Which metric should I fix first?

Largest Contentful Paint, in almost every case. It is the one visitors feel most directly, it is the most common failure of the three, and the work that fixes it — server response time, image weight, render-blocking resources — tends to improve the other two as a side effect.

Is a fast site enough to improve conversions?

It removes a reason to leave; it does not supply a reason to act. Speed is a floor rather than a strategy — worth fixing first because nothing else you do on the page gets a fair test until it is.