9.8 sec in total
2.4 sec
7.2 sec
214 ms
Click here to check amazing Blog So Net content for Japan. Otherwise, check out these important facts you probably never knew about blog.so-net.ne.jp
おトクなブログを選ぶならSSブログ。1アカウントで5ブログ・5ギガの大容量。デザインカスタマイズも自由自在。すべて無料で利用できます。
Visit blog.so-net.ne.jpWe analyzed Blog.so-net.ne.jp page load time and found that the first response time was 2.4 sec and then it took 7.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.
blog.so-net.ne.jp performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value12.4 s
0/100
25%
Value18.1 s
0/100
10%
Value10,170 ms
0/100
30%
Value0.285
42/100
15%
Value20.6 s
2/100
10%
2367 ms
441 ms
946 ms
363 ms
548 ms
Our browser made a total of 214 requests to load all elements on the main page. We found that 66% of them (142 requests) were addressed to the original Blog.so-net.ne.jp, 4% (9 requests) were made to Pagead2.googlesyndication.com and 3% (7 requests) were made to Web-jp.ad-v.jp. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Blog.so-net.ne.jp.
Page size can be reduced by 1.0 MB (47%)
2.2 MB
1.2 MB
In fact, the total size of Blog.so-net.ne.jp main page is 2.2 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. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 65.7 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 65.7 kB or 80% of the original size.
Potential reduce by 20.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. Blog So Net images are well optimized though.
Potential reduce by 880.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 880.3 kB or 70% of the original size.
Potential reduce by 65.2 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. Blog.so-net.ne.jp needs all CSS files to be minified and compressed as it can save up to 65.2 kB or 85% of the original size.
Number of requests can be reduced by 104 (50%)
206
102
The browser has sent 206 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog So Net. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
blog.so-net.ne.jp
2367 ms
common.css
441 ms
portal.css
946 ms
global.js
363 ms
myblog_cms.js
548 ms
popup.js
366 ms
tag.js
724 ms
client_info.js
549 ms
event.js
585 ms
text_range.js
728 ms
layer.js
913 ms
word_processor.js
873 ms
yahoo-min.js
1083 ms
event-min.js
1089 ms
dom-min.js
1165 ms
element-min.js
1277 ms
dragdrop-min.js
1099 ms
animation-min.js
1159 ms
container-min.js
1845 ms
connection-min.js
1451 ms
tabview-min.js
1256 ms
menu-min.js
1546 ms
seesaa.js
1601 ms
JSON.js
1413 ms
Cookiejar.js
1280 ms
panel.js
1392 ms
container.css
1453 ms
menu.css
1644 ms
myblog_overyui.css
1559 ms
blog.css
495 ms
detect
409 ms
tag_cloud.js
774 ms
detect
327 ms
s_code.js
679 ms
sc_blog.js
350 ms
detect
327 ms
so-net.gif
195 ms
h1_blog.gif
183 ms
logo_blog_H.gif
161 ms
tools_bg.gif
186 ms
tools_btn_bg3.gif
148 ms
login_sts_bg.gif
184 ms
login_sts_login.gif
294 ms
btn_search.gif
318 ms
btn_more_L.gif
363 ms
s_y2k7d00000330.png
365 ms
noimage.gif
366 ms
s_H28b15.png
389 ms
s_1-beb8a.png
441 ms
s_blg39820A.png
473 ms
s_IMG_4471.png
545 ms
s_040598.png
546 ms
s_tokyomarathon2016img_4-40ca8.png
549 ms
s_E8BE9EE8A1A8.png
583 ms
s_E88BA5E697A6E982A3E381AEE6BF80E38284E3819BE6AF94E8BC83E794BBE5838F-52470.png
586 ms
s_510E7B3BBE6B581E6B0B7E3838EE383ADE38383E382B3E58FB7.png
630 ms
s_20160126-OHT1I50078-T.png
736 ms
m_2016-03-01T00:15:38-cdaac.jpg
1326 ms
m_2016-03-01T00:15:15-12fea.jpg
1304 ms
m_2016-03-01T00:02:23-ccc30.JPG
815 ms
m_2016-02-29T23:36:48-4d441.gif
735 ms
m_2016-02-29T22:59:45-7feed.jpg
952 ms
m_2016-02-29T22:57:38-cfb01.jpg
1098 ms
m_2016-02-29T22:39:19-58d4f.jpg
1027 ms
m_2016-02-29T22:35:38-b7a6c.jpg
970 ms
m_2016-02-29T22:22:14-73c19.JPG
1740 ms
m_2016-02-29T22:17:16-77d7f.jpg
1178 ms
m_2016-02-29T22:15:58-c35b5.jpg
1342 ms
m_2016-02-29T22:11:32-ce709.JPG
1460 ms
icn_mappie.jpg
1384 ms
icn_uotake.jpg
1462 ms
midorikawa.jpg
811 ms
browserDataDetect.js
329 ms
icn_watai.jpg
1352 ms
icn_cozy.jpg
1321 ms
icn_hagitomo.jpg
1395 ms
icn_new.gif
1477 ms
icn_butsuyoku.jpg
1477 ms
icn_okenkikaku.jpg
1434 ms
icn_ses.jpg
1391 ms
icn_jta.jpg
1456 ms
icn_sengyo.jpg
1411 ms
icn_kato.jpg
1465 ms
_s_wordrobe.png
1469 ms
detected
332 ms
_s_sengoshi.png
1477 ms
_s_nanagoo2.png
1463 ms
_s_ryo1216.png
1494 ms
_s_ya42853.png
1378 ms
_s_hidepachi.png
1705 ms
_s_y-k-f-c.png
1700 ms
_s_07-yutaji.png
1464 ms
_s_xml_xsl.png
1479 ms
_s_okina-02.png
1439 ms
adsbygoogle.js
4 ms
CM8Function.js
105 ms
ca-pub-8889161714405753.js
25 ms
zrt_lookup.html
29 ms
show_ads_impl.js
43 ms
profile_notavailable.gif
1488 ms
_s_hi-mylife.png
1516 ms
ads
130 ms
_s_mercariguide.png
1432 ms
osd.js
6 ms
_s_cat-collection-app.png
1427 ms
detected
324 ms
372 ms
adj
65 ms
beacon
41 ms
medium_521.jpg
1407 ms
medium_520.jpg
1454 ms
medium_403.jpg
1374 ms
medium_514.jpg
1330 ms
showad.js
9 ms
showad.js
26 ms
AdServerServlet
84 ms
medium_746.jpg
1210 ms
PugMaster
26 ms
p-P7x87XHnVfbWr.gif
12 ms
pixel
25 ms
sync
9 ms
9 ms
generic
6 ms
demconf.jpg
6 ms
Pug
57 ms
blank.gif
3 ms
generic
5 ms
Pug
51 ms
Pug
47 ms
event
21 ms
Pug
42 ms
detected
331 ms
medium_630.jpg
1121 ms
36 ms
0
102 ms
pixel
34 ms
lidar.js
15 ms
sbhK2lTE.js
68 ms
medium_1185.jpg
1224 ms
HTKL00533001.jpg
155 ms
adServer.bs
107 ms
verify_selector.js
148 ms
blank.gif
150 ms
medium_1186.jpg
1194 ms
pixel
99 ms
pixel
99 ms
cTrvNaRi.html
21 ms
POSTPET_banner300-48.png
1171 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
6 ms
blog.so-net_300-48.jpg
1146 ms
digibook_090924.jpg
1327 ms
nicotto_bnr.png
1117 ms
s5323069563601
9 ms
verifyr.js
33 ms
facebook_momo02.png
1114 ms
client-verify.adtricity.com
372 ms
beacon.js
24 ms
0
13 ms
bg.png
29 ms
adchoices.en.png
56 ms
qr.gif
1108 ms
mailto_bg.gif
1123 ms
ads
205 ms
icn_new.gif
1059 ms
btn_top.gif
1132 ms
btn_guest.gif
1114 ms
sd
74 ms
icn_search.gif
1090 ms
main_bg2.jpg
1105 ms
main_bg_090618.jpg
1944 ms
btn_regist_top201007.gif
1148 ms
guide_makeblog.gif
1141 ms
aclk
49 ms
pixel
34 ms
adj
50 ms
beacon
35 ms
arrow_L_bk.gif
1115 ms
pixel
30 ms
express_flash_html_inpage_rendering_lib_200_120.js
99 ms
guide_searchblog.gif
1076 ms
guide_searchblogger.gif
1111 ms
Pix-1x1.gif
51 ms
ttl_theme_m.gif
1189 ms
BA163-728x90.html
17 ms
activeview
13 ms
runtime.js
91 ms
dotline_tate_s.gif
1111 ms
menu_on_bg_tm1.gif
1059 ms
arrow_orange.gif
1092 ms
btn_more.gif
969 ms
ttl_entries_m.gif
1022 ms
menu_on_bg.gif
1088 ms
icn_no1.gif
1088 ms
icn_no2.gif
1094 ms
icn_no3.gif
1080 ms
icn_no4.gif
1060 ms
icn_no5.gif
1131 ms
icn_no6.gif
1121 ms
icn_no7.gif
1104 ms
icn_no8.gif
1080 ms
icn_no9.gif
1136 ms
icn_no10.gif
1128 ms
ttl_officialblogs_m.gif
1153 ms
ttl_userblogs_m.gif
1145 ms
ttl_design_m.gif
1118 ms
tips_sankakuRL.gif
1104 ms
ttl_wn_m.gif
1211 ms
pr_head.gif
1200 ms
ttl_tag_m.gif
1168 ms
dotline.gif
1112 ms
arrow_foot.gif
1104 ms
activeview
18 ms
activeview
28 ms
dest4.html
17 ms
blog.so-net.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
Image elements do not have [alt] attributes
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.
blog.so-net.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
blog.so-net.ne.jp SEO score
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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.so-net.ne.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Blog.so-net.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.
blog.so-net.ne.jp
Open Graph description is not detected on the main page of Blog So Net. 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: