5.2 sec in total
513 ms
3.9 sec
706 ms
Visit horikawad.hatenadiary.com now to see the best up-to-date Horikawad Hatenadiary content for Japan and also check out these interesting facts you probably never knew about horikawad.hatenadiary.com
クマムシ博士のブログ
Visit horikawad.hatenadiary.comWe analyzed Horikawad.hatenadiary.com page load time and found that the first response time was 513 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
horikawad.hatenadiary.com performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value2.7 s
84/100
25%
Value16.0 s
0/100
10%
Value2,190 ms
6/100
30%
Value0.004
100/100
15%
Value28.9 s
0/100
10%
513 ms
974 ms
544 ms
516 ms
317 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Horikawad.hatenadiary.com, 11% (11 requests) were made to Cdn1.www.st-hatena.com and 7% (7 requests) were made to Blog.st-hatena.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Blog.st-hatena.com.
Page size can be reduced by 2.7 MB (69%)
4.0 MB
1.2 MB
In fact, the total size of Horikawad.hatenadiary.com main page is 4.0 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. Javascripts take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 82.9 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 11.6 kB, which is 11% 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 82.9 kB or 81% of the original size.
Potential reduce by 32.9 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. Horikawad Hatenadiary images are well optimized though.
Potential reduce by 2.3 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 2.3 MB or 81% of the original size.
Potential reduce by 286.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. Horikawad.hatenadiary.com needs all CSS files to be minified and compressed as it can save up to 286.9 kB or 83% of the original size.
Number of requests can be reduced by 49 (52%)
95
46
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Horikawad 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 29 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
horikawad.hatenadiary.com
513 ms
blog.css
974 ms
f3db0947c3160541d1fbd9c7d74a763e1f53dac7
544 ms
line-button.js
516 ms
widget.js
317 ms
HatenaStar.js
1327 ms
widgets.js
141 ms
plusone.js
99 ms
bookmark_button.js
668 ms
react-with-addons.min.js
62 ms
react-dom.min.js
61 ms
jquery-1.9.1.min.js
224 ms
jquery-ui.1.10.0.custom.min.js
225 ms
jquery.flot.0.8.3.js
222 ms
jquery.flot.time.0.8.3.js
222 ms
hatenablog.js
1865 ms
texts-ja.js
681 ms
api.js
73 ms
counter.js
576 ms
css
26 ms
analytics.js
18 ms
20160223214502.jpg
430 ms
button-only.gif
215 ms
20150502111938.jpg
1507 ms
profile.gif
382 ms
8386679086_e72be4c6bd_m.jpg
78 ms
20160223212154.jpg
1505 ms
20150413175315.jpg
1213 ms
20160112160752.jpg
808 ms
20160112162319.jpg
953 ms
20140201162344.jpg
107 ms
20140201162736.jpg
105 ms
20140201163031.jpg
102 ms
collect
10 ms
collect
113 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
53 ms
00236.gif
35 ms
jSRN_P_7sFA
93 ms
widget-hatenadiary.css
193 ms
favicon.gif
179 ms
00128.gif
7 ms
www-embed-player-vflfNyN_r.css
26 ms
www-embed-player.js
44 ms
00391.gif
425 ms
00928.gif
10 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
9 ms
ad_status.js
55 ms
00114.gif
46 ms
00163.gif
41 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
52 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
55 ms
collect
136 ms
cb=gapi.loaded_0
89 ms
394 ms
409 ms
417 ms
reset.css
11 ms
entry-button.css
10 ms
bbtn-l_v3.png
13 ms
blogs
179 ms
recaptcha__en.js
29 ms
sdk.js
69 ms
102
213 ms
327 ms
xd_arbiter.php
66 ms
xd_arbiter.php
156 ms
globalheader.css
159 ms
json
296 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
95 ms
show.json
788 ms
archive_module
295 ms
notices.count.json
1109 ms
comment.gif
314 ms
entries.json
427 ms
hatena-star-add-button.png
230 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
147 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
175 ms
notices.count.json
963 ms
init
236 ms
dropdown@2x.png
333 ms
share_button.php
102 ms
share_button.php
149 ms
share_button.php
158 ms
wy1X4hBW7e7.js
156 ms
LVx-xkvaJ0b.png
212 ms
blogicon-regular.woff
298 ms
info
222 ms
hatena-follow-button.png
162 ms
star.gif
190 ms
profile.gif
526 ms
profile.gif
36 ms
profile.gif
35 ms
profile.gif
206 ms
profile.gif
354 ms
profile.gif
33 ms
profile.gif
582 ms
profile.gif
364 ms
profile.gif
337 ms
profile.gif
206 ms
jSRN_P_7sFA
86 ms
ad_status.js
8 ms
jot.html
38 ms
horikawad.hatenadiary.com accessibility score
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
Image elements do not have [alt] attributes
horikawad.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
horikawad.hatenadiary.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Horikawad.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 Horikawad.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.
horikawad.hatenadiary.com
Open Graph data is detected on the main page of Horikawad Hatenadiary. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: