4.7 sec in total
349 ms
3.9 sec
490 ms
Click here to check amazing Hotcake Hatenadiary content for Japan. Otherwise, check out these important facts you probably never knew about hotcake.hatenadiary.jp
すてきなこいびとはちみつとかしてゆく
Visit hotcake.hatenadiary.jpWe analyzed Hotcake.hatenadiary.jp page load time and found that the first response time was 349 ms and then it took 4.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.
hotcake.hatenadiary.jp performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value2.9 s
81/100
25%
Value16.2 s
0/100
10%
Value3,700 ms
1/100
30%
Value0
100/100
15%
Value28.8 s
0/100
10%
349 ms
799 ms
504 ms
671 ms
939 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 3% of them (4 requests) were addressed to the original Hotcake.hatenadiary.jp, 15% (19 requests) were made to Blog.st-hatena.com and 7% (8 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 Blog.st-hatena.com.
Page size can be reduced by 2.6 MB (66%)
3.9 MB
1.3 MB
In fact, the total size of Hotcake.hatenadiary.jp main page is 3.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. Javascripts take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 59.0 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 10.8 kB, which is 15% 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 59.0 kB or 83% of the original size.
Potential reduce by 7.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. Hotcake Hatenadiary images are well optimized though.
Potential reduce by 2.4 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.4 MB or 79% of the original size.
Potential reduce by 118.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. Hotcake.hatenadiary.jp needs all CSS files to be minified and compressed as it can save up to 118.8 kB or 84% of the original size.
Number of requests can be reduced by 61 (55%)
111
50
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hotcake 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 41 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
hotcake.hatenadiary.jp
349 ms
blog.css
799 ms
fb5b04e69f96d6f228502f276ba89509b759d0fe
504 ms
hatena_afc_ydn-compiled.js
671 ms
hatena_dfp2.js
939 ms
HatenaStar.js
1547 ms
widgets.js
52 ms
plusone.js
81 ms
bookmark_button.js
664 ms
react-with-addons.min.js
57 ms
react-dom.min.js
61 ms
jquery-1.9.1.min.js
218 ms
jquery-ui.1.10.0.custom.min.js
218 ms
jquery.flot.0.8.3.js
211 ms
jquery.flot.time.0.8.3.js
217 ms
hatenablog.js
2118 ms
texts-ja.js
786 ms
api.js
59 ms
analytics.js
22 ms
button-only.gif
171 ms
profile.gif
690 ms
bg.gif
149 ms
profile.gif
810 ms
donut.png
454 ms
title-h1-bg.png
295 ms
kira1.png
442 ms
date.png
445 ms
kira2.png
448 ms
embed
1741 ms
baloon.png
431 ms
show_ads.js
9 ms
show_ads_impl.js
46 ms
ads
208 ms
12798196_615506825273359_1635182367_n.jpg
864 ms
osd.js
34 ms
12819091_1706614852886035_2125913731_n.jpg
1158 ms
embed
477 ms
side-list.png
250 ms
side-line.png
254 ms
search.png
255 ms
audience
306 ms
jstag
17 ms
gpt.js
5 ms
title-bg.gif
239 ms
kira3.png
245 ms
pubads_impl_82.js
22 ms
container.html
7 ms
dfp.config.json
188 ms
cb=gapi.loaded_0
46 ms
embed.css
152 ms
http%3A%2F%2Fmika-rika-free.jp%2Fwp-content%2Fthemes%2Fmikarika%2Fimages%2Fcommon%2Fmr_share.png
1055 ms
favicon.ico
1121 ms
entry.count.image
767 ms
293 ms
494 ms
652 ms
487 ms
00990.gif
437 ms
reset.css
179 ms
entry-button.css
177 ms
ads
275 ms
blogs
208 ms
recaptcha__en.js
37 ms
sdk.js
86 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
21 ms
show.json
1211 ms
archive_module
193 ms
recent_comments
324 ms
notices.count.json
1057 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
30 ms
bbtn-l_v3.png
27 ms
142 ms
xd_arbiter.php
86 ms
xd_arbiter.php
143 ms
globalheader.css
156 ms
api.js
15 ms
ajs.php
426 ms
ads
220 ms
cdn-ak.favicon.st-hatena.com
874 ms
entry.count.image
202 ms
147 ms
http%3A%2F%2Flyricalschool.com%2Fwp%2Fwp-content%2Fuploads%2F2016%2F02%2F0306.jpg
888 ms
jot.html
2 ms
profile.gif
684 ms
show.json
949 ms
profile.gif
191 ms
notices.count.json
818 ms
init
205 ms
dropdown@2x.png
150 ms
ajs.php
343 ms
fastbutton
61 ms
fastbutton
99 ms
fastbutton
58 ms
blogicon-regular.woff
299 ms
00000.gif
3 ms
info
179 ms
hatena-follow-button.png
149 ms
adsbygoogle.js
8 ms
lg.php
192 ms
rs=AGLTcCMZQMkD3nQb9neyXrDGlfp1IpCqrw
24 ms
ca-pub-5973519624968530.js
34 ms
zrt_lookup.html
32 ms
ads
202 ms
cb=gapi.loaded_0
28 ms
cb=gapi.loaded_1
26 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
34 ms
ads
202 ms
lg.php
174 ms
2530
56 ms
push
56 ms
6486ee8831ec61a50a12d1798da21d2e_1.html
32 ms
m
33 ms
st.v2.js
35 ms
pixel
14 ms
4f65c37d23a53433a8172d800e75c3fb.jpg
9 ms
cvo.gif
64 ms
2530
19 ms
push
21 ms
6486ee8831ec61a50a12d1798da21d2e_1.html
15 ms
adex.ashx
189 ms
gr
9 ms
pixel_details.html
15 ms
pixel
14 ms
hotcake.hatenadiary.jp 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
hotcake.hatenadiary.jp 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
hotcake.hatenadiary.jp 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 Hotcake.hatenadiary.jp 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 Hotcake.hatenadiary.jp 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.
hotcake.hatenadiary.jp
Open Graph data is detected on the main page of Hotcake Hatenadiary. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: