3.8 sec in total
262 ms
3.2 sec
284 ms
Welcome to audi.com.mx homepage info - get ready to check Audi best content for Mexico right away, or after learning these important things about audi.com.mx
Conoce nuestros modelos y descubre más acerca de nuestra visión sobre el futuro de la movilidad. Así como novedades, servicios y promociones de Audi en México.
Visit audi.com.mxWe analyzed Audi.com.mx page load time and found that the first response time was 262 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
audi.com.mx performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value19.9 s
0/100
25%
Value13.8 s
1/100
10%
Value5,220 ms
0/100
30%
Value0.029
100/100
15%
Value25.3 s
0/100
10%
262 ms
126 ms
26 ms
405 ms
86 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 65% of them (43 requests) were addressed to the original Audi.com.mx, 30% (20 requests) were made to Assets.audi.com and 2% (1 request) were made to Tms.audi.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Audi.com.mx.
Page size can be reduced by 343.1 kB (18%)
1.9 MB
1.5 MB
In fact, the total size of Audi.com.mx main page is 1.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 974.7 kB which makes up the majority of the site volume.
Potential reduce by 291.6 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 291.6 kB or 88% of the original size.
Potential reduce by 50.3 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. Audi images are well optimized though.
Potential reduce by 550 B
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 680 B
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. Audi.com.mx has all CSS files already compressed.
Number of requests can be reduced by 53 (91%)
58
5
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Audi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
audi.com.mx
262 ms
www.audi.com.mx
126 ms
es.html
26 ms
audi-core-ci-reset-and-basic.min.css
405 ms
audi-core-css.min.css
86 ms
audi-core-ci.min.css
21 ms
audi-core-ci-application.min.css
414 ms
audi-core-application.css
89 ms
nemo-application.min.css
389 ms
nemo-editorial.min.css
402 ms
nemo-configurator-editorial.min.css
408 ms
es.i18n.1709826943552.js
394 ms
audi-microkernel.js
89 ms
jquery-3.6.0.min.js
764 ms
jquery.easing.1.4.1.min.js
779 ms
jquery.placeholder.min.js
785 ms
audi-polyfills.js
88 ms
audi-polyfill-loading.js
88 ms
audi-core-vendor.js
88 ms
audi-core-utils.js
94 ms
audi-core-ci.js
776 ms
audi-core-application.js
91 ms
audi-core-global.js
90 ms
bundle.editorial.js
776 ms
bundle.search-providers.js
795 ms
bundle.configurator.js
1175 ms
modelstartpage.js
1143 ms
audi-core-tracking-objects.js
91 ms
audi-core-application-tracking.js
90 ms
bundle.editorial-tracking.js
1173 ms
modelstartpage-tracking.js
780 ms
audi-microkernel-persistence.js
92 ms
Bootstrap.js
94 ms
audi-core-tracking-events.js
92 ms
app.css
91 ms
vtp.css
781 ms
vtp.js
1139 ms
vtp.legacy.js
1167 ms
model-band.css
1181 ms
model-band.js
1527 ms
model-band.legacy.js
1523 ms
footnotes-block.css
1556 ms
vtp-image-teaser.css
1555 ms
vtp-image-teaser.js
1554 ms
vtp-image-teaser.legacy.js
1603 ms
audi-feature-hub-integrator-csr.js
101 ms
audi-fonts-css.min.css
15 ms
fbevents.js
43 ms
down-small.svg
1470 ms
cancel.svg
1490 ms
forward-small.svg
1523 ms
1px.gif
1176 ms
home_Promociones_1920x1080%20(1).jpg
1514 ms
garantia_home_1080x1080.jpg
1507 ms
back-large.svg
1158 ms
forward-large.svg
1159 ms
AudiType-WideBold.woff
405 ms
AudiType-WideNormal.woff
405 ms
AudiType-WideLight.woff
441 ms
AudiType-ExtendedBold.woff
403 ms
AudiType-ExtendedNormal.woff
390 ms
audi-core-ci-icons-legacy.min.css
385 ms
nemo-search-providers.min.css
8 ms
nemo-form.min.css
364 ms
es.extcolors.css
11 ms
icons.nemo_market_icons.css
8 ms
audi.com.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
audi.com.mx best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
audi.com.mx SEO score
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 Audi.com.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 Audi.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.
audi.com.mx
Open Graph data is detected on the main page of Audi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: