Tools & Wizards About Us
traveling.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

traveling.com

Vacations, Cheap Flights, Cheap Hotels, Cars, Tours - Traveling.com

Page Load Speed

836 ms in total

First Response

80 ms

Resources Loaded

594 ms

Page Rendered

162 ms

traveling.com screenshot

About Website

Visit traveling.com now to see the best up-to-date Traveling content for United States and also check out these interesting facts you probably never knew about traveling.com

Book your trip with Traveling.com. Buy airline tickets, reserve hotels, car rentals, read reviews, and find exclusive deals on travel. Traveling.com

Visit traveling.com

Key Findings

We analyzed Traveling.com page load time and found that the first response time was 80 ms and then it took 756 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

traveling.com performance score

0

Network Requests Diagram

traveling.com

80 ms

www.traveling.com

149 ms

normalize.css

26 ms

jquery-ui.css

47 ms

default.css

51 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 92% of them (36 requests) were addressed to the original Traveling.com, 5% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (149 ms) belongs to the original domain Traveling.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 362.7 kB (48%)

Content Size

749.1 kB

After Optimization

386.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Traveling.com main page is 749.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 394.7 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 31.8 kB

  • Original 37.7 kB
  • After minification 30.9 kB
  • After compression 5.9 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 6.8 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 31.8 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 3.0 kB

  • Original 243.2 kB
  • After minification 240.2 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Traveling images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 268.6 kB

  • Original 394.7 kB
  • After minification 383.9 kB
  • After compression 126.0 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 268.6 kB or 68% of the original size.

CSS Optimization

-81%

Potential reduce by 59.3 kB

  • Original 73.5 kB
  • After minification 59.1 kB
  • After compression 14.3 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Traveling.com needs all CSS files to be minified and compressed as it can save up to 59.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (32%)

Requests Now

37

After Optimization

25

  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Traveling. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

traveling.com

traveling.com

80 ms

www.traveling.com

www.traveling.com

149 ms

normalize.css

normalize.css

26 ms

jquery-ui.css

jquery-ui.css

47 ms

default.css

default.css

51 ms

site.css

site.css

45 ms

home.css

home.css

49 ms

jquery.js

jquery.js

75 ms

jquery-ui.js

jquery-ui.js

133 ms

base.js

base.js

68 ms

analytics.js

analytics.js

89 ms

logo.png

logo.png

32 ms

gradient.png

gradient.png

29 ms

search-form-parts-bg.png

search-form-parts-bg.png

30 ms

bg-btn.png

bg-btn.png

29 ms

correct.png

correct.png

30 ms

secured-by.png

secured-by.png

31 ms

home-us.jpg

home-us.jpg

68 ms

las-vegas.jpg

las-vegas.jpg

53 ms

new-york.jpg

new-york.jpg

52 ms

orlando.jpg

orlando.jpg

52 ms

san-francisco.jpg

san-francisco.jpg

53 ms

los-angeles.jpg

los-angeles.jpg

52 ms

home-europe.jpg

home-europe.jpg

73 ms

london.jpg

london.jpg

75 ms

paris.jpg

paris.jpg

75 ms

barcelona.jpg

barcelona.jpg

76 ms

rome.jpg

rome.jpg

79 ms

venice.jpg

venice.jpg

87 ms

home-asia.jpg

home-asia.jpg

95 ms

sydney.jpg

sydney.jpg

97 ms

dubai.jpg

dubai.jpg

97 ms

beijing.jpg

beijing.jpg

98 ms

singapore.jpg

singapore.jpg

101 ms

bangkok.jpg

bangkok.jpg

109 ms

ui-bg_highlight-soft_100_eeeeee_1x100.png

ui-bg_highlight-soft_100_eeeeee_1x100.png

115 ms

calendar.png

calendar.png

117 ms

collect

collect

7 ms

collect

collect

55 ms

SEO Factors

traveling.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Traveling.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Traveling.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

traveling.com

Open Graph description is not detected on the main page of Traveling. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: