7.7 sec in total
1.1 sec
6.1 sec
489 ms
Welcome to so-office.jp homepage info - get ready to check So Office best content for Japan right away, or after learning these important things about so-office.jp
都内セットアップオフィスの掲載多数!移転コストはトータル比較する時代。費用メリットをしっかり把握!セットアップオフィス、居抜きオフィスはそのまんまオフィスにお任せください。
Visit so-office.jpWe analyzed So-office.jp page load time and found that the first response time was 1.1 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
so-office.jp performance score
1090 ms
340 ms
349 ms
11 ms
739 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 93% of them (82 requests) were addressed to the original So-office.jp, 3% (3 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain So-office.jp.
Page size can be reduced by 117.4 kB (17%)
704.4 kB
587.0 kB
In fact, the total size of So-office.jp main page is 704.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 592.1 kB which makes up the majority of the site volume.
Potential reduce by 22.0 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 22.0 kB or 79% of the original size.
Potential reduce by 39.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. So Office images are well optimized though.
Potential reduce by 10.9 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 10.9 kB or 35% of the original size.
Potential reduce by 45.1 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. So-office.jp needs all CSS files to be minified and compressed as it can save up to 45.1 kB or 84% of the original size.
Number of requests can be reduced by 18 (21%)
84
66
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of So Office. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
so-office.jp
1090 ms
import.css
340 ms
jquery.superbox.css
349 ms
jquery.min.js
11 ms
jquery.superbox.js
739 ms
slidemenu_vertical.js
371 ms
reset.css
174 ms
main.css
675 ms
ga.js
89 ms
background.jpg
518 ms
headerTopBgR201211R.gif
522 ms
headerTopBgR201211L.gif
371 ms
gnaviTop.jpg
171 ms
gnaviSub_taikyo.png
371 ms
gnaviSub_kariru.png
339 ms
gnaviSub_owner.png
540 ms
gnaviSub_voice.png
508 ms
headerLogin.gif
556 ms
headerTopBg201211.gif
555 ms
headerLogo.gif
676 ms
headerBtn_karitai.jpg
688 ms
headerBtn_taikyo.jpg
694 ms
headerTopBgR201211.gif
1077 ms
blank.gif
738 ms
bg_separator.jpg
739 ms
top_banner.jpg
1011 ms
topPickupH2.gif
859 ms
topPickupBg.gif
867 ms
611_1.jpg
1106 ms
badge_dicker.gif
922 ms
jre.gif
1031 ms
bit-arrow.gif
1041 ms
581_1.jpg
1659 ms
mita.gif
1178 ms
hibiya.gif
1202 ms
page-list-bg.gif
1214 ms
page-list-chiyoda.gif
1253 ms
page-list-chuo.gif
1288 ms
page-list-minato.gif
1346 ms
page-list-shinjuku.gif
1374 ms
page-list-shibuya.gif
1388 ms
page-list-other.gif
1432 ms
page-list-all.gif
1472 ms
649_1.jpg
1851 ms
badge_new.gif
1546 ms
inpage_linkid.js
3 ms
__utm.gif
16 ms
collect
61 ms
ga-audiences
41 ms
badge_wanted.gif
1401 ms
shinjuku.gif
1282 ms
648_1.jpg
1665 ms
647_1.jpg
1529 ms
infoIcon_signed.gif
1236 ms
infoIcon_info.gif
1285 ms
602_1.jpg
1331 ms
hanzomon.gif
1380 ms
606_1.jpg
1425 ms
marunouchi.gif
1481 ms
612_1.jpg
1352 ms
ginza.gif
1385 ms
rightBg.gif
1398 ms
right01title.gif
1420 ms
right01Bg.gif
1456 ms
right02title.gif
1357 ms
right02Bg.gif
1351 ms
right03title.gif
1320 ms
right03Bg.gif
1256 ms
rightAreaBg.gif
1307 ms
rightArea01.gif
1323 ms
rightArea02.gif
1326 ms
rightArea03.gif
1298 ms
rightArea04.gif
1236 ms
rightArea05.gif
1235 ms
rightArea06.gif
1303 ms
rightArea07.gif
1277 ms
rightRoundBg.gif
1295 ms
rightBtn_reg.jpg
1239 ms
rightRoundFoot.gif
1212 ms
sideLoginbt.jpg
1223 ms
rightRoundBgMedia.gif
1265 ms
blog.jpg
1227 ms
sfbs.jpg
1221 ms
chintai.jpg
1207 ms
rightTel.gif
1145 ms
footerBit.gif
1128 ms
loader.gif
1140 ms
www.so-office.jp
1398 ms
so-office.jp SEO score
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise So-office.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 So-office.jp main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
so-office.jp
Open Graph description is not detected on the main page of So Office. 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: