Learning on Web Dev Open is free for all.

Immersive Web > Budgets, accessibility and the black screenProfiling what you cannot see
Phase 07Budgets, accessibility and the black screen367 of 434

Profiling what you cannot see

renderer.info, a stats panel, a GPU frame capture, and the one question that matters: are you CPU bound or GPU bound?

Build40 minAI pair

Build this in your own editor

This one runs on your machine rather than in the browser workbench. Work to the outcomes below, then come back and mark it complete.

You should now be able to

  • Read draw calls, triangles and memory from the renderer
  • Distinguish a CPU-bound frame from a GPU-bound one
  • Capture and read a single frame of GPU commands
Ask the community

Loading…

← PreviousThe budget comes before the sceneBudgets, accessibility and the black screenNext →What a mid-range phone can holdBudgets, accessibility and the black screen