3.4 sec in total
473 ms
2.8 sec
146 ms
Visit audi.co.kr now to see the best up-to-date Audi content for South Korea and also check out these interesting facts you probably never knew about audi.co.kr
아우디코리아 공식홈페이지입니다.
Visit audi.co.krWe analyzed Audi.co.kr page load time and found that the first response time was 473 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
audi.co.kr performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value8.7 s
1/100
25%
Value12.2 s
3/100
10%
Value11,420 ms
0/100
30%
Value0.126
83/100
15%
Value24.4 s
0/100
10%
473 ms
391 ms
39 ms
313 ms
497 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 95% of them (53 requests) were addressed to the original Audi.co.kr, 2% (1 request) were made to Assets.adobedtm.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Audi.co.kr.
Page size can be reduced by 1.1 MB (23%)
4.8 MB
3.7 MB
In fact, the total size of Audi.co.kr main page is 4.8 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. 65% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.
Potential reduce by 79.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. This page needs HTML code to be minified as it can gain 10.2 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 79.8 kB or 88% of the original size.
Potential reduce by 371.7 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 399.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 399.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.co.kr 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 5 (10%)
52
47
The browser has sent 52 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 6 to 1 for JavaScripts and as a result speed up the page load time.
audi.co.kr
473 ms
www.audi.co.kr
391 ms
kn.html
39 ms
css.css
313 ms
cms4i-models.css
497 ms
libs.js
305 ms
openconfigurator.js
222 ms
satelliteLib-82454481c510e62d9798b3cc70195d2c4bdb2004.js
65 ms
jquery.min.js
51 ms
js.js
275 ms
s_code.js
583 ms
cms4i-models.js
475 ms
audi_logo_new.gif
136 ms
101004_teaser_modelle.jpg
167 ms
icons-sfb0aa41833.png
195 ms
fv_971x399.jpg
789 ms
151016_audi%20banner_1.jpg
134 ms
arrows.png
200 ms
home-main_218x60.jpg
141 ms
151016_audi%20banner_2.jpg
141 ms
550x274_0000_a1.png
203 ms
550x274_0000_a1%20sporback.png
236 ms
amalfi_white_01.png
249 ms
a3sportback_01.png
513 ms
s3sedan_navigation.png
269 ms
A3-etron_550x274.jpg
291 ms
a4_model_flyout.png
308 ms
s4_model_flyout.png
326 ms
a5_model_flyout.png
635 ms
a5sb_flyout.png
403 ms
a5cabriolet_model.png
379 ms
s5_model_flyout.png
410 ms
rs5_model_flyout.png
494 ms
new%20A6_model_flyout.png
488 ms
s6_model_flyout.png
717 ms
a7%20flyout.png
552 ms
s7%20flyout.png
574 ms
rs7%20flyout.png
562 ms
A8_model_flyout2.png
647 ms
A8L_model_flyout2.png
620 ms
A8LW12_model_flyout2.png
845 ms
S8_model_flyout2.png
698 ms
newq3_model_flyout.png
696 ms
q5_flyout.png
1296 ms
model_Par_0043_Image.png
781 ms
sq5_flyout.png
791 ms
q7_flyout.png
667 ms
tt-coupe_navi_2016.png
713 ms
tt-r_navi_2016.png
707 ms
AudiType-ExtendedNormal.woff
1025 ms
AudiType-ExtendedBold.woff
919 ms
tts-coupe_navi_2016_2.png
750 ms
r8_coupe_flyout.png
730 ms
r8_spyder_flyout.png
716 ms
s6176258040592
81 ms
print.css
47 ms
audi.co.kr 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.co.kr 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.co.kr 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
Tap targets are not sized appropriately
KO
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Audi.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it does not match the claimed German language. Our system also found out that Audi.co.kr 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.co.kr
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: