Practice the vocabulary of measuring how a real user actually experiences a page's loading and stability.
0 / 5 completed
1 / 5
At standup, a dev mentions a set of metrics, including how long the largest visible element takes to render and how much the page's layout unexpectedly shifts, measured from real users' actual browsers rather than only a synthetic lab test. What are these metrics called?
Core Web Vitals are a set of metrics, including Largest Contentful Paint and Cumulative Layout Shift, measured from real users' actual browsers via field data, not only from a synthetic lab test. Server response time only measures how long the backend takes to respond, saying nothing about what a real user visually experiences once the response reaches their browser. This real-user, field-measured basis is what makes Core Web Vitals a standardized signal of actual perceived page experience.
2 / 5
During a design review, the team wants a metric specifically measuring how much visible content unexpectedly shifts position after it's already rendered, like an image loading in without space reserved for it. Which capability supports this?
Cumulative Layout Shift, or CLS, specifically measures how much visible content unexpectedly shifts position after it's already rendered, like an image loading in without space reserved for it and pushing the rest of the page down. Largest Contentful Paint measures how long the biggest visible element takes to render, which is an entirely separate concern from content moving around afterward. This distinct metric is what lets a team diagnose and fix a visually jarring shift specifically, rather than conflating it with a slow initial render.
3 / 5
In a code review, a dev notices the metric is collected via a browser API on real users' actual page visits and aggregated over time, rather than measured once in a synthetic lab environment. What does this represent?
Field data collection from real users, gathered via a browser API on their actual page visits and aggregated over time, reflects the genuine range of devices, networks, and conditions real visitors experience. A synthetic lab measurement taken once in a controlled environment can miss how the page actually performs on a slower device or network in the real world. This field-based collection is what makes Core Web Vitals a meaningful signal of real, lived page experience rather than an idealized lab result.
4 / 5
An incident report shows Largest Contentful Paint regressed noticeably after a redesign, traced to a large hero image with no explicit width or height reserved in the layout, causing a shift and delaying when the largest element finally settled into place. What practice would prevent this?
Reserving explicit width and height for a large image lets the browser allocate its space upfront, so the layout doesn't shift once the image loads and the largest element settles into its final position without an added delay. Continuing to omit that explicit sizing is exactly what caused the regression this incident describes. This reserved-space practice is a standard, low-effort fix for both Cumulative Layout Shift and a related Largest Contentful Paint regression caused by the same missing dimensions.
5 / 5
During a PR review, a teammate asks why the team fixes a Cumulative Layout Shift issue based on real-user field data instead of relying only on a synthetic lab test's score. What is the reasoning?
A synthetic lab test runs under one controlled condition, which can look fine while missing how the page actually performs on a slower device or a spotty network connection a real visitor might be using. Real-user field data reflects that actual range of devices and networks, which is precisely what Core Web Vitals is designed to capture. The tradeoff is that field data takes longer to accumulate and diagnose than a synthetic lab test's instantly available score, making the lab test still useful for quick, pre-release iteration.
What does the "Core Web Vitals Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to core web vitals vocabulary through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.