7.7 sec in total
491 ms
6.4 sec
749 ms
Welcome to hogem.hatenablog.com homepage info - get ready to check Hogem Hatenablog best content for Japan right away, or after learning these important things about hogem.hatenablog.com
linuxとhttpdとperlのメモ
Visit hogem.hatenablog.comWe analyzed Hogem.hatenablog.com page load time and found that the first response time was 491 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
hogem.hatenablog.com performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value2.8 s
83/100
25%
Value13.7 s
2/100
10%
Value5,050 ms
0/100
30%
Value0
100/100
15%
Value29.0 s
0/100
10%
491 ms
774 ms
337 ms
521 ms
364 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 5% of them (5 requests) were addressed to the original Hogem.hatenablog.com, 12% (13 requests) were made to Blog.st-hatena.com and 7% (8 requests) were made to Cdn.api.b.hatena.ne.jp. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Blog.st-hatena.com.
Page size can be reduced by 2.5 MB (76%)
3.3 MB
803.9 kB
In fact, the total size of Hogem.hatenablog.com main page is 3.3 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 114.2 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 23.2 kB, which is 17% 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 114.2 kB or 85% of the original size.
Potential reduce by 18.8 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, Hogem Hatenablog needs image optimization as it can save up to 18.8 kB or 16% 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.2 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.2 MB or 77% of the original size.
Potential reduce by 153.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. Hogem.hatenablog.com needs all CSS files to be minified and compressed as it can save up to 153.9 kB or 84% of the original size.
Number of requests can be reduced by 65 (64%)
101
36
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hogem 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 50 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
hogem.hatenablog.com
491 ms
blog.css
774 ms
ce7635c0c232c5fde9a02ec43b6788944dc869c2
337 ms
hatena_afc_ydn-compiled.js
521 ms
widget.js
364 ms
hatena_dfp2.js
701 ms
HatenaStar.js
1143 ms
widgets.js
54 ms
plusone.js
80 ms
bookmark_button.js
698 ms
react-with-addons.min.js
58 ms
react-dom.min.js
61 ms
jquery-1.9.1.min.js
48 ms
jquery-ui.1.10.0.custom.min.js
50 ms
jquery.flot.0.8.3.js
47 ms
jquery.flot.time.0.8.3.js
46 ms
hatenablog.js
1807 ms
texts-ja.js
641 ms
api.js
65 ms
analytics.js
13 ms
profile.gif
338 ms
button-only.gif
173 ms
profile.gif
407 ms
1328355984
194 ms
show_ads.js
4 ms
show_ads_impl.js
40 ms
ads
285 ms
osd.js
25 ms
embed.css
150 ms
entry.count.image
361 ms
1328355984
345 ms
blog-icon-noimage.png
159 ms
embed-logo.gif
294 ms
ads
156 ms
ads
117 ms
00007.gif
10 ms
1420894082
162 ms
search_w.png
147 ms
favicon.gif
172 ms
audience
349 ms
jstag
81 ms
gpt.js
79 ms
cb=gapi.loaded_0
51 ms
pubads_impl_82.js
18 ms
244 ms
220 ms
221 ms
221 ms
222 ms
217 ms
453 ms
container.html
10 ms
embed.css
149 ms
entry.count.image
187 ms
1420894082
173 ms
embed-logo.gif
155 ms
reset.css
9 ms
entry-button.css
9 ms
bbtn-l_v3.png
5 ms
dfp.config.json
192 ms
json
380 ms
hatena_bigmining.js
50 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
23 ms
show.json
864 ms
archive_module
165 ms
notices.count.json
791 ms
blogs
329 ms
recaptcha__en.js
102 ms
00000.gif
26 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
50 ms
ads
343 ms
globalheader.css
170 ms
api.js
19 ms
jot.html
6 ms
ajs.php
398 ms
ads
266 ms
notices.count.json
390 ms
init
171 ms
dropdown@2x.png
304 ms
ajs.php
326 ms
ads
348 ms
blogicon-regular.woff
293 ms
info
164 ms
hatena-follow-button.png
147 ms
adsbygoogle.js
4 ms
lg.php
401 ms
ca-pub-5973519624968530.js
18 ms
zrt_lookup.html
16 ms
ads
159 ms
DIGITALICE_PT.js
804 ms
abg.js
43 ms
ads
192 ms
lg.php
187 ms
ads
196 ms
alternatead-300x250-red-pc.html
7 ms
ad
366 ms
46062_banner.png
1241 ms
167 ms
push
33 ms
gp_match
30 ms
pixel
13 ms
f5haBxUNekXc.gif
223 ms
hatena-star-add-button.png
148 ms
comment.gif
311 ms
entries.json
1108 ms
dmp
323 ms
gtm.js
14 ms
tdim-0.11.2.js
27 ms
segment
298 ms
pageviews
9 ms
hogem.hatenablog.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
hogem.hatenablog.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
hogem.hatenablog.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 Hogem.hatenablog.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 Hogem.hatenablog.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.
hogem.hatenablog.com
Open Graph data is detected on the main page of Hogem Hatenablog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: