Over a million developers have joined DZone.
Platinum Partner

Taking Your Web Performance's Temperature Using a Heat Map

· Performance Zone

The Performance Zone is brought to you in partnership with New Relic. Quickly learn how to use Docker and containers in general to create packaged images for easy management, testing, and deployment of software.

In this Heat Map example, web site’s Performance data is overlay with color, where red means “slowest” and green means “fastest” (with various color grades in between). I added this Heat Map example because the chart data was difficult to “crunch”, to analyze for patterns; adding color made this easier. Download the Excel sheet here. Otherwise, see the below “Before” and “After”.

Before: Raw Chart Data:

After: Heat Map:

Side by Side:

The chart data is the arithmetic mean average of six weeks’ worth of web site response time measurements (in milliseconds), broken down by Day of Week and by Hour of Day. I then used Excel’s built-in /Conditional Formatting/Color Scales/Red – Yellow – Green Color Scale/.

Document Complete / OnLoad:

_The following is optional reading material._

Here are some potential fact statements we get from looking at this Heat Map:

01. The weekends are the “fastest”.

02. The weekdays are the “slowest”.

03. Response Time slows starting at around 07:00 AM PT and Response Time speeds starting at around 07:00 PM PT.

04. The “slowest” (i.e. the most red) “Day of Week”/”Hour of Day” combination is Wednesday at 05:00 PM PT.

05. The “fastest” (i.e. the most green) “Day of Week”/”Hour of Day” combination is Wednesday at 02:00 AM PT.

06. Interestingly enough, the “fastest” and “slowest” “Day of Week”/”Hour of Day” combination was on a Wednesday.

07. Friday afternoons were “faster” when compared to other weekday afternoons (insert comment here RE: folks getting ready for the weekend!).

Download the Excel file here: https://docs.google.com/open?id=0B9n5Sarv4oonMEdtOTlvOHNib0E


I used his model to chart the performance heat map of Google Search (search for a keyword) and decided to compare the Wait time (1st byte) and their Search Query Time:

Google’s Wait Time vs. Google Search Query Time


Here is the same for Etsy’s home page, Wait time and the Etsy server time:

Etsy’s Wait Time vs. Etsy’s Server Time


(Data from June 1 2012 to July 13 2012, Time in EST)

I used these 2 examples mainly because not only we are plotting a Catchpoint metric but also overlaying customer telemetry coming from Google (how long it takes for Google to spit the results) or Etsy (how long it takes for their server to build the html). What would be cool is to get traffic volume during those days and hours to correlate the performance metrics and usage pattern. But what these chart show is clearly a performance degradation during certain days and hours of day that are driven by volume, users, usage…

Enjoy the Summer and try to keep your Web Performance Cool!
Thank you Leo for sharing this!

The Performance Zone is brought to you in partnership with New Relic. Read more about providing a framework that gets you started on the right path to move your IT services to cloud computing, and give you an understanding as to why certain applications should not move to the cloud.


Published at DZone with permission of Mehdi Daoudi , DZone MVB .

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}