4.2 sec in total
302 ms
3.6 sec
284 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 302 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
xocalo.mx performance score
name
value
score
weighting
Value10.4 s
0/100
10%
Value26.7 s
0/100
25%
Value20.3 s
0/100
10%
Value4,480 ms
0/100
30%
Value0.002
100/100
15%
Value27.8 s
0/100
10%
302 ms
639 ms
200 ms
369 ms
665 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 83% of them (82 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 (1.4 sec) belongs to the original domain Xocalo.mx.
Page size can be reduced by 1.6 MB (44%)
3.7 MB
2.1 MB
In fact, the total size of Xocalo.mx main page is 3.7 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. 75% 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 1.7 MB which makes up the majority of the site volume.
Potential reduce by 46.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. 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 46.3 kB or 79% of the original size.
Potential reduce by 9.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. Xocalo images are well optimized though.
Potential reduce by 1.0 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.0 MB or 80% of the original size.
Potential reduce by 556.6 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 556.6 kB or 83% of the original size.
Number of requests can be reduced by 55 (66%)
83
28
The browser has sent 83 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 35 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
xocalo.mx
302 ms
xocalo.mx
639 ms
js
200 ms
font-awesome.css
369 ms
bootstrap.css
665 ms
animate.css
501 ms
superfish.css
475 ms
flexslider.css
522 ms
owl.carousel.css
614 ms
slidebars.css
607 ms
ilightbox.css
638 ms
comments.css
636 ms
loadings.css
655 ms
utilities.css
749 ms
framework.css
784 ms
style.min.css
793 ms
styles.css
746 ms
settings.css
823 ms
css
452 ms
style.css
750 ms
frontend.css
825 ms
jquery-ui.css
845 ms
frontendstyles.css
844 ms
style.css
1158 ms
jquery-1.12.4.min.js
449 ms
jquery-migrate.min.js
847 ms
jquery.themepunch.tools.min.js
934 ms
jquery.themepunch.revolution.min.js
918 ms
core.min.js
844 ms
datepicker.min.js
844 ms
moment-with-locales.js
925 ms
css
420 ms
jquery-ui.min.js
405 ms
bootstrap.min.js
849 ms
jquery.ui.touch-punch.min.js
848 ms
modernizr.min.js
850 ms
jquery.cookie.min.js
849 ms
js
546 ms
superfish.js
852 ms
hoverIntent.js
853 ms
jquery.flexslider.js
862 ms
owl.carousel.js
857 ms
jquery.lazyload.js
859 ms
imagesloaded.pkgd.js
833 ms
analytics.js
183 ms
isotope.pkgd.js
590 ms
jquery.waypoints.js
485 ms
jquery.countTo.js
460 ms
jquery.validate.js
442 ms
collect
268 ms
additional-methods.js
417 ms
slidebars.js
403 ms
ilightbox.js
379 ms
theme.js
457 ms
framework.js
295 ms
regenerator-runtime.min.js
300 ms
wp-polyfill.min.js
296 ms
index.js
258 ms
frontend.js
259 ms
wp-embed.min.js
280 ms
logo-xocalo-x2-white.png
68 ms
logo-xocalo-small-white.png
204 ms
432-min.jpg
654 ms
433.jpg
1403 ms
icon-xocalo-min.png
202 ms
logo-xocalo-x2-white.png
300 ms
00000000000000000000000000000000
285 ms
icon-01.png
307 ms
icon-02.png
307 ms
icon-04.png
331 ms
intro-04-min-600x400.jpg
306 ms
intro-06-min-600x400.jpg
723 ms
intro-01-min-600x400.jpg
305 ms
intro-03-min-600x400.jpg
304 ms
intro-08-min-600x400.jpg
330 ms
intro-07-min-600x400.jpg
330 ms
bg-footer-min.jpg
330 ms
logo-xocalo-small-white.png
273 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
205 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
218 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
244 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
229 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
242 ms
fontawesome-webfont.woff
270 ms
revolution.extension.slideanims.min.js
199 ms
revolution.extension.actions.min.js
235 ms
revolution.extension.layeranimation.min.js
236 ms
revolution.extension.navigation.min.js
242 ms
gen_204
74 ms
gABAAAABQCXAAMAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAADgCuAAEAAAAAAAEABwAAAAEAAAAAAAIABwBgAAEAAAAAAAMABwA2AAEAAAAAAAQABwB1AAEAAAAAAAUACwAVAAEAAAAAAAYABwBLAAEAAAAAAAoAGgCKAAMAAQQJAAEADgAHAAMAAQQJAAIADgBnAAMAAQQJAAMADgA9AAMAAQQJAAQADgB8AAMAAQQJAAUAFgAgAAMAAQQJAAYADgBSAAMAAQQJAAoANACkaWNvbW9vbgBpAGMAbwBtAG8AbwBuVmVyc2lvbiAxLjAAVgBlAHIAcwBpAG8AbgAgADEALgAwaWNvbW9vbgBpAGMAbwBtAG8AbwBuaWNvbW9vbgBpAGMAbwBtAG8AbwBuUmVndWxhcgBSAGUAZwB1AGwAYQByaWNvbW9vbgBpAGMAbwBtAG8AbwBuRm9udCBnZW5lcmF0ZWQgYnkgSWNvTW9vbi4ARgBvAG4AdAAgAGcAZQBuAGUAcgBhAHQAZQBkACAAYgB5ACAASQBjAG8ATQBvAG8AbgAuAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
13 ms
icon-02.png
193 ms
icon-01.png
191 ms
icon-05.png
175 ms
footer-logo.png
183 ms
icon-03.png
191 ms
icon-04.png
193 ms
ic_keyboard_arrow_down_24px.svg
73 ms
gridtile.png
68 ms
revicons.woff
68 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: