13.2 sec in total
342 ms
9.9 sec
3 sec
Welcome to future-shop.jp homepage info - get ready to check Future Shop best content for Japan right away, or after learning these important things about future-shop.jp
SaaS型ECサイト構築プラットフォームfutureshopは、ECサイトリニューアル・立ち上げに選ばれています。利用中の6店舗に1店舗は年商1億円突破。CMS機能「commerce creator」では、さらにデザインの自由度が向上。定期的にバージョンアップを実施し、常に最新のシステムが利用できます。
Visit future-shop.jpWe analyzed Future-shop.jp page load time and found that the first response time was 342 ms and then it took 12.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
future-shop.jp performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value17.3 s
0/100
25%
Value25.2 s
0/100
10%
Value3,570 ms
1/100
30%
Value0.358
30/100
15%
Value46.6 s
0/100
10%
342 ms
709 ms
1268 ms
1348 ms
1701 ms
Our browser made a total of 189 requests to load all elements on the main page. We found that 83% of them (156 requests) were addressed to the original Future-shop.jp, 3% (5 requests) were made to Google-analytics.com and 3% (5 requests) were made to Clarity.ms. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Future-shop.jp.
Page size can be reduced by 901.7 kB (15%)
6.1 MB
5.2 MB
In fact, the total size of Future-shop.jp main page is 6.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. 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 4.7 MB which makes up the majority of the site volume.
Potential reduce by 146.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. This page needs HTML code to be minified as it can gain 25.9 kB, which is 15% 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 146.9 kB or 85% of the original size.
Potential reduce by 16.2 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. Future Shop images are well optimized though.
Potential reduce by 404.1 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 404.1 kB or 50% of the original size.
Potential reduce by 334.5 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. Future-shop.jp needs all CSS files to be minified and compressed as it can save up to 334.5 kB or 89% of the original size.
Number of requests can be reduced by 51 (28%)
180
129
The browser has sent 180 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Future Shop. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and as a result speed up the page load time.
future-shop.jp
342 ms
future-shop.jp
709 ms
www.future-shop.jp
1268 ms
renewal.min.css
1348 ms
app.min.js
1701 ms
gtm.js
498 ms
header-news-prev-button.svg
171 ms
header-news-next-button.svg
343 ms
logo.svg
571 ms
header-dropdown-arrow-down.svg
574 ms
header-navigation-bg.svg
575 ms
logo-white.svg
576 ms
header-x-icon.svg
579 ms
header-facebook-icon.svg
716 ms
mv-bg-character.svg
719 ms
mv-slide-pc-01.jpg
1447 ms
mv-slide-pc-02.jpg
728 ms
mv-slide-pc-03.jpg
1449 ms
mv-slide-pc-04.jpg
1446 ms
mv-slide-pc-05.jpg
1447 ms
icon-arrow-prev-bk.svg
1057 ms
icon-arrow-next-bk.svg
1058 ms
bnr_future20thsquare.png
1449 ms
maincopy-handwrite-line.svg
1446 ms
icon-arrow-prev-disable.svg
1654 ms
exsample-slide-pc-01.png
1956 ms
exsample-slide-pc-02.png
1797 ms
exsample-slide-pc-03.png
1958 ms
exsample-slide-pc-04.png
1971 ms
exsample-slide-pc-05.png
1766 ms
exsample-slide-pc-06.png
1826 ms
exsample-slide-pc-07.png
1931 ms
exsample-slide-pc-08.png
2293 ms
exsample-slide-pc-09.png
1971 ms
exsample-slide-pc-10.png
2102 ms
exsample-slide-pc-11.png
2126 ms
exsample-slide-pc-12.png
2295 ms
problem01-title-bg-character.svg
2142 ms
problem-handwrite-arrow-right.svg
2138 ms
problem01_kv_pc.jpg
2274 ms
problem01-handwrite-line.svg
2160 ms
ZenKakuGothicNew-Bold.ttf
2499 ms
ZenKakuGothicNew-Medium.ttf
2680 ms
js
528 ms
destination
918 ms
ytag.js
1126 ms
analytics.js
81 ms
fbevents.js
112 ms
3vfuypwodv
203 ms
3vge4nrw56
477 ms
a8sales.js
192 ms
g551y44eds
500 ms
tracking.js
1664 ms
bat.js
153 ms
ZenKakuGothicNew-Regular.ttf
2215 ms
Lato-Bold.ttf
1894 ms
Lato-Black.ttf
1941 ms
Lato-Regular.ttf
1941 ms
problem-open-icon.svg
2122 ms
collect
84 ms
collect
384 ms
collect
99 ms
problem01-point-pc-01.jpg
1995 ms
97083991.js
26 ms
problem01-point-pc-02.jpg
1985 ms
js
707 ms
problem01-point-pc-03.jpg
2139 ms
collect
300 ms
97083991
582 ms
clarity.js
581 ms
ch-plugin-web.js
653 ms
problem01-point-pc-04.jpg
1853 ms
ga-audiences
415 ms
ga-audiences
398 ms
problem01-bottom-bg-character.svg
1821 ms
icon-double_quotation-top.svg
1823 ms
collect
191 ms
icon-double_quotation-bottom.svg
1514 ms
icon-itreview.svg
1619 ms
problem01-box-bg-character.svg
1619 ms
problem-close-icon.svg
1620 ms
problem02-title-bg-character.svg
1621 ms
179 ms
problem-handwrite-arrow-left.svg
1546 ms
ch-plugin-core.4808bef7.vendor.js
75 ms
ch-plugin-core-20240425224444.js
76 ms
problem02_kv_pc.jpg
1547 ms
a8crossDomain.js
37 ms
37 ms
problem02-handwrite-line.svg
1396 ms
problem02-service-icon-pc-01.png
1366 ms
problem02-service-icon-pc-02.png
1368 ms
problem02-service-icon-pc-03.png
1266 ms
problem02-service-icon-pc-04.png
1345 ms
problem02-service-icon-pc-05.png
1406 ms
problem02-service-icon-pc-06.png
1396 ms
problem02-service-icon-pc-07.png
1395 ms
problem02-service-icon-pc-08.png
1266 ms
problem02-service-icon-pc-09.png
1246 ms
problem02-service-icon-pc-10.png
1332 ms
problem02-external-logo-pc-01.png
1390 ms
problem02-external-logo-pc-02.png
1271 ms
problem02-external-logo-pc-03.png
1246 ms
problem02-external-logo-pc-04.png
1235 ms
problem02-external-logo-pc-05.png
1241 ms
problem02-external-logo-pc-06.png
1132 ms
problem02-external-logo-pc-07.png
1190 ms
problem02-external-logo-pc-08.png
1097 ms
problem02-external-logo-pc-09.png
1006 ms
problem02-external-logo-pc-10.png
1018 ms
problem02-external-logo-pc-11.png
1020 ms
problem02-external-logo-pc-12.png
1043 ms
problem02-external-logo-pc-13.png
1053 ms
problem02-external-logo-pc-14.png
1005 ms
problem02-bottom-bg-character.svg
1006 ms
problem02-box-bg-character.svg
1017 ms
problem03-title-bg-character.svg
1023 ms
problem03_kv_pc.jpg
1032 ms
problem03-handwrite-line.svg
986 ms
problem03-point-pc-01.jpg
991 ms
problem03-point-pc-02.jpg
992 ms
problem03-point-pc-03-01.jpg
1001 ms
problem03-point-pc-03-02.jpg
967 ms
problem03-point-pc-04.jpg
1026 ms
problem03-box-bg-character.svg
1027 ms
problem04-title-bg-character.svg
1032 ms
problem04_kv_pc.jpg
1036 ms
problem04-handwrite-line.svg
1042 ms
problem04-pickup-icon-pc-01.png
1079 ms
pickup-arrow.svg
1033 ms
problem04-pickup-icon-pc-02.png
1025 ms
problem04-pickup-icon-pc-03.png
1032 ms
problem04-pickup-icon-pc-04.png
1036 ms
problem04-bottom-bg-character.svg
1043 ms
problem04-box-bg-character.svg
1080 ms
problem05-title-bg-character.svg
1032 ms
problem05_kv_pc.jpg
1027 ms
problem05-handwrite-line.svg
1029 ms
problem05-support-img-pc-01.jpg
1034 ms
problem05-support-img-pc-02.jpg
1046 ms
problem05-support-img-pc-03.jpg
1082 ms
problem05-support-img-pc-04.jpg
1032 ms
problem05-support-img-pc-05.jpg
1028 ms
problem05-bottom-bg-character.svg
1029 ms
problem05-award-pc.png
1034 ms
problem05-box-bg-character.svg
1037 ms
achievement-handwrite-line.svg
1081 ms
achievement-img-pc.jpg
1033 ms
price-handwrite-arrow.svg
1028 ms
study-img-01_pc.jpg
1030 ms
study-logo-01_pc.jpg
1030 ms
study-logo-02_pc.jpg
1036 ms
study-logo-03_pc.jpg
1082 ms
study-logo-04_pc.jpg
1032 ms
study-logo-05_pc.jpg
1028 ms
study-logo-06_pc.jpg
1029 ms
study-logo-07_pc.jpg
1031 ms
study-logo-08_pc.jpg
1038 ms
study-logo-09_pc.jpg
1061 ms
study-logo-10_pc.jpg
1031 ms
study-logo-11_pc.jpg
1029 ms
study-logo-12_pc.jpg
1029 ms
study-logo-13_pc.jpg
1028 ms
study-logo-14_pc.jpg
1039 ms
study-logo-15_pc.jpg
1060 ms
study-logo-16_pc.jpg
1031 ms
study-logo-17_pc.jpg
1028 ms
study-logo-18_pc.jpg
1029 ms
study-logo-19_pc.jpg
1027 ms
study-logo-20_pc.jpg
1037 ms
main.png
1061 ms
link_mark_blank_blue.svg
1031 ms
ogp.jpg
1195 ms
ogp.png
1029 ms
ogp.png
1026 ms
meeting-img-01-pc.jpg
1028 ms
download-handwrite-line.svg
1060 ms
download-bg_pc.jpg
1045 ms
footer-title.svg
1041 ms
footer-x-icon.svg
1036 ms
footer-facebook-icon.svg
1049 ms
footer-privacy-img.jpg
1107 ms
footer-iso-img.jpg
1084 ms
totop.svg
1079 ms
bnr_chat.svg
1038 ms
pd.js
266 ms
collect
60 ms
analytics
337 ms
c.gif
10 ms
future-shop.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
future-shop.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
future-shop.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Future-shop.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 Future-shop.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.
future-shop.jp
Open Graph data is detected on the main page of Future Shop. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: