12.3 sec in total
929 ms
11.1 sec
233 ms
Welcome to cha.com.tw homepage info - get ready to check Cha best content for Taiwan right away, or after learning these important things about cha.com.tw
民國58年創立迄今,正新鋁業一路走來超過五十個年頭。從上一代的董事長劉金原手中接棒,身為第二代的劉南宏總經理戮力打造「正新精品門窗」的品牌,讓猶如房屋之眼的門窗,不僅給予室內與室外介面的安全保護,也給消費者滿滿幸福。
Visit cha.com.twWe analyzed Cha.com.tw page load time and found that the first response time was 929 ms and then it took 11.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
cha.com.tw performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value16.4 s
0/100
25%
Value22.1 s
0/100
10%
Value480 ms
60/100
30%
Value1.25
1/100
15%
Value18.9 s
3/100
10%
929 ms
1767 ms
421 ms
1252 ms
7 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 56% of them (71 requests) were addressed to the original Cha.com.tw, 26% (33 requests) were made to Static.xx.fbcdn.net and 4% (5 requests) were made to Translate.googleapis.com. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Cha.com.tw.
Page size can be reduced by 401.3 kB (20%)
2.0 MB
1.6 MB
In fact, the total size of Cha.com.tw main page is 2.0 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. 75% 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 1.6 MB which makes up the majority of the site volume.
Potential reduce by 24.6 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 3.4 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 24.6 kB or 80% of the original size.
Potential reduce by 220.8 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. Obviously, Cha needs image optimization as it can save up to 220.8 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 61.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 61.5 kB or 32% of the original size.
Potential reduce by 94.3 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. Cha.com.tw needs all CSS files to be minified and compressed as it can save up to 94.3 kB or 79% of the original size.
Number of requests can be reduced by 68 (57%)
120
52
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cha. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
cha.com.tw
929 ms
1767 ms
style.css
421 ms
global.css
1252 ms
font-awesome.min.css
7 ms
cross-nav.css
420 ms
animate.css
427 ms
jquery-1.6.1.min.js
1552 ms
js_paging_slider_function.js
812 ms
element.js
33 ms
rotator.css
410 ms
cross_nav_bg.jpg
417 ms
ga.js
55 ms
global_bg.gif
493 ms
gtm.js
60 ms
cross_nav_divider.gif
491 ms
logo_cha_tiny.gif
701 ms
logo_baluk_tiny.gif
703 ms
logo_dawaki_tiny.gif
701 ms
line_black.png
917 ms
faq.png
918 ms
logo.gif
925 ms
translateelement.css
97 ms
main.js
123 ms
rotator_reel_1.jpg
2191 ms
rotator_reel_2.jpg
2585 ms
rotator_reel_3.jpg
3086 ms
paging_1.jpg
2032 ms
paging_2.gif
1621 ms
paging_3.gif
1623 ms
slide_icon_ribbon_head.png
2057 ms
slide_icon_b.png
2381 ms
slide_b.jpg
3298 ms
slide_icon_a.png
2489 ms
slide_a.jpg
3531 ms
slide_icon_c.png
2801 ms
slide_c.jpg
3572 ms
slide_icon_d.png
3148 ms
slide_d.jpg
3868 ms
slide_icon_e.png
3562 ms
slide_e.jpg
4337 ms
slide_icon_f.png
3737 ms
slide_f.jpg
5107 ms
slide_icon_h.png
4049 ms
slide_h.jpg
4882 ms
slide_icon_ribbon_tail.png
4191 ms
heading_news.gif
4336 ms
icon_popup.gif
4519 ms
heading_fb_home.gif
4631 ms
banner_baluk.jpg
5308 ms
banner_tostem.jpg
4974 ms
fontawesome-webfont.woff
38 ms
__utm.gif
17 ms
likebox.php
302 ms
collect
55 ms
element_main.js
55 ms
ga-audiences
70 ms
translate_24dp.png
28 ms
l
49 ms
cleardot.gif
13 ms
te_ctrl3.gif
12 ms
hDvwL1_H7g-.css
39 ms
56WNbrUYLbL.css
40 ms
yZ--Yu0PDbV.css
45 ms
QD6_ejUFoCN.css
74 ms
xxJgcoj8mOR.css
61 ms
gbh6x73jsGH.css
47 ms
khX_DTDmaMU.css
79 ms
q68gy-v_YMF.js
89 ms
FJmpeSpHpjS.js
88 ms
0wM5s1Khldu.js
123 ms
1bNoFZUdlYZ.js
125 ms
njO1TPvGzoR.js
127 ms
1QuX41zDRrx.js
128 ms
Oagsvfb4VWi.js
123 ms
LTv6ZK-5zxz.js
132 ms
1FCa-btixu2.js
148 ms
IjqSyiwKeaX.js
152 ms
rBxSIHk4zIe.js
152 ms
n6VgtouijQL.js
145 ms
7BE0CZr3HTs.js
145 ms
pQrUxxo5oQp.js
161 ms
_UYztdBNTjs.js
160 ms
-7JBD_ybv4q.js
164 ms
Kt4tkgSRvHH.js
160 ms
banner_safety_lock.gif
4756 ms
banner_glass_sm.gif
5138 ms
logo_bottom.gif
4864 ms
391172_446604008703296_2051843126_n.jpg
162 ms
safe_image.php
162 ms
b8XhdWI9eAN.js
43 ms
safe_image.php
49 ms
safe_image.php
47 ms
safe_image.php
111 ms
314084_260646383965727_909880646_n.jpg
35 ms
12419822_1093108427386181_1864653260_n.jpg
45 ms
wL6VQj7Ab77.png
22 ms
s7jcwEQH7Sx.png
31 ms
aeO1ik7i7-T.png
44 ms
QDwYpIaRyfG.png
31 ms
l5aPruN9xMM.png
33 ms
K00K-UgnsKu.png
42 ms
K_65vAc89SX.png
43 ms
paging_bg.png
4762 ms
icon_language.gif
4870 ms
upper_right_nav_login.gif
4912 ms
I6-MnjEovm5.js
5 ms
upper_right_nav_contact.gif
4871 ms
upper_right_nav_homepage.gif
4874 ms
upper_right_nav_facebook.gif
4950 ms
upper_right_nav_youtube.gif
4319 ms
upper_right_nav_yahoo_blog.gif
4379 ms
nav_dropdown_bg.png
3967 ms
arrow_red.gif
4106 ms
slide_icon_ribbon.png
3981 ms
button_more.gif
3981 ms
icon_new.gif
3900 ms
bullet_orange_bracket.gif
3850 ms
social_facebook.gif
3670 ms
social_youtube.gif
3526 ms
social_yahoo_blog.gif
3501 ms
arrow_square_white.gif
3486 ms
arrow_gray.gif
3301 ms
icon_yahoo.gif
3281 ms
icon_youtube.gif
3325 ms
icon_facebook.gif
3312 ms
icon_language.gif
1569 ms
cha.com.tw 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.
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
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.
cha.com.tw 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
General
Impact
Issue
Detected JavaScript libraries
cha.com.tw SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cha.com.tw can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Cha.com.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.
cha.com.tw
Open Graph description is not detected on the main page of Cha. 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: