Over a million developers have joined DZone.

The Critical Rendering Path

DZone's Guide to

The Critical Rendering Path

· Performance Zone ·
Free Resource

xMatters delivers integration-driven collaboration that relays data between systems, while engaging the right people to proactively resolve issues. Read the Monitoring in a Connected Enterprise whitepaper and learn about 3 tools for resolving incidents quickly.

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.

Discovering, responding to, and resolving incidents is a complex endeavor. Read this narrative to learn how you can do it quickly and effectively by connecting AppDynamics, Moogsoft and xMatters to create a monitoring toolchain.


Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}