19.6 sec in total
360 ms
8 sec
11.3 sec
Visit wikitravel.org now to see the best up-to-date Wikitravel content for United States and also check out these interesting facts you probably never knew about wikitravel.org
Open source travel guide featuring up-to-date information on attractions hotels restaurants travel tips and more. Free and reliable advice written by Wikitravellers from around the globe.
Visit wikitravel.orgWe analyzed Wikitravel.org page load time and found that the first response time was 360 ms and then it took 19.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
wikitravel.org performance score
360 ms
450 ms
466 ms
1278 ms
1361 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 90% of them (62 requests) were addressed to the original Wikitravel.org, 4% (3 requests) were made to Ajax.googleapis.com and 1% (1 request) were made to Tag.crsspxl.com. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Loadus.exelator.com.
Page size can be reduced by 1.4 MB (15%)
9.4 MB
8.0 MB
In fact, the total size of Wikitravel.org main page is 9.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 8.3 MB which makes up the majority of the site volume.
Potential reduce by 52.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. This page needs HTML code to be minified as it can gain 27.9 kB, which is 45% 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 52.5 kB or 85% of the original size.
Potential reduce by 645.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. Wikitravel images are well optimized though.
Potential reduce by 626.4 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 626.4 kB or 66% of the original size.
Potential reduce by 70.8 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. Wikitravel.org needs all CSS files to be minified and compressed as it can save up to 70.8 kB or 82% of the original size.
Number of requests can be reduced by 23 (34%)
68
45
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wikitravel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
Main_Page
360 ms
all.css
450 ms
jquery.min.js
466 ms
jquery-ui.css
1278 ms
jquery-ui.min.js
1361 ms
jquery.main.js
431 ms
hp.js
426 ms
responsive.css
1227 ms
s1.js
991 ms
eucookie.min.js
2945 ms
3294 ms
bg-page.gif
2521 ms
main-menu.png
1584 ms
bg-input.jpg
1612 ms
map.png
2070 ms
1.png
1626 ms
2.png
1625 ms
3.png
1812 ms
4.png
1855 ms
5.png
1854 ms
6.png
1855 ms
7.png
1878 ms
8.png
1942 ms
9.png
2006 ms
10.png
1979 ms
11.png
2007 ms
12.png
2043 ms
13.png
2120 ms
14.png
2074 ms
15.png
2074 ms
16.png
2102 ms
17.png
2103 ms
18.png
2120 ms
19.png
2139 ms
20.png
2145 ms
21.png
2093 ms
icon-social.png
2094 ms
header-carusel.png
2094 ms
61_1503690419.jpg
2275 ms
btn-carusel.png
2143 ms
bg-text-widget.png
2153 ms
60_1503684953.jpg
2284 ms
58_1503943373.jpg
2285 ms
57_1501697373.jpg
2252 ms
52_1501698362.jpg
2230 ms
43_1488319699.jpg
2150 ms
bg-pagination.png
2151 ms
btn-prev.png
898 ms
btn-next.png
854 ms
19_1483157768.jpg
878 ms
bg-text-widget-carousel.png
839 ms
20_1483158255.jpg
835 ms
21_1483158550.jpg
793 ms
22_1483158922.jpg
888 ms
23_1483159309.jpg
886 ms
bg-slider-box.png
792 ms
icon-arrow.png
791 ms
alerts.png
841 ms
alerts-overlay.png
758 ms
events.png
871 ms
1.jpg
724 ms
2.jpg
768 ms
header-widget3.png
672 ms
5_1480982506.jpg
672 ms
bg-text-overline.png
689 ms
10_1503349747.jpg
690 ms
8_1480982143.jpg
688 ms
logo.png
670 ms
ga.js
1494 ms
wikitravel.org SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wikitravel.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Wikitravel.org 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.
wikitravel.org
Open Graph description is not detected on the main page of Wikitravel. 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: