4.7 sec in total
415 ms
3.6 sec
643 ms
Visit moxi.com.mx now to see the best up-to-date Moxi content and also check out these interesting facts you probably never knew about moxi.com.mx
Fine dining in San Miguel de Allende. Join Michelin-star chef Vincente Torres at Moxi in Hotel Matilda. Reserve your table now.
Visit moxi.com.mxWe analyzed Moxi.com.mx page load time and found that the first response time was 415 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
moxi.com.mx performance score
name
value
score
weighting
Value8.4 s
0/100
10%
Value32.2 s
0/100
25%
Value72.8 s
0/100
10%
Value75,540 ms
0/100
30%
Value0.001
100/100
15%
Value104.8 s
0/100
10%
415 ms
87 ms
78 ms
70 ms
76 ms
Our browser made a total of 189 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Moxi.com.mx, 2% (4 requests) were made to Static.sojern.com and 2% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (920 ms) relates to the external source Thehotelsnetwork.com.
Page size can be reduced by 241.6 kB (3%)
9.7 MB
9.4 MB
In fact, the total size of Moxi.com.mx main page is 9.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. 85% 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.8 MB which makes up the majority of the site volume.
Potential reduce by 114.2 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 114.2 kB or 84% of the original size.
Potential reduce by 14.6 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. Moxi images are well optimized though.
Potential reduce by 54.7 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 54.7 kB or 14% of the original size.
Potential reduce by 58.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. Moxi.com.mx needs all CSS files to be minified and compressed as it can save up to 58.1 kB or 17% of the original size.
Number of requests can be reduced by 137 (76%)
180
43
The browser has sent 180 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Moxi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 100 to 1 for JavaScripts and from 39 to 1 for CSS and as a result speed up the page load time.
415 ms
wp-emoji-release.min.js
87 ms
layerslider.css
78 ms
style.min.css
70 ms
frontend__premium_only.css
76 ms
all.css
766 ms
mediaelementplayer-legacy.min.css
145 ms
wp-mediaelement.min.css
146 ms
style.css
176 ms
font-awesome.min.css
172 ms
style.min.css
302 ms
style.css
291 ms
dripicons.css
303 ms
stylesheet.min.css
351 ms
print.css
582 ms
style_dynamic.css
578 ms
responsive.min.css
659 ms
style_dynamic_responsive.css
677 ms
js_composer.min.css
584 ms
elementor-icons.min.css
706 ms
animations.min.css
682 ms
frontend-legacy.min.css
705 ms
frontend.min.css
739 ms
post-1449.css
722 ms
frontend.min.css
722 ms
post-1659.css
756 ms
post-1651.css
758 ms
post-1200.css
754 ms
post-1195.css
759 ms
post-1190.css
759 ms
post-1005.css
765 ms
post-708.css
772 ms
post-699.css
760 ms
post-665.css
770 ms
style.css
773 ms
css
714 ms
greensock.js
782 ms
jquery.min.js
776 ms
infochat.js
732 ms
js
773 ms
hotel_price_widget.js
920 ms
fancybox.css
755 ms
front.css
752 ms
nivo-slider.min.css
744 ms
default.min.css
759 ms
jquery-migrate.min.js
728 ms
layerslider.kreaturamedia.jquery.js
666 ms
layerslider.transitions.js
635 ms
email-decode.min.js
631 ms
frontend__premium_only.js
651 ms
core.min.js
531 ms
accordion.min.js
527 ms
controlgroup.min.js
528 ms
checkboxradio.min.js
274 ms
button.min.js
266 ms
datepicker.min.js
166 ms
mouse.min.js
178 ms
resizable.min.js
177 ms
draggable.min.js
144 ms
dialog.min.js
237 ms
droppable.min.js
197 ms
menu.min.js
193 ms
progressbar.min.js
165 ms
selectable.min.js
103 ms
sortable.min.js
160 ms
slider.min.js
155 ms
spinner.min.js
157 ms
tooltip.min.js
152 ms
tabs.min.js
176 ms
effect.min.js
177 ms
effect-drop.min.js
180 ms
effect-fade.min.js
446 ms
effect-slide.min.js
336 ms
style.css
168 ms
doubletaptogo.js
334 ms
modernizr.min.js
334 ms
jquery.appear.js
448 ms
hoverIntent.min.js
437 ms
counter.js
438 ms
easypiechart.js
454 ms
mixitup.js
435 ms
jquery.prettyPhoto.min.js
434 ms
jquery.fitvids.js
435 ms
jquery.flexslider-min.js
426 ms
mediaelement-and-player.min.js
431 ms
mediaelement-migrate.min.js
422 ms
wp-mediaelement.min.js
426 ms
infinitescroll.min.js
421 ms
jquery.waitforimages.js
427 ms
jquery.form.min.js
428 ms
waypoints.min.js
404 ms
jplayer.min.js
409 ms
bootstrap.carousel.js
405 ms
skrollr.js
411 ms
Chart.min.js
406 ms
jquery.easing.1.3.js
356 ms
abstractBaseClass.js
360 ms
jquery.countdown.js
355 ms
jquery.multiscroll.min.js
360 ms
jquery.justifiedGallery.min.js
353 ms
bigtext.js
350 ms
jquery.sticky-kit.min.js
354 ms
owl.carousel.min.js
332 ms
typed.js
330 ms
jquery.carouFredSel-6.2.1.min.js
329 ms
lemmon-slider.min.js
329 ms
jquery.fullPage.min.js
179 ms
jquery.mousewheel.min.js
166 ms
jquery.touchSwipe.min.js
163 ms
isotope.pkgd.min.js
166 ms
fbevents.js
205 ms
gtm.js
219 ms
packery-mode.pkgd.min.js
176 ms
jquery.stretch.js
165 ms
imagesloaded.js
173 ms
rangeslider.min.js
174 ms
jquery.event.move.js
171 ms
jquery.twentytwenty.js
159 ms
default_dynamic.js
165 ms
default.min.js
164 ms
comment-reply.min.js
319 ms
js_composer_front.min.js
317 ms
qode-like.min.js
314 ms
jquery.nivo.slider.pack.js
312 ms
frontend.js
313 ms
frontend-modules.min.js
302 ms
jquery.sticky.min.js
347 ms
frontend.min.js
341 ms
dialog.min.js
339 ms
waypoints.min.js
340 ms
swiper.min.js
337 ms
share-link.min.js
334 ms
frontend.min.js
338 ms
modula-wl.js
379 ms
logo-black-web.png
365 ms
logo-white-web.png
360 ms
m-black.png
333 ms
m-purple.png
334 ms
us.png
350 ms
mx.png
357 ms
moxi-restaurant-san-miguel1.jpg
371 ms
moxi-restaurant-san-miguel3.jpg
361 ms
moxi-restaurant-san-miguel2.jpg
364 ms
restaurante-san-miguel-de-allende3.jpg
355 ms
green-line.png
350 ms
Uchepos-2-scaled-500x99999.jpg
368 ms
Papadzul-1-scaled-500x99999.jpg
369 ms
ga.js
275 ms
Pan-Frances-scaled-500x99999.jpg
338 ms
Latkes-Salmon-scaled-500x99999.jpg
357 ms
Huevos-motulenos-2-scaled-99999x500.jpg
251 ms
Chicken-and-waffles1-scaled-500x99999.jpg
350 ms
Chicken-and-waffles-2-scaled-99999x500.jpg
321 ms
Tostada-de-Jaiba-1-scaled-500x99999.jpg
345 ms
Pescado-Zarandeado-scaled-500x99999.jpg
323 ms
Pescado-Zarandeado-1-scaled-500x99999.jpg
344 ms
Crab-Cakes-scaled-99999x500.jpg
324 ms
identity.js
169 ms
367888076966862
184 ms
Gilroy-Light.otf
197 ms
Gilroy-Light.otf
199 ms
Silk-Serif-Bold.otf
198 ms
Gilroy-ExtraBold.otf
198 ms
Gilroy-ExtraBold.otf
201 ms
fontawesome-webfont.woff
206 ms
Barbacoa-de-Cordero-scaled-500x99999.jpg
173 ms
mui-new-logo-184x300.jpg
171 ms
AGO6083-1.jpg
467 ms
AGO6087-1.jpg
205 ms
AGO6142-1.jpg
458 ms
AGO6167-1.jpg
459 ms
GfuMPh5A.jpg
471 ms
JtRrEWSw.jpg
452 ms
s9OmW-ng.jpg
445 ms
AGO6167.jpg
450 ms
logo-m-white.png
436 ms
logo-design-hotel-300x26.png
440 ms
DESSERTS-1-olgi1p0ayntv1l65g5ttoni8fiagyqizdwcjgt5gbi.jpg
436 ms
444 ms
background-hand-1.jpg
436 ms
sjrn_autocx.js
239 ms
__utm.gif
165 ms
loading.gif
74 ms
collect
62 ms
11.html
38 ms
hasher.js
26 ms
create_params.js
29 ms
ga-audiences
48 ms
gen_204
254 ms
moxi.com.mx accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
moxi.com.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
moxi.com.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Moxi.com.mx 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 Moxi.com.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.
moxi.com.mx
Open Graph description is not detected on the main page of Moxi. 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: