1.7 sec in total
94 ms
1.5 sec
161 ms
Visit xocalo.mx now to see the best up-to-date Xocalo content and also check out these interesting facts you probably never knew about xocalo.mx
Piso flotado, Azoteas elevadas, Piso elevado, Azoteas flotantes, Piso falso, Piso flotante, Piso ajustable
Visit xocalo.mxWe analyzed Xocalo.mx page load time and found that the first response time was 94 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
xocalo.mx performance score
name
value
score
weighting
Value9.4 s
0/100
10%
Value24.8 s
0/100
25%
Value15.3 s
1/100
10%
Value290 ms
80/100
30%
Value0.001
100/100
15%
Value20.7 s
2/100
10%
94 ms
637 ms
68 ms
89 ms
154 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 86% of them (81 requests) were addressed to the original Xocalo.mx, 5% (5 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (637 ms) belongs to the original domain Xocalo.mx.
Page size can be reduced by 1.7 MB (45%)
3.9 MB
2.1 MB
In fact, the total size of Xocalo.mx main page is 3.9 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. 70% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 49.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. 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 49.9 kB or 79% of the original size.
Potential reduce by 8.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. Xocalo images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 76% of the original size.
Potential reduce by 585.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. Xocalo.mx needs all CSS files to be minified and compressed as it can save up to 585.0 kB or 83% of the original size.
Number of requests can be reduced by 54 (70%)
77
23
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xocalo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
xocalo.mx
94 ms
xocalo.mx
637 ms
js
68 ms
font-awesome.css
89 ms
bootstrap.css
154 ms
animate.css
187 ms
superfish.css
128 ms
flexslider.css
163 ms
owl.carousel.css
172 ms
slidebars.css
173 ms
ilightbox.css
223 ms
comments.css
209 ms
loadings.css
239 ms
utilities.css
271 ms
framework.css
280 ms
style.min.css
322 ms
styles.css
270 ms
settings.css
302 ms
css
34 ms
style.css
311 ms
frontend.css
304 ms
jquery-ui.css
315 ms
frontendstyles.css
304 ms
style.css
383 ms
jquery-1.12.4.min.js
22 ms
jquery-migrate.min.js
375 ms
jquery.themepunch.tools.min.js
401 ms
jquery.themepunch.revolution.min.js
373 ms
core.min.js
357 ms
datepicker.min.js
379 ms
moment-with-locales.js
514 ms
css
53 ms
jquery-ui.min.js
5 ms
bootstrap.min.js
398 ms
jquery.ui.touch-punch.min.js
398 ms
modernizr.min.js
402 ms
jquery.cookie.min.js
399 ms
js
98 ms
superfish.js
402 ms
hoverIntent.js
442 ms
jquery.flexslider.js
445 ms
owl.carousel.js
446 ms
jquery.lazyload.js
448 ms
imagesloaded.pkgd.js
446 ms
isotope.pkgd.js
436 ms
jquery.waypoints.js
402 ms
jquery.countTo.js
366 ms
jquery.validate.js
376 ms
additional-methods.js
368 ms
slidebars.js
410 ms
ilightbox.js
395 ms
theme.js
375 ms
framework.js
359 ms
wp-polyfill-inert.min.js
353 ms
regenerator-runtime.min.js
377 ms
wp-polyfill.min.js
378 ms
index.js
368 ms
frontend.js
344 ms
00000000000000000000000000000000
31 ms
logo-xocalo-x2-white.png
32 ms
logo-xocalo-small-white.png
90 ms
432-min.jpg
184 ms
433.jpg
196 ms
icon-xocalo-min.png
93 ms
icon-01.png
91 ms
icon-02.png
92 ms
icon-03.png
92 ms
icon-04.png
92 ms
icon-05.png
93 ms
intro-04-min-600x400.jpg
93 ms
intro-06-min-600x400.jpg
94 ms
intro-01-min-600x400.jpg
94 ms
intro-03-min-600x400.jpg
184 ms
intro-08-min-600x400.jpg
183 ms
intro-07-min-600x400.jpg
184 ms
footer-logo.png
94 ms
bg-footer-min.jpg
165 ms
logo-xocalo-x2-white.png
164 ms
logo-xocalo-small-white.png
105 ms
icon-01.png
104 ms
icon-02.png
103 ms
icon-03.png
135 ms
icon-04.png
126 ms
icon-05.png
134 ms
footer-logo.png
131 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf
99 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf
107 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf
113 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf
119 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVcUwaEQXjM.ttf
120 ms
fontawesome-webfont.woff
141 ms
revolution.extension.slideanims.min.js
94 ms
revolution.extension.actions.min.js
114 ms
gABAAAABQCXAAMAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAADgCuAAEAAAAAAAEABwAAAAEAAAAAAAIABwBgAAEAAAAAAAMABwA2AAEAAAAAAAQABwB1AAEAAAAAAAUACwAVAAEAAAAAAAYABwBLAAEAAAAAAAoAGgCKAAMAAQQJAAEADgAHAAMAAQQJAAIADgBnAAMAAQQJAAMADgA9AAMAAQQJAAQADgB8AAMAAQQJAAUAFgAgAAMAAQQJAAYADgBSAAMAAQQJAAoANACkaWNvbW9vbgBpAGMAbwBtAG8AbwBuVmVyc2lvbiAxLjAAVgBlAHIAcwBpAG8AbgAgADEALgAwaWNvbW9vbgBpAGMAbwBtAG8AbwBuaWNvbW9vbgBpAGMAbwBtAG8AbwBuUmVndWxhcgBSAGUAZwB1AGwAYQByaWNvbW9vbgBpAGMAbwBtAG8AbwBuRm9udCBnZW5lcmF0ZWQgYnkgSWNvTW9vbi4ARgBvAG4AdAAgAGcAZQBuAGUAcgBhAHQAZQBkACAAYgB5ACAASQBjAG8ATQBvAG8AbgAuAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
8 ms
xocalo.mx accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
xocalo.mx best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
xocalo.mx SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xocalo.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Xocalo.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.
xocalo.mx
Open Graph data is detected on the main page of Xocalo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: