Tools & Wizards About Us
capitaltraveler.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

capitaltraveler.com

Page Load Speed

4.8 sec in total

First Response

671 ms

Resources Loaded

3.8 sec

Page Rendered

308 ms

capitaltraveler.com screenshot

About Website

Visit capitaltraveler.com now to see the best up-to-date Capitaltraveler content and also check out these interesting facts you probably never knew about capitaltraveler.com

Book and save big on cheap flights. Capitaltraveler offers unbeatable economy or business class airline tickets at cheapest available airfare.

Visit capitaltraveler.com

Key Findings

We analyzed Capitaltraveler.com page load time and found that the first response time was 671 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

capitaltraveler.com performance score

0

Network Requests Diagram

www.capitaltraveler.com

671 ms

prettyPhoto.css

235 ms

style.css

308 ms

style1.css

168 ms

wp-email-capture-styles.css

123 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 38% of them (22 requests) were addressed to the original Capitaltraveler.com, 14% (8 requests) were made to Apis.google.com and 10% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (714 ms) relates to the external source Dohop.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 291.0 kB (62%)

Content Size

466.1 kB

After Optimization

175.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Capitaltraveler.com main page is 466.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. 55% of websites need less resources to load. Javascripts take 279.3 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 23.3 kB

  • Original 30.9 kB
  • After minification 27.8 kB
  • After compression 7.5 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 23.3 kB or 76% of the original size.

Image Optimization

-69%

Potential reduce by 63.6 kB

  • Original 92.6 kB
  • After minification 28.9 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. Obviously, Capitaltraveler needs image optimization as it can save up to 63.6 kB or 69% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-54%

Potential reduce by 150.7 kB

  • Original 279.3 kB
  • After minification 265.0 kB
  • After compression 128.6 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 150.7 kB or 54% of the original size.

CSS Optimization

-84%

Potential reduce by 53.4 kB

  • Original 63.4 kB
  • After minification 52.7 kB
  • After compression 10.0 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. Capitaltraveler.com needs all CSS files to be minified and compressed as it can save up to 53.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (69%)

Requests Now

55

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.capitaltraveler.com

www.capitaltraveler.com

671 ms

prettyPhoto.css

prettyPhoto.css

235 ms

style.css

style.css

308 ms

style1.css

style1.css

168 ms

wp-email-capture-styles.css

wp-email-capture-styles.css

123 ms

shortcodes.css

shortcodes.css

189 ms

jquery.js

jquery.js

331 ms

jquery-migrate.min.js

jquery-migrate.min.js

259 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

260 ms

custom.js

custom.js

381 ms

loader.js

loader.js

310 ms

twocolumns.css

twocolumns.css

258 ms

show_ads.js

show_ads.js

76 ms

comment-reply.min.js

comment-reply.min.js

276 ms

wp-embed.min.js

wp-embed.min.js

639 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

114 ms

bg.png

bg.png

95 ms

ct-logo1.png

ct-logo1.png

53 ms

email1.png

email1.png

102 ms

zrt_lookup.html

zrt_lookup.html

117 ms

show_ads_impl.js

show_ads_impl.js

121 ms

11087602-1455056035612

11087602-1455056035612

173 ms

ads

ads

369 ms

osd.js

osd.js

289 ms

plusone.js

plusone.js

358 ms

714 ms

s_bg.jpg

s_bg.jpg

69 ms

right_icon.jpg

right_icon.jpg

71 ms

s1_bg.jpg

s1_bg.jpg

246 ms

ads

ads

509 ms

ga.js

ga.js

217 ms

sprite.png

sprite.png

100 ms

loader.gif

loader.gif

100 ms

m_js_controller.js

m_js_controller.js

180 ms

abg.js

abg.js

322 ms

__utm.gif

__utm.gif

61 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

41 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

191 ms

fastbutton

fastbutton

348 ms

favicon

favicon

316 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

358 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

180 ms

nessie_icon_magazine_black.png

nessie_icon_magazine_black.png

244 ms

nessie_icon_magazine_white.png

nessie_icon_magazine_white.png

277 ms

postmessageRelay

postmessageRelay

366 ms

s

s

196 ms

x_button_blue2.png

x_button_blue2.png

149 ms

jquery.min.js

jquery.min.js

208 ms

jquery-ui.min.js

jquery-ui.min.js

284 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

154 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

120 ms

9aKOW9kHIBrJTB9ONj-e1oyTZuOGlgCE-J5p-KupNmo.js

9aKOW9kHIBrJTB9ONj-e1oyTZuOGlgCE-J5p-KupNmo.js

57 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

248 ms

rpc:shindig_random.js

rpc:shindig_random.js

110 ms

flight_b.png

flight_b.png

288 ms

hotel_w.png

hotel_w.png

276 ms

car_w.png

car_w.png

287 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

66 ms

SEO Factors

capitaltraveler.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Capitaltraveler.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Capitaltraveler.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

capitaltraveler.com

Open Graph description is not detected on the main page of Capitaltraveler. 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: