13.8 sec in total
1.9 sec
4.2 sec
7.8 sec
Visit kuro.tw now to see the best up-to-date Kuro content for Taiwan and also check out these interesting facts you probably never knew about kuro.tw
Kuro's Blog 隨手寫寫,就是個人的筆記。
Visit kuro.twWe analyzed Kuro.tw page load time and found that the first response time was 1.9 sec and then it took 11.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
kuro.tw performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value4.5 s
38/100
25%
Value2.6 s
97/100
10%
Value170 ms
93/100
30%
Value0.002
100/100
15%
Value4.2 s
85/100
10%
1884 ms
497 ms
24 ms
468 ms
519 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Kuro.tw, 22% (30 requests) were made to User-image.logdown.io and 19% (26 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Kuro.tw.
Page size can be reduced by 806.5 kB (15%)
5.3 MB
4.5 MB
In fact, the total size of Kuro.tw main page is 5.3 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 4.3 MB which makes up the majority of the site volume.
Potential reduce by 87.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 87.4 kB or 79% of the original size.
Potential reduce by 185.2 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. Kuro images are well optimized though.
Potential reduce by 454.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 454.6 kB or 61% of the original size.
Potential reduce by 79.2 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. Kuro.tw needs all CSS files to be minified and compressed as it can save up to 79.2 kB or 69% of the original size.
Number of requests can be reduced by 63 (48%)
131
68
The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kuro. 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 8 to 1 for CSS and as a result speed up the page load time.
kuro.tw
1884 ms
modernizr-2.0.js
497 ms
jquery.min.js
24 ms
octopress.js
468 ms
screen.css
519 ms
default_code_highlight.css
522 ms
css
26 ms
css
38 ms
MathJax.js
23 ms
ga.js
204 ms
2V8wHgLUTEawU5iJstYS_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-12-20%20%E4%B8%8B%E5%8D%8812.21.25.png
254 ms
embedviz
337 ms
mhzctMFXFoHMJn
489 ms
NdKfJWerFlauo9
216 ms
top_controls
686 ms
Jrbqo6EaTJswhfBQUF6g_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-12-20%20%E4%B8%8B%E5%8D%881.23.36.png
242 ms
eTI8r7EXSQWaH80HZuKH_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-12-20%20%E4%B8%8B%E5%8D%881.39.54.png
300 ms
NMpkG3LeTOWaYaNf9pYC_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-12-20%20%E4%B8%8B%E5%8D%881.40.01.png
240 ms
VA6ir3TRyutauy6ALqdH_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-12-20%20%E4%B8%8B%E5%8D%881.42.43.png
210 ms
Mz3vq9BKRZ2dkSd5SP6W_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-12-20%20%E4%B8%8B%E5%8D%881.54.29.png
301 ms
swZcbhnQPmhiWQBwTbDG_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-12-20%20%E4%B8%8B%E5%8D%881.55.08.png
302 ms
mM3agzeTGGGdM2p4YjZq_2015-12-20%2003.33.30.png
300 ms
j4wccnAOTZWhLzubTUDw_2015-12-20%2003.33.43.png
302 ms
UsvTpRmSDWhtT8junGNw_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-10-15%20%E4%B8%8A%E5%8D%8810.16.22.png
302 ms
vFIqF2IuSOuhKhR0mKUt_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-10-15%20%E4%B8%8A%E5%8D%8810.33.31.png
489 ms
QrsLmP03QNamaW0qrqjT_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-10-15%20%E4%B8%8A%E5%8D%8810.37.48.png
349 ms
Wf4cjXTQTrCXlw0UDWMl_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-10-15%20%E4%B8%8A%E5%8D%8810.05.47.png
352 ms
AUqRTPyFQX29z5TdLGaM_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-10-15%20%E4%B8%8A%E5%8D%8810.06.19.png
363 ms
fNpq4j4rTEuynwQAcxOO_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-10-15%20%E4%B8%8A%E5%8D%8810.07.40.png
393 ms
bbUWtz7RXqdpZsizK5Lw_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-10-15%20%E4%B8%8A%E5%8D%8810.08.07.png
363 ms
wYMPpnlHTRmrgoywrKGc_%E6%9C%AA%E5%91%BD%E5%90%8D.png
524 ms
66zfnteRQy6L50MJQUZ1_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-10-15%20%E4%B8%8A%E5%8D%8810.11.18.png
649 ms
pDQ7qI4WSDub29jPiglU_%E6%9C%AA%E5%91%BD%E5%90%8D.png
452 ms
thibCn9zRMO435hQgjFd_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-10-15%20%E4%B8%8A%E5%8D%8810.11.57.png
486 ms
TK4RPNQtQNiXcQBclDeu_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-10-15%20%E4%B8%8A%E5%8D%8810.12.09.png
441 ms
csg65yBiQIyKcj1PAnNk_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-10-15%20%E4%B8%8A%E5%8D%8810.58.53.png
526 ms
JJNbZ5DRRmehqBdoDytm_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-10-15%20%E4%B8%8A%E5%8D%8810.13.03.png
526 ms
7cjQA7USzGy7nGrQRLDr_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-10-15%20%E4%B8%8A%E5%8D%8810.20.02.png
727 ms
wMQb7zI8R72jFxu7a3g4_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-10-15%20%E4%B8%8A%E5%8D%8811.03.53.png
725 ms
lNUGoyd7RB2MOsx8i1cw_image.png
753 ms
4DhTbWRwSvujvsxZC2Z5_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-05-20%20%E4%B8%8B%E5%8D%8811.54.46.png
776 ms
NyZaTlSTDuH8v6DRzWAY_%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7%202015-05-19%20%E4%B8%8B%E5%8D%8811.34.22.png
694 ms
SIxIklSuRka61onbK0IK_IMG_8751.jpg
677 ms
HX5wrVYQ8WW8gkKhK8rQ_2015-05-11%2015.12.02.jpg
753 ms
line-tile.png
398 ms
noise.png
648 ms
code_bg.png
381 ms
all.js
92 ms
TeX-AMS_HTML.js
78 ms
widgets.js
79 ms
count.js
136 ms
atrk.js
136 ms
inpage_linkid.js
13 ms
rss.png
249 ms
__utm.gif
72 ms
__utm.gif
63 ms
MenuArrow-15.png
39 ms
embedviz
358 ms
139 ms
count-data.js
174 ms
atrk.gif
63 ms
jsMath2jax.js
34 ms
xd_arbiter.php
34 ms
xd_arbiter.php
56 ms
test.png
298 ms
combined_jquery.js
59 ms
global.js
83 ms
combined_li_tracking.js
90 ms
font-awesome.css
89 ms
combined_presentation.css
94 ms
combined_player_presentation.js
101 ms
combined_old_embed.js
98 ms
ga.js
155 ms
beacon.js
142 ms
d3js-taipei-meetup-1-638.jpg
261 ms
49546255
185 ms
lead-form
183 ms
1x1.gif
44 ms
logo_embed_20x20_v1.png
80 ms
fontawesome-webfont.woff
81 ms
js
150 ms
icons.svg
74 ms
top-controls-f5835eeebda5ed930cbc66bfeb9c068a.css
94 ms
__utm.gif
50 ms
__utm.gif
41 ms
nr-885.min.js
64 ms
01b3a24ca2
45 ms
common.js
41 ms
map.js
63 ms
util.js
108 ms
onion.js
106 ms
ping
57 ms
01b3a24ca2
69 ms
StaticMapService.GetMapImage
323 ms
openhand_8_8.cur
96 ms
stats.js
75 ms
controls.js
87 ms
infowindow.js
28 ms
ViewportInfoService.GetViewportInfo
86 ms
transparent.png
26 ms
vt
102 ms
mapslt
169 ms
mapslt
188 ms
css
156 ms
mapslt
175 ms
mapslt
172 ms
mapslt
183 ms
mapslt
174 ms
mapslt
163 ms
mapslt
166 ms
mapslt
164 ms
mapslt
163 ms
mapslt
180 ms
mapslt
201 ms
google4.png
101 ms
marker.js
87 ms
mapcnt6.png
60 ms
vt
49 ms
vt
39 ms
vt
46 ms
vt
45 ms
vt
51 ms
vt
75 ms
vt
69 ms
vt
98 ms
vt
70 ms
vt
73 ms
vt
105 ms
vt
115 ms
tmapctrl.png
29 ms
cb_scout5.png
45 ms
tmapctrl4.png
43 ms
imgs8.png
32 ms
vt
136 ms
AuthenticationService.Authenticate
25 ms
kuro.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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
kuro.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
kuro.tw 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
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 Kuro.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 Kuro.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.
kuro.tw
Open Graph description is not detected on the main page of Kuro. 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: