Question 31
What is `content-visibility: auto`?
It skips rendering work for offscreen content until needed, improving rendering performance for long pages.
Question 31
It skips rendering work for offscreen content until needed, improving rendering performance for long pages.
Question 32
contain restricts layout/paint/style scope for elements to improve rendering isolation and performance.
Question 33
will-change hints future changes for optimization, but overuse can increase memory use. Apply sparingly and temporarily.
Question 34
Animating transform/opacity is typically smoother and cheaper than animating layout-affecting properties like width or top.
Question 35
Large paint areas, expensive shadows/filters, and layout thrashing can reduce smoothness.
Question 36
Provide robust fallback stacks and font-display strategy to reduce invisible text and layout shifts.
Question 37
It shows fallback text immediately while webfont loads, improving perceived performance.
Question 38
Body text generally benefits from line-height around 1.4 to 1.7 depending on font and measure.
Question 39
A typical target is ~45-75 characters per line to reduce eye strain and improve scanability.
Question 40
They reduce cross-browser inconsistencies in default element styling, creating a predictable baseline.
Question 41
Utility CSS emphasizes composition in markup, while semantic CSS uses named classes tied to components. Many projects combine both.
Question 42
Small reusable classes can reduce duplication and improve consistency, especially in design systems.
Question 43
Use root-level variables for tokens and override by theme scope ([data-theme="dark"]) for maintainable theming.
Question 44
filter affects the element itself; backdrop-filter affects content behind the element.
Question 45
Useful for decorative overlays that should not block clicks or interaction.