Every quarter, we take a look at the performance of 50 of the UK’s top retail home pages.
Typically, we see the numbers creep up every time. On average, Britain’s retail sites seem to be getting progressively slower. However, averages can be misleading, so for Q2 of 2016, we looked at distributions for a range of key metrics, comparing this quarter with the same period last year.
Many of our recent improvements to Performance Analyser have been about visual performance. For example, we now report on Speed Index (the rate at which a page becomes visually complete above the fold) and time to visually complete. The new Performance Heatmap is also a great way to see which parts of a web page display within given KPIs.
The problem: knowing when a page is ‘finished’
Looking at a web page in this way can really help to understand its performance from the visitor’s point of view. However, it also introduces a problem: how do you know when the page has reached its final state?
If you want detailed, accurate insight into how your website’s performing, Performance Analyser, our real-browser testing and analysis tool, is an excellent way to get the answers you need. You can run single page tests or crawls in a number of real browsers, as well as schedule regular tests.
I’ve been working on Performance Analyser for some time now, and I thought I’d run through a few of the things that I think make it a bit special.