9.6 sec in total
585 ms
5.3 sec
3.6 sec
Visit wataruumino.hatenablog.jp now to see the best up-to-date Wataruumino Hatenablog content for Japan and also check out these interesting facts you probably never knew about wataruumino.hatenablog.jp
アニメ 考察 羽海野渉
Visit wataruumino.hatenablog.jpWe analyzed Wataruumino.hatenablog.jp page load time and found that the first response time was 585 ms and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
wataruumino.hatenablog.jp performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value3.9 s
51/100
25%
Value12.7 s
3/100
10%
Value6,690 ms
0/100
30%
Value0
100/100
15%
Value26.6 s
0/100
10%
585 ms
777 ms
365 ms
345 ms
533 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Wataruumino.hatenablog.jp, 15% (13 requests) were made to Ecx.images-amazon.com and 10% (8 requests) were made to Blog.hatena.ne.jp. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Blog.st-hatena.com.
Page size can be reduced by 2.7 MB (67%)
4.1 MB
1.4 MB
In fact, the total size of Wataruumino.hatenablog.jp main page is 4.1 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. 65% of websites need less resources to load. Javascripts take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 103.6 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 103.6 kB or 78% of the original size.
Potential reduce by 186.5 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, Wataruumino Hatenablog needs image optimization as it can save up to 186.5 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
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 81% of the original size.
Potential reduce by 83.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. Wataruumino.hatenablog.jp needs all CSS files to be minified and compressed as it can save up to 83.8 kB or 83% of the original size.
Number of requests can be reduced by 41 (51%)
80
39
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wataruumino Hatenablog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
wataruumino.hatenablog.jp
585 ms
blog.css
777 ms
03b717e17ae889163f9c8305ddb7ef8be6ffee55
365 ms
hatena_afc_ydn-compiled.js
345 ms
hatena_dfp2.js
533 ms
HatenaStar.js
1136 ms
widgets.js
303 ms
plusone.js
253 ms
bookmark_button.js
823 ms
react-with-addons.min.js
182 ms
react-dom.min.js
188 ms
jquery-1.9.1.min.js
138 ms
jquery-ui.1.10.0.custom.min.js
143 ms
jquery.flot.0.8.3.js
144 ms
jquery.flot.time.0.8.3.js
153 ms
hatenablog.js
1953 ms
texts-ja.js
616 ms
api.js
171 ms
analytics.js
52 ms
41yfUBsl3XL._SL160_.jpg
52 ms
20151122204901.png
1899 ms
profile.gif
228 ms
6141nz1P41L._SL160_.jpg
30 ms
51W5zrSIVpL._SL160_.jpg
49 ms
51teJL6U44L._SL160_.jpg
31 ms
51xrMSF5xNL._SL160_.jpg
47 ms
51bfzoMnZkL._SL160_.jpg
30 ms
51mS1G1AGZL._SL160_.jpg
46 ms
51nDKUmNSuL._SL160_.jpg
58 ms
51OwRgrebBL._SL160_.jpg
43 ms
51MP9z1Z6RL._SL160_.jpg
108 ms
51XbciwbYgL._SL160_.jpg
111 ms
61IvT9eCY6L._SL160_.jpg
106 ms
51joZdZ6KTL._SL160_.jpg
95 ms
button-only.gif
274 ms
profile.gif
420 ms
collect
24 ms
collect
63 ms
show_ads.js
12 ms
show_ads_impl.js
108 ms
ads
321 ms
osd.js
51 ms
ads
234 ms
ads
151 ms
search_w.png
427 ms
audience
390 ms
jstag
379 ms
gpt.js
378 ms
cb=gapi.loaded_0
285 ms
blogs
245 ms
pubads_impl_82.js
118 ms
dfp.config.json
269 ms
recaptcha__en.js
257 ms
717 ms
714 ms
711 ms
561 ms
702 ms
701 ms
701 ms
container.html
158 ms
globalheader.css
410 ms
sdk.js
149 ms
hatena_bigmining.js
138 ms
log
405 ms
show.json
1287 ms
archive_module
393 ms
notices.count.json
842 ms
reset.css
144 ms
entry-button.css
145 ms
log
397 ms
401 ms
bbtn-l_v3.png
239 ms
notices.count.json
634 ms
init
262 ms
xd_arbiter.php
46 ms
xd_arbiter.php
72 ms
992085f9af3ef0e5b6df8b80575405cdc6ed5718
269 ms
992085f9af3ef0e5b6df8b80575405cdc6ed5718
395 ms
global-logo@2x.png
295 ms
ads
478 ms
blogicon-regular.woff
293 ms
info
170 ms
hatena-follow-button.png
147 ms
wataruumino.hatenablog.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
wataruumino.hatenablog.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
wataruumino.hatenablog.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 Wataruumino.hatenablog.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 Wataruumino.hatenablog.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.
wataruumino.hatenablog.jp
Open Graph data is detected on the main page of Wataruumino Hatenablog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: