Grundfos: Performance is crucial for the web experience


Slow load times is often cited as one of the key reasons why people leave a website. Making a website really fast is quite complicated though, and unfortunately there is no silver bullet. At Grundfos, the world's largest pump manufacturer with more than 18,000 employees globally, they built performance into their website relaunch project from the very beginning. How did they manage to implement as many performance gains as possible and thus improve the user experience?

I recently had a conversation with Thomas Ørgaard Bredgaard who is Department Head, Web Management at the Denmark-based headquarters and a member of our groups for online professionals. He shared several critical and hard-earned lessons on performance and how it relates to a global, complex and large business-to-business company.

The Grundfos website performance challenge

Unlike media or transportation companies who experience extreme peaks due to breaking news or inclement weather, Grundfos as a B2B company did not have to worry so much about load balancing to handle peaks. With up to 6 million visitors projected next year to Grundfos websites and a distributed IT infrastructure led from the headquarters in Bjerringbro, Denmark, the key challenge in the recent website redesign was to ensure that the website was equally fast for a customer or distributor visiting the site from Beijing, Boston or Brisbane.

As illustrated by this recent tweet from user experience expert Jared Spool, slow performance can lead to bad publicity. For Grundfos, the main concern was users leaving the site for competitors or resorting to more expensive phone calls or e-mails for product inquiries.

Besides the global reach, Grundfos also has a website packed with several different content types, including videos and several applications. This required extensive testing and several layers of performance improvements to get right.

Further complicating the matter was the lack of industry best practices when it comes to performance guidelines. As Thomas said:

We were unable to find any standards or reports detailing performance requirements for a large, complex and global B2B company. To establish a working definition of acceptable performance requirements we had to get inspiration from the consumer space and vendors specializing in content delivery.

According to Thomas, Grundfos used the below 2 sources as main inspiration to define acceptable performance:

The many elements of the solution

To make sure that the new website would be delivered within a time-frame of 2,5 to 5 seconds, depending on content type, Grundfos had to undertake several actions, some complicated and technically demanding, while others were more about project management.

A key step according to Thomas was creating a cross-functional web performance team including members from IT and business units. As Thomas said:

This team meets regularly to review performance improving initiatives and also discuss any issues, such as areas of the website which are performing poorly. The main focus of the team is to find potential improvements, whether governance initiatives to prevent large images on the frontpage or purely technical issues

Here some other steps which Grundfos have implemented:

  • Performance goals have been built into the service level agreement (SLA) with the IT department, profiling both up-times and load-times
  • To measure and benchmark performance globally, Grundfos decided to work with Gomez, a vendor specializing in web load testing, cross-browser testing, and web performance management
  • The relaunch was based on a new Web CMS (Day CQ5). During the Day CQ5 CMS implementation Grundfos used web performance best practices from Google and Yahoo Yslow to keep the focus on performance from the beginning. Testing happened often and early to make sure that potential slow areas could quickly be identified and addressed
  • During the project planning the concept of static vs. dynamic delivery, also known as "frying vs. baking", was carefully considered. In brief, the idea is to ensure that only those website elements which are truly dynamic, e.g. application output, are generated at every request, while other static elements (e.g. the Grundfos logo and press releases) are published to a server for quick delivery. Day CQ5 has several performance guidelines and Grundfos implemented caching as well as static publishing as much as possible
  • jQuery, a fast and concise JavaScript Library, was implemented using the Google Libraries API, which is a content distribution network and loading architecture for the most popular, open-source JavaScript libraries

In addition, Grundfos is currently considering using a content delivery network, such as Akamai, to leverage a globally distributed hosting infrastructure.

Learn more

If you don't have a large and globally distributed IT infrastructure like Grundfos, another option for performance improvements may be cloud computing.

Besides quick response-times and doing what you can to makes your website fast, you should also consider up-times, to ensure that the website is actually up and running most of the time.

In a recent eConsultancy article, slow load times were cited as one of 25 reasons why I'll leave your website in 10 seconds

Join our community for online professionals and benefit from the insights of experienced online professionals whilst cutting out the time consuming digging and the awkward small-talk.

Janus Boye

Janus Boye
CEO and Head of Research

As founder and managing director at J. Boye, Janus has grown the business from an office at home in 2003 to an international operation today with members in Europe and North America.

Janus is a frequent speaker at industry events and chairs the renowned J. Boye Conferences held since 2005 in Denmark and since 2009 in Philadelphia, US. Among the organisations that have recently called upon Janus' expertise are  local government agencies, the UN in New York and companies such as Brother, Carlsberg and Red Bull.

2 Responses to “Grundfos: Performance is crucial for the web experience”

  1. [...] Read how Grundfos treated performance as crucial part of the web experience [...]

  2. Craig Hyde says:

    Good post on the importance of speed. If a site is too slow, people just won’t use it.

    It’s an interesting point about the lack of a standard for specific types of sites. My company focuses on improving speed and availability for web applications, and a common question we get is “What is good for us?” Our process is to use comparable alternatives to benchmark against, and work to be better than your competition.

    (Disclaimer: I’m a co-founder or

Leave a Reply

Most popular posts from our blog
August 12, 2009 by Janus Boye
Selecting the right CMS is not an easy task with; there is in excess of 1,000 vendors in the very dynamic CMS…
February 16, 2010 by Janus Boye
All modern CMS vendors claim to be capable of delivering content to mobile devices. Some even offer additional modules to make the…
March 21, 2011 by Janus Boye
You may be impressed by some of the features during a CMS product presentation, but in reality many of the features that…
Recent comments
April 8, 2014 by Bertrand
I would include the Apache Sling website in this list ( ) as it's what powers AEM. Understanding the…
April 8, 2014 by Scott Liewehr
Great resource, Janus. And thanks for the mention.
March 15, 2014 by John
Their site may not even be a CMS but more of a custom built web application. Also, how do you…