5.7 sec in total
565 ms
4.5 sec
642 ms
Visit edwin.co.jp now to see the best up-to-date EDWIN content for Japan and also check out these interesting facts you probably never knew about edwin.co.jp
EDWIN(エドウイン)の公式ブランドサイト。最新のイベントやニュース情報、採用情報をご案内しております。
Visit edwin.co.jpWe analyzed Edwin.co.jp page load time and found that the first response time was 565 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
edwin.co.jp performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value15.2 s
0/100
25%
Value8.0 s
22/100
10%
Value1,640 ms
12/100
30%
Value0.31
38/100
15%
Value18.6 s
3/100
10%
565 ms
711 ms
175 ms
696 ms
40 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 70% of them (66 requests) were addressed to the original Edwin.co.jp, 6% (6 requests) were made to Googletagmanager.com and 5% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Edwin.co.jp.
Page size can be reduced by 105.0 kB (1%)
8.7 MB
8.6 MB
In fact, the total size of Edwin.co.jp main page is 8.7 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. Only a small number of websites need less resources to load. Images take 8.5 MB which makes up the majority of the site volume.
Potential reduce by 40.0 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 17.4 kB, which is 37% 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 40.0 kB or 85% of the original size.
Potential reduce by 25.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. EDWIN images are well optimized though.
Potential reduce by 672 B
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 39.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. Edwin.co.jp needs all CSS files to be minified and compressed as it can save up to 39.3 kB or 80% of the original size.
Number of requests can be reduced by 33 (36%)
91
58
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EDWIN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
edwin.co.jp
565 ms
edwin.co.jp
711 ms
reset.css
175 ms
common.css
696 ms
css2
40 ms
style.css
666 ms
jquery.min.js
27 ms
swiper.min.css
669 ms
swiper-bundle.min.js
40 ms
common.js
502 ms
onload.js
519 ms
swiper-bundle.min.js
15 ms
gtm.js
66 ms
gtm.js
150 ms
analytics.js
65 ms
pagetop.png
243 ms
logo_edwin.svg
241 ms
bdd0c941f34a429d71db4577355feaf4caa2cee6.jpg
965 ms
505_24SS_1500_939.jpg
904 ms
JERSEYSbanner_200240229_2_1500_939.jpg
778 ms
1500X939.jpg
946 ms
edwin_ladies_hatarakuro_sp.jpg
755 ms
edwin_conceptshop.jpg
415 ms
EDWIN_logo.png
614 ms
503.png
781 ms
505.png
929 ms
jerseys.png
951 ms
denisura.png
948 ms
hatarakuro.png
1069 ms
edwin_concept_2.png
1102 ms
4186c9a179f6729d5c60e137a490df7686c61361.jpg
1278 ms
4c95fab7de4958a76410705e6ea2e78eced96ae9.jpg
1449 ms
bnr_top_sustainability.jpg
1295 ms
ef3f9039dd9152084f889146003c115b5c7fd202-thumb-220xauto-2300.jpg
1139 ms
520651084e6d8b4b0238c35d96a9e18fd9ae788e-thumb-220xauto-2253.jpg
1234 ms
3de5ab40f439f99ddba6c8a4890cd28e6efd9f6c-thumb-220xauto-2196.jpg
1276 ms
thumbnail_edwin_conceptshop_yurakucho-thumb-220xauto-2146.jpg
1318 ms
luten2024_thumbnail-thumb-220xauto-2107.jpg
1399 ms
1080-thumb-220xauto-1947.jpg
1455 ms
714dfd47284496c43429fd77d06e27f1e2e7cd81-thumb-220xauto-1945.jpg
1446 ms
993d6a41b25f8f485686b5d510bd31f3c0547629-thumb-220xauto-1915.jpg
1468 ms
okome_1080_1080-thumb-220xauto-1909.jpg
1495 ms
0928_0322-thumb-220xauto-1804.jpg
1566 ms
a36ba0bfd8238531e35aa466629a43b141e4dca2.jpg
1614 ms
9638c4995903bce0584271f82348cb5a9a856749.jpg
1614 ms
1080_1080.jpg
1803 ms
fec5a09c62c1349daa79e1ef70159a72ca9aa3aa.jpg
1641 ms
JERSEYSbanner_200240229_2_1080_1080.jpg
1850 ms
edwin_harajuku_main_02.jpg
1731 ms
thumnbnail_ishimasan.jpg
1781 ms
thumbnail_juken.jpg
1770 ms
font
518 ms
linkid.js
49 ms
js
115 ms
destination
227 ms
uwt.js
425 ms
fbevents.js
276 ms
ytag.js
811 ms
sprocket-jssdk.js
398 ms
collect
197 ms
collect
447 ms
collect
245 ms
collect
329 ms
js
194 ms
destination
333 ms
ig_01.jpg
1579 ms
cfb4e76305a5eb1a6e5626c4cd5dd8b2ba136109.jpg
1660 ms
edwin_essentials_banner_1080_1080.jpg
1542 ms
ga-audiences
59 ms
adsct
190 ms
adsct
94 ms
thumbnail_harajuku6th.jpg
1343 ms
adsct
113 ms
adsct
199 ms
adsct
205 ms
adsct
220 ms
img_pttd_vol2.jpg
1227 ms
b07fbf572828574e59075c489bf3588296e4219d.jpg
1216 ms
f825afd40707d6ad6c3ad60bc12f0113236dbec0.jpg
1252 ms
60th_359BF.jpg
1168 ms
core.jpg
1195 ms
bnt_sq_60thanniv.jpg
1180 ms
img_story.jpg
1211 ms
202109_edwin_hatarakuro.jpg
1214 ms
Conceptshop_eds.jpg
1427 ms
Conceptshop_IndigoGarments.jpg
1169 ms
Conceptshop_item.jpg
1353 ms
sns_findus.png
1151 ms
sns_logo_twitter.png
1099 ms
sns_logo_fb.png
1064 ms
sns_logo_insta.png
1126 ms
sns_logo_youtube.png
1163 ms
link_ex_icon-w.png
1189 ms
link_ex_icon.png
1112 ms
edwin.co.jp accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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>).
edwin.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
edwin.co.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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edwin.co.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 Edwin.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.
edwin.co.jp
Open Graph description is not detected on the main page of EDWIN. 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: