Tools & Wizards About Us
in-sq.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

in-sq.com

レンタルオフィス・バーチャルオフィスをお探しなら株式会社ハッチ・ワーク運営のインスクエア

Page Load Speed

6.2 sec in total

First Response

579 ms

Resources Loaded

5.2 sec

Page Rendered

405 ms

in-sq.com screenshot

About Website

Visit in-sq.com now to see the best up-to-date In Sq content for Japan and also check out these interesting facts you probably never knew about in-sq.com

インスクエアは株式会社ハッチ・ワークが運営するサービス付きレンタルオフィス・バーチャルオフィスです。室内内装とオフィスインフラを備え付けたオフィスビルで初期コストを抑えてオフィスを開業。有人受付、電話受付応対・大小さまざまなタイプの会議室を備えた、ワンランク上のレンタルオフィス・バーチャルオフィスです。

Visit in-sq.com

Key Findings

We analyzed In-sq.com page load time and found that the first response time was 579 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

in-sq.com performance score

0

Network Requests Diagram

in-sq.com

579 ms

in-sq.com

1003 ms

ytag.js

904 ms

gtm.js

99 ms

jquery-1.11.0.js

743 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 88% of them (69 requests) were addressed to the original In-sq.com, 3% (2 requests) were made to Connect.facebook.net and 1% (1 request) were made to S.yimg.jp. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain In-sq.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 204.5 kB (5%)

Content Size

4.4 MB

After Optimization

4.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of In-sq.com main page is 4.4 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. 50% of websites need less resources to load. Images take 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 55.2 kB

  • Original 69.7 kB
  • After minification 65.1 kB
  • After compression 14.5 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 55.2 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 96.7 kB

  • Original 4.2 MB
  • After minification 4.1 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. In Sq images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 50.8 kB

  • Original 102.7 kB
  • After minification 102.7 kB
  • After compression 52.0 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 50.8 kB or 49% of the original size.

CSS Optimization

-22%

Potential reduce by 1.9 kB

  • Original 8.6 kB
  • After minification 8.6 kB
  • After compression 6.7 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. In-sq.com needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (11%)

Requests Now

76

After Optimization

68

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of In Sq. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

in-sq.com

in-sq.com

579 ms

in-sq.com

in-sq.com

1003 ms

ytag.js

ytag.js

904 ms

gtm.js

gtm.js

99 ms

jquery-1.11.0.js

jquery-1.11.0.js

743 ms

allCommon.css

allCommon.css

710 ms

topCommon.css

topCommon.css

726 ms

element.js

element.js

47 ms

jquery.bxslider.js

jquery.bxslider.js

740 ms

247 ms

mieruca-hm.js

mieruca-hm.js

18 ms

sdk.js

sdk.js

80 ms

logo.jpg

logo.jpg

192 ms

eng.jpg

eng.jpg

187 ms

telbk.png

telbk.png

378 ms

headInquiryBtn.png

headInquiryBtn.png

371 ms

spMenu.png

spMenu.png

189 ms

spMenuTel.png

spMenuTel.png

550 ms

shdwBk.jpg

shdwBk.jpg

373 ms

nav_02.jpg

nav_02.jpg

380 ms

nav.jpg

nav.jpg

746 ms

banner_renew.png

banner_renew.png

1238 ms

btn_contact.png

btn_contact.png

567 ms

btn_instagram.png

btn_instagram.png

571 ms

ico_instagram.png

ico_instagram.png

726 ms

topView_09.jpg

topView_09.jpg

1267 ms

topView_01.jpg

topView_01.jpg

1482 ms

topView_02.jpg

topView_02.jpg

1483 ms

topView_03.jpg

topView_03.jpg

1955 ms

topView_04.jpg

topView_04.jpg

1663 ms

topView_06.jpg

topView_06.jpg

1426 ms

cCntrbk.jpg

cCntrbk.jpg

1453 ms

cCntrTop.jpg

cCntrTop.jpg

1610 ms

topPlan01.jpg

topPlan01.jpg

1655 ms

topPlan02.jpg

topPlan02.jpg

1681 ms

topPlan03.jpg

topPlan03.jpg

1671 ms

itduceIkebukuro.png

itduceIkebukuro.png

1790 ms

exteriorI01.jpg

exteriorI01.jpg

1842 ms

exteriorI02.jpg

exteriorI02.jpg

1852 ms

itduceUeno.png

itduceUeno.png

1861 ms

exteriorU01.jpg

exteriorU01.jpg

1872 ms

exteriorU02.jpg

exteriorU02.jpg

1973 ms

imgL01.jpg

imgL01.jpg

2030 ms

imgL02.jpg

imgL02.jpg

2050 ms

imgS01.jpg

imgS01.jpg

2229 ms

imgS02.jpg

imgS02.jpg

2064 ms

imgS03.jpg

imgS03.jpg

2140 ms

imgS04.jpg

imgS04.jpg

2101 ms

sdk.js

sdk.js

11 ms

43 ms

imgS05.jpg

imgS05.jpg

2037 ms

over_generation.jpg

over_generation.jpg

2062 ms

bn_TA_top.png

bn_TA_top.png

2071 ms

bnr_telecube_top.jpg

bnr_telecube_top.jpg

1963 ms

scCntrbk.jpg

scCntrbk.jpg

1975 ms

scCntrTop.jpg

scCntrTop.jpg

2032 ms

face_07.jpg

face_07.jpg

2042 ms

face_06.jpg

face_06.jpg

1891 ms

face_01.jpg

face_01.jpg

1882 ms

face_02.jpg

face_02.jpg

1946 ms

face_03.jpg

face_03.jpg

1801 ms

face_04.jpg

face_04.jpg

1849 ms

face_05.jpg

face_05.jpg

1377 ms

supImg02.jpg

supImg02.jpg

1352 ms

supImg03.jpg

supImg03.jpg

1209 ms

supImg04.jpg

supImg04.jpg

1247 ms

supImg05.jpg

supImg05.jpg

1227 ms

ftBnrTtl.jpg

ftBnrTtl.jpg

1302 ms

ServiceMembbnr_01.jpg

ServiceMembbnr_01.jpg

1191 ms

Membbnr_03.jpg

Membbnr_03.jpg

1160 ms

ftLinkChapInq.jpg

ftLinkChapInq.jpg

1162 ms

ftLinkChapServ.jpg

ftLinkChapServ.jpg

1212 ms

ftLinkChapAbut.jpg

ftLinkChapAbut.jpg

1211 ms

ftrLogo.jpg

ftrLogo.jpg

1182 ms

footer_instagram.png

footer_instagram.png

1147 ms

footerBk.png

footerBk.png

1150 ms

p_mark.png

p_mark.png

1163 ms

pd.js

pd.js

17 ms

SEO Factors

in-sq.com SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise In-sq.com 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 In-sq.com 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.

Social Sharing Optimization

in-sq.com

Open Graph description is not detected on the main page of In Sq. 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: