The Basics of Reading a Website Performance Waterfall Graph

When you’re using various tools to get information on what exactly is making your website slow, the most common method to display detailed information is a waterfall graph.

In this article, I will show you some tools that provide waterfall graphs and also give an explanation of how to read a simple waterfall graph.

The tool used in this graph is AOL Pagetest.

Some other tools that use waterfall graphs are:

Actually reading this graph is far easier than it looks.

The wider the graph, the slower your site is.

Any item that makes the graph wider by itself is singlehandedly making your page slower.

Each item is a “request”, where the browser talks to your web server to request a document.

In AOL PageTest, the time that the user first sees content (referred to as “Start Render”) is denoted by a green line that runs vertically along the graph.

Thus, my site shows a white page for 2.5 seconds until the first three resources have finished loading.

After the green line, the user can scroll around on the page, but other items are still downloading!

The dark blue line at the end is when the browser stops showing the loading indicators and when the page is considered “finished” loading:  anything loaded after this point is not preventing the page from loading faster.

how-to-read-waterfall-graph.png.png

  • Share/Bookmark
  1. Internet Strategist’s avatar

    Why did you select AOL Pagetest over the others you mention? This is definitely something I’ve been wondering how to measure for some time. I may not have the necessary skills to actually implement it in practice.

    By the way, what type of blog content “enthralls” you? I would have asked you on Twitter, but can’t get to you there.

    Reply

    1. mjc’s avatar

      ah, my twitter is http://twitter.com/projct :)

      I tend to use AOL PageTest primarily when looking to share results with someone: the fact that the results are returned with a permanent URL is very handy.

      Additionally, it’s free, open source, and pretty versatile.

      I would use Fiddler when trying to debug a performance regression in IE, if it’s already apparent not to be a javascript or rendering issue. The others are pretty similar, excepting that IBM’s tool is a lot more detailed, but overkill for most cases.

      As far as what enthralls me? hmm. Those who are consistently pushing the limits of technology, philosophy, language, photography. If you want to see my subscription list I am on Toluu as ‘mjc’.

      Reply

Bad Behavior has blocked 236 access attempts in the last 7 days.

Site speeded up by PHP Speedy Site speeded up by PHP Speedy