What is the difference between "rendering" via the "content-visibility: auto" CSS property compared to lazy-loading images via "loading=\"lazy\""?
Correct! Well done.
Incorrect.
The correct answer is B) "content-visibility: auto" skips rendering (layout and paint) work for off-screen content of any kind until it is near the viewport, while "loading=\"lazy\"" specifically defers the network fetch of an image/iframe until it is near the viewport
Correct Answer
"content-visibility: auto" skips rendering (layout and paint) work for off-screen content of any kind until it is near the viewport, while "loading=\"lazy\"" specifically defers the network fetch of an image/iframe until it is near the viewport
content-visibility optimizes rendering cost for any off-screen subtree by skipping layout/paint, while native lazy-loading specifically defers fetching image/iframe resources — they address different bottlenecks (rendering vs. network) and can be used together.