6.6 sec in total
519 ms
5.3 sec
704 ms
Visit methane.hatenablog.jp now to see the best up-to-date Methane Hatenablog content for Japan and also check out these interesting facts you probably never knew about methane.hatenablog.jp
このブログに乗せているサンプルコードはすべてNYSLです。
Visit methane.hatenablog.jpWe analyzed Methane.hatenablog.jp page load time and found that the first response time was 519 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
methane.hatenablog.jp performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value2.8 s
83/100
25%
Value11.5 s
5/100
10%
Value3,290 ms
2/100
30%
Value0
100/100
15%
Value25.3 s
0/100
10%
519 ms
762 ms
340 ms
361 ms
518 ms
Our browser made a total of 146 requests to load all elements on the main page. We found that 5% of them (8 requests) were addressed to the original Methane.hatenablog.jp, 9% (13 requests) were made to Google-analytics.com and 8% (12 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Cdn-ak.f.st-hatena.com.
Page size can be reduced by 4.1 MB (79%)
5.2 MB
1.1 MB
In fact, the total size of Methane.hatenablog.jp main page is 5.2 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. 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. Javascripts take 4.8 MB which makes up the majority of the site volume.
Potential reduce by 99.8 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 18.3 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 99.8 kB or 84% of the original size.
Potential reduce by 19.6 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, Methane Hatenablog needs image optimization as it can save up to 19.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 3.9 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 3.9 MB or 82% 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. Methane.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 92 (68%)
136
44
The browser has sent 136 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Methane 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 58 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
methane.hatenablog.jp
519 ms
blog.css
762 ms
965d5e07719062a2c21ac0a13fdf90f4bfd6f4a0
340 ms
hatena_afc_ydn-compiled.js
361 ms
hatena_dfp2.js
518 ms
HatenaStar.js
1185 ms
widgets.js
56 ms
plusone.js
81 ms
bookmark_button.js
756 ms
react-with-addons.min.js
56 ms
react-dom.min.js
64 ms
jquery-1.9.1.min.js
44 ms
jquery-ui.1.10.0.custom.min.js
44 ms
jquery.flot.0.8.3.js
44 ms
jquery.flot.time.0.8.3.js
43 ms
hatenablog.js
1789 ms
texts-ja.js
677 ms
api.js
59 ms
analytics.js
8 ms
20160302004342.gif
1160 ms
profile.gif
1117 ms
button-only.gif
314 ms
20160302004350.gif
2479 ms
profile.gif
1091 ms
collect
8 ms
collect
56 ms
collect
8 ms
collect
9 ms
collect
61 ms
collect
71 ms
show_ads.js
16 ms
show_ads_impl.js
50 ms
ads
278 ms
osd.js
35 ms
ads
220 ms
search_w.png
148 ms
audience
404 ms
jstag
78 ms
gpt.js
76 ms
cb=gapi.loaded_0
50 ms
pubads_impl_82.js
20 ms
521 ms
520 ms
499 ms
499 ms
497 ms
container.html
8 ms
dfp.config.json
218 ms
collect
55 ms
blogs
220 ms
recaptcha__en.js
78 ms
sdk.js
125 ms
user.segment.json
229 ms
67 ms
segmentation.js
116 ms
hatena_bigmining.js
65 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
42 ms
show.json
982 ms
archive_module
219 ms
notices.count.json
719 ms
collect
37 ms
collect
37 ms
collect
42 ms
collect
42 ms
84 ms
86 ms
reset.css
63 ms
entry-button.css
61 ms
55 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
104 ms
bbtn-l_v3.png
96 ms
95 ms
94 ms
ads
370 ms
cnt
209 ms
redirect.js
83 ms
cnt
350 ms
cnt
319 ms
cnt
355 ms
globalheader.css
152 ms
hatenablog.js
905 ms
texts-ja.js
191 ms
api.js
26 ms
116 ms
xd_arbiter.php
72 ms
xd_arbiter.php
133 ms
collect
28 ms
ajs.php
353 ms
ads
228 ms
jot.html
2 ms
ajs.php
299 ms
ads
223 ms
adsbygoogle.js
6 ms
lg.php
251 ms
ca-pub-5973519624968530.js
21 ms
zrt_lookup.html
18 ms
ads
281 ms
ads
244 ms
lg.php
168 ms
13824727330278340992
65 ms
abg.js
36 ms
m_js_controller.js
44 ms
googlelogo_color_112x36dp.png
31 ms
notices.count.json
176 ms
dropdown@2x.png
168 ms
init
174 ms
s
22 ms
x_button_blue2.png
23 ms
push
36 ms
25 ms
pixel
15 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
6 ms
alternatead-300x250-red-pc.html
45 ms
ad
385 ms
collect
49 ms
fastbutton
59 ms
fastbutton
96 ms
fastbutton
103 ms
fastbutton
106 ms
fastbutton
158 ms
collect
18 ms
blogicon-regular.woff
293 ms
info
167 ms
hatena_bookmark_comment
416 ms
hatena_bookmark_comment
332 ms
hatena_bookmark_comment
364 ms
hatena_bookmark_comment
354 ms
hatena_bookmark_comment
343 ms
hatena-follow-button.png
164 ms
rs=AGLTcCOnajr3RJY7XpQMDAZWyUDsx4v9Qw
4 ms
cb=gapi.loaded_0
18 ms
cb=gapi.loaded_1
19 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
49 ms
cb=gapi.loaded_0
27 ms
cb=gapi.loaded_1
26 ms
collect
5 ms
46062_banner.png
1143 ms
bookmark_blogparts.js
345 ms
api.js
121 ms
activeview
41 ms
208 ms
157 ms
345 ms
activeview
15 ms
profile_s.gif
196 ms
hatena-star-add-button.png
147 ms
methane.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
methane.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
methane.hatenablog.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Methane.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 Methane.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.
methane.hatenablog.jp
Open Graph data is detected on the main page of Methane Hatenablog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: