Over a million developers have joined DZone.

The Critical Rendering Path

DZone's Guide to

The Critical Rendering Path

· Performance Zone ·
Free Resource

Learn how error monitoring with Sentry closes the gap between the product team and your customers. With Sentry, you can focus on what you do best: building and scaling software that makes your users’ lives better.

In Part 3 of Google developer advocate Ilya Grigorik's Crash Course on Web Performance talk, the presenter explains what is so "critical" about the critical rendering path, or the order in which a browser loads your web app's resources.

Grigorik explains that in your web app you shouldn't wait to render the full HTML file, "flush early, flush often," he says, and provide your user with a blank screen until the entire render tree is ready.

But modern web apps aren't just HTML and CSS. JavaScript can be both your friend and foe when developing high-performance web apps, so Grigorik provides some JavaScript performance pitfalls, how JavaScript fits into the critical rendering path and how to optimize the rendering path by eliminating JavaScript from the critical rendering path.

What’s the best way to boost the efficiency of your product team and ship with confidence? Check out this ebook to learn how Sentry's real-time error monitoring helps developers stay in their workflow to fix bugs before the user even knows there’s a problem.


Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}