7 sec in total
544 ms
6.3 sec
130 ms
Click here to check amazing Hatena content for Japan. Otherwise, check out these important facts you probably never knew about hatena.ne.jp
はてなが運営するポータルサイト。ブログもウェブアルバムもニュースも、はてながあればネットがさらに便利になります。
Visit hatena.ne.jpWe analyzed Hatena.ne.jp page load time and found that the first response time was 544 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
hatena.ne.jp performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value6.6 s
8/100
25%
Value13.6 s
2/100
10%
Value2,380 ms
5/100
30%
Value0.009
100/100
15%
Value22.2 s
1/100
10%
544 ms
1316 ms
602 ms
498 ms
642 ms
Our browser made a total of 237 requests to load all elements on the main page. We found that 18% of them (43 requests) were addressed to the original Hatena.ne.jp, 18% (43 requests) were made to Cdn.b.st-hatena.com and 17% (40 requests) were made to Cdn-ak.favicon.st-hatena.com. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Cdn-ak.f.st-hatena.com.
Page size can be reduced by 744.0 kB (16%)
4.8 MB
4.0 MB
In fact, the total size of Hatena.ne.jp main page is 4.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. 55% of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 106.9 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 106.9 kB or 77% of the original size.
Potential reduce by 154.1 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. Hatena images are well optimized though.
Potential reduce by 380.7 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 380.7 kB or 64% of the original size.
Potential reduce by 102.4 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. Hatena.ne.jp needs all CSS files to be minified and compressed as it can save up to 102.4 kB or 87% of the original size.
Number of requests can be reduced by 141 (61%)
230
89
The browser has sent 230 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hatena. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and as a result speed up the page load time.
hatena.ne.jp
544 ms
www.hatena.ne.jp
1316 ms
portal2012.css
602 ms
portal2013.js
498 ms
hatena_dfp2.js
642 ms
ad
452 ms
ad
373 ms
ad
410 ms
ad
457 ms
ad
532 ms
track.js
180 ms
gtm.js
43 ms
one-header.png
545 ms
http%3A%2F%2Fcdn-ak.b.st-hatena.com%2Fentryimage%2F280489193-1456715903.jpg
345 ms
cdn-ak.favicon.st-hatena.com
228 ms
23792-1455605974.jpg
35 ms
20160128173635.jpg
3578 ms
cdn-ak.favicon.st-hatena.com
222 ms
cdn-ak.favicon.st-hatena.com
222 ms
cdn-ak.favicon.st-hatena.com
223 ms
cdn-ak.favicon.st-hatena.com
227 ms
cdn-ak.favicon.st-hatena.com
222 ms
cdn-ak.favicon.st-hatena.com
413 ms
cdn-ak.favicon.st-hatena.com
225 ms
cdn-ak.favicon.st-hatena.com
226 ms
cdn-ak.favicon.st-hatena.com
225 ms
cdn-ak.favicon.st-hatena.com
228 ms
cdn-ak.favicon.st-hatena.com
228 ms
cdn-ak.favicon.st-hatena.com
230 ms
cdn-ak.favicon.st-hatena.com
422 ms
cdn-ak.favicon.st-hatena.com
231 ms
cdn-ak.favicon.st-hatena.com
231 ms
cdn-ak.favicon.st-hatena.com
232 ms
cdn-ak.favicon.st-hatena.com
233 ms
cdn-ak.favicon.st-hatena.com
232 ms
cdn-ak.favicon.st-hatena.com
236 ms
cdn-ak.favicon.st-hatena.com
233 ms
cdn-ak.favicon.st-hatena.com
421 ms
cdn-ak.favicon.st-hatena.com
237 ms
cdn-ak.favicon.st-hatena.com
237 ms
cdn-ak.favicon.st-hatena.com
236 ms
cdn-ak.favicon.st-hatena.com
238 ms
cdn-ak.favicon.st-hatena.com
838 ms
cdn-ak.favicon.st-hatena.com
238 ms
cdn-ak.favicon.st-hatena.com
238 ms
cdn-ak.favicon.st-hatena.com
244 ms
cdn-ak.favicon.st-hatena.com
244 ms
cdn-ak.favicon.st-hatena.com
246 ms
cdn-ak.favicon.st-hatena.com
245 ms
cdn-ak.favicon.st-hatena.com
607 ms
cdn-ak.favicon.st-hatena.com
247 ms
cdn-ak.favicon.st-hatena.com
253 ms
23787-1455093431.jpg
27 ms
23786-1455007269.jpg
27 ms
20160229093403.jpg
200 ms
20160229104723.png
185 ms
20151025190714.jpg
198 ms
20150915154557.jpg
176 ms
20160225191128.png
198 ms
http%3A%2F%2Fcdn-ak.b.st-hatena.com%2Fentryimage%2F280481373-1456706126.jpg
491 ms
http%3A%2F%2Fcdn-ak.b.st-hatena.com%2Fentryimage%2F280480961-1456705480.jpg
880 ms
http%3A%2F%2Fcdn-ak.b.st-hatena.com%2Fentryimage%2F280482437-1456707493.jpg
518 ms
http%3A%2F%2Ff.st-hatena.com%2Fimages%2Ffotolife%2FA%2FArufa%2F20160226%2F20160226133533.png%3F1456728472
687 ms
http%3A%2F%2Fimg.f.hatena.ne.jp%2Fimages%2Ffotolife%2Fh%2Fhatenabookmark%2F20160225%2F20160225174131.png
695 ms
http%3A%2F%2Ff.st-hatena.com%2Fimages%2Ffotolife%2Fh%2Fhatenablog%2F20160220%2F20160220012128.png
512 ms
logo-portal-top2@2x.png
161 ms
logo@2x.png
156 ms
search.png
160 ms
dropdown.gif
301 ms
usermenu.png
307 ms
notify@2x.png
316 ms
count-bg.png
319 ms
bookmark.png
320 ms
s-link-icon-bookmark@2x.png
341 ms
blog.png
448 ms
s-link-icon-blog@2x.png
460 ms
bkuma.png
476 ms
s-link-icon-bkuma@2x.png
477 ms
news.png
640 ms
s-link-icon-news@2x.png
512 ms
question.png
596 ms
s-link-icon-question@2x.png
613 ms
antenna.png
634 ms
s-link-icon-antenna@2x.png
638 ms
keyword.png
682 ms
s-link-icon-keyword@2x.png
742 ms
haiku.png
767 ms
s-link-icon-haiku@2x.png
793 ms
fotolife.png
799 ms
s-link-icon-fotolife@2x.png
848 ms
loading32.gif
917 ms
appicon-presso@2x.png
956 ms
appicon-bookmark@2x.png
983 ms
appicon-blog@2x.png
1183 ms
appicon-bkuma@2x.png
1040 ms
chrome-store-icon@2x.png
1068 ms
guest-button.png
1116 ms
my.json
1160 ms
header.en.js
1021 ms
widgets.js
6 ms
analytics.js
5 ms
dc.js
52 ms
collect
4 ms
collect
28 ms
collect
74 ms
like.php
93 ms
audience
361 ms
jstag
22 ms
gpt.js
10 ms
s-bookmark-icon@2x.png
996 ms
pubads_impl_81.js
20 ms
serial.portal.json
347 ms
container.html
20 ms
cdn-ak.favicon.st-hatena.com
38 ms
cdn-ak.favicon.st-hatena.com
460 ms
cdn-ak.favicon.st-hatena.com
200 ms
cdn-ak.favicon.st-hatena.com
205 ms
s-blog-icon@2x.png
971 ms
s-question-icon@2x.png
1053 ms
hotlist
784 ms
hotkeyword.json
729 ms
46020_banner.png
314 ms
23028_banner.jpg
302 ms
23320_banner.png
566 ms
00396.gif
194 ms
00363.gif
197 ms
00078.gif
191 ms
00250.gif
166 ms
00393.gif
163 ms
43733_banner.png
399 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
30 ms
segmentation.js
31 ms
hatena_bigmining.js
52 ms
00085.gif
111 ms
user.segment.json
1225 ms
redirect.js
49 ms
cnt
258 ms
cnt
338 ms
cnt
342 ms
cnt
339 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
11 ms
like.php
67 ms
00051.gif
41 ms
00954.gif
381 ms
00175.gif
30 ms
vpc6VNjRPXV.js
413 ms
LVx-xkvaJ0b.png
207 ms
login
711 ms
00131.gif
5 ms
segment
300 ms
00217.gif
5 ms
s-hatenanews-icon@2x.png
807 ms
jot
96 ms
00586.gif
350 ms
00029.gif
6 ms
00091.gif
6 ms
00176.gif
6 ms
00087.gif
5 ms
00251.gif
6 ms
00075.gif
5 ms
00226.gif
6 ms
00116.gif
7 ms
00225.gif
356 ms
00381.gif
191 ms
00100.gif
6 ms
00091.gif
6 ms
00150.gif
5 ms
ads
246 ms
00086.gif
13 ms
profile.gif
480 ms
anon-questioner.gif
161 ms
profile.gif
489 ms
profile.gif
681 ms
profile.gif
548 ms
profile.gif
551 ms
00036.gif
17 ms
00252.gif
4 ms
00224.gif
6 ms
00159.gif
5 ms
ajs.php
356 ms
osd.js
10 ms
00301.gif
6 ms
00035.gif
6 ms
00131.gif
5 ms
00045.gif
5 ms
00001.gif
5 ms
00026.gif
5 ms
00114.gif
5 ms
00118.gif
5 ms
00393.gif
5 ms
00007.gif
6 ms
00101.gif
188 ms
show_ads.js
4 ms
lg.php
169 ms
ca-pub-5973519624968530.js
35 ms
zrt_lookup.html
40 ms
show_ads_impl.js
50 ms
00000.gif
14 ms
00001.gif
5 ms
ads
182 ms
osd.js
8 ms
adj
74 ms
beacon
54 ms
SageOne_US_OwnerTrial_300x250.jpg
44 ms
lidar.js
22 ms
sbhK2lTE.js
41 ms
pixel
36 ms
push
67 ms
pixel
34 ms
pixel
31 ms
cTrvNaRi.html
15 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
4 ms
sd
5 ms
pixel
13 ms
activeview
14 ms
activeview
15 ms
activeview
20 ms
beacon.html
16 ms
dmp
299 ms
gtm.js
14 ms
sd
11 ms
pixel
19 ms
cs
434 ms
Pug
19 ms
set
152 ms
sync
8 ms
conversion_async.js
15 ms
tdim-0.11.2.js
11 ms
tap.php
5 ms
sync
369 ms
segment
276 ms
15 ms
41 ms
pageviews
11 ms
mapuser
151 ms
sync
211 ms
sync
204 ms
hatena.ne.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
hatena.ne.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
Missing source maps for large first-party JavaScript
hatena.ne.jp SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hatena.ne.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Hatena.ne.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.
hatena.ne.jp
Open Graph description is not detected on the main page of Hatena. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: