4.2 sec in total
63 ms
3.2 sec
986 ms
Welcome to spacetokyo.jp homepage info - get ready to check Spacetokyo best content right away, or after learning these important things about spacetokyo.jp
腕時計の歴代人気モデルを再現した「復刻版モデル」は、流行に左右されないデザインガ魅力です。ブランドの歴史を象徴するモデルが多いので、特別の1本になります。今回は、復刻版モデルと伝統的なデザインを取り入れたモデルを紹介していきます。この記事を読んで、各ブランドのこだわりや特徴を理解してほしいと思います。
Visit spacetokyo.jpWe analyzed Spacetokyo.jp page load time and found that the first response time was 63 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
spacetokyo.jp performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value13.9 s
0/100
25%
Value5.5 s
55/100
10%
Value970 ms
28/100
30%
Value0
100/100
15%
Value13.4 s
11/100
10%
63 ms
55 ms
10 ms
28 ms
38 ms
Our browser made a total of 143 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Spacetokyo.jp, 80% (114 requests) were made to Thewatchcompany.co.jp and 4% (6 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Thewatchcompany.co.jp.
Page size can be reduced by 293.7 kB (27%)
1.1 MB
800.4 kB
In fact, the total size of Spacetokyo.jp main page is 1.1 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. 75% 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 416.9 kB which makes up the majority of the site volume.
Potential reduce by 252.9 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 252.9 kB or 81% of the original size.
Potential reduce by 7.3 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. Spacetokyo images are well optimized though.
Potential reduce by 33.4 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.
Potential reduce by 18 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. Spacetokyo.jp has all CSS files already compressed.
Number of requests can be reduced by 112 (81%)
139
27
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Spacetokyo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 113 to 1 for JavaScripts and as a result speed up the page load time.
spacetokyo.jp
63 ms
55 ms
blog.min.css
10 ms
require.min.js
28 ms
requirejs-min-resolver.min.js
38 ms
mixins.min.js
38 ms
requirejs-config.min.js
37 ms
api.js
80 ms
addthis_widget.js
178 ms
jquery.mobile.custom.min.js
14 ms
dataPost.min.js
7 ms
bootstrap.min.js
12 ms
translate-inline.min.js
11 ms
jquery.min.js
145 ms
mute-migrate.min.js
22 ms
template.min.js
20 ms
confirm.min.js
20 ms
main.min.js
109 ms
translate.min.js
118 ms
recaptcha__en.js
298 ms
gtm.js
400 ms
space.gif
1899 ms
ja_icon.png
33 ms
en_icon.png
31 ms
menu_bg.gif
32 ms
logo-header.svg
34 ms
twc_logo.svg
31 ms
tax_free.png
187 ms
Loader.gif
163 ms
placeholder.jpg
186 ms
post_5_4992.jpg
198 ms
post_5_4962_s.jpg
186 ms
post_5_5017_s.jpg
186 ms
tel_icon.svg
197 ms
twc-icon-contact.svg
195 ms
twc_blog_topbanner.jpg
319 ms
MiniCart.js
202 ms
customer-data.min.js
195 ms
translator.min.js
204 ms
polyfill.min.js
1858 ms
domReady.min.js
202 ms
quick-search.min.js
202 ms
advanceSearch.min.js
203 ms
theme.min.js
202 ms
lazyload.min.js
205 ms
underscore-min.js
190 ms
modal.min.js
202 ms
mage.min.js
201 ms
scripts.min.js
194 ms
common.min.js
275 ms
jquery-migrate.min.js
278 ms
jquery-ui.min.js
161 ms
jquery.cookie.min.js
276 ms
icons.woff
155 ms
knockout-min.js
122 ms
section-config.min.js
120 ms
storage.min.js
120 ms
webfont.min.js
16 ms
sticky.min.js
16 ms
modernizr.min.js
17 ms
twc-custom.min.js
16 ms
text.min.js
13 ms
key-codes.min.js
479 ms
tab.min.js
1046 ms
page-cache.min.js
1044 ms
my-account-minicart.min.js
1044 ms
addThis.min.js
1045 ms
validation.min.js
1045 ms
cookies.min.js
1046 ms
catalog-add-to-cart.min.js
1046 ms
invalidation-processor.min.js
1046 ms
app.min.js
1047 ms
jquery.storageapi.min.js
1047 ms
url.min.js
1045 ms
swiper-trigger.js
15 ms
modal-popup.html
78 ms
modal-slide.html
78 ms
modal-custom.html
80 ms
space.gif
76 ms
transition.min.js
67 ms
destination
104 ms
fbevents.js
161 ms
ytag.js
988 ms
analytics.js
213 ms
modal.min.js
136 ms
matchMedia.min.js
150 ms
jquery.colorbox.min.js
151 ms
console-logger.min.js
147 ms
addthis_widget.js
144 ms
validation.min.js
142 ms
product-ids-resolver.min.js
139 ms
element.min.js
138 ms
react.production.min.js
167 ms
react-dom.production.min.js
209 ms
swiper-bundle.min.js
221 ms
collapse.min.js
135 ms
dropdown.min.js
135 ms
types.min.js
115 ms
layout.min.js
133 ms
js-translation.json
731 ms
141 ms
1513114388796641
104 ms
product-ids.min.js
42 ms
main.min.js
13 ms
registry.min.js
41 ms
events.min.js
39 ms
class.min.js
39 ms
local.min.js
39 ms
moment.min.js
27 ms
jquery.metadata.min.js
28 ms
links.min.js
67 ms
logger.min.js
68 ms
entry-factory.min.js
67 ms
console-output-handler.min.js
68 ms
formatter.min.js
69 ms
message-pool.min.js
66 ms
levels-pool.min.js
67 ms
logger-utils.min.js
68 ms
collect
65 ms
arrays.min.js
44 ms
compare.min.js
47 ms
misc.min.js
45 ms
objects.min.js
46 ms
strings.min.js
48 ms
template.min.js
48 ms
wrapper.min.js
49 ms
es6-collections.min.js
49 ms
jquery.validate.min.js
148 ms
collect
325 ms
js
125 ms
120 ms
FormData.min.js
100 ms
qrcode@1.png
179 ms
bottom_logo.svg
179 ms
entry.min.js
177 ms
website-rule.min.js
12 ms
storage-manager.min.js
5 ms
ga-audiences
20 ms
storage-service.min.js
4 ms
ids-storage.min.js
4 ms
data-storage.min.js
5 ms
ids-storage-compare.min.js
4 ms
query-builder.min.js
4 ms
spacetokyo.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
spacetokyo.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
Browser errors were logged to the console
Page has valid source maps
spacetokyo.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
Tap targets are not sized appropriately
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spacetokyo.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 Spacetokyo.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.
spacetokyo.jp
Open Graph data is detected on the main page of Spacetokyo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: