15 sec in total
465 ms
13.7 sec
882 ms
Click here to check amazing Santiago Express content for Mexico. Otherwise, check out these important facts you probably never knew about santiagoexpress.mx
Blvd. Luis Donaldo Colosio #911, Parque Industrial Korian(carretera a Parral km. 35) a un costado del puente de la carretera a Parral, a una cuadra del salón Real del Campanario3
Visit santiagoexpress.mxWe analyzed Santiagoexpress.mx page load time and found that the first response time was 465 ms and then it took 14.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
santiagoexpress.mx performance score
465 ms
485 ms
256 ms
253 ms
153 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 57% of them (55 requests) were addressed to the original Santiagoexpress.mx, 14% (14 requests) were made to Maps.googleapis.com and 10% (10 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (12 sec) belongs to the original domain Santiagoexpress.mx.
Page size can be reduced by 1.3 MB (19%)
6.8 MB
5.5 MB
In fact, the total size of Santiagoexpress.mx main page is 6.8 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. 60% of websites need less resources to load. Images take 5.2 MB which makes up the majority of the site volume.
Potential reduce by 35.8 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 21.1 kB, which is 51% 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 35.8 kB or 87% of the original size.
Potential reduce by 116.1 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. Santiago Express images are well optimized though.
Potential reduce by 670.8 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 670.8 kB or 68% of the original size.
Potential reduce by 475.2 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. Santiagoexpress.mx needs all CSS files to be minified and compressed as it can save up to 475.2 kB or 88% of the original size.
Number of requests can be reduced by 49 (51%)
96
47
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Santiago Express. 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 26 to 1 for CSS and as a result speed up the page load time.
santiagoexpress.mx
465 ms
bootstrap.css
485 ms
bootstrap-theme.css
256 ms
font-awesome.css
253 ms
color.css
153 ms
style.css
336 ms
responsive.css
289 ms
datepicker.css
448 ms
css
53 ms
themetypo.css
326 ms
sass-compiled.css
355 ms
css
71 ms
css
73 ms
css
72 ms
css
75 ms
css
73 ms
flexslider.css
367 ms
csshake.css
821 ms
hover.css
943 ms
normalize.css
500 ms
demo.css
518 ms
component.css
551 ms
modernizr.custom.js
577 ms
cleanSlider.css
638 ms
jquery-1.4.2.min.js
1293 ms
jquery.cleanSlider.js
690 ms
jquery.js
1014 ms
bootstrap.min.js
777 ms
jquery.bxslider.min.js
768 ms
bootstrap-datepicker.js
886 ms
waypoints-min.js
908 ms
functions.js
917 ms
jquery.flexslider-min.js
948 ms
css
16 ms
css
16 ms
css
15 ms
embed
208 ms
logo.png
156 ms
carretera.png
12010 ms
img1.jpg
473 ms
img2.jpg
942 ms
img3.jpg
655 ms
img4.jpg
654 ms
img5.jpg
1327 ms
01.jpg
1530 ms
02.jpg
1609 ms
03.jpg
1669 ms
04.jpg
1450 ms
05.jpg
1784 ms
06.jpg
1882 ms
trip-gallery1.jpg
2175 ms
trip-gallery2.jpg
2689 ms
trip-gallery3.jpg
2285 ms
poster01.jpg
2284 ms
still01.jpg
2223 ms
poster02.jpg
2599 ms
still02.jpg
2522 ms
poster03.jpg
2710 ms
still03.jpg
2578 ms
partner2.jpg
2790 ms
partner3.jpg
2932 ms
partner4.jpg
2913 ms
footer.png
4390 ms
fontawesome-webfont.woff
3172 ms
ga.js
29 ms
bg2.png
2805 ms
__utm.gif
15 ms
js
84 ms
init_embed.js
71 ms
common.js
104 ms
map.js
104 ms
google4.png
28 ms
overlay.js
25 ms
util.js
207 ms
onion.js
20 ms
search_impl.js
205 ms
StaticMapService.GetMapImage
367 ms
stats.js
232 ms
openhand_8_8.cur
225 ms
kh
251 ms
transparent.png
145 ms
ViewportInfoService.GetViewportInfo
146 ms
ViewportInfoService.GetViewportInfo
145 ms
controls.js
35 ms
css
74 ms
entity11.png
74 ms
vt
62 ms
vt
82 ms
vt
57 ms
vt
59 ms
vt
80 ms
vt
76 ms
vt
88 ms
mapcnt6.png
33 ms
tmapctrl.png
54 ms
AuthenticationService.Authenticate
27 ms
QuotaService.RecordEvent
25 ms
santiagoexpress.mx SEO score
PT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Santiagoexpress.mx can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Santiagoexpress.mx 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.
santiagoexpress.mx
Open Graph description is not detected on the main page of Santiago Express. 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: