About Us
Services
Our clients
Press Room
Careers
Policies
Buttons
Performance Tracking
Blog
Performance Tracking  > 2017 Vacation Planning

WebSitePulse 2017 Vacation Planning Websites Performance Report Summary


Vacation planning season is over and we are finished monitoring 13 of the most popular international websites for travel and tourism for the period between May 25th and June 30th, 2017 for our 2017 Vacation Planning Season Report.

The overall performance of the monitored travel booking websites demonstrated their preparedness to meet the challenges of the expected heavy web traffic during the whole 2017 vacation planning season.

We have found out the daily average response time from all monitored websites was 4.443 sec. The daily average responses by locations are as follow:

  • Washington DC (US East Coast) – 3.472 sec
  • San Francisco, CA (US West Coast) – 3.934 sec
  • Sydney (Australia) – 5.929 sec
  • Amsterdam (Netherlands, Europe) – 4.45 sec

This year travelocity.com was the speed leader among the 13 monitored websites with an average response time of 1.28 seconds, followed by tingo.com (1.58 sec) and cheaptickets.com (1.838 sec). Far away at the bottom of the table was homeaway.com with 10.566 seconds average response time which may have caused some lost profit. The daily average uptime for the entire group of 13 websites for 2017 travel planning season was 99.96%. The daily average uptime by locations are as follow:

  • Washington DC (US East Coast) – 99.96%
  • San Francisco, CA (US West Coast) – 99.97%
  • Sydney (Australia) – 99.96%
  • Amsterdam (Netherlands, Europe) – 99.95%

We have two winners with 100% average uptime for this year’s vacation planning season and they are booking.com and tripadvisor.com, followed by travelocity.com (99.999%) and tingo.com (99.999%). At the bottom of the availability chart stands hotels.com with 99.746% which leaves them with a room for some improvements.

For more details, see the reports below:

Average Response times for the whole period
#TargetSan FranciscoAmsterdamWashingtonSydneyAvg. resp. time
1travelocity.com1.1101.2361.1251.6481.280
2tingo.com1.7361.3540.9042.3251.580
3cheaptickets.com1.5551.7771.5402.4791.838
4ebookers.com2.0732.1171.9093.0332.283
5orbitz.com1.8912.2461.6383.5322.327
6expedia.com1.9202.6231.8603.0722.369
7tripadvisor.com3.9883.0282.6604.4943.542
8hotels.com3.8414.3383.9764.9774.283
9travelzoo.com3.2794.4303.5757.1424.607
10booking.com6.8794.1244.8078.5286.084
11airbnb.com5.7626.2673.22811.2016.614
12choicehotels.com9.09412.55910.3349.52210.377
13homeaway.com8.01311.7497.57314.93010.566

Average Uptime for the whole period
#TargetSan FranciscoAmsterdamWashingtonSydneyAvg. uptime
1tripadvisor.com100.000%100.000%100.000%100.000%100.000%
2booking.com100.000%100.000%100.000%100.000%100.000%
3travelocity.com100.000%99.995%100.000%100.000%99.999%
4tingo.com100.000%100.000%100.000%99.995%99.999%
5choicehotels.com100.000%99.995%100.000%99.993%99.997%
6travelzoo.com100.000%99.989%99.995%100.000%99.996%
7cheaptickets.com99.983%99.995%100.000%99.995%99.993%
8orbitz.com99.987%100.000%99.994%99.987%99.992%
9ebookers.com99.989%99.995%99.976%99.995%99.989%
10homeaway.com100.000%99.987%99.978%99.982%99.987%
11expedia.com99.993%99.985%99.940%99.993%99.978%
12airbnb.com99.799%99.777%99.801%99.782%99.790%
13hotels.com99.798%99.653%99.815%99.716%99.746%

Best regards, and takeITeasy™ with WebSitePulse™

Iavor Marinoff, CEO


Methodology:
Performance and availability are measured for a typical travel-related booking web transaction at 15 minute monitoring interval, every day, 24/7. The WebSitePulse application monitoring service is used to collect data and to create the reports.
The steps in each transaction are comparable for all websites, and reflect the real online buyers' experience. The simultaneous monitoring is performed from four locations of the WebSitePulse global monitoring network: San Francisco, CA; Washington, DC; Sydney, Australia, and Amsterdam, Netherlands. In case of a detected malfunction or unavailability, the system performs automated error verification from four independent resources and only after the above procedure is performed and has returned consistent results, the detected error is confirmed, recorded, and included in the daily performance reports. In these cases, an advanced WebSitePulse exclusive feature comes into play - Forced Monitoring -, which automatically switches to a 3 minute monitoring interval for increased accuracy.

About WebSitePulse:
WebSitePulse is a leading provider of global, independent, and objective availability and performance monitoring of web sites, servers, network components, web applications, e-business- and email round-trip transactions.

Contact:
For more information about this report please contact:
George T., CTO
phone: 1-407-380-1600
email:


Reproduction:
WebSitePulse launched the Performance and Uptime Reports program to keep the general public and the Internet community informed about the performance of specific websites and the challenges their webmasters, owners and operators are facing on a daily basis, especially when the web traffic intensifies due to some special events through the year. Some of the most popular web destinations, related to each particular event, are selected for the purpose of the Reports, and data from their performance measurements is made available on the WebSitePulse public website.

With the intention to broadly disseminate this information for the benefit of the Internet community, we encourage the use of this information without prior approval and under the following Terms and Conditions:
  • WebSitePulse should be referred as the "Source" of the information;
  • WebSitePulse should be acknowledged as the owner of the copyrights of the information in the Reports;
  • The texts of the Reports could be changed or altered to better suit the needs and the style of the publisher without prior notice to WebSitePulse. However, the integrity and the meaning of the information should be preserved;

The Data from the performance measurements cannot be changed or manipulated and should be used "as is".