20.1 sec in total
2 sec
17.8 sec
283 ms
Visit choco.tw now to see the best up-to-date CHOCO content for Taiwan and also check out these interesting facts you probably never knew about choco.tw
Visit choco.twWe analyzed Choco.tw page load time and found that the first response time was 2 sec and then it took 18.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
choco.tw performance score
name
value
score
weighting
Value2.2 s
77/100
10%
Value4.8 s
31/100
25%
Value9.6 s
11/100
10%
Value70 ms
99/100
30%
Value0.003
100/100
15%
Value5.3 s
72/100
10%
2046 ms
430 ms
1110 ms
914 ms
470 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 78% of them (47 requests) were addressed to the original Choco.tw, 7% (4 requests) were made to Google-analytics.com and 3% (2 requests) were made to Static.mediav.com. The less responsive or slowest element that took the longest time to load (5.4 sec) relates to the external source 3m.mediav.com.
Page size can be reduced by 98.8 kB (15%)
667.1 kB
568.3 kB
In fact, the total size of Choco.tw main page is 667.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 504.5 kB which makes up the majority of the site volume.
Potential reduce by 25.9 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 4.8 kB, which is 15% 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 25.9 kB or 82% of the original size.
Potential reduce by 9.0 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. CHOCO images are well optimized though.
Potential reduce by 64.0 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 64.0 kB or 49% of the original size.
Potential reduce by 7 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. Choco.tw has all CSS files already compressed.
Number of requests can be reduced by 16 (27%)
59
43
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CHOCO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
choco.tw
2046 ms
type-9po.css
430 ms
jquery-1.2.6.pack.js
1110 ms
cycle.js
914 ms
btn_e.gif
470 ms
talking-choco-FB.jpg
478 ms
icon_01.gif
489 ms
1456486192.jpg
989 ms
main_btn_01.jpg
1108 ms
main_btn_02.jpg
883 ms
main_btn_03.jpg
901 ms
main_btn_04.jpg
1765 ms
main_btn_05.jpg
1778 ms
main_btn_06.jpg
1591 ms
main_btn_07.jpg
2181 ms
main_btn_08.jpg
1792 ms
main_btn_09.jpg
1781 ms
main_btn_10.jpg
2080 ms
1458202842.jpg
2555 ms
1458203366.jpg
2993 ms
bg_02.jpg
2221 ms
PINKTEDDY_1.jpg
3306 ms
bg_04.jpg
2481 ms
CHOCO3X5_1.jpg
3574 ms
CHOCO1X7_1.jpg
4162 ms
CHOCO6X5_1.jpg
4128 ms
bg_up.jpg
3537 ms
bg_h.jpg
3821 ms
2011ROSE5X3_1.jpg
4701 ms
1401182807.jpg
4508 ms
1397624524.jpg
4512 ms
1397624410.jpg
5238 ms
btn_ab.gif
4503 ms
btn_co.gif
4519 ms
bg_01.jpg
4317 ms
bg_03.jpg
4253 ms
bg_down.jpg
4676 ms
oeya_url_cookie.js
1735 ms
analytics.js
47 ms
ga.js
69 ms
collect
33 ms
mvl.js
2011 ms
__utm.gif
24 ms
mba.js
896 ms
mv.js
4 ms
b
4174 ms
t
4666 ms
t
3944 ms
ckmap.htm
5406 ms
m
421 ms
main_btn_o_01.jpg
708 ms
main_btn_o_02.jpg
485 ms
main_btn_o_03.jpg
482 ms
main_btn_o_04.jpg
486 ms
main_btn_o_05.jpg
487 ms
main_btn_o_06.jpg
482 ms
main_btn_o_07.jpg
903 ms
main_btn_o_08.jpg
904 ms
main_btn_o_09.jpg
907 ms
main_btn_o_10.jpg
903 ms
choco.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
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
choco.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
choco.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
ZH
N/A
BIG5
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Choco.tw can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Choco.tw main page’s claimed encoding is big5. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
choco.tw
Open Graph description is not detected on the main page of CHOCO. 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: