2.2 sec in total
174 ms
1.9 sec
136 ms
Welcome to crtraveler.com homepage info - get ready to check Crtraveler best content right away, or after learning these important things about crtraveler.com
The best source of information for the traveler in Costa Rica. Costa Rica Travel Articles, Costa Rica Photo Galleries, Maps, Travel Blog, Tourism and Costa Rica Hotels Directory.
Visit crtraveler.comWe analyzed Crtraveler.com page load time and found that the first response time was 174 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
crtraveler.com performance score
174 ms
588 ms
74 ms
105 ms
109 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Crtraveler.com, 88% (100 requests) were made to Costaricatraveler.com and 8% (9 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (613 ms) relates to the external source Costaricatraveler.com.
Page size can be reduced by 296.5 kB (28%)
1.0 MB
745.4 kB
In fact, the total size of Crtraveler.com main page is 1.0 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. 50% of websites need less resources to load. Images take 722.9 kB which makes up the majority of the site volume.
Potential reduce by 26.3 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 21% 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 26.3 kB or 81% of the original size.
Potential reduce by 71.0 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. Crtraveler images are well optimized though.
Potential reduce by 188.1 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 188.1 kB or 69% of the original size.
Potential reduce by 11.1 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. Crtraveler.com needs all CSS files to be minified and compressed as it can save up to 11.1 kB or 80% of the original size.
Number of requests can be reduced by 43 (39%)
110
67
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Crtraveler. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
crtraveler.com
174 ms
index_eng.php
588 ms
default.css
74 ms
mainpage.css
105 ms
carousel.css
109 ms
pngfix.js
105 ms
utilities.js
141 ms
container_core-min.js
114 ms
carousel_eng.js
210 ms
imageMenu.css
166 ms
mootools.js
207 ms
imageMenu.js
179 ms
swfobjet.js
170 ms
jsapi
21 ms
t13n
33 ms
brand
36 ms
common.js
194 ms
t13n
50 ms
brand
55 ms
external.js
149 ms
logo_travel.gif
92 ms
idioma.gif
41 ms
transparente.png
70 ms
menu_dg.gif
42 ms
menu_left.gif
69 ms
menu_center.gif
67 ms
icono_inicio.gif
88 ms
icono_costarica.gif
89 ms
icono_galeria.gif
91 ms
icono_mapas.gif
93 ms
icono_blog.gif
133 ms
icono_viajero.gif
134 ms
icono_directorio.gif
135 ms
menu_right.gif
159 ms
search_arrow.gif
161 ms
white.jpg
158 ms
left-enabled.gif
159 ms
right-enabled.gif
194 ms
54_tn.jpg
175 ms
53_tn.jpg
191 ms
52_tn.jpg
190 ms
51_tn.jpg
206 ms
50_tn.jpg
224 ms
49_tn.jpg
241 ms
48_tn.jpg
288 ms
46_tn.jpg
289 ms
45_tn.jpg
281 ms
44_tn.jpg
306 ms
43_tn.jpg
343 ms
42_tn.jpg
318 ms
41_tn.jpg
349 ms
40_tn.jpg
378 ms
39_tn.jpg
355 ms
4_tn.png
421 ms
14 ms
3_tn.jpg
404 ms
1_tn.jpg
410 ms
transliteration.css
4 ms
transliteration.I.js
11 ms
2_tn.png
381 ms
38_tn.jpg
388 ms
18 ms
google_custom_search_watermark.gif
68 ms
ajax_goto.php
613 ms
37_tn.jpg
368 ms
36_tn.jpg
398 ms
ga.js
50 ms
inputtools.js
14 ms
35_tn.jpg
399 ms
34_tn.jpg
391 ms
33_tn.jpg
391 ms
28_tn.jpg
400 ms
27_tn.jpg
447 ms
26_tn.jpg
413 ms
25_tn.jpg
420 ms
__utm.gif
12 ms
24_tn.jpg
402 ms
23_tn.jpg
387 ms
22_tn.jpg
429 ms
21_tn.jpg
443 ms
20_tn.jpg
436 ms
19_tn.jpg
428 ms
18_tn.jpg
436 ms
17_tn.jpg
457 ms
15_tn.jpg
471 ms
14_tn.jpg
474 ms
13_tn.jpg
440 ms
12_tn.jpg
453 ms
11_tn.jpg
426 ms
10_tn.jpg
430 ms
9_tn.jpg
435 ms
8_tn.jpg
421 ms
7_tn.jpg
418 ms
6_tn.jpg
403 ms
banner-Travel-PASS.gif
510 ms
facebook-icon-mini.jpg
412 ms
twitter-icon-mini.jpg
396 ms
advertise_here.gif
355 ms
footer_left.jpg
366 ms
footer_phone.jpg
397 ms
fooer_mail.jpg
386 ms
footer_address.jpg
390 ms
footer_right.jpg
397 ms
bg_pagecontentjpg.jpg
364 ms
directory_eng.jpg
481 ms
living_eng.jpg
438 ms
traveler_eng.jpg
481 ms
magazine_eng.jpg
515 ms
costarica_eng.jpg
434 ms
more.jpg
358 ms
bullet.gif
396 ms
footer_bg.jpg
410 ms
footer_bg_green.jpg
428 ms
left-disabled.gif
56 ms
crtraveler.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Crtraveler.com 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 Crtraveler.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.
crtraveler.com
Open Graph description is not detected on the main page of Crtraveler. 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: