DeepFrontend
Learning Paths
Practice
System Design & DS
Design Studio
Data Structures Curriculum
Real-World Case Studies
Careers
Job Board
Resume Builder
Blog
Sign in
Search
⌘K
Go Pro
Loading compiler resources...
Next.js Quiz Practice
Active Recall Drill Session
← Exit Session
Question 1 of 1
medium
Next.js
Why might you deliberately wrap an ENTIRE page in loading.tsx rather than trying to make a critical data request non-blocking?
A
This is never appropriate
B
Some data genuinely must resolve before ANYTHING meaningful can be shown — forcing it to be non-blocking wouldn't make sense; a whole-page loading state is the honest UX for that case
C
loading.tsx only works for entire pages, never partial content
D
It's required by Next.js for all dynamic routes
Check Answer