INP (Interaction to Next Paint) thresholds: • ≤200ms → ✓ Good • 200–500ms → ⚠️ Needs Improvement (380ms is in this range) • >500ms → ❌ Poor
Key vocabulary: • threshold — the boundary value that separates Good / Needs Improvement / Poor • needs improvement / within acceptable range — language for nuanced client reporting • LCP, CLS, INP — the three Core Web Vitals metrics Google uses in search ranking
2 / 10
A performance audit shows these Lighthouse scores for a SaaS dashboard:
61 is in the "Needs Improvement" range — not broken, but a significant opportunity. Accessibility (94), Best Practices (92), and SEO (88) are all in the Good/Needs Improvement range.
Key phrases for stakeholder communication: • "significant opportunities" — technical debt framing without alarm • "in good shape" — informal but clear status for non-technical reviewers • "bottleneck" — the limiting factor in a system; the constraint preventing improvement
Common Lighthouse performance issues: Render-blocking resources, large unoptimised images, unused JavaScript, long main-thread tasks, no caching headers.
3 / 10
A team has optimized their landing page. Before vs. after measurements:
How would you describe these results to the product manager?
What changed: • LCP: 5.8s (Poor: >4s) → 2.1s (Good: ≤2.5s) — major improvement, moved from Poor to Good • FCP: 3.2s (Needs Improvement: >1.8s) → 0.9s (Good: ≤1.8s) — moved to Good • TBT: 840ms → 120ms — 85.7% reduction; TBT directly measures main-thread blocking
Core Web Vitals vocabulary: • LCP (Largest Contentful Paint) — when the main content of the page loads • FCP (First Contentful Paint) — when the first text/image appears (not a Core Web Vital but key metric) • TBT (Total Blocking Time) — sum of time the main thread was blocked over 50ms tasks • "moved out of the Poor zone" — precise language referencing the threshold categories
A developer says: "Our CLS jumped from 0.05 to 0.31 after the banner redesign." Which response shows the correct understanding of what this means for users?
CLS (Cumulative Layout Shift) measures visual stability — how much the content moves around unexpectedly as the page loads.
• 0.05 → ✓ Good (≤0.1 threshold) • 0.31 → ❌ Poor (>0.25 threshold) — significant jump across TWO thresholds
What a CLS of 0.31 feels like: You're about to click a button, and the page shifts — your click lands on a different element. This leads to accidental ad clicks, form submissions, or navigation errors. High CLS is one of the most frustrating UX issues.
Common causes of CLS: • Images/videos without explicit width/height attributes • Ads, embeds, or iframes appearing above existing content • Dynamically injected content (cookie banners, notification bars) • Web fonts causing FOUT (Flash of Unstyled Text)
Key vocab: • visual stability — how consistent the page layout is during loading • layout shift — when a visible element changes position unexpectedly • FOUT — Flash of Unstyled Text: text renders in fallback font then jumps when web font loads
5 / 10
A team wants to present their Core Web Vitals improvement to stakeholders. Which framing is most effective and accurate?
The best stakeholder framing combines: 1. Results in plain language ("all three Core Web Vitals into the Good zone") 2. Specific numbers (before → after for each metric) 3. Business context ("Google ranking signal", "reduce bounce rate")
Why the other options fail: • "Lighthouse score went up" — Lighthouse score is a lab test, not field data. It's useful but doesn't prove real-user experience. • "No direct impact" — This is false. Core Web Vitals directly affect user experience AND Google Search ranking since 2021. • "Wait 2.5 seconds less" — Technically inaccurate. LCP is when the largest content element renders, not total page load. Users don't wait from 0 — they see content progressively.
Core Web Vitals in communication: • Always cite the zone (Good / Needs Improvement / Poor) alongside the raw number • Connect to business KPIs: bounce rate, conversion, organic ranking • Use "field data" (real user monitoring, RUM) vs "lab data" (Lighthouse) distinction when presenting to engineers
6 / 10
Alex (Senior Developer) comments on a pull request:
'The LCP is still high at 4.1s. We need to investigate the image delivery and consider lazy loading strategies. This impacts page performance significantly.' What does Alex *primarily* mean in this context?
Alex is focusing on Largest Contentful Paint (LCP), a Core Web Vital. LCP measures how long it takes for the largest element visible in the viewport to render – a slow LCP directly impacts perceived page load speed and user satisfaction. While redesigns can sometimes affect LCP, Alex's comment specifically targets the technical metric.
7 / 10
You're drafting a Slack message to your team regarding a recent Core Web Vitals audit:
'We've identified some areas for improvement. Specifically, our Current Layout Shift (CLS) score is at 0.15 – above the recommended threshold of 0.1. This means elements on the page are shifting unexpectedly as users scroll, which can be jarring and frustrating.' Which of the following best explains *why* a high CLS score is problematic?
A high Core Web Vital score – in this case CLS – doesn't inherently relate to navigation or design. Instead, it points to instability: unexpected shifts in page layout while the user is navigating. This creates a negative user experience and violates best practices for usability.
8 / 10
You're preparing a PR description for a change that improved First Contentful Paint (FCP). The previous FCP was 6.5 seconds; the new FCP is 2.8 seconds. Which of the following statements accurately summarizes this improvement for reviewers?
FCP measures the time it takes for *any* content to appear on the screen. Reducing FCP from 6.5s to 2.8s demonstrates a substantial improvement in initial page load speed – the first thing users see is much faster, directly impacting perceived performance and user satisfaction.
9 / 10
Sarah (Product Manager) asks you to explain the implications of a sudden increase in Cumulative Layout Shift (CLS) from 0.08 to 0.25 after a new promotional banner was added:
'What does this mean for our users?' Which explanation is most appropriate?
A high CLS score means that elements are moving around unexpectedly as users scroll. This can disrupt the intended layout and cause visual confusion, negatively impacting the user experience – this is what Sarah is asking about. Focusing on aesthetics or faster loading doesn't address the core issue of instability.
10 / 10
Your team is presenting Core Web Vitals improvements to stakeholders. Which statement best frames the value proposition for a non-technical audience?
For non-technical stakeholders, it's crucial to translate technical jargon into tangible benefits. Reducing page load times (as measured by Core Web Vitals) directly translates to faster user experiences and increased engagement – a key metric for business success.
What will I practise in "Core Web Vitals in English"?
This module focuses on Numbers, Data & Metrics — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Numbers, Data & Metrics exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around numbers, data & metrics — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Numbers, Data & Metrics exercises?
See the Numbers, Data & Metrics hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.