10.7 sec in total
1.1 sec
8.8 sec
845 ms
Click here to check amazing 100SHIKI content for Japan. Otherwise, check out these important facts you probably never knew about 100shiki.com
2000年1月20日に思いつきで始めたサイトですが、気がついたら18年ぐらい経っていてびっくりですね...。 これまで毎日更新してきましたが、本日、2018年8月31日をもって更新終了としたいと思います。突然ですが。いままで読んでいただいた皆様、ありがとうございました。 このサイトを通じていろいろなことがありました
Visit 100shiki.comWe analyzed 100shiki.com page load time and found that the first response time was 1.1 sec and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
100shiki.com performance score
1142 ms
616 ms
477 ms
1154 ms
835 ms
Our browser made a total of 179 requests to load all elements on the main page. We found that 22% of them (39 requests) were addressed to the original 100shiki.com, 8% (14 requests) were made to Facebook.com and 7% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain 100shiki.com.
Page size can be reduced by 883.5 kB (33%)
2.7 MB
1.8 MB
In fact, the total size of 100shiki.com main page is 2.7 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. 60% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 97.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. 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 97.5 kB or 83% of the original size.
Potential reduce by 222.1 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, 100SHIKI needs image optimization as it can save up to 222.1 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 283.1 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 283.1 kB or 64% of the original size.
Potential reduce by 280.9 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. 100shiki.com needs all CSS files to be minified and compressed as it can save up to 280.9 kB or 87% of the original size.
Number of requests can be reduced by 77 (44%)
175
98
The browser has sent 175 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 100SHIKI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.100shiki.com
1142 ms
style.css
616 ms
comment-style.css
477 ms
jquery.js
1154 ms
jquery-migrate.min.js
835 ms
scroll.js
801 ms
jscript.js
960 ms
comment.js
1120 ms
bookmark_button.js
684 ms
all.js
159 ms
widget.js
355 ms
wp-emoji-release.min.js
1166 ms
rakuten_widget.js
1186 ms
wp-embed.min.js
588 ms
conversion.js
19 ms
oct.js
57 ms
sdk.js
75 ms
button-only@2x.png
179 ms
image.phtml
309 ms
minilogov.gif
1107 ms
20531083655_ab72299d2b_s.jpg
191 ms
19683590624_9048a0f38c_s.jpg
207 ms
18831607960_5e33575e2e_s.jpg
212 ms
17189938888_8d9c18931e_s.jpg
199 ms
17191510439_55a6c04128_s.jpg
202 ms
17170277547_9afc381018_s.jpg
204 ms
17377403811_e33ccaa7d9_s.jpg
224 ms
17351777156_f0d50ac3ff_s.jpg
208 ms
16755209544_5ff8852299_s.jpg
223 ms
15726491777_674bddc8af_s.jpg
222 ms
15886449456_ebeb494a34_s.jpg
224 ms
15912258285_968e3cd754_s.jpg
226 ms
15289991664_2e257456a8_s.jpg
242 ms
20537465071_06444b1ef9_s.jpg
224 ms
20537460741_c7f93b0218_s.jpg
205 ms
19908402314_c8a3edc75a_s.jpg
222 ms
20537450101_cdc8d526b1_s.jpg
226 ms
search_button.gif
311 ms
29_logo.png
1944 ms
28_logo.png
1074 ms
27_logo.png
1307 ms
26_logo.png
754 ms
25_logo.png
2065 ms
24_logo.png
2094 ms
23_logo.png
1673 ms
22_logo.png
2792 ms
21_logo.png
3099 ms
20_logo.png
2772 ms
ex-cloud.gif
2261 ms
bebit_banner.gif
2420 ms
bizid_web.gif
2448 ms
20279973876_13f233ed03_s.jpg
220 ms
20279969466_292cfe31e2_s.jpg
208 ms
19685241333_90ac911d0d_s.jpg
206 ms
150 ms
header.gif
2756 ms
search_area.gif
2728 ms
rss_button.gif
2797 ms
twitter_button.gif
3089 ms
side.gif
3074 ms
xd_arbiter.php
229 ms
xd_arbiter.php
361 ms
btn.js
118 ms
280 ms
meta_bottom.gif
3069 ms
meta_top.gif
3102 ms
category_icon.gif
3117 ms
write_comment.gif
3370 ms
pager2.gif
3332 ms
pager1.gif
3347 ms
widget.css
181 ms
favicon.gif
258 ms
vertical.js
17 ms
head.gif
179 ms
load.gif
487 ms
foot.gif
249 ms
logo.gif
465 ms
reset.css
5 ms
entry-button.css
6 ms
imageul.phtml
431 ms
button-counter.gif
4 ms
644 ms
293 ms
292 ms
394 ms
385 ms
395 ms
540 ms
556 ms
610 ms
mtwidget04.affiliate.rakuten.co.jp
532 ms
footer.gif
2912 ms
copyright.gif
3020 ms
footer_line.gif
3020 ms
arrow4.gif
3163 ms
ga.js
5 ms
widgets.js
176 ms
__utm.gif
154 ms
segmentation.js
206 ms
fbds.js
166 ms
adsct
268 ms
adsct
203 ms
json
200 ms
button
50 ms
button
57 ms
button
69 ms
button
70 ms
button
67 ms
button
68 ms
button
67 ms
button
66 ms
button
85 ms
button
85 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
148 ms
27 ms
92 ms
button.css
93 ms
shared.js
92 ms
button.js
91 ms
cnt
363 ms
cnt
360 ms
like.php
78 ms
like.php
108 ms
like.php
113 ms
like.php
101 ms
like.php
102 ms
like.php
115 ms
like.php
136 ms
pocket_button.png
6 ms
vpc6VNjRPXV.js
308 ms
LVx-xkvaJ0b.png
273 ms
like.php
131 ms
like.php
136 ms
like.php
117 ms
like_box.php
132 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
88 ms
jTuqQ-OPDr6.css
133 ms
n370yiaI2G6.css
149 ms
_rx8naC75Dy.js
221 ms
x5F9OMjKyLw.js
220 ms
ICDbTSzjQEg.js
154 ms
TTCre3391I0.js
158 ms
pc_pcview_all.css
20 ms
front_merged.js
44 ms
mtwidget03.affiliate.ashiato.rakuten.co.jp
310 ms
getMWConf.php
412 ms
minilogov.gif
34 ms
loading.gif
14 ms
buttons.gif
37 ms
207284_200102886686919_6512483_n.jpg
199 ms
12646944_959189574163343_5183655306366744497_n.jpg
239 ms
12715503_1122133211171378_778573563840904077_n.jpg
312 ms
10258110_10152447602033277_9008958171720020563_n.jpg
347 ms
12219636_439774812885767_1324354530255839168_n.jpg
354 ms
12439130_1547991325517812_2097223068795657235_n.jpg
356 ms
12540917_1110554715643950_6952833343972313730_n.jpg
353 ms
wL6VQj7Ab77.png
75 ms
s7jcwEQH7Sx.png
66 ms
jot.html
33 ms
9784865102383.jpg
334 ms
a.gif
578 ms
9784798034713.jpg
522 ms
9784798034713.jpg
296 ms
I6-MnjEovm5.js
41 ms
vlXaquuXMrr.js
74 ms
script.phtml
2534 ms
beacon.html
36 ms
60 ms
pixel
24 ms
cs
295 ms
Pug
22 ms
set
302 ms
sd
4 ms
sync
7 ms
tap.php
14 ms
sync
332 ms
mapuser
150 ms
sync
207 ms
sync
263 ms
100shiki.com SEO score
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 100shiki.com 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 100shiki.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.
100shiki.com
Open Graph data is detected on the main page of 100SHIKI. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: