10.8 sec in total
55 ms
10.4 sec
333 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 55 ms and then it took 10.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
moxi.com.mx performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value19.4 s
0/100
25%
Value19.2 s
0/100
10%
Value1,300 ms
18/100
30%
Value0
100/100
15%
Value26.1 s
0/100
10%
55 ms
4597 ms
176 ms
225 ms
181 ms
Our browser made a total of 167 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Moxi.com.mx, 94% (157 requests) were made to Hotelmatilda.com and 1% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (4.6 sec) relates to the external source Hotelmatilda.com.
Page size can be reduced by 246.7 kB (11%)
2.2 MB
2.0 MB
In fact, the total size of Moxi.com.mx main page is 2.2 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 891.6 kB which makes up the majority of the site volume.
Potential reduce by 108.0 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 108.0 kB or 83% of the original size.
Potential reduce by 357 B
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 81.2 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. This website has mostly compressed JavaScripts.
Potential reduce by 57.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 57.1 kB or 18% of the original size.
Number of requests can be reduced by 138 (87%)
159
21
The browser has sent 159 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 98 to 1 for JavaScripts and from 36 to 1 for CSS and as a result speed up the page load time.
moxi.com.mx
55 ms
4597 ms
layerslider.css
176 ms
style.min.css
225 ms
frontend__premium_only.css
181 ms
all.min.css
36 ms
mediaelementplayer-legacy.min.css
80 ms
wp-mediaelement.min.css
86 ms
style.css
186 ms
font-awesome.min.css
157 ms
style.min.css
155 ms
style.css
233 ms
dripicons.css
326 ms
stylesheet.min.css
421 ms
print.css
252 ms
style_dynamic.css
249 ms
responsive.min.css
447 ms
style_dynamic_responsive.css
307 ms
js_composer.min.css
329 ms
elementor-icons.min.css
320 ms
animations.min.css
489 ms
frontend-legacy.min.css
385 ms
frontend.min.css
598 ms
post-1449.css
473 ms
frontend.min.css
459 ms
post-1659.css
484 ms
post-1651.css
629 ms
post-1200.css
533 ms
post-1195.css
541 ms
post-1190.css
550 ms
post-1005.css
560 ms
post-708.css
603 ms
post-699.css
618 ms
post-665.css
615 ms
style.css
629 ms
css
43 ms
greensock.js
731 ms
jquery.min.js
702 ms
jquery-migrate.min.js
745 ms
js
71 ms
js
81 ms
hotel_price_widget.js
131 ms
front.css
683 ms
layerslider.kreaturamedia.jquery.js
629 ms
layerslider.transitions.js
618 ms
email-decode.min.js
539 ms
frontend__premium_only.js
611 ms
core.min.js
604 ms
accordion.min.js
601 ms
controlgroup.min.js
596 ms
checkboxradio.min.js
701 ms
button.min.js
578 ms
datepicker.min.js
586 ms
mouse.min.js
588 ms
resizable.min.js
535 ms
draggable.min.js
524 ms
dialog.min.js
557 ms
droppable.min.js
680 ms
menu.min.js
634 ms
progressbar.min.js
466 ms
selectable.min.js
534 ms
sortable.min.js
484 ms
slider.min.js
500 ms
spinner.min.js
503 ms
tooltip.min.js
533 ms
tabs.min.js
516 ms
effect.min.js
572 ms
effect-drop.min.js
502 ms
effect-fade.min.js
522 ms
effect-slide.min.js
553 ms
doubletaptogo.js
486 ms
modernizr.min.js
501 ms
jquery.appear.js
501 ms
hoverIntent.min.js
584 ms
style.css
527 ms
counter.js
628 ms
easypiechart.js
522 ms
mixitup.js
734 ms
jquery.prettyPhoto.min.js
574 ms
jquery.fitvids.js
572 ms
jquery.flexslider-min.js
703 ms
mediaelement-and-player.min.js
692 ms
mediaelement-migrate.min.js
552 ms
wp-mediaelement.min.js
543 ms
infinitescroll.min.js
659 ms
jquery.waitforimages.js
659 ms
jquery.form.min.js
627 ms
waypoints.min.js
605 ms
jplayer.min.js
601 ms
bootstrap.carousel.js
661 ms
skrollr.js
634 ms
Chart.min.js
597 ms
jquery.easing.1.3.js
572 ms
abstractBaseClass.js
555 ms
jquery.countdown.js
545 ms
jquery.multiscroll.min.js
547 ms
jquery.justifiedGallery.min.js
545 ms
bigtext.js
545 ms
jquery.sticky-kit.min.js
595 ms
owl.carousel.min.js
537 ms
typed.js
546 ms
jquery.carouFredSel-6.2.1.min.js
539 ms
lemmon-slider.min.js
547 ms
jquery.fullPage.min.js
515 ms
jquery.mousewheel.min.js
535 ms
jquery.touchSwipe.min.js
596 ms
isotope.pkgd.min.js
542 ms
packery-mode.pkgd.min.js
547 ms
jquery.stretch.js
518 ms
fbevents.js
67 ms
gtm.js
67 ms
imagesloaded.js
538 ms
rangeslider.min.js
478 ms
ga.js
87 ms
jquery.event.move.js
488 ms
jquery.twentytwenty.js
450 ms
TweenLite.min.js
469 ms
ScrollToPlugin.min.js
440 ms
smoothPageScroll.min.js
461 ms
default_dynamic.js
356 ms
default.min.js
374 ms
comment-reply.min.js
388 ms
js_composer_front.min.js
392 ms
qode-like.min.js
390 ms
frontend.js
415 ms
frontend-modules.min.js
419 ms
jquery.sticky.min.js
440 ms
__utm.gif
16 ms
frontend.min.js
473 ms
dialog.min.js
418 ms
waypoints.min.js
428 ms
swiper.min.js
488 ms
share-link.min.js
506 ms
frontend.min.js
465 ms
isotope.min.js
466 ms
isotope-packery.min.js
451 ms
jquery-modula.min.js
601 ms
Gilroy-Light.otf
655 ms
Gilroy-Light.otf
479 ms
Silk-Serif-Bold.otf
480 ms
fontawesome-webfont.woff
627 ms
Gilroy-ExtraBold.otf
599 ms
Gilroy-ExtraBold.otf
508 ms
logo-black-web.png
498 ms
logo-white-web.png
566 ms
m-black.png
534 ms
m-purple.png
548 ms
us.png
566 ms
mx.png
544 ms
restaurant-san-miguel-de-allende-1.jpg
541 ms
san-miguel-de-allende-restaurant-1.jpg
532 ms
san-miguel-michelin-star-restaurant-1.jpg
570 ms
EZK_4098-1.jpg
667 ms
green-line.png
546 ms
EZK_6378-300x200.jpg
559 ms
EZK_6150-200x300.jpg
542 ms
EZK_6362-300x200.jpg
675 ms
EZK_6357-200x300.jpg
556 ms
EZK_6345-300x200.jpg
541 ms
EZK_6205-200x300.jpg
566 ms
EZK_6229-300x200.jpg
664 ms
moxi-menu-2023-1.jpg
584 ms
logo-m-white.png
592 ms
logo-design-hotel-300x26.png
583 ms
DESSERTS-1-qjc7v5zs3luec2lqoaxbn9u9cq5qk2bw8i2eqou3tq.jpg
591 ms
3818 ms
bird-background.jpg
583 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
Page has valid source maps
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: