Tools & Wizards About Us
spacely.co.jp screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

spacely.co.jp

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

Page Load Speed

10 sec in total

First Response

343 ms

Resources Loaded

7.8 sec

Page Rendered

1.8 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 343 ms and then it took 9.6 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

58

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.1 s

31/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

343 ms

info.spacely.co.jp

182 ms

xql4fhx.css

109 ms

jquery-3.6.0.js

74 ms

autoptimize_single_bed3250eba1f961467bc00c90ef1895f.js

549 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Spacely.co.jp, 81% (64 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.5 sec) relates to the external source Info.spacely.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 209.5 kB (8%)

Content Size

2.7 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Spacely.co.jp main page is 2.7 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 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 56.9 kB

  • Original 75.4 kB
  • After minification 75.4 kB
  • After compression 18.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 56.9 kB or 75% of the original size.

Image Optimization

-6%

Potential reduce by 152.6 kB

  • Original 2.6 MB
  • After minification 2.5 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

-0%

Potential reduce by 0 B

  • Original 56 B

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.

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

74

After Optimization

47

  • Images
  • JavaScript
  • CSS

The browser has sent 74 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

343 ms

info.spacely.co.jp

info.spacely.co.jp

182 ms

xql4fhx.css

xql4fhx.css

109 ms

jquery-3.6.0.js

jquery-3.6.0.js

74 ms

autoptimize_single_bed3250eba1f961467bc00c90ef1895f.js

autoptimize_single_bed3250eba1f961467bc00c90ef1895f.js

549 ms

215ffc287a.js

215ffc287a.js

142 ms

autoptimize_b34613823c9b44a56edbb742b3bdf9c8.css

autoptimize_b34613823c9b44a56edbb742b3bdf9c8.css

951 ms

autoptimize_single_bf708d0b6e9635cfb7080ffb92ce1f72.css

autoptimize_single_bf708d0b6e9635cfb7080ffb92ce1f72.css

598 ms

autoptimize_single_b38fb931640cd8c4ac98dc73167a35a0.css

autoptimize_single_b38fb931640cd8c4ac98dc73167a35a0.css

612 ms

jquery.min.js

jquery.min.js

739 ms

jquery-migrate.min.js

jquery-migrate.min.js

594 ms

jquery.bind-first-0.2.3.min.js

jquery.bind-first-0.2.3.min.js

1073 ms

js.cookie-2.1.3.min.js

js.cookie-2.1.3.min.js

1135 ms

autoptimize_single_b536928a37a2635f577a787d3559b1a0.js

autoptimize_single_b536928a37a2635f577a787d3559b1a0.js

1301 ms

slick.css

slick.css

72 ms

slick-theme.css

slick-theme.css

80 ms

animate.min.css

animate.min.css

86 ms

aos.css

aos.css

75 ms

modal-video.min.css

modal-video.min.css

73 ms

slick.min.js

slick.min.js

85 ms

aos.js

aos.js

88 ms

jquery-modal-video.min.js

jquery-modal-video.min.js

87 ms

autoptimize_single_f89263c0c2f24398a1df52eead69f5f8.js

autoptimize_single_f89263c0c2f24398a1df52eead69f5f8.js

1296 ms

addthis_widget.js

addthis_widget.js

67 ms

lazyload.min.js

lazyload.min.js

1297 ms

core.min.js

core.min.js

1627 ms

autoptimize_single_00d212ab5fd7f1a73fd1958f973dc36b.js

autoptimize_single_00d212ab5fd7f1a73fd1958f973dc36b.js

1808 ms

mobile-detect.min.js

mobile-detect.min.js

1836 ms

wp-embed.min.js

wp-embed.min.js

1704 ms

asyncdc.min.js

asyncdc.min.js

1717 ms

p.css

p.css

18 ms

css

css

32 ms

logo@2x.png

logo@2x.png

618 ms

top-word.svg

top-word.svg

1161 ms

infographics_20231110_001-e1701162444200.png

infographics_20231110_001-e1701162444200.png

1382 ms

continue@2x.png

continue@2x.png

1327 ms

satisfy@2x.png

satisfy@2x.png

1457 ms

am@2x.png

am@2x.png

842 ms

tt@2x.png

tt@2x.png

1179 ms

mf@2x.png

mf@2x.png

1553 ms

goodroom@2x.png

goodroom@2x.png

1698 ms

rc@2x.png

rc@2x.png

1552 ms

zaitaku.jpg

zaitaku.jpg

1826 ms

tab-sp@2x.png

tab-sp@2x.png

2420 ms

contents001.png

contents001.png

2143 ms

contents002.png

contents002.png

2266 ms

contents003.png

contents003.png

2291 ms

contents004.png

contents004.png

2418 ms

nasset.png

nasset.png

2463 ms

vivi.png

vivi.png

3186 ms

yamane.png

yamane.png

3274 ms

Union.png

Union.png

2825 ms

Union03.png

Union03.png

3121 ms

Union02.png

Union02.png

3125 ms

top-cta-card.png

top-cta-card.png

3386 ms

contents013.png

contents013.png

3486 ms

contents014.png

contents014.png

3805 ms

contents015.png

contents015.png

3834 ms

contents016.png

contents016.png

3874 ms

contents017.png

contents017.png

3515 ms

contents018.png

contents018.png

3600 ms

steps01.png

steps01.png

4460 ms

steps02.png

steps02.png

4532 ms

steps03.png

steps03.png

3599 ms

step001.png

step001.png

3988 ms

step002.png

step002.png

3511 ms

step003.png

step003.png

3819 ms

20240921_%E3%82%A6%E3%82%A3%E3%83%BC%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%9E%E3%82%AC%E3%82%B8%E3%83%B3%E3%83%90%E3%83%8A%E3%83%BC_%E4%B8%8D%E5%8B%95%E7%94%A3%E3%83%8B%E3%83%A5%E3%83%BC%E3%82%B9.png

20240921_%E3%82%A6%E3%82%A3%E3%83%BC%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%9E%E3%82%AC%E3%82%B8%E3%83%B3%E3%83%90%E3%83%8A%E3%83%BC_%E4%B8%8D%E5%8B%95%E7%94%A3%E3%83%8B%E3%83%A5%E3%83%BC%E3%82%B9.png

3597 ms

%E3%80%90PR%E3%80%91%E5%90%88%E5%90%8C%E8%AA%BF%E6%9F%BB%E3%83%AA%E3%83%AA%E3%83%BC%E3%82%B92024_%E5%A4%89%E6%9B%B4.jpg

%E3%80%90PR%E3%80%91%E5%90%88%E5%90%8C%E8%AA%BF%E6%9F%BB%E3%83%AA%E3%83%AA%E3%83%BC%E3%82%B92024_%E5%A4%89%E6%9B%B4.jpg

4425 ms

20240917_%E3%82%A6%E3%82%A3%E3%83%BC%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%9E%E3%82%AC%E3%82%B8%E3%83%B3_%E3%83%8B%E3%83%A5%E3%83%BC%E3%82%B9%E3%82%B3%E3%83%A9%E3%83%A0%E7%A0%94%E4%BF%AE-1.png

20240917_%E3%82%A6%E3%82%A3%E3%83%BC%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%9E%E3%82%AC%E3%82%B8%E3%83%B3_%E3%83%8B%E3%83%A5%E3%83%BC%E3%82%B9%E3%82%B3%E3%83%A9%E3%83%A0%E7%A0%94%E4%BF%AE-1.png

3574 ms

yakudachi-banner-index-1.png

yakudachi-banner-index-1.png

3912 ms

yakudachi-banner-index-2.png

yakudachi-banner-index-2.png

3956 ms

logo2@2x.png

logo2@2x.png

3728 ms

fb@2x.png

fb@2x.png

3416 ms

instagram@2x.png

instagram@2x.png

3407 ms

twitter@2x.png

twitter@2x.png

3788 ms

youtube@2x.png

youtube@2x.png

3506 ms

line@2x.png

line@2x.png

3561 ms

popup_blue.png

popup_blue.png

3602 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: