24.3 sec in total
936 ms
22.3 sec
1.1 sec
Visit tokrin.com now to see the best up-to-date Tokrin content for Taiwan and also check out these interesting facts you probably never knew about tokrin.com
とっくりん:テイルズオブやファイナルファンタジーなどのゲーム最新情報、アニメ、漫画など気になったことを取り上げていくブログです。
Visit tokrin.comWe analyzed Tokrin.com page load time and found that the first response time was 936 ms and then it took 23.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
tokrin.com performance score
936 ms
516 ms
346 ms
49 ms
560 ms
Our browser made a total of 153 requests to load all elements on the main page. We found that 3% of them (5 requests) were addressed to the original Tokrin.com, 31% (48 requests) were made to Livedoor.blogimg.jp and 13% (20 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Spnet33.i-mobile.co.jp.
Page size can be reduced by 474.1 kB (25%)
1.9 MB
1.4 MB
In fact, the total size of Tokrin.com main page is 1.9 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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 177.2 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 34.6 kB, which is 17% 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 177.2 kB or 87% of the original size.
Potential reduce by 22.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. Tokrin images are well optimized though.
Potential reduce by 138.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 138.5 kB or 55% of the original size.
Potential reduce by 135.8 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. Tokrin.com needs all CSS files to be minified and compressed as it can save up to 135.8 kB or 91% of the original size.
Number of requests can be reduced by 43 (30%)
144
101
The browser has sent 144 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tokrin. 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 12 to 1 for CSS and as a result speed up the page load time.
tokrin.com
936 ms
template.css
516 ms
site.css
346 ms
jquery.min.js
49 ms
c2.js
560 ms
smartphone.js
563 ms
ad.js
354 ms
popular_articles_with_image_plugin.js
719 ms
ads.js
50 ms
widgets.js
18 ms
rakuten_widget.js
920 ms
ldblog_categorize_foldable_plugin.js
306 ms
recent_comments.js
325 ms
link-enhancer-common.js
218 ms
8dfe8d5a.gif
330 ms
b6900f55.jpg
485 ms
41dzKgGjmeL._SX200_.jpg
27 ms
613NyxkvxfL._SX200_.jpg
27 ms
a87a9aa1.jpg
482 ms
4a5d2224.jpg
506 ms
56a5affd.jpg
673 ms
92bd4612.png
650 ms
b6900f55.jpg
504 ms
a87a9aa1.jpg
511 ms
4a5d2224.jpg
684 ms
56a5affd.jpg
868 ms
64bf166f.jpg
812 ms
ac57930f.jpg
1300 ms
8caf859d.jpg
1394 ms
8c5f7608.jpg
1294 ms
ebcf0c54-s.jpg
1397 ms
424d8af6.png
971 ms
2bb0cbd3.jpg
1390 ms
c4cd26fc.jpg
1391 ms
33c6c09c-s.jpg
1397 ms
d382c980-s.jpg
1398 ms
905b4b80.jpg
1905 ms
a1ca3db3-s.jpg
1714 ms
59db2bb4.jpg
1622 ms
be6d3f7f.jpg
1726 ms
2cea3f1d.jpg
1702 ms
d1d756a0.jpg
1620 ms
4b5ca138.jpg
1886 ms
e36108d0.jpg
1741 ms
eb1321ad.jpg
1865 ms
db9d0770.jpg
2038 ms
f8a73280-s.jpg
2108 ms
ed09933e.jpg
1900 ms
00b8ca2f.jpg
2200 ms
f14e4bc9.jpg
2103 ms
d69b453d-s.jpg
2113 ms
30f6379e.jpg
2287 ms
b654c68d.jpg
2685 ms
3691e0a6.jpg
2562 ms
d30186eb.jpg
2803 ms
cb3d027a.jpg
2563 ms
c
315 ms
popular_articles.json
405 ms
adcore.js
20 ms
adcore_pc.js
44 ms
adcore_pc_inline.js
18 ms
ad_spot.aspx
19710 ms
8dfe8d5a.gif
41 ms
e97aaed3.jpg
2252 ms
fb56187a.jpg
2146 ms
7e97f3cb.jpg
2301 ms
8caf859d.jpg
380 ms
4b5ca138.jpg
373 ms
00b8ca2f.jpg
371 ms
64bf166f.jpg
803 ms
be6d3f7f.jpg
799 ms
8c5f7608.jpg
803 ms
f8a73280-s.jpg
799 ms
2cea3f1d.jpg
795 ms
ed09933e.jpg
799 ms
5cf851cb.jpg
1029 ms
b0cd6002.jpg
2168 ms
66a37d26.jpg
2172 ms
mtwidget04.affiliate.rakuten.co.jp
989 ms
ad_spot.aspx
623 ms
recent_comments.json
620 ms
htmlbanner
1079 ms
htmlbanner
1118 ms
ad_spot.aspx
20143 ms
24b95094.jpg
2178 ms
u.js
581 ms
timeline.0eae788bc4fdbe9cd3e72dca3bc26358.js
44 ms
tweet.00c2bb81d4f3f312a9a021c715a1c9dc.js
54 ms
button.71000885400e222c3c0eec823f8f93f0.js
55 ms
64081f27.gif
2003 ms
syndication
506 ms
710112200556302336
585 ms
tweets.json
527 ms
syndication
519 ms
tweet_button.fd774b599f565016d763dd860cb31c79.ja.html
172 ms
008b0273.jpg
2854 ms
6b7e7c82.jpg
1687 ms
9a3a7c17.gif
1682 ms
style.css
257 ms
ad_creative.ashx
354 ms
6177069c.gif
1623 ms
00e88e51.gif
1640 ms
tweet.f7130f11be9c2719286897ede16853b9.light.ltr.css
4 ms
tweet.f7130f11be9c2719286897ede16853b9.light.ltr.css
8 ms
GbmW-_ag_normal.jpg
202 ms
syndication_bundle_v1_54a085602387c0466bf99924918f2119d047889b.css
58 ms
syndication_bundle_v1_54a085602387c0466bf99924918f2119d047889b.css
54 ms
timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css
22 ms
timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css
23 ms
CfhhtbCUAAAxv0W.jpg:small
278 ms
CfhN-BsUUAEsLaj.jpg:small
246 ms
CffVSGVWsAAUkEF.jpg:small
263 ms
CfeCMQtUYAA0Mq6.jpg:small
213 ms
Cfctb7lUEAA3GjG.jpg:small
222 ms
CfcL0puUIAA7RNG.jpg:small
232 ms
Cfb_EJzUIAAEOOy.jpg:small
241 ms
CfY4oxMUsAA65yC.jpg:small
243 ms
CfXkQRPUsAAHR9G.png:small
262 ms
CfXIojZUYAAyytW.jpg:small
310 ms
CfW6UdxUYAEFP7L.jpg:small
274 ms
CfW37brUMAUM6Tn.jpg:small
303 ms
CfSZi9rUIAEndKe.jpg:small
302 ms
CfRsbQMUYAAgjzZ.jpg:small
301 ms
CfRlubfUYAAdyPE.jpg:small
310 ms
CfOlUF2UsAATcOr.jpg:small
309 ms
CfNRRKFUUAAP-Wq.jpg:small
325 ms
CfMdq4PUYAAj-Il.jpg:small
325 ms
CfJbJYXVIAAP6Ev.jpg:small
328 ms
syndication_bundle_v1_54a085602387c0466bf99924918f2119d047889b.css
21 ms
syndication_bundle_v1_54a085602387c0466bf99924918f2119d047889b.css
32 ms
pc_pcview_all.css
25 ms
front_merged.js
57 ms
mtwidget03.affiliate.ashiato.rakuten.co.jp
719 ms
getMWConf.php
295 ms
loading.gif
7 ms
buttons.gif
17 ms
19.gif
524 ms
b2.bin
673 ms
jot.html
3 ms
imgrc0067482459.jpg
266 ms
a.gif
497 ms
mochimugi1a.jpg
232 ms
2015-kamihanki.jpg
233 ms
e114677h_l.jpg
231 ms
imgrc0063155095.jpg
241 ms
9000009984074.jpg
273 ms
64081f27.gif
29 ms
9a3a7c17.gif
47 ms
6177069c.gif
20 ms
00e88e51.gif
43 ms
imgrc0090521616.jpg
49 ms
mc10-th300a.jpg
78 ms
RestoreXidToMediaStorage.html
223 ms
tokrin.com SEO score
ZH
&L
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tokrin.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed language. Our system also found out that Tokrin.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.
tokrin.com
Open Graph data is detected on the main page of Tokrin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: