11.5 sec in total
638 ms
6.3 sec
4.6 sec
Click here to check amazing Negative Hateblo content for Japan. Otherwise, check out these important facts you probably never knew about negative.hateblo.jp
経済統計屋。気分悪くなったらごめんなさい (´・д・`) ゴメンネ データサイエンティストという呼称が好きじゃないんです https://twitter.com/dscax
Visit negative.hateblo.jpWe analyzed Negative.hateblo.jp page load time and found that the first response time was 638 ms and then it took 10.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
negative.hateblo.jp performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value2.8 s
83/100
25%
Value15.2 s
1/100
10%
Value4,910 ms
0/100
30%
Value0.004
100/100
15%
Value28.2 s
0/100
10%
638 ms
770 ms
363 ms
332 ms
321 ms
Our browser made a total of 171 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Negative.hateblo.jp, 10% (17 requests) were made to Cdn1.www.st-hatena.com and 10% (17 requests) were made to Cdn-ak.f.st-hatena.com. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Cdn-ak.f.st-hatena.com.
Page size can be reduced by 1.3 MB (30%)
4.3 MB
3.0 MB
In fact, the total size of Negative.hateblo.jp main page is 4.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. 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. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 197.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. 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 197.8 kB or 75% of the original size.
Potential reduce by 63.4 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. Negative Hateblo images are well optimized though.
Potential reduce by 948.3 kB
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 948.3 kB 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. Negative.hateblo.jp needs all CSS files to be minified and compressed as it can save up to 82.3 kB or 83% of the original size.
Number of requests can be reduced by 80 (51%)
157
77
The browser has sent 157 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Negative 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 51 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
negative.hateblo.jp
638 ms
blog.css
770 ms
5252c0d27e3f98cd3be38ec4e4ec4e97b9453032
363 ms
line-button.js
332 ms
hatena_afc_ydn-compiled.js
321 ms
hatena_dfp2.js
745 ms
HatenaStar.js
1149 ms
widgets.js
43 ms
plusone.js
86 ms
bookmark_button.js
669 ms
react-with-addons.min.js
32 ms
jquery-1.9.1.min.js
31 ms
jquery-ui.1.10.0.custom.min.js
31 ms
jquery.flot.0.8.3.js
29 ms
jquery.flot.time.0.8.3.js
29 ms
hatenablog.js
1789 ms
texts-ja.js
619 ms
api.js
55 ms
css
28 ms
20090705220652.jpg
1466 ms
profile.gif
192 ms
button-only.gif
343 ms
20131227223318.jpg
1222 ms
20131217182717.jpg
1064 ms
20131204194901.jpg
1043 ms
20101010183339.jpg
1744 ms
20131204195357.jpg
878 ms
20131204195736.jpg
1455 ms
20131204195947.jpg
1945 ms
20131204200430.jpg
2459 ms
20131204200833.jpg
2249 ms
20131204201040.jpg
2459 ms
20131204201220.jpg
1690 ms
20120928114057.jpg
2063 ms
20131204201337.jpg
3258 ms
profile.gif
532 ms
analytics.js
10 ms
20130508182629.png
1956 ms
20130508065221.gif
1956 ms
collect
6 ms
collect
92 ms
collect
3 ms
collect
102 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
31 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
32 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
32 ms
vzIUHo9z-oJ4WgkpPOtg1_esZW2xOQ-xsNqO47m55DA.woff
31 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
32 ms
mnpfi9pxYH-Go5UiibESIj8E0i7KZn-EPnyo3HZu7kw.woff
32 ms
show_ads.js
11 ms
zrt_lookup.html
23 ms
show_ads_impl.js
44 ms
ads
317 ms
osd.js
16 ms
ads
126 ms
ads
90 ms
search_g.png
147 ms
20130508065220.gif
1052 ms
audience
325 ms
jstag
68 ms
gpt.js
66 ms
cb=gapi.loaded_0
45 ms
pubads_impl_81.js
17 ms
225 ms
210 ms
223 ms
220 ms
204 ms
220 ms
428 ms
container.html
6 ms
reset.css
8 ms
entry-button.css
8 ms
bbtn-l_v3.png
10 ms
dfp.config.json
209 ms
blogs
261 ms
recaptcha__en.js
55 ms
sdk.js
54 ms
user.segment.json
261 ms
segmentation.js
29 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
29 ms
show.json
1085 ms
archive_module
233 ms
notices.count.json
963 ms
cnt
227 ms
redirect.js
93 ms
follow_button.6a78875565a912489e9aef879c881358.ja.html
35 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
76 ms
ads
403 ms
176 ms
xd_arbiter.php
51 ms
xd_arbiter.php
71 ms
globalheader.css
183 ms
api.js
25 ms
notices.count.json
660 ms
init
233 ms
dropdown@2x.png
305 ms
ajs.php
466 ms
ads
250 ms
jot.html
2 ms
fastbutton
63 ms
fastbutton
116 ms
fastbutton
206 ms
fastbutton
110 ms
fastbutton
146 ms
fastbutton
151 ms
fastbutton
156 ms
blogicon-regular.woff
304 ms
ajs.php
388 ms
ads
241 ms
hatena-follow-button.png
179 ms
info
184 ms
rs=AGLTcCPNzfuyiR2SRdOysTpopVYTZZwedQ
62 ms
cb=gapi.loaded_0
60 ms
cb=gapi.loaded_1
62 ms
grlryt2bdKIyfMSOhzd1eA.woff
50 ms
cb=gapi.loaded_0
14 ms
cb=gapi.loaded_1
15 ms
adsbygoogle.js
6 ms
lg.php
208 ms
ca-pub-5973519624968530.js
19 ms
ads
182 ms
ads
234 ms
ads
224 ms
lg.php
199 ms
alternatead-300x250-red.html
3 ms
ad
367 ms
alternatead-300x250-red-pc.html
3 ms
ad
355 ms
45855_banner.png
355 ms
45914_banner.png
542 ms
hatena-star-add-button.png
155 ms
comment.gif
323 ms
entries.json
577 ms
beacon.html
55 ms
pixel
17 ms
cs
329 ms
Pug
19 ms
set
327 ms
tap.php
8 ms
sync
9 ms
sync
316 ms
share_button.php
69 ms
sd
36 ms
share_button.php
115 ms
share_button.php
107 ms
share_button.php
100 ms
share_button.php
161 ms
share_button.php
163 ms
share_button.php
164 ms
vpc6VNjRPXV.js
78 ms
LVx-xkvaJ0b.png
81 ms
mapuser
149 ms
sync
158 ms
sync
290 ms
star.gif
152 ms
profile.gif
188 ms
profile.gif
425 ms
profile.gif
405 ms
profile.gif
353 ms
profile.gif
354 ms
profile.gif
355 ms
profile.gif
536 ms
profile.gif
676 ms
profile.gif
534 ms
profile.gif
547 ms
profile.gif
771 ms
profile.gif
627 ms
profile.gif
718 ms
profile.gif
724 ms
profile.gif
727 ms
negative.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
negative.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
negative.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 Negative.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 Negative.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.
negative.hateblo.jp
Open Graph data is detected on the main page of Negative Hateblo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: