15.3 sec in total
507 ms
11 sec
3.8 sec
Click here to check amazing Charlie Hateblo content for Japan. Otherwise, check out these important facts you probably never knew about charlie.hateblo.jp
フロントエンド系(html5,css3,javascript)の効率よい開発のための情報を蓄積
Visit charlie.hateblo.jpWe analyzed Charlie.hateblo.jp page load time and found that the first response time was 507 ms and then it took 14.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
charlie.hateblo.jp performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value2.8 s
83/100
25%
Value13.1 s
2/100
10%
Value5,410 ms
0/100
30%
Value0
100/100
15%
Value26.6 s
0/100
10%
507 ms
656 ms
361 ms
400 ms
424 ms
Our browser made a total of 254 requests to load all elements on the main page. We found that 3% of them (7 requests) were addressed to the original Charlie.hateblo.jp, 9% (23 requests) were made to Cdn-ak.f.st-hatena.com and 6% (15 requests) were made to Blog.st-hatena.com. The less responsive or slowest element that took the longest time to load (9.4 sec) relates to the external source Cdn-ak.f.st-hatena.com.
Page size can be reduced by 5.2 MB (27%)
19.1 MB
13.9 MB
In fact, the total size of Charlie.hateblo.jp main page is 19.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. 80% 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. Images take 15.5 MB which makes up the majority of the site volume.
Potential reduce by 201.3 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 201.3 kB or 76% of the original size.
Potential reduce by 2.4 MB
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, Charlie Hateblo needs image optimization as it can save up to 2.4 MB or 15% 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.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 2.5 MB or 79% of the original size.
Potential reduce by 121.0 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. Charlie.hateblo.jp needs all CSS files to be minified and compressed as it can save up to 121.0 kB or 83% of the original size.
Number of requests can be reduced by 118 (50%)
235
117
The browser has sent 235 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Charlie 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 64 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
charlie.hateblo.jp
507 ms
blog.css
656 ms
7524d02f500197786e6c169fc68a921ec7ce2bc2
361 ms
line-button.js
400 ms
hatena_afc_ydn-compiled.js
424 ms
adsbygoogle.js
15 ms
hatena_dfp2.js
503 ms
HatenaStar.js
1432 ms
widgets.js
98 ms
plusone.js
128 ms
bookmark_button.js
723 ms
react-with-addons.min.js
96 ms
react-dom.min.js
99 ms
jquery-1.9.1.min.js
90 ms
jquery-ui.1.10.0.custom.min.js
88 ms
jquery.flot.0.8.3.js
84 ms
jquery.flot.time.0.8.3.js
84 ms
hatenablog.js
2062 ms
texts-ja.js
645 ms
api.js
103 ms
analytics.js
22 ms
20160310164612.png
735 ms
ir
383 ms
profile.gif
383 ms
button-only.gif
379 ms
20160310165105.png
1341 ms
20160313130153.png
1246 ms
20160313130212.png
1015 ms
20160313130226.png
1056 ms
20160313130238.png
679 ms
20160313130249.png
1023 ms
20160313130312.png
1055 ms
20160313130324.png
2176 ms
20160223161449.png
1548 ms
20160221175846.png
5227 ms
20160221174047.png
9377 ms
20160221165121.jpg
3034 ms
20160217143830.png
3997 ms
20160217143145.png
2325 ms
20160217143153.png
2837 ms
20160217143201.png
2837 ms
20140907160438.jpg
3504 ms
20140907160943.jpg
3373 ms
20140907161330.jpg
3636 ms
20140514163216.gif
3974 ms
20140514164341.gif
3864 ms
20140514163227.gif
4128 ms
ir
166 ms
profile.gif
386 ms
183000
209 ms
share_1.png
118 ms
content_bg.gif
158 ms
category.png
305 ms
collect
18 ms
collect
77 ms
TitilliumText22L003-webfont.woff
195 ms
173000
271 ms
080000
333 ms
comment.png
283 ms
show_ads.js
4 ms
ga-audiences
19 ms
show_ads_impl.js
52 ms
embed.css
256 ms
http%3A%2F%2Fcdn-ak.f.st-hatena.com%2Fimages%2Ffotolife%2Ff%2Ffushimik%2F20160223%2F20160223161449.png
900 ms
entry.count.image
350 ms
183000
325 ms
blog-icon-noimage.png
267 ms
embed-logo.gif
356 ms
ads
288 ms
osd.js
64 ms
entry.count.image
362 ms
173000
300 ms
http%3A%2F%2Fcdn-ak.f.st-hatena.com%2Fimages%2Ffotolife%2Ff%2Ffushimik%2F20160217%2F20160217143830.png
1830 ms
entry.count.image
308 ms
080000
292 ms
http%3A%2F%2Fcdn-ak.f.st-hatena.com%2Fimages%2Ffotolife%2Ff%2Ffushimik%2F20160310%2F20160310164612.png
863 ms
cm
171 ms
cm
237 ms
cm
212 ms
cm
198 ms
cm
323 ms
cm
325 ms
embed
372 ms
183000
211 ms
00001.gif
36 ms
ads
234 ms
510pfxopHcL._SL100_.jpg
48 ms
162 ms
buy-from-tan.gif
32 ms
41lLailWaNL._SL100_.jpg
14 ms
186 ms
51MwLJGtcgL._SL100_.jpg
10 ms
155 ms
417TMt9qhyL._SL100_.jpg
11 ms
164 ms
00001.gif
8 ms
entry.count.image
183 ms
51L2lgNrRpL._SL100_.jpg
34 ms
81 ms
41CJ8BfuiuL._SL100_.jpg
37 ms
131 ms
embed
343 ms
embed
341 ms
00001.gif
22 ms
cdn-ak.favicon.st-hatena.com
270 ms
convenient-smartphone-preview-function-of-google-chrome.html
162 ms
entry.count.image
268 ms
ads
113 ms
ca-pub-8368702628165310.js
73 ms
zrt_lookup.html
49 ms
ads
35 ms
search_g.png
215 ms
embed
1395 ms
embed
1017 ms
audience
522 ms
jstag
146 ms
gpt.js
146 ms
btn.js
500 ms
cb=gapi.loaded_0
439 ms
pubads_impl_82.js
339 ms
00118.gif
20 ms
369 ms
308 ms
367 ms
306 ms
367 ms
307 ms
486 ms
blogs
287 ms
sdk.js
89 ms
user.segment.json
280 ms
hatena_bigmining.js
77 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
68 ms
show.json
945 ms
archive_module
272 ms
notices.count.json
881 ms
button
191 ms
button
240 ms
button
249 ms
button
256 ms
button
253 ms
button
252 ms
button
334 ms
recaptcha__en.js
363 ms
container.html
268 ms
dfp.config.json
282 ms
354 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
160 ms
reset.css
159 ms
entry-button.css
159 ms
globalheader.css
215 ms
api.js
145 ms
button.css
324 ms
shared.js
322 ms
button.js
322 ms
xd_arbiter.php
202 ms
xd_arbiter.php
385 ms
bbtn-l_v3.png
56 ms
http%3A%2F%2Fpostd.cc%2Fwp%2Fwp-content%2Fuploads%2F2014%2F12%2Fcolumnblocks_coloured-0.jpg
249 ms
favicon.ico
333 ms
entry.count.image
220 ms
214 ms
pocket_button.png
57 ms
notices.count.json
520 ms
init
205 ms
ads
503 ms
dropdown@2x.png
296 ms
jot.html
2 ms
00628.gif
249 ms
https%3A%2F%2Favatars1.githubusercontent.com%2Fu%2F684879%3Fv%3D3%26s%3D400
458 ms
favicon.ico
111 ms
entry.count.image
303 ms
ElasticTabstops
208 ms
fastbutton
75 ms
fastbutton
182 ms
fastbutton
157 ms
fastbutton
111 ms
fastbutton
191 ms
fastbutton
173 ms
fastbutton
128 ms
blogicon-regular.woff
309 ms
info
219 ms
rs=AGLTcCPp65oTnX7XI_ISus95mcUHkH7hXw
68 ms
hatena-follow-button.png
224 ms
cb=gapi.loaded_0
81 ms
cb=gapi.loaded_1
79 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
117 ms
ajs.php
337 ms
ads
247 ms
00003.gif
5 ms
ajs.php
258 ms
ads
218 ms
lg.php
244 ms
ca-pub-5973519624968530.js
31 ms
ads
266 ms
expansion_embed.js
23 ms
ads
297 ms
adj
134 ms
adServerESI.aspx
213 ms
beacon
102 ms
ads
259 ms
lg.php
174 ms
skeleton.gif
107 ms
adj
69 ms
beacon
57 ms
intel-vid4.png
88 ms
lidar.js
24 ms
sbhK2lTE.js
23 ms
pixel
49 ms
push
148 ms
cTrvNaRi.html
28 ms
pixel
110 ms
pixel
111 ms
lidar.js
24 ms
sbhK2lTE.js
107 ms
pixel
80 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
26 ms
adj
112 ms
adServerESI.aspx
249 ms
beacon
20 ms
setuid
255 ms
adj
117 ms
cTrvNaRi.html
16 ms
adServerESI.aspx
233 ms
beacon
91 ms
skeleton.gif
89 ms
intel-vid1.png
43 ms
skeleton.gif
56 ms
pixel
95 ms
push
82 ms
139 ms
pixel
114 ms
intel-vid3.png
119 ms
sd
117 ms
59 ms
12 ms
pixel
24 ms
pixel
21 ms
hatena-star-add-button.png
152 ms
comment.gif
371 ms
entries.json
452 ms
dmp
319 ms
gtm.js
62 ms
tdim-0.11.2.js
17 ms
segment
353 ms
share_button.php
96 ms
share_button.php
137 ms
share_button.php
187 ms
share_button.php
154 ms
share_button.php
270 ms
share_button.php
278 ms
share_button.php
208 ms
wy1X4hBW7e7.js
31 ms
LVx-xkvaJ0b.png
18 ms
charlie.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
charlie.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
charlie.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 Charlie.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 Charlie.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.
charlie.hateblo.jp
Open Graph data is detected on the main page of Charlie Hateblo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: