10.1 sec in total
527 ms
6.8 sec
2.8 sec
Click here to check amazing Moznion Hatenadiary content for Japan. Otherwise, check out these important facts you probably never knew about moznion.hatenadiary.com
ギジュツ的な事をメーンで書く予定です
Visit moznion.hatenadiary.comWe analyzed Moznion.hatenadiary.com page load time and found that the first response time was 527 ms 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.
moznion.hatenadiary.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value4.0 s
50/100
25%
Value24.5 s
0/100
10%
Value13,130 ms
0/100
30%
Value0.025
100/100
15%
Value45.9 s
0/100
10%
527 ms
860 ms
547 ms
70 ms
779 ms
Our browser made a total of 226 requests to load all elements on the main page. We found that 1% of them (3 requests) were addressed to the original Moznion.hatenadiary.com, 8% (18 requests) were made to Cdn1.www.st-hatena.com and 7% (15 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Cdn-ak.f.st-hatena.com.
Page size can be reduced by 4.5 MB (69%)
6.6 MB
2.0 MB
In fact, the total size of Moznion.hatenadiary.com main page is 6.6 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. Javascripts take 5.0 MB which makes up the majority of the site volume.
Potential reduce by 243.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 243.5 kB or 73% of the original size.
Potential reduce by 175.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, Moznion Hatenadiary needs image optimization as it can save up to 175.0 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 4.0 MB
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 4.0 MB or 81% of the original size.
Potential reduce by 87.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. Moznion.hatenadiary.com needs all CSS files to be minified and compressed as it can save up to 87.9 kB or 83% of the original size.
Number of requests can be reduced by 135 (65%)
209
74
The browser has sent 209 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Moznion Hatenadiary. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 75 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
moznion.hatenadiary.com
527 ms
blog.css
860 ms
54f814dbf01b442019e125505392b36a5ca45ddc
547 ms
widgets.js
70 ms
hatena_afc_ydn-compiled.js
779 ms
comment-widget.js
684 ms
hatena_dfp2.js
491 ms
HatenaStar.js
1368 ms
widgets.js
87 ms
plusone.js
122 ms
bookmark_button.js
824 ms
react-with-addons.min.js
101 ms
react-dom.min.js
106 ms
jquery-1.9.1.min.js
83 ms
jquery-ui.1.10.0.custom.min.js
82 ms
jquery.flot.0.8.3.js
79 ms
jquery.flot.time.0.8.3.js
81 ms
hatenablog.js
2048 ms
texts-ja.js
723 ms
api.js
101 ms
css
64 ms
analytics.js
8 ms
20160307122343.png
2120 ms
profile.gif
341 ms
button-only.gif
186 ms
20160222000426.png
1570 ms
20160214162920.png
1073 ms
header.png
180 ms
leqv3v-yTsJNC7nFznSMqVkQc6VGVFSmCnC_l7QZG60.woff
64 ms
mrl8jkM18OlOQN8JLgasDxM0YzuT7MdOe03otPbuUS0.woff
112 ms
show_ads.js
20 ms
show_ads_impl.js
69 ms
ads
317 ms
osd.js
41 ms
ads
269 ms
ads
124 ms
next.png
382 ms
search.png
384 ms
audience
432 ms
jstag
92 ms
gpt.js
67 ms
cb=gapi.loaded_0
44 ms
pubads_impl_82.js
14 ms
470 ms
458 ms
457 ms
457 ms
650 ms
618 ms
651 ms
container.html
10 ms
blogs
209 ms
recaptcha__en.js
147 ms
sdk.js
85 ms
profile.gif
254 ms
cdn-ak.favicon.st-hatena.com
421 ms
entry.count.image
458 ms
comment-widget.css
419 ms
bookmark.show
259 ms
entry.count
421 ms
tweet.2c548e167cf5bdb0bd941e41896f257d.js
68 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
126 ms
user.segment.json
429 ms
118 ms
segmentation.js
120 ms
hatena_bigmining.js
116 ms
show.json
1185 ms
archive_module
231 ms
notices.count.json
1018 ms
comment.gif
368 ms
entries.json
617 ms
68 ms
hatena-star-add-button.png
186 ms
97 ms
69 ms
351 ms
dfp.config.json
337 ms
syndication
260 ms
tweets.json
253 ms
tweets.json
248 ms
cnt
191 ms
redirect.js
90 ms
globalheader.css
189 ms
widgets.js
61 ms
hatenablog.js
1526 ms
texts-ja.js
247 ms
api.js
59 ms
cnt
385 ms
cnt
382 ms
xd_arbiter.php
127 ms
xd_arbiter.php
208 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
101 ms
reset.css
114 ms
entry-button.css
115 ms
bbtn-l_v3.png
51 ms
entry.count
571 ms
share-twitter@2x.png
168 ms
share-facebook@2x.png
326 ms
share-bookmark@2x.png
321 ms
proxy.jpg
247 ms
tweet.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
39 ms
tweet.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
37 ms
vk3saipas44bso1hon3n_normal.png
73 ms
Lh5Iipt-_normal.jpeg
59 ms
wwXJk6kk_normal.png
60 ms
ads
348 ms
star.gif
158 ms
profile.gif
15 ms
profile.gif
14 ms
profile.gif
195 ms
profile.gif
13 ms
profile.gif
15 ms
profile.gif
14 ms
profile.gif
14 ms
profile.gif
18 ms
profile.gif
478 ms
profile.gif
24 ms
profile.gif
19 ms
profile.gif
19 ms
profile.gif
381 ms
profile.gif
659 ms
profile.gif
25 ms
profile.gif
443 ms
jot.html
7 ms
ajs.php
386 ms
ads
287 ms
expansion_embed.js
30 ms
ads
228 ms
adj
124 ms
adServerESI.aspx
117 ms
beacon
116 ms
adsbygoogle.js
14 ms
lg.php
192 ms
ca-pub-5973519624968530.js
82 ms
zrt_lookup.html
43 ms
intel-vid4.png
56 ms
lidar.js
19 ms
sbhK2lTE.js
18 ms
pixel
50 ms
push
91 ms
skeleton.gif
119 ms
cTrvNaRi.html
10 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
22 ms
pixel
59 ms
setuid
88 ms
ads
246 ms
adj
50 ms
adServerESI.aspx
47 ms
beacon
24 ms
skeleton.gif
21 ms
intel-vid3.png
17 ms
pixel
54 ms
push
14 ms
sd
10 ms
adex.ashx
244 ms
131 ms
138 ms
alternatead-300x250-red.html
31 ms
sd
21 ms
setuid
94 ms
pixel
87 ms
ad
543 ms
notices.count.json
324 ms
dropdown@2x.png
183 ms
init
181 ms
adj
44 ms
adServerESI.aspx
27 ms
beacon
19 ms
pixel
35 ms
push
18 ms
pixel
26 ms
24 ms
pixel
67 ms
pixel
69 ms
setuid
134 ms
pixel
133 ms
sd
129 ms
fastbutton
110 ms
fastbutton
64 ms
fastbutton
113 ms
fastbutton
147 ms
fastbutton
165 ms
fastbutton
139 ms
fastbutton
118 ms
hatena-follow-button.png
162 ms
blogicon-regular.woff
298 ms
info
218 ms
cb=gapi.loaded_0
25 ms
cb=gapi.loaded_1
25 ms
grlryt2bdKIyfMSOhzd1eA.woff
67 ms
cb=gapi.loaded_0
43 ms
cb=gapi.loaded_1
41 ms
cb=gapi.loaded_0
12 ms
cb=gapi.loaded_1
11 ms
45855_banner.png
581 ms
dmp
329 ms
gtm.js
19 ms
beacon.html
47 ms
bookmark.show
199 ms
entry.count
183 ms
entry.count.image
223 ms
tdim-0.11.2.js
23 ms
sd
46 ms
pixel
19 ms
cs
385 ms
setuid
22 ms
Pug
22 ms
set
300 ms
sync
301 ms
segment
297 ms
share_button.php
119 ms
sync
163 ms
entry.count
185 ms
share_button.php
198 ms
share_button.php
154 ms
share_button.php
254 ms
share_button.php
241 ms
wy1X4hBW7e7.js
30 ms
share_button.php
205 ms
LVx-xkvaJ0b.png
15 ms
share_button.php
235 ms
mapuser
196 ms
sync
195 ms
pageviews
21 ms
sync
236 ms
tap.php
300 ms
moznion.hatenadiary.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
moznion.hatenadiary.com 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
Page has valid source maps
moznion.hatenadiary.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Moznion.hatenadiary.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 Moznion.hatenadiary.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.
moznion.hatenadiary.com
Open Graph data is detected on the main page of Moznion Hatenadiary. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: