6.1 sec in total
438 ms
5 sec
703 ms
Click here to check amazing Locondo content for Japan. Otherwise, check out these important facts you probably never knew about locondo.co.jp
ジェイドグループは「業界に革新を」をビジョンに掲げ、靴を買うならロコンドでお馴染みのLOCONDO.jpなどのECモール事業、ブランド様のシステムや物流支援を行うプラットフォーム事業、自社ブランドの開発生産販売を行うブランド事業を運営しています。
Visit locondo.co.jpWe analyzed Locondo.co.jp page load time and found that the first response time was 438 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
locondo.co.jp performance score
438 ms
434 ms
351 ms
296 ms
446 ms
Our browser made a total of 140 requests to load all elements on the main page. We found that 53% of them (74 requests) were addressed to the original Locondo.co.jp, 14% (20 requests) were made to Scontent.cdninstagram.com and 10% (14 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Locondo.co.jp.
Page size can be reduced by 679.2 kB (24%)
2.8 MB
2.1 MB
In fact, the total size of Locondo.co.jp main page is 2.8 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. 65% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 66.6 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 66.6 kB or 76% of the original size.
Potential reduce by 14.0 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. Locondo images are well optimized though.
Potential reduce by 549.9 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 549.9 kB or 69% of the original size.
Potential reduce by 48.7 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. Locondo.co.jp needs all CSS files to be minified and compressed as it can save up to 48.7 kB or 82% of the original size.
Number of requests can be reduced by 45 (34%)
133
88
The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Locondo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
locondo.co.jp
438 ms
www.locondo.co.jp
434 ms
index.html
351 ms
reset.css
296 ms
style.css
446 ms
sp.css
345 ms
drawer.css
510 ms
simplePagination.css
346 ms
remodal.css
390 ms
remodal-default-theme.css
442 ms
jquery.min.js
12 ms
instafeed.min.js
527 ms
jquery.simplyscroll.js
528 ms
jquery.bgswitcher.js
584 ms
iscroll-min.js
9 ms
dropdown.min.js
5 ms
jquery.drawer.js
589 ms
remodal.js
736 ms
jquery.matchHeight-min.js
675 ms
jquery.simplePagination.js
688 ms
recent
487 ms
embed
318 ms
logo.png
307 ms
kiseki_rokonnya.png
306 ms
arr.gif
306 ms
about_img.jpg
306 ms
icon_ec.gif
304 ms
logo_locondo.gif
304 ms
logo_locolet.gif
581 ms
logo_locomall.gif
588 ms
icon_platform.gif
464 ms
logo_boem.gif
463 ms
logo_boss.gif
471 ms
logo_locochoc.gif
468 ms
icon_media.gif
606 ms
arr2.gif
605 ms
bg_hokkori_delivery.gif
650 ms
delivery_title01.gif
677 ms
icon_today.gif
677 ms
icon_otameshi.gif
709 ms
icon_concierge.gif
731 ms
delivery_title02.gif
734 ms
icon_shop.gif
809 ms
icon_delivery.gif
846 ms
icon_maker.gif
844 ms
delivery_title03.gif
904 ms
icon_challenge.gif
878 ms
icon_responsibility.gif
882 ms
icon_team.gif
971 ms
link.gif
1011 ms
greeting_subtitle.gif
1014 ms
flow_arr.gif
1023 ms
mail.png
1028 ms
flow2.gif
1097 ms
flow3.gif
1138 ms
flow4.gif
1192 ms
employee_img01.jpg
1713 ms
ga.js
148 ms
employee_img02.jpg
1480 ms
__utm.gif
19 ms
js
47 ms
init_embed.js
26 ms
employee_img03.jpg
1173 ms
employee_img04.jpg
1774 ms
employee_img05.jpg
1517 ms
employee_img06.jpg
1920 ms
employee_img07.jpg
1466 ms
employee_img08.jpg
1759 ms
common.js
60 ms
map.js
60 ms
google4.png
25 ms
overlay.js
19 ms
util.js
17 ms
onion.js
17 ms
search_impl.js
17 ms
StaticMapService.GetMapImage
266 ms
employee_img09.jpg
1448 ms
employee_img10.jpg
1751 ms
employee_img11.jpg
1693 ms
12362346_553370318147149_66483748_n.jpg
133 ms
stats.js
74 ms
openhand_8_8.cur
64 ms
employee_img12.jpg
1627 ms
1169214_460588807457813_1348857421_n.jpg
98 ms
12139717_1651536691788927_2012288454_n.jpg
133 ms
12277400_440271426158804_925397706_n.jpg
133 ms
11324906_1703733459857996_1956524893_n.jpg
132 ms
12357837_1675696565978319_2058128884_n.jpg
132 ms
12317869_732078773589919_1010690128_n.jpg
132 ms
12362125_1501567423481417_1022160312_n.jpg
132 ms
12256875_193574134311164_665466408_n.jpg
172 ms
12256676_1726430880913857_1617061973_n.jpg
169 ms
12120522_1629677370629674_49693055_n.jpg
220 ms
10499077_470290433143858_811638720_n.jpg
219 ms
12784042_1725757484377587_1915020409_n.jpg
169 ms
11410751_1693605654193583_2101239865_n.jpg
219 ms
12331657_1005583402820691_1983514348_n.jpg
218 ms
11939318_1675884866024168_1643306746_n.jpg
297 ms
1172209_871584566290282_316662584_n.jpg
217 ms
12353375_192170794463912_259725925_n.jpg
255 ms
12317862_993631894031642_1536429527_n.jpg
251 ms
11371242_610313035775697_130133476_n.jpg
253 ms
employee_img13.jpg
1829 ms
employee_img14.jpg
2077 ms
ViewportInfoService.GetViewportInfo
87 ms
controls.js
13 ms
ViewportInfoService.GetViewportInfo
50 ms
transparent.png
49 ms
kh
78 ms
kh
104 ms
employee_img15.jpg
1897 ms
pdf.gif
1748 ms
css
110 ms
entity11.png
65 ms
pagetop.gif
1699 ms
mapcnt6.png
53 ms
sv5.png
60 ms
ViewportInfoService.GetViewportInfo
39 ms
tmapctrl.png
48 ms
t_icon.gif
1721 ms
f_icon.gif
1825 ms
vt
146 ms
vt
137 ms
vt
116 ms
vt
125 ms
vt
133 ms
vt
110 ms
vt
196 ms
vt
192 ms
vt
194 ms
vt
207 ms
y_icon.gif
1801 ms
mainimage01.jpg
2359 ms
mainimage02.jpg
2205 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
35 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
43 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
52 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
53 ms
close.png
1838 ms
AuthenticationService.Authenticate
14 ms
locondo.co.jp SEO score
![]()
JA
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Locondo.co.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 Locondo.co.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.
locondo.co.jp
Open Graph description is not detected on the main page of Locondo. 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: