16.6 sec in total
2.9 sec
13.6 sec
205 ms
Welcome to auo.com homepage info - get ready to check AUO best content for China right away, or after learning these important things about auo.com
AUO is an enthusiastic, technology-driven company, delivering products and solution services that advance the frontier of innovation for display, system solutions, industrial intelligence, healthcare ...
Visit auo.comWe analyzed Auo.com page load time and found that the first response time was 2.9 sec and then it took 13.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
auo.com performance score
name
value
score
weighting
Value9.7 s
0/100
10%
Value12.7 s
0/100
25%
Value13.9 s
1/100
10%
Value250 ms
84/100
30%
Value0.313
37/100
15%
Value11.7 s
17/100
10%
2881 ms
3834 ms
428 ms
430 ms
455 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 94% of them (82 requests) were addressed to the original Auo.com, 6% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Auo.com.
Page size can be reduced by 321.7 kB (22%)
1.5 MB
1.2 MB
In fact, the total size of Auo.com main page is 1.5 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. 15% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 180.4 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 180.4 kB or 84% of the original size.
Potential reduce by 32.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. AUO images are well optimized though.
Potential reduce by 91.6 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 91.6 kB or 66% of the original size.
Potential reduce by 17.7 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. Auo.com needs all CSS files to be minified and compressed as it can save up to 17.7 kB or 72% of the original size.
Number of requests can be reduced by 62 (73%)
85
23
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AUO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
auo.com
2881 ms
auo.com
3834 ms
layout.css
428 ms
style.css
430 ms
sizeDefault.css
455 ms
index.css
465 ms
product.css
482 ms
news.css
643 ms
links.css
643 ms
ajax.js
678 ms
string.js
696 ms
form.js
725 ms
date.js
855 ms
calendar.js
1068 ms
verifying_code.js
901 ms
fontSizeControl.js
936 ms
common.js
964 ms
image.js
1066 ms
menu.js
1125 ms
jquery.js
1723 ms
index.js
1199 ms
product.js
1202 ms
news.js
1277 ms
body.css
858 ms
tp5.js
240 ms
tp4.js
227 ms
tp6.js
215 ms
tp3.js
240 ms
tp1.css
216 ms
tp2.css
429 ms
tp3.css
430 ms
tp4.css
448 ms
tp5.css
474 ms
tp6.css
474 ms
tp7.css
640 ms
tp8.css
639 ms
tp9.css
668 ms
tp10.css
670 ms
link.js
241 ms
index_wheel.js
230 ms
index_menu.js
236 ms
bg_header_line.png
240 ms
94042c07a651d0ce15c2778c6e8faf2e.png
227 ms
btn_go_off.jpg
253 ms
bbb314215bfa63841e3aa0d78b65ab6a.jpg
1093 ms
btn_arrow_left_off.jpg
239 ms
btn_arrow_right_off.jpg
219 ms
6a352afc3e08bb90cf9fceee86f381f4.jpg
456 ms
btn_bottom_left_off.gif
465 ms
800ad550566e636e99e6824576c043e6.jpg
965 ms
9ed4b4c71d9c372ef3f702619f2f5923.jpg
761 ms
7432521e6ded558b4a9ef3656faf0c97.jpg
750 ms
75403d4c63e4d74f99d2cafb64e3482d.gif
902 ms
34b65104acb666fb4c708d934ffe07f6.jpg
1181 ms
27bb10bd3bd9e9edd8c81196d4fe5ef6.jpg
1451 ms
0ffad277ff16db422d1fc13d9989d005.jpg
1021 ms
71835f8f0923c83e52fb3233868c0aad.JPG
1371 ms
btn_bottom_right_off.gif
1203 ms
icon_footer_1.gif
1262 ms
icon_footer_2.gif
1306 ms
icon_footer_4.gif
1409 ms
icon_stay_dot_off.gif
1432 ms
bg_content.jpg
1490 ms
bg_index_content_2.png
1510 ms
bg_index_content_frame.jpg
1580 ms
bg_frame_top.jpg
1579 ms
bg_frame.jpg
1624 ms
icon_1.gif
1629 ms
bg_frame_bottom.jpg
1681 ms
bg_index_content_bottom.png
1676 ms
bg_bottom_blue_left.jpg
1747 ms
icon_index_blueblock.gif
1802 ms
img_bottom_line.jpg
1861 ms
bg_bottom_blue_right.jpg
1860 ms
icon_kv_off.png
1819 ms
icon_kv_on.png
1848 ms
bg_footer.jpg
1890 ms
ga.js
30 ms
__utm.gif
12 ms
__utm.gif
21 ms
__utm.gif
22 ms
__utm.gif
22 ms
_20151022111637_24583.jpg
2825 ms
_20150615172812_91895.jpg
5244 ms
cbf3fcd80f6b090998b3e93281b9e330.jpg
5348 ms
_20150615172919_58740.jpg
3054 ms
_20150615173128_94038.jpg
3430 ms
auo.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
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
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>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
auo.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
auo.com 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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Auo.com 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 Auo.com 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.
auo.com
Open Graph description is not detected on the main page of AUO. 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: