5.4 sec in total
229 ms
4.6 sec
609 ms
Visit audi.com.au now to see the best up-to-date Audi content for Australia and also check out these interesting facts you probably never knew about audi.com.au
Explore new and used Audi models. Offering luxury, performance & safety. Find your nearest Audi dealer, book a service, or calculate finance repayments.
Visit audi.com.auWe analyzed Audi.com.au page load time and found that the first response time was 229 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
audi.com.au performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value27.1 s
0/100
25%
Value26.0 s
0/100
10%
Value4,310 ms
1/100
30%
Value0
100/100
15%
Value30.7 s
0/100
10%
229 ms
526 ms
427 ms
407 ms
71 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 69% of them (47 requests) were addressed to the original Audi.com.au, 26% (18 requests) were made to Assets.audi.com and 1% (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.au.
Page size can be reduced by 391.6 kB (21%)
1.9 MB
1.5 MB
In fact, the total size of Audi.com.au 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 879.2 kB which makes up the majority of the site volume.
Potential reduce by 375.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 375.7 kB or 89% of the original size.
Potential reduce by 14.1 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 915 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 865 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.au has all CSS files already compressed.
Number of requests can be reduced by 51 (82%)
62
11
The browser has sent 62 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 28 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
audi.com.au
229 ms
www.audi.com.au
526 ms
en.html
427 ms
audi-core-ci-reset-and-basic.min.css
407 ms
audi-core-css.min.css
71 ms
audi-core-ci.min.css
59 ms
audi-core-ci-application.min.css
447 ms
audi-core-application.css
68 ms
nemo-application.min.css
432 ms
nemo-editorial.min.css
411 ms
nemo-configurator-editorial.min.css
441 ms
en.i18n.1709827109952.js
444 ms
audi-microkernel.js
76 ms
jquery-3.6.0.min.js
807 ms
jquery.easing.1.4.1.min.js
792 ms
jquery.placeholder.min.js
848 ms
audi-polyfills.js
70 ms
audi-polyfill-loading.js
69 ms
audi-core-vendor.js
70 ms
audi-core-utils.js
70 ms
audi-core-ci.js
849 ms
audi-core-application.js
72 ms
audi-core-global.js
71 ms
bundle.editorial.js
829 ms
bundle.search-providers.js
845 ms
bundle.configurator.js
1168 ms
modelstartpage.js
1204 ms
audi-core-tracking-objects.js
69 ms
audi-core-application-tracking.js
73 ms
bundle.editorial-tracking.js
1220 ms
modelstartpage-tracking.js
855 ms
Bootstrap.js
76 ms
optimize.js
98 ms
audi-core-tracking-events.js
72 ms
app.css
76 ms
vtp.css
851 ms
vtp.js
1238 ms
vtp.legacy.js
1229 ms
model-band.css
1236 ms
model-band.js
1546 ms
model-band.legacy.js
1603 ms
nemo-editorial-teaser.min.css
1604 ms
offer-teasers.css
1606 ms
audi-feature-hub-integrator-csr.js
74 ms
audi-fonts-css.min.css
10 ms
down-small.svg
1207 ms
cancel.svg
1204 ms
forward-small.svg
1447 ms
1px.gif
1203 ms
570x857_EOFY_home-mobile.jpg
1502 ms
570x857_EOFY_campaign.jpg
1523 ms
570x857_Q6_e-tron.png
1497 ms
570x857-Q4-e-tron.jpg
1207 ms
570x857-Dynamic-black-home-page.jpg
1208 ms
748x2500-AUDI_X23_HERO_02_COMP_18-cc-stage-new-300123.jpg
1209 ms
570x857_Audi_Q3_Cliff_06_RGB_v1.jpg
1209 ms
570x857-Join-my-audi.jpg
1550 ms
back-large.svg
1171 ms
forward-large.svg
1172 ms
forward-small.svg
76 ms
AudiType-WideBold.woff
428 ms
AudiType-WideNormal.woff
15 ms
AudiType-WideLight.woff
408 ms
audi-core-ci-icons-legacy.min.css
393 ms
nemo-search-providers.min.css
19 ms
nemo-form.min.css
383 ms
en.extcolors.css
379 ms
icons.nemo_market_icons.css
15 ms
audi.com.au 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
Links do not have a discernible name
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.au 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
Issues were logged in the Issues panel in Chrome Devtools
audi.com.au SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Audi.com.au 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 Audi.com.au 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.au
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: