4.4 sec in total
434 ms
3.1 sec
911 ms
Click here to check amazing ASUS content for China. Otherwise, check out these important facts you probably never knew about asus.com
Driven by innovation & committed to quality, ASUS has a wide selection of best in class products. Find & buy a laptop, phone, router, monitor, motherboard & more
Visit asus.comWe analyzed Asus.com page load time and found that the first response time was 434 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
asus.com performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value6.9 s
6/100
25%
Value8.0 s
22/100
10%
Value2,230 ms
6/100
30%
Value0.545
13/100
15%
Value16.3 s
5/100
10%
434 ms
816 ms
117 ms
196 ms
40 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 57% of them (58 requests) were addressed to the original Asus.com, 12% (12 requests) were made to Dlcdnimgs.asus.com and 9% (9 requests) were made to Dlcdnrog.asus.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Cdn.fonts.net.
Page size can be reduced by 434.4 kB (16%)
2.6 MB
2.2 MB
In fact, the total size of Asus.com main page is 2.6 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. 85% 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.2 MB which makes up the majority of the site volume.
Potential reduce by 374.3 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 374.3 kB or 85% of the original size.
Potential reduce by 59.4 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. ASUS images are well optimized though.
Potential reduce by 53 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 613 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. Asus.com has all CSS files already compressed.
Number of requests can be reduced by 38 (46%)
83
45
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ASUS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
asus.com
434 ms
asus.com
816 ms
www.asus.com
117 ms
gtm.js
196 ms
jquery.min.js
40 ms
d03fa1226.css
83 ms
98bcb1226.css
107 ms
c494d1226.css
104 ms
e29521226.css
125 ms
51e7d1226.css
129 ms
963851226.css
145 ms
app-fc8ad1226.js
123 ms
6a11a1226.js
170 ms
813f01226.js
172 ms
ed43b1226.js
172 ms
cdd061226.js
173 ms
e335e1226.js
177 ms
0c7cf1226.js
175 ms
6584f1226.js
174 ms
b20e61226.js
174 ms
1a0a81226.js
174 ms
4eaeab2a-7799-4cea-a477-9d3fee23da54.css
65 ms
69852dc2-bbe3-40d4-9053-e412b00d6f45.css
80 ms
9d6c4993-7af8-42eb-aef7-5ba3591e71b6.css
63 ms
9207232b-0445-4c65-b8d6-acac7c66a782.js
99 ms
overview.js
174 ms
global.js
265 ms
ROG_normal.svg
220 ms
ROG_hover.svg
218 ms
ProArt_normal.svg
216 ms
ProArt_hover.svg
221 ms
IoT_normal.svg
216 ms
IoT_hover.svg
391 ms
fseda5gem1ps9l7i-0_0_desktop_0_1X.webp
396 ms
rduud5feliqsxwxc-0_0_desktop_0_1X.jpg
395 ms
fekrw86ni7rl4vgw-0_0_desktop_0_1X.jpg
398 ms
3iuxzxzbeiqntk0l-0_0_desktop_0_1X.webp
393 ms
7u0rilvy3ec7thnq-0_0_desktop_0_1X.jpg
399 ms
vjoj5d49cv9dqcuv-0_0_desktop_0_1X.jpg
394 ms
wvkm2ksywnpqzn2q-0_0_desktop_0_1X.jpg
401 ms
mxhbgt9oorohtl9b-0_0_desktop_1_1X.jpg
397 ms
mxhbgt9oorohtl9b-0_1_desktop_1_1X.png
398 ms
mxhbgt9oorohtl9b-1_0_desktop_0_1X.jpg
399 ms
mxhbgt9oorohtl9b-1_1_desktop_0_1X.png
401 ms
mxhbgt9oorohtl9b-2_0_desktop_2_1X.jpg
402 ms
mxhbgt9oorohtl9b-3_0_desktop_3_1X.jpg
390 ms
mxhbgt9oorohtl9b-4_0_desktop_4_1X.webp
370 ms
mxhbgt9oorohtl9b-5_0_desktop_5_1X.webp
356 ms
logo-001.svg
98 ms
logo-blue001.svg
110 ms
header_search_light_normal.svg
268 ms
header_search_light_hover.svg
269 ms
header_logout_light_normal.svg
270 ms
header_logout_light_hover.svg
269 ms
footer_light_seemore.svg
272 ms
gtm.js
210 ms
72fe61226.css
60 ms
76d6e1226.js
69 ms
RQQXY-PWR8Y-FJH4F-ZT6TK-8WW94
908 ms
MyriadRegular_normal_normal.woff
879 ms
TTNormsProRegular_normal_normal.woff
946 ms
TTNormsProNormal_normal_normal.woff
983 ms
TTNormsProMedium_normal_normal.woff
947 ms
MyriadSemibold_normal_normal.woff
1167 ms
promotionbanner.min.js
749 ms
locationreminder.min.js
748 ms
mxhbgt9oorohtl9b-4_0_desktop_4_1X.webp
339 ms
160041226.js
98 ms
alert-info.js
37 ms
getRating
132 ms
EcommerceList
152 ms
SearchWording
160 ms
GetQuickLink
163 ms
HotCampaignsList
164 ms
ContentHubList
185 ms
mxhbgt9oorohtl9b-5_0_desktop_5_1X.webp
54 ms
fseda5gem1ps9l7i-0_0_desktop_0_1X.webp
73 ms
3iuxzxzbeiqntk0l-0_0_desktop_0_1X.webp
71 ms
alert-info.css
35 ms
GetCookieNotice
167 ms
config.json
74 ms
bv.js
85 ms
20201028111025.jpg
116 ms
20230912015154.jpg
74 ms
20230329045224.jpg
74 ms
20220706043811.jpg
75 ms
20221006020920.jpg
87 ms
20210915053500.jpg
75 ms
20201028111043.jpg
137 ms
20230313110854.jpg
122 ms
1701904656381.webp
100 ms
1701315929488.webp
91 ms
1700351859781.webp
100 ms
1699458684756.webp
100 ms
1699590544241.webp
99 ms
1697843191625.webp
98 ms
169750156552.webp
99 ms
1696672240385.webp
109 ms
1695852581519.webp
110 ms
analytics.js
79 ms
24_cross_normal.svg
42 ms
FontSubsetter.ashx
86 ms
asus.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
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
asus.com 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
asus.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
Image elements do not have [alt] attributes
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Asus.com 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 Asus.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.
asus.com
Open Graph description is not detected on the main page of ASUS. 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: