3.3 sec in total
931 ms
2.2 sec
242 ms
Welcome to auxi.mx homepage info - get ready to check AUXI best content right away, or after learning these important things about auxi.mx
Visit auxi.mxWe analyzed Auxi.mx page load time and found that the first response time was 931 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
auxi.mx performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value11.5 s
0/100
25%
Value10.2 s
8/100
10%
Value410 ms
67/100
30%
Value0.323
35/100
15%
Value11.6 s
18/100
10%
931 ms
113 ms
86 ms
59 ms
61 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 96% of them (76 requests) were addressed to the original Auxi.mx, 1% (1 request) were made to Maps.google.com and 1% (1 request) were made to Quandl.com. The less responsive or slowest element that took the longest time to load (931 ms) belongs to the original domain Auxi.mx.
Page size can be reduced by 1.4 MB (41%)
3.5 MB
2.1 MB
In fact, the total size of Auxi.mx main page is 3.5 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. 40% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 17.7 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 17.7 kB or 78% of the original size.
Potential reduce by 23.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. AUXI 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 73% of the original size.
Potential reduce by 359.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. Auxi.mx needs all CSS files to be minified and compressed as it can save up to 359.1 kB or 86% of the original size.
Number of requests can be reduced by 51 (69%)
74
23
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AUXI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
auxi.mx
931 ms
k2.css
113 ms
settings.css
86 ms
captions.css
59 ms
flexslider.css
61 ms
camera.css
87 ms
default.css
115 ms
nivo-slider.css
121 ms
elastic.css
140 ms
jquery.kwicks.min.css
141 ms
bootstrap.min.css
253 ms
main.css
227 ms
boxme.responsive.css
180 ms
style.php
273 ms
jquery-ui.css
229 ms
css.css
240 ms
mootools-core.js
350 ms
core.js
280 ms
jquery.min.js
366 ms
jquery-noconflict.js
295 ms
jquery-migrate.min.js
303 ms
k2.js
325 ms
mootools-more.js
474 ms
jquery.themepunch.plugins.min.js
376 ms
jquery.themepunch.revolution.min.js
412 ms
bootstrap.min.js
408 ms
retina-1.1.0.min.js
406 ms
hoverIntent.js
416 ms
superfish.min.js
430 ms
supersubs.js
457 ms
jquery.carouFredSel.js
514 ms
jquery.prettyPhoto.js
492 ms
js
26 ms
jquery.ui.map.min.js
470 ms
jquery.validate.js
510 ms
jquery.parallax-1.1.3.js
512 ms
jquery.isotope.min.js
548 ms
excanvas.js
511 ms
jquery.easy-pie-chart.js
502 ms
jquery.flexslider-min.js
524 ms
jquery.eislideshow.js
497 ms
jquery.easing.1.3.js
471 ms
camera.min.js
564 ms
jquery.nivo.slider.pack.js
503 ms
jquery.kwicks.min.js
487 ms
responsive-nav.min.js
510 ms
main.js
470 ms
jquery-ui.js
684 ms
font-awesome.min.css
479 ms
prettyPhoto.css
481 ms
animate.min.css
519 ms
jquery.easy-pie-chart.css
451 ms
boxme-reset.css
462 ms
marquee.js
613 ms
shattered-gray.png
122 ms
logo.png
119 ms
SLIDER1.jpg
236 ms
slider2.jpg
199 ms
SLIDER3.jpg
195 ms
AVISO%20DE%20PROTECCION%20CLIENTES%201920X502.jpg
397 ms
PAGARE-AUXI-HOME-F.jpg
94 ms
CUENTA-AHORRO-TDD.jpg
135 ms
CREDITO_PRODUCTIVO_HOME.jpg
172 ms
CREDITO_PERSONAL_HOME.jpg
203 ms
CREDITO-HOME.jpg
221 ms
PAGARE-HOME.jpg
229 ms
FINANCIEROS-HOME-V2.jpg
230 ms
CNBV.png
278 ms
CONDUSEF.png
283 ms
telefono.png
281 ms
sobre.png
301 ms
Futura-Book.woff
337 ms
INDEX_MXX.json
12 ms
timer.png
253 ms
loader.gif
264 ms
fontawesome-webfont.woff
316 ms
yql
130 ms
large_left.png
70 ms
large_right.png
69 ms
auxi.mx accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
auxi.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
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
auxi.mx SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
ES
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Auxi.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed English language. Our system also found out that Auxi.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.
auxi.mx
Open Graph description is not detected on the main page of AUXI. 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: