4.4 sec in total
421 ms
3.7 sec
273 ms
Welcome to kimi.com.tw homepage info - get ready to check Kimi best content for Taiwan right away, or after learning these important things about kimi.com.tw
崑崙在線,致力於為遊戲玩家提供最好的網頁遊戲和社區遊戲,打造網頁遊戲和社交遊戲第一品牌。
Visit kimi.com.twWe analyzed Kimi.com.tw page load time and found that the first response time was 421 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.
kimi.com.tw performance score
421 ms
446 ms
410 ms
669 ms
421 ms
Our browser made a total of 162 requests to load all elements on the main page. We found that 6% of them (9 requests) were addressed to the original Kimi.com.tw, 40% (65 requests) were made to Static-us.kimi.com.tw and 19% (30 requests) were made to Static.kimi.com.tw. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Static.kimi.com.tw.
Page size can be reduced by 135.4 kB (14%)
934.8 kB
799.4 kB
In fact, the total size of Kimi.com.tw main page is 934.8 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. 40% of websites need less resources to load. Images take 804.5 kB which makes up the majority of the site volume.
Potential reduce by 67.5 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 16.5 kB, which is 21% 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 67.5 kB or 85% of the original size.
Potential reduce by 57.7 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. Kimi images are well optimized though.
Potential reduce by 43 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 10.1 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. Kimi.com.tw needs all CSS files to be minified and compressed as it can save up to 10.1 kB or 78% of the original size.
Number of requests can be reduced by 30 (20%)
149
119
The browser has sent 149 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kimi. 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 as a result speed up the page load time.
kimi.com.tw
421 ms
446 ms
style.css
410 ms
jquery-1.5.1.min.js
669 ms
islogin.js
421 ms
lpjump.js
442 ms
jquery.min.js
444 ms
kl_sso.js
129 ms
kf.php
438 ms
kf.php
486 ms
kf.php
487 ms
conversion.js
17 ms
total.js
411 ms
pt.kimi.com.tw.js
417 ms
kf.php
455 ms
fbds.js
81 ms
20120924031423853.gif
225 ms
20160223045145600.jpg
101 ms
20141023102838645.jpg
400 ms
20140715110214483.jpg
405 ms
20130425121153796.jpg
404 ms
20140924091547545.jpg
416 ms
20140917123935350.jpg
419 ms
20160224051359774.jpg
433 ms
bg_line.jpg
225 ms
btn_login_fb.gif
224 ms
btn_fb.gif
223 ms
navline.gif
235 ms
ico_news.jpg
407 ms
ico_13_h.gif
411 ms
ico_13_n.gif
418 ms
ico_13_b.gif
424 ms
ico_13_.gif
437 ms
hazg.jpg
442 ms
logo_1mobile.gif
608 ms
logo_ml.gif
613 ms
logo_km.gif
623 ms
20160224050727380.jpg
177 ms
20160108055406413.jpg
178 ms
20151021012837408.jpg
140 ms
20150915042955196.jpg
177 ms
20151201060250828.jpg
178 ms
20150703025424445.jpg
176 ms
20150522065812220.jpg
220 ms
20150325050858531.jpg
243 ms
20150529013420864.jpg
241 ms
20130731061056590.jpg
290 ms
20121219031214365.jpg
244 ms
20160108110937163.jpg
222 ms
20151021025000641.jpg
235 ms
20150703025533411.jpg
243 ms
20150323065603259.gif
268 ms
20140530024216843.jpg
287 ms
20150915030040233.jpg
292 ms
20150828033253995.gif
287 ms
20150529014408843.gif
292 ms
20140430095919494.jpg
301 ms
20131129033609731.jpg
320 ms
20140227062602687.jpg
322 ms
20150225054209638.gif
317 ms
20141106055603495.gif
318 ms
20150324105423996.gif
321 ms
20141106062648642.jpg
334 ms
20140821124325823.gif
358 ms
20140326032415381.jpg
357 ms
20150522065228636.gif
358 ms
20141224030846592.jpg
358 ms
20141117105937283.gif
359 ms
20140818044010902.gif
366 ms
20150901063522998.jpg
381 ms
20151201070524349.jpg
383 ms
20130522125139902.jpg
385 ms
sdk.js
177 ms
login.php
422 ms
bgg.jpg
820 ms
bgg_head.jpg
848 ms
bg_nav_index.gif
647 ms
kf.php
455 ms
kf.php
464 ms
side_bg.jpg
786 ms
news_line.jpg
791 ms
bgg_tit_36.jpg
801 ms
bg_pic_178.gif
854 ms
btn_gry.gif
982 ms
btn_orange.gif
990 ms
bg_pic_360.jpg
1034 ms
like.php
86 ms
6 ms
20140508102302844.jpg
297 ms
vpc6VNjRPXV.js
309 ms
vpc6VNjRPXV.js
405 ms
LVx-xkvaJ0b.png
397 ms
20120928110011866.jpg
257 ms
20130911023618767.jpg
231 ms
20121009025207871.jpg
254 ms
20120928110123883.jpg
253 ms
20121009025255594.jpg
254 ms
20140912113923706.jpg
255 ms
20120924031423853.gif
216 ms
23 ms
20121009060217285.jpg
210 ms
xd_arbiter.php
130 ms
xd_arbiter.php
263 ms
20140715111446590.jpg
219 ms
20140730025228203.jpg
215 ms
20130307114240429.jpg
215 ms
20131111054754117.jpg
218 ms
20120928110253108.jpg
218 ms
20130705104519283.jpg
204 ms
20130425121153796.jpg
198 ms
20130507084937600.jpg
195 ms
20121009060828566.jpg
195 ms
20150216034402537.jpg
202 ms
20130717123410676.jpg
202 ms
20141023102838645.jpg
116 ms
20130425121153796.jpg
125 ms
20140715110214483.jpg
124 ms
20140924091547545.jpg
114 ms
20140917123935350.jpg
120 ms
kf_ivt.php
235 ms
off_root1373883315.gif
262 ms
20160224051359774.jpg
175 ms
btn_login.gif
632 ms
bgg_nav_231.gif
642 ms
20130717103933539.jpg
48 ms
on_root1373535534.jpg
442 ms
20130717104007488.jpg
80 ms
on_root1373535739.jpg
619 ms
ga.js
36 ms
53 ms
26 ms
isLogin.php
231 ms
right.js
226 ms
__utm.gif
24 ms
37 ms
page.php
80 ms
Q9XBNpmpoXR.css
42 ms
_rx8naC75Dy.js
78 ms
t-KLv3gqZy0.js
105 ms
uLtKx7ldlvR.js
223 ms
style.css
205 ms
20160217095306.jpg
875 ms
lpjump.js
210 ms
12650994_817764798333286_7807462518397492661_n.png
381 ms
417964_372501966192907_1999222476_n.jpg
424 ms
12742734_994887170590665_8915123551913761934_n.jpg
461 ms
10478137_954491431279935_8455769710150148464_n.jpg
535 ms
12241735_1107514795940484_8467951915197209154_n.jpg
492 ms
10557231_919219508095173_5574438948763375419_n.jpg
498 ms
941098_1689933654577343_2606562270107450618_n.jpg
499 ms
11953220_898467663533644_8275645693843891676_n.jpg
500 ms
11392921_1042811842414418_8760707520161154551_n.jpg
532 ms
1000364_948652355151336_8888702149520367348_n.jpg
539 ms
549238_418499291577597_616443628_n.jpg
539 ms
10306466_530588743713771_7496899878075212760_n.jpg
540 ms
wL6VQj7Ab77.png
54 ms
CSXXCvknpgK.png
55 ms
R9a_DtVRZgv.js
45 ms
cUDgRFxaoIk.js
40 ms
0JBr1QHp8Gi.js
44 ms
kDOzhTr2W91.js
39 ms
3 ms
kimi.com.tw SEO score
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kimi.com.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 Kimi.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.
kimi.com.tw
Open Graph description is not detected on the main page of Kimi. 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: