6.1 sec in total
725 ms
4.8 sec
568 ms
Welcome to xlarge.jp homepage info - get ready to check XLARGE best content for Japan right away, or after learning these important things about xlarge.jp
「XLARGE (エクストララージ)」のオフィシャルサイト。1991年設立。LA発のストリートブランド。最新ニュースや商品情報、ショップリスト・ECサイト等ご紹介しています。
Visit xlarge.jpWe analyzed Xlarge.jp page load time and found that the first response time was 725 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
xlarge.jp performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value17.7 s
0/100
25%
Value9.1 s
13/100
10%
Value670 ms
44/100
30%
Value1.2
1/100
15%
Value27.5 s
0/100
10%
725 ms
1146 ms
179 ms
359 ms
893 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 47% of them (37 requests) were addressed to the original Xlarge.jp, 23% (18 requests) were made to Scontent.cdninstagram.com and 13% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Xlarge.jp.
Page size can be reduced by 735.1 kB (43%)
1.7 MB
971.3 kB
In fact, the total size of Xlarge.jp main page is 1.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. 60% of websites need less resources to load. Images take 778.4 kB which makes up the majority of the site volume.
Potential reduce by 36.8 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 7.5 kB, which is 18% 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 36.8 kB or 86% of the original size.
Potential reduce by 22.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. XLARGE images are well optimized though.
Potential reduce by 385.5 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 385.5 kB or 71% of the original size.
Potential reduce by 290.8 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. Xlarge.jp needs all CSS files to be minified and compressed as it can save up to 290.8 kB or 85% of the original size.
Number of requests can be reduced by 12 (18%)
67
55
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of XLARGE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
xlarge.jp
725 ms
www.xlarge.jp
1146 ms
lib.css
179 ms
styles.css
359 ms
lib.js
893 ms
script.min.js
368 ms
css
74 ms
css
86 ms
webantenna.js
490 ms
12446072_954248697957600_632068382_n.jpg
277 ms
h_logo_xlarge1.png
183 ms
h_logo_plusl.png
182 ms
h_logo_va.png
193 ms
h_sp_menu.png
181 ms
top_news_cover_dummy.png
419 ms
2016_25th_trueogstreetwear_banner.jpg
698 ms
2016_spring_consoritum_woodwood2_th.jpg
418 ms
news_0226_th.jpg
528 ms
20160225_calif_th.jpg
418 ms
2016_spring_inspiration_th.jpg
603 ms
2016_spring_ftc_lookbook_th.jpg
589 ms
2016_spring_woodwood_th.jpg
761 ms
2016_spring_xftc_top_th.jpg
950 ms
2016_spring_consortium_nicekicks_th.jpg
705 ms
news_0219_th.jpg
763 ms
2016_spring_yeezy350_th.jpg
985 ms
2016_spring_sarcastic_th1.jpg
872 ms
h1-1_.gif
1233 ms
format_0212_th.jpg
937 ms
nove_th.jpg
939 ms
2016_spring_ollie_th.jpg
1046 ms
2016spring_trueogstreetwear_countdown_th3.gif
1805 ms
2016spring_trueogstreetwear_countdown_th2.gif
1461 ms
2016spring_trueogstreetwear_countdown_th1.gif
2022 ms
banner2.png
1176 ms
banner1.png
1220 ms
h_logo_xlarge2.png
1367 ms
spmenu_close.png
1394 ms
12728433_799026080203804_1688802693_n.jpg
414 ms
11848828_1684834421758492_2004979127_n.jpg
475 ms
12747685_1676634409257910_1534911162_n.jpg
495 ms
12747550_1353158208043833_1698443657_n.jpg
495 ms
12783508_197412283950491_2026285455_n.jpg
494 ms
12446045_147979105588993_1953314821_n.jpg
493 ms
12716723_1089659424401386_1286454456_n.jpg
494 ms
11848820_569761399851501_1391119872_n.jpg
547 ms
12677306_841321742644321_1797041715_n.jpg
529 ms
12717083_1518072065164221_1497305594_n.jpg
567 ms
12716800_971599032915748_1571312645_n.jpg
530 ms
12751480_505761396277130_1961385271_n.jpg
531 ms
12748252_1687997301474072_789026280_n.jpg
531 ms
12748218_182041715498958_2139960464_n.jpg
568 ms
12729621_456770541187777_1368575901_n.jpg
573 ms
12747663_666883016798314_296270629_n.jpg
570 ms
1723108_462176933985763_1523416537_n.jpg
570 ms
gtm.js
62 ms
Gj781SYwh2A
136 ms
top_ogbox.gif
1396 ms
sprite_top-s3462cc8b13.png
1545 ms
sprite_common-s90c8c79e26.png
1553 ms
_webantenna.png
169 ms
fpTVHK8qsXbIeTHTrnQH6Nog-We9VNve39Jr4Vs_aDc.woff
61 ms
fpTVHK8qsXbIeTHTrnQH6PULlOK_XQENnt2ryrY843E.woff
82 ms
M2Jd71oPJhLKp0zdtTvoMzNrcjQuD0pTu1za2FULaMs.woff
107 ms
toadOcfmlt9b38dHJxOBGFkQc6VGVFSmCnC_l7QZG60.woff
120 ms
toadOcfmlt9b38dHJxOBGJ6-ys_j0H4QL65VLqzI3wI.woff
131 ms
ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff
130 ms
UnXpojilM3XslYxUnWuVe_esZW2xOQ-xsNqO47m55DA.woff
130 ms
wZLYhRRxZWGToTRP78bqJQ.woff
130 ms
analytics.js
33 ms
collect
25 ms
collect
86 ms
www-embed-player-vflZsBgOl.css
84 ms
www-embed-player.js
104 ms
base.js
176 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
37 ms
ad_status.js
38 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
26 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
26 ms
xlarge.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA IDs are not unique
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
xlarge.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
xlarge.jp SEO score
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xlarge.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 Xlarge.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.
xlarge.jp
Open Graph data is detected on the main page of XLARGE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: