A Republican Candidate’s Debate Performance vs. Website Responsiveness

A Republican Candidate’s Debate Performance vs. Website Responsiveness
By Dan Berkowitz

There were no fatal gaffes or significant surprises in the first Republican debate of the 2016 presidential race, and while it will take new polling to know how the candidates actually fared, there is a clear winner in the campaign website speed race. The Donald Trump site was the fastest of the ten candidates in the debate both leading up to and during the debate, as measured by AppDynamics. The site was among the lowest in total page weight (the amount of data being pushed through to users) which is likely a contributing factor to its consistent speedy performance.


Among the other candidates, Jeb Bush’s site was more than twice as fast on debate night as it was in the days before, likely due to some late night content trimming. Prior to the debate, the Bush site trailed the pack in second-to-last place, but by debate night, it moved up almost to the top, trailing only the Trump campaign site. Chris Christie’s campaign site also saw a big performance gain, loading more than 58 percent faster on debate night than during the week before, again likely because of last minute page weight reductions.

On the flip side, Marco Rubio’s campaign site saw a significant slowdown by the time the debates were over, with the homepage slowing down nearly 62 percent compared to the pre-debate measurement on Wednesday.

“The cable news pundits seemed to be impressed with Rubio’s debate performance,” said Peter Kacandes, senior product marketing manager at AppDynamics. “We can’t know for sure, but it’s possible that his site got a lot of traffic as a result, and slowed down under the load. We’ll be looking at the site after the debate excitement has died down to see if it recaptures speed with a more normal load.”

The speed gains by the Bush and Christie sites had nothing to do with the candidates’ performance in Cleveland, but more with structural changes made to their sites in time for the debates. Campaign web teams have learned from the most recent presidential elections that a top performing site that delivers solid user experience is essential for visibility, fundraising, and messaging. It is to the Bush and Christie teams’ credit that they were optimizing performance right up to the time their candidates stepped onstage.

“The Bush web team dramatically cut the weight of their homepage in time for the debate,” Kacandes said. “Just the day before, the site homepage weighed in at a hefty 7.8 megabytes, but on debate night, it was down to just over a single megabyte. That’s a huge reduction, and it delivered results with a homepage that loaded twice as fast. Similarly, the Christie homepage shed nearly two-thirds of its weight, going from six megabytes to just over two megabytes, and realized a big gain in speed as a result.”

Here is how the websites performed on average over the course of the week before Thursday and on average over the two hours before the debates ended Thursday night:

Candidate Website Pre-Debate End-User Response Time in Seconds
www.donaldjtrump.com 2.2
www.marcorubio.com 3.9
www.johnkasich.com 5.8
www.mikehuckabee.com 6.2
www.randpaul.com 8.3
www.tedcruz.com 8.7
www.chrischristie.com 9.5
www.bencarson.com 11.2
www.jeb2016.com 12.7
www.scottwalker.com 14.1


Candidate Website Debate Night End-User Response Time in Seconds
www.donaldjtrump.com 2.3
www.jeb2016.com 5.9
www.chrischristie.com 6.0
www.marcorubio.com 6.3
www.johnkasich.com 6.5
www.mikehuckabee.com 6.6
www.randpaul.com 8.4
www.tedcruz.com 8.3
www.bencarson.com 12.8
www.scottwalker.com 13.5

AppDynamics measured the ten candidates’ websites from two locations, one on the East Coast and one on the West Coast, using the Google Chrome web browser. While the actual experience of end users varies due to a variety of factors, the synthetic measurements offers an accurate, relative ranking of the performance of the candidates’ websites.

Dan Berkowitz is the Senior Director of Corporate Communications at AppDynamics.