13.6 sec in total
1.1 sec
10.8 sec
1.7 sec
Click here to check amazing Lafs Hatenablog content for Japan. Otherwise, check out these important facts you probably never knew about lafs.hatenablog.com
ウェブも電子書籍もDVDもCDも編集しちゃうよでもいちばん仕事多いのはけっきょく紙
Visit lafs.hatenablog.comWe analyzed Lafs.hatenablog.com page load time and found that the first response time was 1.1 sec and then it took 12.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
lafs.hatenablog.com performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value2.8 s
83/100
25%
Value11.7 s
4/100
10%
Value3,350 ms
2/100
30%
Value0
100/100
15%
Value24.1 s
0/100
10%
1089 ms
901 ms
333 ms
137 ms
329 ms
Our browser made a total of 153 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Lafs.hatenablog.com, 12% (19 requests) were made to Blog.st-hatena.com and 11% (17 requests) were made to Cdn.api.b.hatena.ne.jp. The less responsive or slowest element that took the longest time to load (7.7 sec) relates to the external source Cdn-ak.f.st-hatena.com.
Page size can be reduced by 1.3 MB (50%)
2.5 MB
1.3 MB
In fact, the total size of Lafs.hatenablog.com main page is 2.5 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 173.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 21.3 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 173.0 kB or 86% of the original size.
Potential reduce by 22.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. Lafs Hatenablog images are well optimized though.
Potential reduce by 1.0 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 1.0 MB or 69% of the original size.
Potential reduce by 82.3 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. Lafs.hatenablog.com needs all CSS files to be minified and compressed as it can save up to 82.3 kB or 84% of the original size.
Number of requests can be reduced by 71 (48%)
147
76
The browser has sent 147 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lafs 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 52 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
lafs.hatenablog.com
1089 ms
blog.css
901 ms
6a9c85fa776e7d2fd7dd6752f07f87b257db94a5
333 ms
widgets.js
137 ms
hatena_afc_ydn-compiled.js
329 ms
hatena_dfp2.js
803 ms
HatenaStar.js
1078 ms
widgets.js
184 ms
plusone.js
56 ms
bookmark_button.js
798 ms
react-with-addons.min.js
39 ms
jquery-1.9.1.min.js
24 ms
jquery-ui.1.10.0.custom.min.js
23 ms
jquery.flot.0.8.3.js
27 ms
jquery.flot.time.0.8.3.js
27 ms
hatenablog.js
2617 ms
texts-ja.js
584 ms
api.js
51 ms
20140202235650.jpg
1166 ms
profile.gif
455 ms
button-only.gif
627 ms
theme17.png
164 ms
20131117230354.jpg
7701 ms
20131117230220.jpg
5664 ms
profile.gif
197 ms
analytics.js
18 ms
radius10-width800-top.png
322 ms
radius10-width800-bottom.png
402 ms
box-800.png
441 ms
radius10-width500-bottom.png
442 ms
radius10-width500-top.png
475 ms
box-500.png
466 ms
collect
6 ms
collect
50 ms
collect
4 ms
collect
55 ms
show_ads.js
5 ms
zrt_lookup.html
16 ms
show_ads_impl.js
43 ms
ads
243 ms
osd.js
33 ms
00012.gif
9 ms
yads.js
487 ms
yads_vimps-1.4.1.js
597 ms
tag
567 ms
ads
137 ms
ads
91 ms
pager.png
151 ms
radius6-width285-top.png
148 ms
box-285.png
149 ms
radius6-width285-bottom.png
152 ms
search_g.png
159 ms
audience
352 ms
jstag
59 ms
gpt.js
58 ms
cb=gapi.loaded_0
47 ms
pubads_impl_81.js
7 ms
211 ms
222 ms
249 ms
213 ms
225 ms
234 ms
525 ms
531 ms
536 ms
527 ms
537 ms
533 ms
666 ms
677 ms
885 ms
container.html
9 ms
reset.css
9 ms
entry-button.css
17 ms
bbtn-l_v3.png
4 ms
dfp.config.json
264 ms
blogs
183 ms
recaptcha__en.js
82 ms
sdk.js
328 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
75 ms
tweet.04d20138f67ab41d6b4af6cc583926d9.js
111 ms
show.json
805 ms
archive_module
205 ms
notices.count.json
861 ms
syndication
205 ms
tweets.json
341 ms
tweets.json
251 ms
follow_button.6a78875565a912489e9aef879c881358.ja.html
50 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
164 ms
globalheader.css
334 ms
widgets.js
177 ms
api.js
143 ms
ads
404 ms
116 ms
xd_arbiter.php
235 ms
xd_arbiter.php
450 ms
tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css
30 ms
tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css
75 ms
1261737916_emote_smile_normal.png
141 ms
taro03_normal.JPG
135 ms
notices.count.json
677 ms
init
188 ms
2070afaffac8e67d58441e14f9cc8c1e347ea12d
328 ms
2070afaffac8e67d58441e14f9cc8c1e347ea12d
319 ms
global-logo@2x.png
325 ms
tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css
33 ms
tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css
51 ms
ajs.php
402 ms
ads
201 ms
irdG64Ft_normal.png
19 ms
rxve0yYM_normal.jpg
14 ms
e20e35865f95dfd17dac4d1cc6f4db8f_normal.jpeg
15 ms
blogicon-regular.woff
294 ms
info
200 ms
hatena-follow-button.png
157 ms
ajs.php
410 ms
ads
233 ms
adsbygoogle.js
9 ms
lg.php
173 ms
jot.html
41 ms
ca-pub-5973519624968530.js
29 ms
ads
170 ms
ads
206 ms
alternatead-300x250-red.html
3 ms
ad
405 ms
ads
163 ms
lg.php
172 ms
ads
177 ms
alternatead-300x250-red-pc.html
3 ms
ad
366 ms
45851_banner.png
491 ms
45913_banner.png
644 ms
hatena-star-add-button.png
148 ms
comment.gif
329 ms
entries.json
1659 ms
share_button.php
65 ms
share_button.php
91 ms
share_button.php
110 ms
share_button.php
104 ms
share_button.php
112 ms
share_button.php
120 ms
share_button.php
113 ms
share_button.php
121 ms
vpc6VNjRPXV.js
487 ms
LVx-xkvaJ0b.png
592 ms
share_button.php
146 ms
share_button.php
136 ms
share_button.php
127 ms
share_button.php
148 ms
share_button.php
142 ms
share_button.php
149 ms
share_button.php
168 ms
lafs.hatenablog.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
lafs.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
lafs.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 Lafs.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 Lafs.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.
lafs.hatenablog.com
Open Graph data is detected on the main page of Lafs Hatenablog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: