Understand Core Web Vitals (LCP, CLS, INP), Lighthouse metrics, and web performance vocabulary in technical context.
0 / 10 completed
1 / 10
LCP (Largest Contentful Paint) measures:
LCP measures perceived load speed — how long until the main content (image, heading) of the page is visible to the user.
2 / 10
CLS (Cumulative Layout Shift) measures:
CLS measures visual stability — how much content unexpectedly shifts during page load. A high CLS score means elements jump around, causing poor UX.
3 / 10
INP (Interaction to Next Paint) measures:
INP replaced FID as a Core Web Vital — it measures how quickly a page responds to user interactions (clicks, taps, key presses) throughout the entire session.
4 / 10
In Lighthouse, a 'Time to Interactive (TTI)' score measures:
TTI measures when the main thread is quiet enough that the page can reliably respond to user input — a key usability milestone beyond just visual load.
5 / 10
A 'render-blocking resource' is:
Render-blocking resources delay the First Contentful Paint — typically synchronous CSS and JavaScript in the document head that must be parsed before rendering begins.
6 / 10
Sarah (Senior Frontend Developer) comments on a PR draft:
'The LCP is consistently over 4 seconds. We need to investigate the loading of this large image – it's likely a render-blocking resource contributing significantly to the delay. Let's prioritize optimizing that asset.' What does Sarah primarily mean in this comment?
Sarah correctly identifies that the LCP – Largest Contentful Paint – is related to the initial loading of content. A 'render-blocking resource' like a large image prevents the browser from rendering the rest of the page quickly. The key takeaway here isn't about CDN usage or image rotation, but the direct impact of this particular asset on first paint.
7 / 10
Mark (DevOps Engineer) sends a Slack message to the team:
'I've run Lighthouse on the staging environment and the CLS score is consistently around 0.15. This indicates significant layout shifts during page loading – elements are moving unexpectedly. We need to address these before deploying.' What does Mark's message relate to?
Mark is referring to Cumulative Layout Shift (CLS). This metric specifically quantifies how often elements on a webpage move around unexpectedly while it's loading. High CLS values create a frustrating user experience and are penalized by search engines – it's not about visual appeal or responsiveness.
8 / 10
The following API response is received from the backend:
{ "status": 'error', "message": 'Resource unavailable due to high server load.' }
Which of the following best describes how this response relates to web performance?
The response indicates a high server load. This directly impacts the backend's ability to process requests efficiently, leading to slower page loading times and a degraded user experience. While other issues could be present, this API error is a key performance bottleneck.
9 / 10
David (Frontend Developer) writes in a PR description:
'I've optimized the critical CSS to reduce render blocking and improve initial page load time. The goal is to achieve a good First Contentful Paint (FCP) score.' What does David primarily focus on?
David is concerned with First Contentful Paint (FCP), which measures when the first piece of content becomes visible on the screen. Optimizing critical CSS – the CSS that's necessary to render the initial viewport – directly reduces this time and improves perceived performance.
10 / 10
During a standup meeting, Emily (Backend Engineer) says:
'I've made some changes to the database queries. I'm monitoring the INP and aiming for a score of under 200ms.' What does Emily's statement refer to?
Emily is tracking Interaction to Next Paint (INP), which measures how quickly a website responds to user interactions – like clicks or taps. A low INP indicates a responsive and performant user experience. It's not about data transfer volume or the database size itself.
This exercise, "Web Performance & Core Web Vitals Vocabulary", tests your understanding of wasm browser vocabulary and phrasing through 10 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 10 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.