Tools & Wizards About Us
tomorrowland.jp screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

tomorrowland.jp

TOMORROWLAND(トゥモローランド)公式通販サイト

Page Load Speed

5.4 sec in total

First Response

361 ms

Resources Loaded

4.9 sec

Page Rendered

66 ms

tomorrowland.jp screenshot

About Website

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

TOMORROWLAND(トゥモローランド)公式通販サイト。レディース、メンズ、キッズの商品情報から、店舗情報、特集、スタッフスタイリングなどをご紹介。最短当日発送、ギフトラッピング無料、10,000円以上(税抜)ご購入で送料無料。

Visit tomorrowland.jp

Key Findings

We analyzed Tomorrowland.jp page load time and found that the first response time was 361 ms and then it took 5 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

tomorrowland.jp performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value18.5 s

0/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value9,980 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.159

73/100

15%

TTI (Time to Interactive)

Value33.2 s

0/100

10%

Network Requests Diagram

tomorrowland.jp

361 ms

tomorrowland.jp

671 ms

store.tomorrowland.co.jp

2268 ms

staffstart.min.js

32 ms

main.js

146 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Tomorrowland.jp, 67% (47 requests) were made to Store.tomorrowland.co.jp and 9% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Store.tomorrowland.co.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tomorrowland.jp main page is 1.5 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 95.3 kB

  • Original 108.5 kB
  • After minification 72.8 kB
  • After compression 13.2 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. This page needs HTML code to be minified as it can gain 35.7 kB, which is 33% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 95.3 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.1 MB
  • After minification 1.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. TOMORROWLAND images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.1 kB

  • Original 226.8 kB
  • After minification 226.4 kB
  • After compression 224.7 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 31 B

  • Original 27.2 kB
  • After minification 27.2 kB
  • After compression 27.2 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. Tomorrowland.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 46 (75%)

Requests Now

61

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tomorrowland.jp

tomorrowland.jp

361 ms

tomorrowland.jp

tomorrowland.jp

671 ms

store.tomorrowland.co.jp

store.tomorrowland.co.jp

2268 ms

staffstart.min.js

staffstart.min.js

32 ms

main.js

main.js

146 ms

top.js

top.js

757 ms

gtm_top.js

gtm_top.js

39 ms

cart.js

cart.js

139 ms

gtm.js

gtm.js

35 ms

global.css

global.css

139 ms

top.css

top.css

770 ms

index.css

index.css

1501 ms

skin.css

skin.css

156 ms

css

css

40 ms

css2

css2

138 ms

css2

css2

163 ms

css2

css2

163 ms

1

1

42 ms

checkout.js

checkout.js

143 ms

evergage.min.js

evergage.min.js

27 ms

widget

widget

20 ms

8sDzhn

8sDzhn

25 ms

27 ms

jquery.min.js

jquery.min.js

21 ms

gssa.js

gssa.js

1009 ms

dwanalytics-22.2.js

dwanalytics-22.2.js

18 ms

dwac-21.7.js

dwac-21.7.js

16 ms

gretel.min.js

gretel.min.js

18 ms

0425_FVCP_1700_138.jpg

0425_FVCP_1700_138.jpg

40 ms

0425_NM_1700_138.jpg

0425_NM_1700_138.jpg

38 ms

hamburger-icon.png

hamburger-icon.png

36 ms

header-icon01.png

header-icon01.png

37 ms

sitelogo@2x.png

sitelogo@2x.png

37 ms

close.png

close.png

38 ms

header-icon02.png

header-icon02.png

40 ms

card-icon.svg

card-icon.svg

39 ms

header-icon04.png

header-icon04.png

48 ms

search.png

search.png

50 ms

hamburger-icon-close.png

hamburger-icon-close.png

48 ms

swiper-arrow-right.png

swiper-arrow-right.png

49 ms

%E3%83%9B%E3%83%AF%E3%82%A4%E3%83%88.png

%E3%83%9B%E3%83%AF%E3%82%A4%E3%83%88.png

50 ms

%E3%83%96%E3%83%A9%E3%83%83%E3%82%AF.png

%E3%83%96%E3%83%A9%E3%83%83%E3%82%AF.png

50 ms

%E3%82%B0%E3%83%AC%E3%83%BC.png

%E3%82%B0%E3%83%AC%E3%83%BC.png

75 ms

%E3%83%96%E3%83%A9%E3%82%A6%E3%83%B3.png

%E3%83%96%E3%83%A9%E3%82%A6%E3%83%B3.png

60 ms

%E3%83%99%E3%83%BC%E3%82%B8%E3%83%A5.png

%E3%83%99%E3%83%BC%E3%82%B8%E3%83%A5.png

70 ms

%E3%82%B0%E3%83%AA%E3%83%BC%E3%83%B3.png

%E3%82%B0%E3%83%AA%E3%83%BC%E3%83%B3.png

71 ms

%E3%83%96%E3%83%AB%E3%83%BC.png

%E3%83%96%E3%83%AB%E3%83%BC.png

75 ms

%E3%83%91%E3%83%BC%E3%83%97%E3%83%AB.png

%E3%83%91%E3%83%BC%E3%83%97%E3%83%AB.png

70 ms

%E3%82%A4%E3%82%A8%E3%83%AD%E3%83%BC.png

%E3%82%A4%E3%82%A8%E3%83%AD%E3%83%BC.png

143 ms

%E3%83%94%E3%83%B3%E3%82%AF.png

%E3%83%94%E3%83%B3%E3%82%AF.png

143 ms

%E3%83%AC%E3%83%83%E3%83%89.png

%E3%83%AC%E3%83%83%E3%83%89.png

82 ms

%E3%82%AA%E3%83%AC%E3%83%B3%E3%82%B8.png

%E3%82%AA%E3%83%AC%E3%83%B3%E3%82%B8.png

143 ms

%E3%82%B7%E3%83%AB%E3%83%90%E3%83%BC.png

%E3%82%B7%E3%83%AB%E3%83%90%E3%83%BC.png

86 ms

%E3%82%B4%E3%83%BC%E3%83%AB%E3%83%89.png

%E3%82%B4%E3%83%BC%E3%83%AB%E3%83%89.png

142 ms

%E3%81%9D%E3%81%AE%E4%BB%96.png

%E3%81%9D%E3%81%AE%E4%BB%96.png

142 ms

app-banner.jpg

app-banner.jpg

143 ms

0215_pc_960_960_w.jpg

0215_pc_960_960_w.jpg

215 ms

0215_sp_750_562_w.jpg

0215_sp_750_562_w.jpg

210 ms

0215_pc_960_960_m.jpg

0215_pc_960_960_m.jpg

159 ms

0215_sp_750_562_m.jpg

0215_sp_750_562_m.jpg

159 ms

icon-plus.png

icon-plus.png

210 ms

icon-arrow-right.png

icon-arrow-right.png

157 ms

arrow_3_tp.svg

arrow_3_tp.svg

211 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75jY0rw_mMI.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75jY0rw_mMI.woff

48 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75jY0rw_mMI.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75jY0rw_mMI.woff

119 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75jY0rw_mMI.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75jY0rw_mMI.woff

176 ms

S6uyw4BMUTPHvxo6WQev.woff

S6uyw4BMUTPHvxo6WQev.woff

112 ms

S6u9w4BMUTPHh7USewyFHi_o.woff

S6u9w4BMUTPHh7USewyFHi_o.woff

119 ms

S6u9w4BMUTPHh6UVewyFHi_o.woff

S6u9w4BMUTPHh6UVewyFHi_o.woff

119 ms

script.js

script.js

148 ms

Accessibility Review

tomorrowland.jp accessibility score

84

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

tomorrowland.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

tomorrowland.jp SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Tomorrowland.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 Tomorrowland.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

tomorrowland.jp

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