Hosting Terms
What is Core Web Vitals?
Core Web Vitals in plain English — the meaning, the comparison, and why it matters to anybody running a website.
Straight answer first
Core Web Vitals are Google's three user-experience measurements — loading (LCP), responsiveness (INP) and visual stability (CLS) — taken from real visitors and used as a ranking signal.
Below: the fuller explanation, a picture that makes it stick, why it matters in practice, and where you will actually run into it.
Written by the Hosting Seller staff · Checked 1 August 2026
0
Terms left unexplained
100+
Definitions, cross-linked
Real
Examples from real kit
Free
To read, naturally
LCP times how long the main content takes to appear, with about 2.5 seconds as the target. INP measures how promptly the page answers when someone interacts with it. CLS measures whether the layout stays still instead of shifting under a reader's thumb. What feeds rankings is field data from actual Chrome users, not a score from a lab run.
Responsibility splits along a clear seam. Hosting owns the foundation, since TTFB sits underneath LCP. The page owns the rest: image discipline, script weight, and reserving space so nothing jumps.
The everyday comparison
A café judged on three things by the people who actually ate there — how quickly the plate arrived, how fast someone came when you raised a hand, and whether the table wobbled. Not by an inspector on a staged visit.
Keep that picture in mind and most of the documentation you will ever read on the subject stops being mysterious.
What is actually at stake
Vitals are the place where hosting and SEO measurably meet. Green field scores are a ranking input you can engineer deliberately, and the split between host floor and page weight tells you exactly where the effort belongs.
That is the test for any technical term, incidentally — not 'do I understand it fully' but 'do I know when it is the answer to my problem'. For this one, you now do.
What it looks like day to day
A shop's LCP drops from 4 seconds to 2.1 through a cached TTFB and a properly sized hero image. Two halves of one metric, each owned by a different layer, both fixed in an afternoon.
Perfectly ordinary once you have seen it, which is rather the point: most hosting concepts are simple machinery wearing an intimidating name.
The Hosting Seller angle
You will meet it in the control panel and occasionally in a support conversation, usually already set the right way. If this term made sense, the natural next reads are TTFB, Cache, Lazy Loading and OPcache.
Real people answer the counter at any hour, including the awkward questions other hosts wave off as out of scope.

Why we bothered with a hundred definitions
Every confusing term in hosting turns into a support ticket sooner or later, so we defined the hundred most common ones properly, once, in the plain English we would use across the counter.
Order an annual plan and the first year of your domain registration is on the house.
- 100+ terms, all in plain English
- Everyday comparisons and real examples
- Related concepts linked together
- Written by the people on the desk
Why Hosting Seller
On every plan, as standard
Honest about what to skip
Most terms are recognise-level rather than operate-level, and the glossary says which is which.
The stakes spelled out
Not only what it is, but when it turns out to be the answer to a problem you are having.
Linked, never siloed
Related terms cross-reference each other, so one lookup grows into a working understanding.
Plain English first
Every term defined for people who run sites, not for other sysadmins — jargon translated rather than restated.
One term, fully landed
Core Web Vitals defined, pictured by comparison and placed in your own control panel — recognise-level in a single read.
Pictures that stick
Each concept gets a comparison you will still remember at the moment you actually need it.
First Steps
From choosing to live
- 1
Find it in your own account
The quickest way to learn a hosting term is to find it in your own panel; five minutes of looking beats an hour of reading about it.
- 2
Check what the defaults are
Our platform ships sensible defaults for this — check rather than assume, and you will know your setup instead of hoping about it.
- 3
Follow the terms next door
Concepts travel in packs — TTFB, Cache and Lazy Loading finish this one's picture, and each is a two-minute read away.
In the Box
Packed with every plan
- A 30-day money-back guarantee on every hosting plan
- Mailboxes that carry your own domain name
- NVMe SSD storage on every shelf, not just the top one
- cPanel, the panel the rest of the trade already knows
- WebP image optimisation built in and costing nothing
- LiteSpeed caching running at the server, not bolted on by plugin
- Site migration done for you by our staff, at no charge
- One-click installs for WordPress and 400+ other applications
- A free SSL certificate on every plan, reissued before it lapses
- Staging copies so changes get tested before they go live
Across the Counter
The questions we get asked most
Where can I see my real vitals?
In Search Console's Core Web Vitals report and in the field data section of PageSpeed Insights, both of which show what genuine visitors experienced wherever you have enough traffic to report. Lab scores are for diagnosis; field scores are what actually counts.
How much do the vitals really affect rankings?
They are a genuine input among many rather than the deciding one. Relevant content still leads, but vitals tip results that are otherwise close, and poor ones weigh on everything. Put plainly: good vitals remove a handicap, they do not write your pages for you.
Where do the servers actually sit?
Our hosting runs from European datacentres with London at the centre, behind server-level caching that keeps cached pages quick for visitors anywhere. For most sites the build of the platform — NVMe disks, LiteSpeed, sensible numbers of accounts per machine — decides the speed far more than the postcode does.
Is there a refund if it does not suit?
Yes — thirty days. Put the hosting through real work, and if it is not right, ask for the money back and you get it; there is no retention script to survive first. Domain registrations are the one carve-out, because registries take that fee the moment the name is placed.
What does round-the-clock support actually stretch to?
People at the counter at every hour, and a scope that takes in the practical work: mailbox setup, DNS records, WordPress trouble, restores. Not 'the server responds, ticket closed'. Ask us something hard before you order — the reply is a fair sample of what you would get afterwards.
What uptime do you commit to, and who is watching?
We commit to 99.9% uptime and watch it continuously. That figure is an operational target rather than a poster line, and the alerting behind it usually has an engineer on a problem before the first customer notices anything is wrong.
Can I bring a domain I already own?
Yes, and transfers in are routine. Unlock the name at your present registrar, collect the auth code, then start the transfer from your client area. Whatever registration time is left comes across with it, and DNS keeps answering the whole way through.
Read next
OPcache
OPcache holds compiled PHP bytecode in memory so that scripts skip recompilation on every request — free sp…
TTFB (Time To First Byte)
TTFB measures the gap between asking for a page and receiving its first byte — the server-and-network share…
Magento Hosting
Hosting with the memory and PHP room Magento genuinely asks for.
WordPress Hosting
WordPress looked after for you — LiteSpeed caching, staging copies and daily backups.
Packing up and moving host? Take our checklist.
A plain running order for a move nobody notices: what to copy first, how to carry email across without dropping a single message, when to point DNS, and the two slips behind nearly every hour of downtime we get called about.
Start on a plan with a plain price tag.
Quick NVMe hosting, SSL and the move in included, and real people on the counter at any hour — on a price that doesn't shift.
See the plans