Master Core Web Vitals vocabulary: LCP, FID/INP, CLS, PageSpeed Insights language, and how to discuss performance scores in technical conversations.
0 / 17 completed
1 / 17
A team reports: 'Our LCP is 2.1s.' According to Core Web Vitals thresholds, this means:
Google's LCP thresholds: Good ≤ 2.5s, Needs Improvement 2.5–4.0s, Poor > 4.0s. A 2.1s LCP passes the Good threshold. LCP is measured from navigation start to when the largest visible element (image, hero text, video poster) is rendered.
2 / 17
CLS (Cumulative Layout Shift) measures:
CLS is a unitless score (not seconds or bytes). Good: ≤ 0.1. It is calculated from the impact fraction × distance fraction of each layout shift. Common causes: images without explicit width/height attributes, late-loading third-party widgets, and dynamically injected banners above existing content.
3 / 17
INP (Interaction to Next Paint) replaced FID as a Core Web Vital because:
FID measured only the input delay of the very first interaction. A page could have a fast FID yet feel laggy on every subsequent click. INP takes the worst (or near-worst) interaction latency across the session. Good: ≤ 200ms; Poor: > 500ms. It became an official Core Web Vital in March 2024.
4 / 17
PageSpeed Insights combines two data sources. They are:
PageSpeed Insights shows two sections: Field Data (CrUX — aggregated real-user Core Web Vitals from Chrome users over the past 28 days) and Lab Data (Lighthouse — a single controlled Chromium run with a simulated network and device). Field data is more reliable for SEO; lab data is better for debugging specific issues.
5 / 17
A developer says 'our page has a high CLS score because we inject a banner above the fold after load.' The correct fix is:
Layout shifts occur when an element appears and pushes existing content. Reserving space (a fixed-height div or CSS aspect-ratio container) as a placeholder means elements move into a pre-allocated area rather than displacing content. This is the standard CLS fix for ads, images, and lazy-loaded components.
6 / 17
During a code review of the new checkout flow, Sarah mentions: 'Our LCP is 2.1 seconds. This is significantly above Google's recommended threshold of 2.5 seconds.' Which of the following statements accurately reflects Sarah's observation regarding Core Web Vitals? LCP stands for Largest Contentful Paint.
Sarah correctly identifies LCP as a measure of *content* load time. While server-side rendering and image compression can influence LCP, the core meaning is that the largest element on the screen isn't loading quickly enough. A high LCP score indicates a potential user experience bottleneck due to slow content delivery.
7 / 17
In a Slack channel dedicated to performance improvements, Mark posts: 'We're seeing a high CLS score – about 0.2!'. What does 'CLS' primarily measure in the context of Core Web Vitals? CLS stands for Cumulative Layout Shift.
CLS measures *layout shift*, which is when elements on a webpage move unexpectedly after the initial load. This can be incredibly frustrating for users. Mark's observation highlights a problem where content is dynamically shifting around, impacting usability and trust – this is what CLS quantifies.
8 / 17
During a standup meeting, David says: 'We're focusing on improving our INP score. It's currently below the recommended threshold.' What does 'INP' represent as a Core Web Vital? INP stands for Interaction to Next Paint.
INP (Interaction to Next Paint) measures how quickly a page responds when a user initiates an action – like clicking a button. It's about the *time* it takes for the next interactive element to become responsive after the initial interaction. A low INP score signals that users are waiting too long for feedback.
9 / 17
You're reviewing a PR that includes changes to the website's performance monitoring. The commit message states: 'Integrating data from both PageSpeed Insights and Lighthouse.' What are these two tools primarily used for in relation to Core Web Vitals? PageSpeed Insights uses Lighthouse under the hood.
PageSpeed Insights leverages Lighthouse's algorithms to provide performance scores. While PageSpeed Insights offers a simplified experience and broader metrics, it relies on Lighthouse for its underlying analysis – providing a more granular understanding of the website's performance issues.
10 / 17
During a code review of the new e-commerce site's loading performance, Alex comments to Ben: 'Our INP is currently 4.8 seconds – that's significantly below what we should be aiming for.' Ben replies, 'Okay, let's investigate. What does 'INP' specifically represent in terms of Core Web Vitals?'
INP stands for Interaction to Next Paint. It's a critical metric measuring how quickly a website responds to user interactions – specifically, the time from when a user first initiates an action (like clicking a button) until the next paint occurs on the screen. It's often misunderstood as just page load time; INP focuses solely on the responsiveness of the *interaction* itself.
11 / 17
You're working with a team to optimize a landing page. A stakeholder asks you, 'What does CLS stand for in the context of Core Web Vitals?' You respond:
CLS stands for Cumulative Layout Shift. It measures how much a page shifts visually while it's loading – essentially, if elements move around unexpectedly. A high CLS score indicates poor visual stability and negatively impacts user experience, even if the overall page load time is acceptable.
12 / 17
You're reviewing the performance metrics for a newly deployed feature. The report shows an LCP of 2.8 seconds and a CLS of 0.25. A senior engineer asks you: 'Considering these scores, what's the most immediate action we should take?'
While both LCP and CLS are important, CLS typically has a greater immediate impact on user perception than LCP. A high CLS of 0.25 is significantly above recommended thresholds and will negatively affect the user experience more directly than a slightly slower LCP. Addressing visual stability should be the priority.
13 / 17
Liam from the performance team sends a Slack message: 'Hey team, our LCP is consistently around 4.2s. Seems like we need to investigate.' Considering Core Web Vitals, what does this message primarily indicate needs attention?
LCP (Largest Contentful Paint) measures the time it takes for the largest element on a webpage to become visible. A value of 4.2s is significantly above Google's recommended threshold of 2.5s, suggesting a problem with resource loading or rendering performance. This message highlights a critical area needing investigation.
14 / 17
Sarah, during a code review, says: 'Our CLS score is fluctuating wildly – sometimes above 0.3! This is causing a jarring user experience.' What does 'CLS' (Cumulative Layout Shift) primarily measure in web performance?
CLS (Cumulative Layout Shift) measures how much a page shifts visually while it's loading. This happens when images or other content unexpectedly move around, creating a distracting and frustrating user experience. A high CLS score indicates a significant problem with layout stability.
15 / 17
Ben, in a PR description for a new feature, writes: 'Optimized image loading to improve INP.' What does 'INP' (Interaction to Next Paint) represent as a Core Web Vital?
INP (Interaction to Next Paint) focuses on measuring the responsiveness of a webpage when a user initiates an interaction – such as clicking a button or tapping a link. It's about how quickly the website responds *after* the initial content has loaded, directly impacting usability.
16 / 17
David reports: 'We're using both PageSpeed Insights and Lighthouse to monitor our website's performance.' What is the primary purpose of utilizing these two tools concurrently?
PageSpeed Insights and Lighthouse are both popular tools for analyzing website performance. They use different algorithms and data sources to measure Core Web Vitals. Combining their results helps identify overlapping issues – areas where both tools flag the same problems – leading to a more thorough understanding of the root causes.
17 / 17
Alex comments on a code review: 'Our INP is currently 6.5 seconds – that's a major concern given our target of 3.0.' What should Alex prioritize addressing first when aiming to improve this metric?
INP (Interaction to Next Paint) is directly influenced by the execution time of JavaScript. Slow JavaScript can significantly delay the responsiveness of user interactions. While image optimization and reducing HTTP requests are important, addressing slow JavaScript code will likely have the most immediate impact on INP.
This exercise, "Core Web Vitals Vocabulary", tests your understanding of wasm browser vocabulary and phrasing through 17 multiple-choice questions drawn from real workplace scenarios.
Is this 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 17 questions. Each one presents a realistic 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.
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.
Who is this Wasm Browser exercise for?
It's designed for IT professionals and learners who want to sound natural discussing wasm browser topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
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 Wasm Browser exercises?
Browse the full Wasm Browser exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.