5 sec in total
955 ms
3.6 sec
390 ms
Click here to check amazing Occugaku content for Japan. Otherwise, check out these important facts you probably never knew about occugaku.com
怖い話の投稿型のまとめサイト。怖い話を厳選し短編、中編、長編と長さごとやカテゴリーごとに分類ししました。意味がわかると怖い話、都市伝説、不思議な話、怪談、ホラーなどここでしか読めない話も多数
Visit occugaku.comWe analyzed Occugaku.com page load time and found that the first response time was 955 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.
occugaku.com performance score
955 ms
324 ms
489 ms
326 ms
327 ms
Our browser made a total of 169 requests to load all elements on the main page. We found that 2% of them (4 requests) were addressed to the original Occugaku.com, 18% (30 requests) were made to Cdn.b.st-hatena.com and 8% (14 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (955 ms) belongs to the original domain Occugaku.com.
Page size can be reduced by 256.0 kB (58%)
437.7 kB
181.7 kB
In fact, the total size of Occugaku.com main page is 437.7 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. 75% 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. HTML takes 134.0 kB which makes up the majority of the site volume.
Potential reduce by 114.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. 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 114.2 kB or 85% of the original size.
Potential reduce by 18.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. Obviously, Occugaku needs image optimization as it can save up to 18.0 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 69.2 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 69.2 kB or 54% of the original size.
Potential reduce by 54.6 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. Occugaku.com needs all CSS files to be minified and compressed as it can save up to 54.6 kB or 83% of the original size.
Number of requests can be reduced by 102 (62%)
164
62
The browser has sent 164 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Occugaku. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
occugaku.com
955 ms
template.css
324 ms
site.css
489 ms
c2.js
326 ms
smartphone.js
327 ms
ad.js
357 ms
blogroll.js
583 ms
default.css
396 ms
show_ads.js
5 ms
bookmark_button.js
323 ms
share.js
293 ms
widgets.js
21 ms
plusone.js
63 ms
ldblog_monthly_plugin.js
296 ms
ldblog_categorize_foldable_plugin.js
298 ms
ga.js
20 ms
b5b0727d.jpg
824 ms
button-only.gif
167 ms
43nw2jcA_bigger.jpeg
6 ms
c
337 ms
__utm.gif
13 ms
roll_data
409 ms
roll_data
165 ms
ca-pub-4767767690169985.js
55 ms
zrt_lookup.html
50 ms
show_ads_impl.js
65 ms
category.gif
210 ms
posted.gif
286 ms
comment.gif
210 ms
share_button.html
325 ms
225 ms
cb=gapi.loaded_0
51 ms
cb=gapi.loaded_1
88 ms
fastbutton
150 ms
ads
255 ms
osd.js
38 ms
like.php
104 ms
share_button.html
355 ms
postmessageRelay
95 ms
1.gif
161 ms
osusumeodekake.jpg
347 ms
blank.gif
347 ms
fastbutton
80 ms
cb=gapi.loaded_0
38 ms
cb=gapi.loaded_1
40 ms
tag.gif
200 ms
like.php
60 ms
share_button.html
316 ms
fastbutton
82 ms
vpc6VNjRPXV.js
539 ms
LVx-xkvaJ0b.png
598 ms
reset.css
56 ms
entry-button.css
55 ms
api.js
53 ms
core:rpc:shindig.random:shindig.sha1.js
65 ms
2536007149-postmessagerelay.js
63 ms
like.php
88 ms
share_button.html
312 ms
fastbutton
72 ms
button-counter.gif
39 ms
share_button.html
341 ms
like.php
69 ms
bt_check_6.png
376 ms
css
90 ms
m_js_controller.js
66 ms
abg.js
66 ms
fastbutton
122 ms
shimarisu.jpg
409 ms
blank.gif
234 ms
like.php
101 ms
share_button.html
253 ms
fastbutton
99 ms
favicon
113 ms
nessie_icon_tiamat_white.png
63 ms
s
71 ms
googlelogo_color_112x36dp.png
92 ms
x_button_blue2.png
58 ms
like.php
48 ms
272 ms
402 ms
449 ms
408 ms
468 ms
270 ms
00000.gif
49 ms
00000.gif
49 ms
00000.gif
47 ms
share_button.html
212 ms
00000.gif
32 ms
fastbutton
88 ms
00000.gif
10 ms
00000.gif
11 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
10 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
88 ms
like.php
81 ms
share_button.html
303 ms
fastbutton
76 ms
00000.gif
21 ms
like.php
51 ms
00000.gif
21 ms
00000.gif
21 ms
ads
190 ms
ads
247 ms
00000.gif
38 ms
01f80472fddc10ec74347f896520e923
574 ms
00000.gif
11 ms
likebox.php
54 ms
00000.gif
5 ms
00000.gif
5 ms
roNeOY-tz5Y.css
87 ms
UHhaxo8Cs3k.css
159 ms
_rx8naC75Dy.js
362 ms
x5F9OMjKyLw.js
377 ms
ICDbTSzjQEg.js
220 ms
TTCre3391I0.js
221 ms
00000.gif
4 ms
00001.gif
7 ms
css
18 ms
00000.gif
20 ms
230 ms
favicon
88 ms
ligo_circle_02_thick_white.png
21 ms
00000.gif
19 ms
js
118 ms
00000.gif
24 ms
00000.gif
17 ms
00000.gif
15 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
24 ms
00000.gif
9 ms
00000.gif
5 ms
img
57 ms
pixel
13 ms
ck-confirm
139 ms
00000.gif
5 ms
Q116_Wu_Com_Awareness_V2_D_160x600_EN_US.jpg
101 ms
lidar.js
18 ms
sbhK2lTE.js
31 ms
00000.gif
42 ms
00000.gif
54 ms
cTrvNaRi.html
51 ms
00000.gif
48 ms
1391863_567725833264479_956896403_n.jpg
296 ms
11219335_1659674697608965_3725858880548810273_n.jpg
359 ms
10584038_1519407391689977_2856140171982457487_n.jpg
427 ms
11825084_1609154832669986_5991745289058229740_n.jpg
493 ms
wL6VQj7Ab77.png
75 ms
s7jcwEQH7Sx.png
74 ms
00000.gif
10 ms
00000.gif
7 ms
00000.gif
5 ms
ninja_onetag.css
380 ms
trac.js
364 ms
activeview
14 ms
00000.gif
5 ms
dot_w.gif
162 ms
I6-MnjEovm5.js
79 ms
vlXaquuXMrr.js
78 ms
__utm.gif
5 ms
activeview
17 ms
popular_articles.json
359 ms
u.js
324 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
31 ms
like.php
70 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
40 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
46 ms
vpc6VNjRPXV.js
202 ms
cookiesync
372 ms
jot.html
2 ms
activeview
14 ms
occugaku.com SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Occugaku.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Occugaku.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.
occugaku.com
Open Graph data is detected on the main page of Occugaku. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: