Intermediate: Performance
intermediate: performance performance — 25 interview questions with traps, follow-ups, and production context. practice out loud; staff loops reward trade-offs,
Introduction
Performance — 25 interview questions with traps, follow-ups, and production context. Practice out loud; staff loops reward trade-offs, not definitions.
Business problem
Business pressure: Product teams need Performance interview questions to ship polished UI without layout regressions, accessibility lawsuits, or LCP regressions that hurt conversion.
- Conversion: Visual polish and performance directly affect checkout and signup funnels.
- Brand: Inconsistent Performance interview questions implementation fragments design system trust.
- Velocity: CSS debt slows every feature team — architecture matters at scale.
Why this feature exists
Platform history: CSS evolved Performance interview questions to solve author needs without JavaScript layout engines or table hacks.
- Problem solved: Declarative styling separated from document structure.
- Rejected alternative: Inline styles and JS layout — unmaintainable at enterprise scale.
Browser rendering perspective
Rendering impact: Performance interview questions affects style recalculation, layout, paint, and composite stages in the browser pipeline.
- Chrome (Blink): Style → LayoutNG → Paint → Viz compositor.
- Firefox (Gecko): Servo-based stylo + WebRender compositing.
- Safari (WebKit): WebKit style resolver + GPU layer promotion rules.
Internal browser workflow
Workflow: Selector match → cascade → computed values → layout tree → paint layers → composite.
Real production example
Production: Netflix, Amazon, and Shopify enforce Performance interview questions patterns via design tokens, lint rules, and visual regression CI.
Enterprise use case
Enterprise: Design systems (Polaris, Carbon, Atlassian) codify Performance interview questions in token pipelines and component APIs.
Accessibility considerations
A11y: CSS must not remove focus visibility, break zoom, or convey state by color alone (WCAG 2.2).
Performance considerations
Performance: Performance interview questions can trigger reflow, expensive selectors, or layer explosion — profile with DevTools Performance panel.
SEO considerations
SEO: CSS affects LCP, CLS, and mobile usability — ranking signals tied to Core Web Vitals.
Scalability considerations
Scale: Performance interview questions choices compound across micro-frontends, white-label tenants, and dark-mode variants.
Common production issues
Production failures: Specificity wars, z-index stacks, and responsive breakpoints that work in Chrome but break Safari.
Debugging guide
Debug: Chrome DevTools → Elements (computed styles), Layout panel, Rendering layers, Coverage for unused CSS.
Interview questions
Intermediate CSS — Performance: explain critical rendering path CSS role.(Intermediate)
critical rendering path CSS role.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 1: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain render blocking CSS link.(Intermediate)
render blocking CSS link.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 2: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain async CSS load pattern.(Intermediate)
async CSS load pattern.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 3: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain preload stylesheet cautions.(Intermediate)
preload stylesheet cautions.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 4: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain unused CSS coverage audit.(Intermediate)
unused CSS coverage audit.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 5: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain selector performance myth vs reality.(Intermediate)
selector performance myth vs reality.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 6: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain reflow expensive properties.(Intermediate)
reflow expensive properties.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 7: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain composite only transform opacity.(Intermediate)
composite only transform opacity.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 8: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain layout thrashing read write batch.(Intermediate)
layout thrashing read write batch.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 9: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain content-visibility auto.(Intermediate)
content-visibility auto.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 10: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain contain property strict.(Intermediate)
contain property strict.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 11: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain font-display swap.(Intermediate)
font-display swap.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 12: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain subset fonts limit weights.(Intermediate)
subset fonts limit weights.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 13: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain inline critical CSS size budget.(Intermediate)
inline critical CSS size budget.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 14: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain HTTP cache CSS fingerprint.(Intermediate)
HTTP cache CSS fingerprint.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 15: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain CSS minification gzip brotli.(Intermediate)
CSS minification gzip brotli.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 16: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain avoid @import chain.(Intermediate)
avoid @import chain.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 17: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain will-change abuse memory.(Intermediate)
will-change abuse memory.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 18: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain CLS from CSS without dimensions.(Intermediate)
CLS from CSS without dimensions.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 19: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain LCP CSS blocking hero.(Intermediate)
LCP CSS blocking hero.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 20: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain DevTools performance panel CSS.(Intermediate)
DevTools performance panel CSS.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 21: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain RUM vs lab CWV.(Intermediate)
RUM vs lab CWV.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 22: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain Safari specific perf quirks.(Intermediate)
Safari specific perf quirks.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 23: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain Interview trap: inline all CSS.(Intermediate)
Interview trap: inline all CSS.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 24: What breaks in production if you ignore this?
Intermediate CSS — Performance: explain performance budget CI gate.(Intermediate)
performance budget CI gate.. Interview trap: memorizing API without browser pipeline story fails senior loops. Tie to measurable outcome: layout stability, a11y conformance, or bundle bytes.
Follow-up: Follow-up 25: What breaks in production if you ignore this?
Hands-on exercise
Mock interview drill: Answer all 25 questions out loud in 45 minutes. Record yourself explaining trade-offs, not just definitions.
Try it yourself
Edit the CSS panel — the preview updates live. Use DevTools Performance and Accessibility panels to validate.