10 sec in total
529 ms
6.1 sec
3.4 sec
Visit deta.hateblo.jp now to see the best up-to-date Deta Hateblo content for Japan and also check out these interesting facts you probably never knew about deta.hateblo.jp
データ解析を担当することになったサラリーマンの備忘録
Visit deta.hateblo.jpWe analyzed Deta.hateblo.jp page load time and found that the first response time was 529 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
deta.hateblo.jp performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value2.8 s
82/100
25%
Value18.9 s
0/100
10%
Value3,180 ms
2/100
30%
Value0
100/100
15%
Value29.2 s
0/100
10%
529 ms
795 ms
351 ms
519 ms
746 ms
Our browser made a total of 207 requests to load all elements on the main page. We found that 1% of them (3 requests) were addressed to the original Deta.hateblo.jp, 6% (12 requests) were made to Apis.google.com and 6% (12 requests) were made to O.twimg.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Blog.st-hatena.com.
Page size can be reduced by 4.8 MB (71%)
6.8 MB
2.0 MB
In fact, the total size of Deta.hateblo.jp main page is 6.8 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. 85% 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 5.6 MB which makes up the majority of the site volume.
Potential reduce by 183.4 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 183.4 kB or 78% of the original size.
Potential reduce by 30.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. Deta Hateblo images are well optimized though.
Potential reduce by 4.5 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 4.5 MB or 80% of the original size.
Potential reduce by 145.6 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. Deta.hateblo.jp needs all CSS files to be minified and compressed as it can save up to 145.6 kB or 84% of the original size.
Number of requests can be reduced by 113 (58%)
194
81
The browser has sent 194 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Deta Hateblo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 82 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
deta.hateblo.jp
529 ms
blog.css
795 ms
0944c3d13d4dd66d31e0c4cc06db22553ee93ed3
351 ms
hatena_afc_ydn-compiled.js
519 ms
hatena_dfp2.js
746 ms
HatenaStar.js
1559 ms
widgets.js
62 ms
plusone.js
94 ms
bookmark_button.js
745 ms
react-with-addons.min.js
67 ms
react-dom.min.js
87 ms
jquery-1.9.1.min.js
55 ms
jquery-ui.1.10.0.custom.min.js
53 ms
jquery.flot.0.8.3.js
53 ms
jquery.flot.time.0.8.3.js
53 ms
hatenablog.js
1935 ms
texts-ja.js
628 ms
api.js
82 ms
analytics.js
14 ms
411xr-FagVL._SL160_.jpg
13 ms
20141227152704.jpg
914 ms
chart
90 ms
profile.gif
597 ms
button-only.gif
222 ms
20141227160956.jpg
1132 ms
20141227165643.jpg
1174 ms
20140520054401.png
705 ms
20140513230959.png
1029 ms
20140508043056.png
666 ms
20140508044224.png
877 ms
profile.gif
557 ms
embed
364 ms
collect
6 ms
collect
55 ms
show_ads.js
13 ms
show_ads_impl.js
51 ms
ads
355 ms
osd.js
25 ms
embed.css
151 ms
http%3A%2F%2Fcdn.sstatic.net%2Fstackoverflow%2Fimg%2Fapple-touch-icon%402.png%3Fv%3D73d79a89bded%26a
226 ms
favicon.ico
15 ms
entry.count.image
389 ms
escaping-backslashes-in-postgresql
363 ms
ads
154 ms
ads
115 ms
00000.gif
9 ms
widgets.js
5 ms
search_g.png
191 ms
audience
455 ms
jstag
38 ms
gpt.js
36 ms
collect
97 ms
pubads_impl_82.js
94 ms
cb=gapi.loaded_0
69 ms
container.html
18 ms
425 ms
436 ms
426 ms
450 ms
424 ms
424 ms
669 ms
blogs
200 ms
recaptcha__en.js
83 ms
sdk.js
272 ms
hatena_bigmining.js
58 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
30 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
31 ms
show.json
1120 ms
MathJax.js
332 ms
archive_module
193 ms
notices.count.json
1151 ms
dfp.config.json
189 ms
syndication
186 ms
324655393903087616
384 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
98 ms
reset.css
27 ms
entry-button.css
28 ms
globalheader.css
186 ms
hatenablog.js
1610 ms
texts-ja.js
218 ms
api.js
34 ms
bbtn-l_v3.png
15 ms
211 ms
xd_arbiter.php
262 ms
xd_arbiter.php
491 ms
ads
408 ms
TeX-AMS-MML_HTMLorMML.js
85 ms
proxy.jpg
257 ms
proxy.jpg
350 ms
proxy.jpg
442 ms
proxy.jpg
618 ms
proxy.jpg
617 ms
proxy.jpg
618 ms
proxy.jpg
615 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
57 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
56 ms
9b158a92b4872b434c97f73e30b87bba_normal.jpeg
121 ms
IIHS-deS_normal.png
25 ms
Mv4fgDci_normal.jpg
25 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
30 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
26 ms
jax.js
77 ms
expansion_embed.js
82 ms
ads
287 ms
fontdata.js
98 ms
bsredirect5.js
280 ms
surly.js
531 ms
ad
91 ms
gen_204
36 ms
proxy.jpg
307 ms
proxy.jpg
231 ms
proxy.jpg
296 ms
proxy.jpg
294 ms
proxy.jpg
121 ms
ajs.php
416 ms
ads
388 ms
bst2tv3.html
249 ms
verifyc.js
74 ms
MathJax_Main-Regular.woff
9 ms
MathJax_Main-Bold.woff
31 ms
MathJax_Math-Italic.woff
145 ms
MathJax_Size1-Regular.woff
31 ms
clk
259 ms
ads
277 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
72 ms
lidar.js
70 ms
antenna2.js
96 ms
dvtp_src.js
124 ms
ca
120 ms
ca-pub-5973519624968530.js
62 ms
zrt_lookup.html
65 ms
ads
412 ms
lg.php
234 ms
index.html
45 ms
firstevent
13 ms
dvtp_src_internal26.js
32 ms
4.gif
143 ms
ba.html
142 ms
easeljs-0.8.1.min.js
148 ms
tweenjs-0.6.1.min.js
162 ms
movieclip-0.8.1.min.js
161 ms
preloadjs-0.6.1.min.js
166 ms
CCT6738_3_Q1_LC_Lifestyle_ACQ_Sp_NED69.99x12_X1DVR10_300x250.js
22 ms
sbhK2lTE.js
112 ms
push
316 ms
t2tv7.html
95 ms
visit.js
224 ms
cTrvNaRi.html
36 ms
4311.js
199 ms
CCT6738_3_Q1_LC_Lifestyle_ACQ_Sp_NED69.99x12_X1DVR10_300x250_atlas_.json
9 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
58 ms
CCT6738_3_Q1_LC_Lifestyle_ACQ_Sp_NED69.99x12_X1DVR10_300x250_atlas_.png
145 ms
2530
96 ms
avs5639.js
123 ms
notices.count.json
273 ms
init
184 ms
dropdown@2x.png
306 ms
event.gif
38 ms
6486ee8831ec61a50a12d1798da21d2e_1.html
224 ms
pixel
46 ms
event.jpg
21 ms
box_19_top-right.png
28 ms
ci.png
27 ms
jot.html
2 ms
fastbutton
74 ms
fastbutton
99 ms
fastbutton
180 ms
fastbutton
253 ms
fastbutton
244 ms
fastbutton
147 ms
fastbutton
239 ms
st.v2.js
65 ms
blogicon-regular.woff
319 ms
info
267 ms
rs=AGLTcCNFg9Lxr6A_1qJE1FafaQPPaU_lFQ
63 ms
hatena-follow-button.png
257 ms
4f65c37d23a53433a8172d800e75c3fb.jpg
217 ms
cvo.gif
207 ms
cb=gapi.loaded_0
152 ms
cb=gapi.loaded_1
146 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
123 ms
gr
34 ms
pixel_details.html
7 ms
hatena-star-add-button.png
150 ms
comment.gif
292 ms
entries.json
486 ms
dmp
308 ms
gtm.js
92 ms
tdim-0.11.2.js
10 ms
segment
304 ms
share_button.php
91 ms
share_button.php
155 ms
share_button.php
153 ms
share_button.php
111 ms
share_button.php
170 ms
share_button.php
168 ms
wy1X4hBW7e7.js
487 ms
LVx-xkvaJ0b.png
574 ms
share_button.php
100 ms
cap
32 ms
ca
28 ms
ca
21 ms
ca
20 ms
pageviews
11 ms
star.gif
148 ms
profile.gif
291 ms
deta.hateblo.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
deta.hateblo.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
deta.hateblo.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 Deta.hateblo.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 Deta.hateblo.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.
deta.hateblo.jp
Open Graph data is detected on the main page of Deta Hateblo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: