2 sec in total
350 ms
1.4 sec
192 ms
Click here to check amazing Audi content for Brazil. Otherwise, check out these important facts you probably never knew about audi.com.br
Visit audi.com.brWe analyzed Audi.com.br page load time and found that the first response time was 350 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
audi.com.br performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value13.2 s
0/100
25%
Value10.6 s
7/100
10%
Value3,720 ms
1/100
30%
Value0.535
14/100
15%
Value20.4 s
2/100
10%
350 ms
333 ms
144 ms
68 ms
41 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 89% of them (64 requests) were addressed to the original Audi.com.br, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (350 ms) belongs to the original domain Audi.com.br.
Page size can be reduced by 1.2 MB (30%)
4.0 MB
2.8 MB
In fact, the total size of Audi.com.br main page is 4.0 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. 80% 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 2.9 MB which makes up the majority of the site volume.
Potential reduce by 109.8 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 109.8 kB or 88% of the original size.
Potential reduce by 392.5 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. Obviously, Audi needs image optimization as it can save up to 392.5 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 434.5 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 434.5 kB or 67% of the original size.
Potential reduce by 257.2 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. Audi.com.br needs all CSS files to be minified and compressed as it can save up to 257.2 kB or 84% of the original size.
Number of requests can be reduced by 9 (14%)
66
57
The browser has sent 66 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 10 to 1 for JavaScripts and as a result speed up the page load time.
audi.com.br
350 ms
www.audi.com.br
333 ms
pt.html
144 ms
css.css
68 ms
cms4i-models.css
41 ms
libs.js
39 ms
google-analytics.data.js
39 ms
google-tag-manager.data.js
41 ms
openconfigurator.js
91 ms
satelliteLib-82454481c510e62d9798b3cc70195d2c4bdb2004.js
49 ms
jquery.min.js
31 ms
js.js
132 ms
s_code.js
130 ms
cms4i-models.js
129 ms
analytics.js
97 ms
logo-audi.png
74 ms
101004_teaser_modelle.jpg
74 ms
icons-sfb0aa41833.png
74 ms
destaque-site-audi.jpg
75 ms
COVER-SITE-2-Q7.jpg
76 ms
971x395_RS3.jpg
78 ms
971x395_Premiacao.jpg
80 ms
hero-arrow.png
76 ms
104x51destaque-site-audi.jpg
77 ms
104x51_Q7.jpg
147 ms
104x51_RS3.jpg
78 ms
Premiacao-104x51.jpg
140 ms
minibanner_msgpresidente.jpg
141 ms
arrows.png
141 ms
background_quickfinder_flyout.png
141 ms
thumb_218_60.jpg
142 ms
destaque_3.jpg
144 ms
A1%20Sportback.jpg
143 ms
550x274-RS-3-Sportback.jpg
143 ms
A3%20Sedan.jpg
145 ms
S3%20Sedan.jpg
144 ms
a3-sportback.jpg
147 ms
A3%20Cabriolet.jpg
145 ms
S3%20Sportback.jpg
147 ms
A4Sedan_menu2.jpg
148 ms
A4Avant_menu2.jpg
148 ms
S4%20Sedan.jpg
178 ms
A5%20Coup%C3%A9.jpg
165 ms
A5%20Sportback.jpg
164 ms
A5%20Cabriolet.jpg
166 ms
S5%20Sportback.jpg
278 ms
A6%20Sedan.jpg
185 ms
A6%20Allroad.jpg
189 ms
RS6%20Avant.jpg
205 ms
A7.jpg
192 ms
S7.jpg
156 ms
collect
71 ms
AudiType-ExtendedNormal.woff
172 ms
AudiType-ExtendedBold.woff
153 ms
RS7_01.jpg
182 ms
a8_lw_12_1415.png
169 ms
s8_sedan_1415.png
179 ms
img-q3-nav.jpg
182 ms
RSQ3_menu_thumb.jpeg
208 ms
q5.png
196 ms
sq5_1415.png
206 ms
550x274_Q7.jpg
205 ms
collect
71 ms
img-tt-coupe-red-nav2.jpg
151 ms
550x274_TT%20Roadster.jpg
159 ms
R8v10Plus_thumb.png
176 ms
r8_menu_thumb.png
171 ms
share_icons.png
216 ms
ga-audiences
45 ms
s61523420296143
83 ms
print.css
79 ms
gtm.js
23 ms
audi.com.br 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
audi.com.br 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
Missing source maps for large first-party JavaScript
audi.com.br SEO score
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
PT
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Audi.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed German language. Our system also found out that Audi.com.br 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.br
Open Graph description is not detected on the main page of Audi. 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: