Tools & Wizards About Us
spacely.co.jp screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    74% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

spacely.co.jp

360°パノラマVRなら「スペースリー」| 利用者数10,000以上、サービス継続率99%のクラウドVRソフト

Page Load Speed

10.4 sec in total

First Response

355 ms

Resources Loaded

7.9 sec

Page Rendered

2.1 sec

spacely.co.jp screenshot

About Website

Click here to check amazing Spacely content for Japan. Otherwise, check out these important facts you probably never knew about spacely.co.jp

「スペースリー」は利用者数7,200を超えるBtoB向けのクラウドVRソフトです。AIによる自動作成で初めての方でも30分で高品質VRが完成！集客や来店数UP、商談成約率UPやVR研修など企業の業績向上やDX推進に貢献します。

Visit spacely.co.jp

Key Findings

We analyzed Spacely.co.jp page load time and found that the first response time was 355 ms and then it took 10 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

spacely.co.jp performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.1 s

63/100

10%

Network Requests Diagram

spacely.co.jp

355 ms

spacely.co.jp

693 ms

info.spacely.co.jp

127 ms

xql4fhx.css

225 ms

jquery-3.6.0.js

64 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Spacely.co.jp, 80% (63 requests) were made to Info.spacely.co.jp and 5% (4 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source Info.spacely.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 211.8 kB (7%)

Content Size

3.2 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Spacely.co.jp main page is 3.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. 45% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 59.1 kB

  • Original 77.9 kB
  • After minification 77.9 kB
  • After compression 18.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 59.1 kB or 76% of the original size.

Image Optimization

-5%

Potential reduce by 152.6 kB

  • Original 3.1 MB
  • After minification 3.0 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. Spacely images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 85 B

  • Original 4.4 kB
  • After minification 4.3 kB
  • After compression 4.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 5 B

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.

Requests Breakdown

Number of requests can be reduced by 27 (36%)

Requests Now

75

After Optimization

48

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

spacely.co.jp

spacely.co.jp

355 ms

spacely.co.jp

spacely.co.jp

693 ms

info.spacely.co.jp

info.spacely.co.jp

127 ms

xql4fhx.css

xql4fhx.css

225 ms

jquery-3.6.0.js

jquery-3.6.0.js

64 ms

autoptimize_single_bed3250eba1f961467bc00c90ef1895f.js

autoptimize_single_bed3250eba1f961467bc00c90ef1895f.js

535 ms

215ffc287a.js

215ffc287a.js

78 ms

autoptimize_5cc9d4697019a2afb54e8a3475e1580b.css

autoptimize_5cc9d4697019a2afb54e8a3475e1580b.css

924 ms

autoptimize_single_6dd14de5fc8e8afac00f2638762c015e.css

autoptimize_single_6dd14de5fc8e8afac00f2638762c015e.css

602 ms

autoptimize_single_08130bb2033ac5659d492b834b6a2587.css

autoptimize_single_08130bb2033ac5659d492b834b6a2587.css

655 ms

jquery.min.js

jquery.min.js

877 ms

jquery-migrate.min.js

jquery-migrate.min.js

677 ms

jquery.bind-first-0.2.3.min.js

jquery.bind-first-0.2.3.min.js

1075 ms

js.cookie-2.1.3.min.js

js.cookie-2.1.3.min.js

1154 ms

autoptimize_single_a7cec92d1492b21855dd5c7736d7bed5.js

autoptimize_single_a7cec92d1492b21855dd5c7736d7bed5.js

1385 ms

slick.css

slick.css

58 ms

slick-theme.css

slick-theme.css

68 ms

animate.min.css

animate.min.css

70 ms

aos.css

aos.css

72 ms

modal-video.min.css

modal-video.min.css

53 ms

slick.min.js

slick.min.js

69 ms

aos.js

aos.js

83 ms

jquery-modal-video.min.js

jquery-modal-video.min.js

56 ms

autoptimize_single_f89263c0c2f24398a1df52eead69f5f8.js

autoptimize_single_f89263c0c2f24398a1df52eead69f5f8.js

1302 ms

addthis_widget.js

addthis_widget.js

56 ms

lazyload.min.js

lazyload.min.js

1420 ms

core.min.js

core.min.js

1631 ms

autoptimize_single_12c41646e8a93608b2dae468ac0c524a.js

autoptimize_single_12c41646e8a93608b2dae468ac0c524a.js

1780 ms

mobile-detect.min.js

mobile-detect.min.js

1870 ms

wp-embed.min.js

wp-embed.min.js

1766 ms

p.css

p.css

24 ms

css

css

30 ms

logo@2x.png

logo@2x.png

745 ms

top-word.svg

top-word.svg

942 ms

infographics_20231110_001-e1701162444200.png

infographics_20231110_001-e1701162444200.png

1326 ms

continue@2x.png

continue@2x.png

1440 ms

satisfy@2x.png

satisfy@2x.png

1496 ms

am@2x.png

am@2x.png

1206 ms

tt@2x.png

tt@2x.png

1290 ms

mf@2x.png

mf@2x.png

1146 ms

goodroom@2x.png

goodroom@2x.png

1711 ms

rc@2x.png

rc@2x.png

1968 ms

zaitaku.jpg

zaitaku.jpg

1832 ms

tab-sp@2x.png

tab-sp@2x.png

2036 ms

contents001.png

contents001.png

1815 ms

contents002.png

contents002.png

1877 ms

contents003.png

contents003.png

2449 ms

contents004.png

contents004.png

2013 ms

nasset.png

nasset.png

2883 ms

vivi.png

vivi.png

2969 ms

yamane.png

yamane.png

2507 ms

Union.png

Union.png

2565 ms

Union03.png

Union03.png

2402 ms

Union02.png

Union02.png

2766 ms

top-cta-card.png

top-cta-card.png

3816 ms

contents013.png

contents013.png

3229 ms

contents014.png

contents014.png

2940 ms

contents015.png

contents015.png

3125 ms

contents016.png

contents016.png

3601 ms

contents017.png

contents017.png

3642 ms

contents018.png

contents018.png

3249 ms

steps01.png

steps01.png

3748 ms

steps02.png

steps02.png

4323 ms

steps03.png

steps03.png

4232 ms

step001.png

step001.png

3746 ms

step002.png

step002.png

3277 ms

step003.png

step003.png

3782 ms

202401_IIFES%E5%87%BA%E5%B1%95%E3%83%90%E3%83%8A%E3%83%BC.png

202401_IIFES%E5%87%BA%E5%B1%95%E3%83%90%E3%83%8A%E3%83%BC.png

3716 ms

202311_7TH_press-release_1030_main.png

202311_7TH_press-release_1030_main.png

4055 ms

202310_AI%E7%A9%BA%E9%96%93%E8%A8%AD%E8%A8%88_press-release_1011_02.jpg

202310_AI%E7%A9%BA%E9%96%93%E8%A8%AD%E8%A8%88_press-release_1011_02.jpg

4145 ms

yakudachi-banner-index-1.png

yakudachi-banner-index-1.png

4245 ms

yakudachi-banner-index-2.png

yakudachi-banner-index-2.png

3887 ms

logo2@2x.png

logo2@2x.png

3369 ms

fb@2x.png

fb@2x.png

3389 ms

instagram@2x.png

instagram@2x.png

3788 ms

twitter@2x.png

twitter@2x.png

3762 ms

youtube@2x.png

youtube@2x.png

3277 ms

line@2x.png

line@2x.png

3706 ms

popup_blue.png

popup_blue.png

3663 ms

Accessibility Review

spacely.co.jp accessibility score

78

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

spacely.co.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

spacely.co.jp SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

Social Sharing Optimization

spacely.co.jp

Open Graph data is detected on the main page of Spacely. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: