8.5 sec in total
1 sec
6.2 sec
1.3 sec
Visit growaround.co.jp now to see the best up-to-date GROWAROUND content for Japan and also check out these interesting facts you probably never knew about growaround.co.jp
東京渋谷にあるセレクトショップGROWAROUND(グロウアラウンド)の公式通販サイト。
Visit growaround.co.jpWe analyzed Growaround.co.jp page load time and found that the first response time was 1 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
growaround.co.jp performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value4.5 s
37/100
25%
Value11.3 s
5/100
10%
Value160 ms
94/100
30%
Value0.308
38/100
15%
Value13.3 s
12/100
10%
1023 ms
175 ms
345 ms
860 ms
868 ms
Our browser made a total of 167 requests to load all elements on the main page. We found that 10% of them (16 requests) were addressed to the original Growaround.co.jp, 56% (94 requests) were made to Bold-hita-2661.boo.jp and 24% (40 requests) were made to Makeshop-multi-images.akamaized.net. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Bold-hita-2661.boo.jp.
Page size can be reduced by 507.3 kB (7%)
6.9 MB
6.4 MB
In fact, the total size of Growaround.co.jp main page is 6.9 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. 60% of websites need less resources to load. Images take 6.6 MB which makes up the majority of the site volume.
Potential reduce by 112.3 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 112.3 kB or 86% of the original size.
Potential reduce by 377.9 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. GROWAROUND images are well optimized though.
Potential reduce by 13.8 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 13.8 kB or 12% of the original size.
Potential reduce by 3.3 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. Growaround.co.jp has all CSS files already compressed.
Number of requests can be reduced by 88 (53%)
165
77
The browser has sent 165 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GROWAROUND. 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 22 to 1 for CSS and as a result speed up the page load time.
growaround.co.jp
1023 ms
m_sys_common.css
175 ms
import.css
345 ms
lightbox.css
860 ms
base.css
868 ms
module.css
883 ms
common.css
912 ms
flexibility.js
917 ms
jquery-1.11.3.min.js
5 ms
jsRSS.cgi
621 ms
commonAPI.php
1100 ms
slick.min.js
1036 ms
lightbox.min.js
1044 ms
lib.js
1059 ms
ui.js
1104 ms
common.js
1093 ms
script
1318 ms
check_history.css
181 ms
pager.css
190 ms
shopdetail.css
345 ms
ranking.css
347 ms
basket.css
347 ms
security.css
369 ms
category_menu.css
358 ms
topicpath.css
369 ms
catalog.css
518 ms
ordercontract.css
524 ms
searchTitle.png
144 ms
bannertitle.gif
180 ms
count2.makeshop.jp
342 ms
0000000200533_cHq4ixE.jpg
126 ms
banner02.png
124 ms
l_searchBtn.png
144 ms
categoryTitle.png
157 ms
l_memberBtn.png
155 ms
mk_main_p_line.gif
152 ms
rpay.png
130 ms
line.png
120 ms
cnv.png
126 ms
smart.png
137 ms
close.png
275 ms
loading.gif
291 ms
prev.png
304 ms
next.png
344 ms
logo01.svgz
357 ms
icon01.svgz
351 ms
icon03.svgz
446 ms
icon04.svgz
461 ms
iconTW.svgz
480 ms
iconIG.svgz
527 ms
iconFB.png
535 ms
ts_bg_pc.png
545 ms
ts_bg_sp.png
781 ms
iconBlog.png
631 ms
bnr_sale1.png
656 ms
bnr_sale2.png
711 ms
banner03.svgz
717 ms
btn01.svgz
737 ms
btn03.svgz
802 ms
logo02.svgz
832 ms
0000000200523_xicmuOh.jpg
126 ms
0000000200503_4C7rC55.jpg
124 ms
0000000200483_JZoroH6.jpg
142 ms
0000000200323_GLVDdTs.jpg
161 ms
0000000200313_lP56LvQ.jpg
139 ms
0000000200303_ZNquStY.jpg
128 ms
0000000200293_U0xeyBe.jpg
142 ms
0000000200633_Nsi7BVg.jpg
131 ms
0000000200573_iALeqAB.jpg
146 ms
0000000200563_0ic7QgA.jpg
156 ms
0000000200543_ogH2sVr.jpg
154 ms
0000000200233_WS1mKag.jpg
152 ms
0000000200223_TIQYbtE.jpg
168 ms
0000000200203_ji2QHTE.jpg
170 ms
0000000200193_tutfaPT.jpg
166 ms
0000000200453_cKWNjBG.jpg
170 ms
0000000200393_1RHuU0L.jpg
170 ms
0000000200383_JcS6rSb.jpg
171 ms
0000000200343_SCL2Ezy.jpg
194 ms
0000000200103_88lSHJM.jpg
173 ms
0000000200083_o1l8ZZZ.jpg
175 ms
0000000200053_EUk6jLT.jpg
194 ms
0000000200033_YtMpihw.jpg
194 ms
0000000200143_jvU35SL.jpg
180 ms
0000000200023_fMTr7SZ.jpg
182 ms
0000000199893_qUMxGv1.jpg
191 ms
0000000199883_aet5OvI.jpg
191 ms
0000000200173_XKlwMpx.jpg
202 ms
0000000200163_3ScLNut.jpg
206 ms
0000000200153_bAP9ROZ.jpg
211 ms
0000000200133_di7G29K.jpg
207 ms
0000000199873_xvnsvvs.jpg
206 ms
0000000199863_iRN07vn.jpg
223 ms
0000000199853_NLxTwoj.jpg
214 ms
0000000199843_YtzFTCf.jpg
316 ms
maintitle2.gif
200 ms
maintitle1.gif
194 ms
icon05.svgz
849 ms
icon06.svgz
854 ms
901 ms
0000000199833_Bv9nQpS.jpg
106 ms
0000000199823_RxOaJSl.jpg
138 ms
0000000199643_WBIhjMb.jpg
97 ms
0000000199623_UXbLtdF.jpg
837 ms
style.min.css
363 ms
sb-instagram.css
193 ms
font-awesome.min.css
50 ms
style-front-end.min.css
187 ms
dashicons.min.css
337 ms
jquery.min.js
350 ms
jquery-migrate.min.js
172 ms
calendar.css
347 ms
jquery-1.11.3.min.js
29 ms
sb-instagram.js
724 ms
core.min.js
389 ms
datepicker.min.js
507 ms
script-front-end.min.js
517 ms
sbi-sprite.png
186 ms
fontawesome-webfont.woff
25 ms
2.jpg
895 ms
7.jpg
559 ms
3.jpg
720 ms
8.jpg
503 ms
4.jpg
860 ms
9.jpg
338 ms
5.jpg
844 ms
10.jpg
1005 ms
1.jpg
937 ms
6.jpg
906 ms
cutthroat.jpg
1021 ms
KSUBI.jpg
1016 ms
hell.jpg
1036 ms
sp5der.jpg
1090 ms
god.jpg
1127 ms
purple.jpg
1177 ms
up.jpg
1189 ms
vala.jpg
1380 ms
kappa.jpg
1214 ms
bxr.jpg
1273 ms
champion.jpg
1316 ms
nike.jpg
1348 ms
ckj.jpg
1360 ms
cmny.jpg
1399 ms
fred-perry.jpg
1457 ms
jordan.jpg
1506 ms
lacoste.jpg
1518 ms
levis.jpg
1530 ms
mn.jpg
1563 ms
y3-1.jpg
1922 ms
new-era.jpg
1640 ms
coogi-1.jpg
1697 ms
pro.jpg
1688 ms
carhartt.jpg
1700 ms
starter.jpg
1746 ms
stonisland.jpg
1825 ms
stussy.jpg
1526 ms
timber.jpg
1390 ms
eptm.jpg
1317 ms
vandala.jpg
1215 ms
tnf-2.jpg
1182 ms
rothco.jpg
1527 ms
brand01.svgz
1186 ms
brand02.svgz
1176 ms
brand03.svgz
1165 ms
brand04.svgz
1114 ms
brand05.svgz
1185 ms
brand06.svgz
1194 ms
growaround.co.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.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
growaround.co.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
Page has valid source maps
growaround.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Growaround.co.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Growaround.co.jp main page’s claimed encoding is euc-jp. 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.
growaround.co.jp
Open Graph description is not detected on the main page of GROWAROUND. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: