7.4 sec in total
462 ms
5.8 sec
1.1 sec
Visit spacee.jp now to see the best up-to-date Spacee content for Japan and also check out these interesting facts you probably never knew about spacee.jp
レンタルスペース・貸し会議室・ミーティングルーム・セミナー会場・レンタルルームを検索するならスペイシー。24時間365日予約受付中!駅、エリア、利用用途などご希望の条件に合わせて検索できます。
Visit spacee.jpWe analyzed Spacee.jp page load time and found that the first response time was 462 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
spacee.jp performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value14.0 s
0/100
25%
Value13.0 s
2/100
10%
Value2,540 ms
4/100
30%
Value0
100/100
15%
Value24.9 s
0/100
10%
462 ms
778 ms
1272 ms
69 ms
65 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 15% of them (15 requests) were addressed to the original Spacee.jp, 51% (50 requests) were made to Cdn-image.spacee.jp and 24% (24 requests) were made to Cdn.spacee.jp. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Cdn-image.spacee.jp.
Page size can be reduced by 143.7 kB (9%)
1.6 MB
1.5 MB
In fact, the total size of Spacee.jp main page is 1.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 773.5 kB which makes up the majority of the site volume.
Potential reduce by 143.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 143.7 kB or 72% of the original size.
Potential reduce by 0 B
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. Spacee images are well optimized though.
Potential reduce by 13 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. This website has mostly compressed JavaScripts.
Potential reduce by 8 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. Spacee.jp has all CSS files already compressed.
Number of requests can be reduced by 19 (20%)
93
74
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Spacee. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
spacee.jp
462 ms
spacee.jp
778 ms
www.spacee.jp
1272 ms
yCAyoozT4QCr7w.js
69 ms
pc_app-8365dcecd07bf92e8e248dd3d83afdea4e59d4382a118485de35e059e0a4f1ee.css
65 ms
add-pc_app-bbe79dc430336a819d9b93f4d6cbd4acdf9e62b3dd2d441d5cbca971096ef2f9.css
132 ms
font-awesome.css
37 ms
main-83170202e3a43d1dc5f3.css
1119 ms
app-17d5169eb781ac4eb7e1.css
770 ms
application-b0c638143e112a23bd1546a0a7d8250456cf38d9d260c7e17bcfcb3cc00dac22.js
94 ms
pc_renewal-1cebf0f45850a3c7896f8bf4df61535e0b288a9ea2d56d727956876e2e221ee6.js
78 ms
4046949.js
115 ms
app-d1c4ab5a80ff06d31396.js
1415 ms
vcd15cbe7772f49c399c6a5babf22c1241717689176015
97 ms
css2
34 ms
css2
49 ms
gtm.js
240 ms
app-icon-4ba5187ab080ddaf768b5591305d740b8a39a4f4785c1049e475271d920d3834.svg
172 ms
menu2_01_2x.webp
207 ms
logo-c01d5345b8c7b4fe56c42d8b5f7bd0eee8dac0aa33aab9b0ff54f5f7590ca57c.svg
173 ms
mobile_app_store_badge_ios-ab86ccae68f037058ccd201423a8e51299dc33792f931f91e7d52e3be47d04ea.svg
197 ms
mobile_app_store_badge_android-46de2f1e687a7d4f611b0349e82f145da55596935aebf402aa2311f1e612c27b.svg
202 ms
area_tokyo-17d913d87abbd527f165b940ff477929b9f52cdfa34aa300c41e48816a53bc2f.webp
184 ms
area_kanagawa-755895f688b5c53a344c557675cfa7b70ad8356a3dc7ba09041e61d1fc686014.webp
189 ms
area_aichi-218a421d256b0b1ffd37b7ead07d52accb59533c2d1184089a8ec8b842d66f68.webp
194 ms
area_osaka-699f57f0c8426175c6116dc04488150cd05e3a336ed168bfb57451fbf0ad532f.webp
197 ms
area_fukuoka-196817593c0931b82ce330b4cd79ee75c5aa84e5ab849ed60715e30c8b6e043a.webp
205 ms
premium-2col-7e965e18b96ed0a7ee20deee095ce0e45402e5fd596f4bc576f355fc6df5964e.webp
213 ms
provider-entry-2col-565be079306fca59d37f55b758eeeb0a05d1ffc25730de10fb1d59868f8c673c.webp
211 ms
corporate-service-2col-8d6d979693bdd5d253c7041e123c7361809a7dcce21bf012e3d414564d577d2c.webp
218 ms
why1-bc8bd0d18d20e6486dfce5bea77a61c73217f85456668e177b48f3cadb86bd27.webp
216 ms
why2-d16538fb2b62760ccf2c23d178af345158fc226e29be89eeb75c0905d7f04ca9.webp
224 ms
why3-f3ec46e3c5d9bcf1cd128dd1d71bd4f308e02b8e89b8a6f574e0935d354137bb.webp
224 ms
why4-b7d212f77597f8d549cdfeb0371bf9332a11cb81ce5681d39cc744f0984eb680.webp
241 ms
hiw1-3925c789f832e7c6137d22602d3d9dda4615a37e72268f5706282c4099cfdccc.webp
242 ms
hiw2-41d20583b735a23c02d99a6013bafc1c9ac45b7df82ec2dfd171c63702176b43.webp
238 ms
hiw3-cd65f85a50cdfa7114749d2b8775e60f231bf05d4bb3a9e9ecd687803489b3bc.webp
240 ms
logo-white-1c4f28fb78b68a7c01659e0b76f21f003e9963ca9f1df2815d1ddb8907a4f6a2.svg
237 ms
menu2_02_2x.webp
221 ms
menu2_03_2x.webp
238 ms
menu2_04_2x.webp
244 ms
menu2_06_2x.webp
247 ms
menu2_07_2x.webp
243 ms
menu2_08_2x.webp
233 ms
menu2_09_2x.webp
239 ms
menu2_10_2x.webp
247 ms
menu2_11_2x.webp
277 ms
menu2_12_2x.webp
276 ms
menu2_13_2x.webp
279 ms
menu2_14_2x.webp
278 ms
menu2_15_2x.webp
280 ms
menu2_16_2x.webp
280 ms
menu2_17_2x.webp
283 ms
menu2_18_2x.webp
282 ms
menu2_19_2x.webp
281 ms
menu2_20_2x.webp
286 ms
menu2_21_2x.webp
283 ms
menu2_22_2x.webp
287 ms
banner_%E3%83%AF%E3%83%B3%E3%82%B3%E3%82%A4%E3%83%B3__4_.jpg
1010 ms
banner_Add_a_heading.jpg
1065 ms
banner_tokushu_400_potluckparty.jpg
1244 ms
banner_tokushu_400_lastminutes.jpg
327 ms
banner_kitchen.jpg
1065 ms
banner_%E5%B0%91%E4%BA%BA%E6%95%B0%E5%90%91%E3%81%91%E3%81%AE%E8%B2%B8%E3%81%97%E4%BC%9A%E8%AD%B0%E5%AE%A4%E3%83%90%E3%83%8A%E3%83%BC.png
1429 ms
banner_tele-work.png
1417 ms
banner_morning.png
2275 ms
banner_%E3%83%AF%E3%83%B3%E3%82%B3%E3%82%A4%E3%83%B3__16_.jpg
1868 ms
banner_tokushu_400_ouchidate.jpg
1826 ms
banner_tokushu_400_over100space.jpg
2035 ms
banner_tokushu_400_over60_meeting.jpg
2214 ms
menu1_01_2x.webp
1447 ms
menu1_02_2x.webp
1465 ms
menu1_03_2x.webp
1495 ms
keyvisual01-3d69c32cca3930fe7df8.jpg
1577 ms
search-36ead8cb44eadf5fec57.svg
863 ms
pin-gray-527524523daa632aeab9.svg
913 ms
user-gray-0f69674763128f7cda50.svg
871 ms
calendar-gray-4abb80189e3c132968eb.svg
879 ms
watch-gray-bb8ff7c6e4e610f482b4.svg
1105 ms
arrow-right-white-bb16fe5abbf627471958.svg
1577 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf
204 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf
260 ms
arrow-signin-1328f7466bd738544894.svg
1515 ms
menu1_04_2x.webp
1312 ms
menu1_05_2x.webp
1307 ms
menu1_06_2x.webp
1309 ms
menu1_07_2x.webp
1321 ms
menu1_08_2x.webp
1335 ms
menu1_09_2x.webp
1353 ms
menu1_10_2x.webp
1388 ms
menu1_11_2x.webp
1406 ms
menu1_12_2x.webp
1425 ms
menu1_14_2x.webp
1410 ms
menu1_15_2x.webp
1433 ms
menu1_16_2x.webp
1450 ms
menu1_17_2x.webp
1472 ms
menu1_13_2x.webp
1487 ms
main.js
14 ms
spacee.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Form elements do not have associated labels
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.
spacee.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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
spacee.jp SEO score
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
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spacee.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 Spacee.jp main page’s claimed encoding is . 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.
spacee.jp
Open Graph data is detected on the main page of Spacee. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: