31.1 sec in total
8.6 sec
21.5 sec
981 ms
Click here to check amazing Audi content for Taiwan. Otherwise, check out these important facts you probably never knew about audi.tw
Log into Facebook to start sharing and connecting with your friends, family, and people you know.
Visit audi.twWe analyzed Audi.tw page load time and found that the first response time was 8.6 sec and then it took 22.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
audi.tw performance score
name
value
score
weighting
Value3.0 s
51/100
10%
Value4.4 s
40/100
25%
Value6.6 s
38/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value3.5 s
92/100
10%
8567 ms
667 ms
5943 ms
5238 ms
104 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 20% of them (26 requests) were addressed to the original Audi.tw, 20% (27 requests) were made to Yesno.tw and 9% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (8.6 sec) belongs to the original domain Audi.tw.
Page size can be reduced by 254.0 kB (22%)
1.1 MB
890.3 kB
In fact, the total size of Audi.tw main page is 1.1 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. 50% of websites need less resources to load. Images take 878.5 kB which makes up the majority of the site volume.
Potential reduce by 37.2 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 37.2 kB or 78% of the original size.
Potential reduce by 83.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 60.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 60.5 kB or 46% of the original size.
Potential reduce by 72.6 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.tw needs all CSS files to be minified and compressed as it can save up to 72.6 kB or 84% of the original size.
Number of requests can be reduced by 68 (54%)
126
58
The browser has sent 126 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 36 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
audi.tw
8567 ms
font.css
667 ms
css.asp
5943 ms
www.yesno.tw
5238 ms
brand
104 ms
slidemenu.css
463 ms
slidemenu.js
725 ms
brand
149 ms
layout.css
216 ms
radius.css
262 ms
show_ads.js
21 ms
clearLinkDot.js
378 ms
shCore.js
606 ms
shBrushBash.js
445 ms
shBrushCss.js
480 ms
shBrushJava.js
749 ms
shBrushJScript.js
496 ms
shBrushSql.js
818 ms
shBrushVb.js
665 ms
shBrushXml.js
713 ms
shCore.css
741 ms
shThemeDefault.css
825 ms
urchin.js
15 ms
PosterSite.css
470 ms
showModalWindow.css
472 ms
a'js.js
4389 ms
swfobject.js
3336 ms
loadMenu.js
686 ms
slidemenu.js
473 ms
css_postersite.asp
789 ms
main.css
225 ms
customer.css
222 ms
layout.css
315 ms
pulldown.css
442 ms
radius.css
448 ms
slidemenu.css
487 ms
nameLogo.png
260 ms
photo.jpg
97 ms
html5-drawing-tool-example.png
253 ms
CSS3-Logo.png
370 ms
sharethis.png
2590 ms
clickEffectWithCSS.jpg
107 ms
textarea-auto-resize.jpg
126 ms
10131183958.gif
3463 ms
2497433461_d1e67e2f90_o.jpg
116 ms
css-gradient.gif
192 ms
closure.jpg
68 ms
htmlBG.png
245 ms
spacer.gif
247 ms
more.png
244 ms
ckeditor.png
722 ms
IE9Beta-1.png
567 ms
scrollbars.png
447 ms
google_custom_search_watermark.gif
94 ms
bodyBG.png
240 ms
bg.png
456 ms
liDot.png
438 ms
zrt_lookup.html
26 ms
show_ads_impl.js
58 ms
ajax-fig1_small.png
49 ms
ajax-fig1_small.png
61 ms
ads
288 ms
osd.js
73 ms
likebox.php
302 ms
ads
271 ms
q_right.png
254 ms
q_left.png
274 ms
__utm.gif
27 ms
oYULo-XyiZp.css
357 ms
ILMlA6xuPbo.css
428 ms
SRSW8M763HA.js
589 ms
ullQFyhrQFI.js
728 ms
y97Ig99UVTs.js
608 ms
KHAtULXOQuz.js
644 ms
4230558780880128617
45 ms
abg.js
50 ms
m_js_controller.js
69 ms
googlelogo_color_112x36dp.png
44 ms
s
6 ms
x_button_blue2.png
64 ms
favicon
90 ms
nessie_icon_tiamat_white.png
21 ms
j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js
12 ms
12806006_966532163440397_7842471044496743579_n.jpg
385 ms
250264_127779420649013_2775110_n.jpg
456 ms
545111_112030235604561_2096376744_n.jpg
599 ms
10409301_10200193584997762_6297193787999777745_n.jpg
592 ms
12592718_945212295556133_2372402728714209534_n.jpg
595 ms
21310_110530862484498_874769158_n.jpg
593 ms
12472788_1006886592736805_9034079877584082335_n.jpg
592 ms
wL6VQj7Ab77.png
70 ms
1JLnMyDN79z.png
70 ms
VXcANLwwL5J.js
78 ms
i8XO-4kv8i7.js
77 ms
bodyBG.jpg
995 ms
Truss.jpg
4249 ms
nav.png
268 ms
BDB59C1A-1747-47BA-A97E-ABAA833B7EA6.png
295 ms
72DB8965-36C8-48F9-87B0-C131E5099F65.jpg
1049 ms
20100314-101%E6%96%BD%E5%B7%A5123.jpg
1022 ms
653ACA2B-A7A5-482E-A48D-B11A9D35321C.jpg
1025 ms
20100511253.jpg
1030 ms
%E9%9B%B2%E6%9E%97%E8%99%8E%E5%B0%BE%E7%AB%AF%E7%99%BC%E8%97%A5%E5%B1%80_981210%E5%AE%8C%E5%B7%A5.JPG
1112 ms
blinkblink.jpg
1554 ms
E4D38524-51CB-46D1-BC98-46A57A593B17.jpg
1254 ms
P1060787.jpg
1275 ms
3BF0F0C3-A073-4415-94CD-51F5C0F10258.jpg
1511 ms
ads
213 ms
ga.js
7 ms
menu.asp
1257 ms
__utm.gif
23 ms
like.php
149 ms
a.js;p=11007202166541;cache=ABAjH0jvqKk29xgIVJTqTeEeYJ1-
121 ms
ca
52 ms
adj
100 ms
beacon
91 ms
Sh_BYjerrZ8.js
225 ms
LVx-xkvaJ0b.png
88 ms
US_b_Spr_GiftCard_SprStay2GiftCardBUSINESS16_234x60-bu.jpg
377 ms
cap
67 ms
pixel
20 ms
lidar.js
4 ms
sbhK2lTE.js
9 ms
cTrvNaRi.html
12 ms
pixel
67 ms
pixel
76 ms
sd
42 ms
activeview
40 ms
yesNo_64x22.png
229 ms
nav-bg.png
229 ms
ca
43 ms
get
35 ms
get
49 ms
audi.tw 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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>).
audi.tw best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
audi.tw 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Audi.tw can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Audi.tw 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.tw
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: