Web Technology Basics

Among Core Web Vitals, the metrics of a web page's user experience, which of the following does CLS (Cumulative Layout Shift) represent?

  1. AThe time until the largest image or block of text on the screen is displayed while the page loads
  2. BThe delay from a user's click or key press until its result is drawn on the screen
  3. CThe amount by which elements unexpectedly shift position during display, caused for example by images or ads that load later
Show answer and explanation

Answer: C. The amount by which elements unexpectedly shift position during display, caused for example by images or ads that load later

Core Web Vitals consist of three metrics: LCP (Largest Contentful Paint) for loading speed, INP (Interaction to Next Paint) for responsiveness to interaction, and CLS for visual stability (INP replaced FID in March 2024). CLS quantifies unexpected shifts in position, such as text being pushed down by images or ads that appear later. Specifying width and height for images and videos so that their space is reserved in advance makes CLS smaller.

  • A. This is LCP, the metric for loading speed.
  • B. This is INP, the metric for responsiveness to interaction.
  • C. Correct. CLS represents visual stability, that is, unexpected layout shifts.
Practice this topic Back to topic

Books on Web Technology Basics Ad

As an Amazon Associate I earn from qualifying purchases.

More Web Technology Basics questions

  1. Which of the following is an appropriate pairing of an image format for web pages with its typical use?
  2. 3,000 bytes of image data are encoded with Base64 and embedded in HTML. If no line breaks are inserted, which of the following is the number of characters after encoding?
  3. A web system is built in three tiers: a web server, an application server and a database server. Which of the following is the processing that the application server mainly handles?
  4. Which of the following correctly describes a reverse proxy?
  5. With CGI, the web server starts the program as a new process every time it receives a request, and the process ends when processing is finished. Which of the following is the main reason that FastCGI and application-server approaches can handle many requests more efficiently than CGI?