jargon

Frontend & browser·topic 7 of 13

Performance and Core Web Vitals

The metrics are not the point; they exist because 'the page feels slow' is not actionable and 'the largest element paints at 4.2 seconds' is. Learn which number moves when you fix which thing.

Read in order · tick what you already know

  1. 01

    you were handed three numbers and told the page fails on one of them, at the 75th percentile.

    Core Web Vitals

  2. 02

    the browser sat waiting with an empty tab before a single byte of HTML came back.

    Time to first byte

  3. 03

    the first text or image appeared, so the user finally knew the page was alive.

    First contentful paint

  4. 04

    the big hero image finally rendered, four seconds after the header was already on screen.

    Largest contentful paint

  5. 05

    you went to click the button, an ad loaded above it, and you clicked something else entirely.

    Cumulative layout shift

  6. 06

    you clicked the checkbox and it took most of a second before the tick appeared.

    Interaction to next paint

  7. 07

    the lab report says two seconds of blocking time and you can see it as a wall of yellow in the profile.

    Total blocking time

  8. 08

    the page looked finished for a while before it would actually respond to a click.

    Time to interactive

  9. 09

    one function held the main thread for 300 milliseconds and every click during it queued up behind it.

    Long task

  10. 10

    the scroll is smooth and then jumps, because a frame took too long and got skipped.

    Jank

  11. 11

    you have about ten milliseconds of your own work per frame before the animation starts dropping.

    Frame budget

  12. 12

    you read `offsetHeight` and wrote a style inside the same loop, and the loop got slower with every item.

    Layout thrashing

  13. 13

    the profiler flags a purple block with a warning triangle where you asked for an element's width.

    Forced synchronous layout

  14. 14

    you told the browser to skip rendering the sections that are off screen and the initial layout got much faster.

    content-visibility

  15. 15

    you ran the audit on your laptop, got a score of 98, and shipped a page that is slow for everyone else.

    Lab data

  16. 16

    the dashboard shows the metric at the 75th percentile across everyone who actually loaded the page last month.

    Field data

  17. 17

    you moved the number from 62 to 91 and nobody could feel the difference on the actual site.

    Lighthouse score

  18. 18

    you showed a response to the click immediately, even though the real work took another second.

    Perceived performance