3.6 sec in total
193 ms
3.1 sec
242 ms
Click here to check amazing XLARGE content for United States. Otherwise, check out these important facts you probably never knew about xlarge.com
XLARGE Clothing. Since 1991. A pioneer of Los Angeles streetwear culture. Find your own styles in our New Arrivals, Collaboration Collections, etc. XLARGE.com also provides the latest news (XLARGE NEW...
Visit xlarge.comWe analyzed Xlarge.com page load time and found that the first response time was 193 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
xlarge.com performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value16.2 s
0/100
25%
Value8.6 s
17/100
10%
Value680 ms
43/100
30%
Value1.192
1/100
15%
Value26.3 s
0/100
10%
193 ms
24 ms
29 ms
40 ms
129 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Xlarge.com, 31% (31 requests) were made to Cdn.shopify.com and 10% (10 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Aecf1b9641147d6c2dac-2747da5878bc1cc774dd571feee3484c.ssl.cf5.rackcdn.com.
Page size can be reduced by 428.9 kB (25%)
1.7 MB
1.3 MB
In fact, the total size of Xlarge.com 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. 70% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 83.5 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 83.5 kB or 78% of the original size.
Potential reduce by 3.4 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 302.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 302.5 kB or 61% of the original size.
Potential reduce by 39.6 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.com needs all CSS files to be minified and compressed as it can save up to 39.6 kB or 71% of the original size.
Number of requests can be reduced by 54 (70%)
77
23
The browser has sent 77 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 29 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
xlarge.com
193 ms
css
24 ms
stylesheet.css
29 ms
option_selection-04f21dade47c181126ac61b64d757485f84671daadfa90e4956a522cda4c2948.js
40 ms
vhx6aym.js
129 ms
jquery.min.js
73 ms
fitvids1.0.js
40 ms
jquery.easing.1.3.js
39 ms
jquery.cycle2.v20130502.min.js
39 ms
jquery.magnific.v0.8.8.js
35 ms
shop.js
40 ms
ga_urchin_forms-0826cdefee6590321eb5c0c435eeebf7a8425a5493a9e95059c40e07e069ad52.js
40 ms
mc-validate.js
18 ms
xlarge.com
204 ms
shopify_stats.js
53 ms
trekkie.storefront.min.js
140 ms
shop_events_listener-dabe00038c134ebede3c66ef50bfdcedb847ac379226dfb9a22bbf438ac8dbef.js
53 ms
fp.js
51 ms
xlarge-twitter.png
834 ms
xlarge-facebook.png
829 ms
xlarge-instagram.png
835 ms
xlarge-tumblr.png
834 ms
logo.png
120 ms
icon-cart-light.png
35 ms
icon-search-dark.png
35 ms
home-slide1.jpg
195 ms
home-slide2.jpg
121 ms
home-slide3.jpg
121 ms
home-slide4.jpg
194 ms
home-slide6.jpg
195 ms
XL_CHOC_deck_large.jpg
121 ms
2016_25th_trueogstreetwear_instagram_large.jpg
192 ms
M16Z9103-BLK_large.jpg
194 ms
M16A5101Black2_large.jpg
194 ms
M16A1109White_large.jpg
194 ms
M16A1201White2_large.jpg
195 ms
M16A1402White_large.jpg
197 ms
M16S9124Black_large.jpg
197 ms
icon-vimeo.png
196 ms
pinit.js
91 ms
plusone.js
203 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
84 ms
hLJcW1QEiiMR5vPSaNpY4U-fPW59AOLtUeD4aixNNGMff4HgggMmeMJ6Mk6f5gI.woff
164 ms
ITWXQkd3x5ZpneGUE0x9exBrCaQPv6nqCog7lS-QJzJff4KgggMmeMJ6Mk6f5gJ.woff
271 ms
vsHljiTUx-oVan3kVJ-qIwRshRx4N5E_nnGzZwxe6i9ff4egggMmeMJ6Mk6f5MS.woff
299 ms
8AxGjPYiwG3b8AARs63tOlxObYMBk05TILenCpxn9bJff4pgggMmeMJ6Mk6f5M6.woff
299 ms
PRmiXeptR36kaC0GEAetxlDMrAYtoOisqqMDW9M_Mqc.ttf
87 ms
jXUWxjF56I1RzFLae1FQzDPlGTkSzgnCu7f5Fwg8Fo3ffOPtggMmeMJ6Mk6f5MS.woff
270 ms
GTzVMlPjQS8b4rYmw0fYI2A21HhJ_GM42_1Uzf9HDVMffO0tggMmeMJ6Mk6f5Mb.woff
267 ms
oYv78ZqryERsM0VRE4cxhyrxtQ8uohmmcQ0isFVFnltffOAtggMmeMJ6Mk6f5gI.woff
298 ms
mZGwyAk92jiR1jK3xCqpGSNfGy3vDUQcPenTcpjRg4SffOKtggMmeMJ6Mk6f5Mt.woff
315 ms
all.js
81 ms
widgets.js
194 ms
closebox.png
139 ms
slide-buttons-arrow.png
80 ms
offsite_event.php
216 ms
identify
225 ms
analytics.js
50 ms
record.gif
114 ms
158 ms
pinit_main.js
65 ms
xd_arbiter.php
46 ms
xd_arbiter.php
108 ms
cb=gapi.loaded_0
63 ms
collect
44 ms
collect
83 ms
page
130 ms
p.gif
126 ms
spr.js
31 ms
merchandise360.min.js
1731 ms
1463749920609530.js
10 ms
6031425752845.js
11 ms
roundtrip.js
7 ms
fbds.js
15 ms
43 ms
spr.css
29 ms
jquery.min.js
28 ms
XBWRFYZETJA4DLFCN4VXTC.js
167 ms
fbevents.hashing.js
8 ms
out
14 ms
24 ms
out
13 ms
out
17 ms
out
16 ms
out
12 ms
out
15 ms
out
15 ms
28 ms
u.php
62 ms
adsct
98 ms
pixel
46 ms
42 ms
377928.gif
19 ms
bounce
12 ms
u.php
45 ms
pixel
19 ms
Pug
23 ms
sd
28 ms
in
5 ms
xlarge.com 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.com 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.com 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xlarge.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Xlarge.com 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.com
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: