Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

xlarge.jp

XLARGE OFFICIAL SITE(エクストララージ オフィシャルサイト)

Page Load Speed

6.1 sec in total

First Response

725 ms

Resources Loaded

4.8 sec

Page Rendered

568 ms

xlarge.jp screenshot

About Website

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.jp

Key Findings

We 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.

Performance Metrics

xlarge.jp performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value17.7 s

0/100

25%

SI (Speed Index)

Value9.1 s

13/100

10%

TBT (Total Blocking Time)

Value670 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value1.2

1/100

15%

TTI (Time to Interactive)

Value27.5 s

0/100

10%

Network Requests Diagram

xlarge.jp

725 ms

www.xlarge.jp

1146 ms

lib.css

179 ms

styles.css

359 ms

lib.js

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 Optimization Overview & Recommendations

Page size can be reduced by 735.1 kB (43%)

Content Size

1.7 MB

After Optimization

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.

HTML Optimization

-86%

Potential reduce by 36.8 kB

  • Original 42.9 kB
  • After minification 35.4 kB
  • After compression 6.1 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.

Image Optimization

-3%

Potential reduce by 22.0 kB

  • Original 778.4 kB
  • After minification 756.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.

JavaScript Optimization

-71%

Potential reduce by 385.5 kB

  • Original 541.8 kB
  • After minification 463.2 kB
  • After compression 156.3 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.

CSS Optimization

-85%

Potential reduce by 290.8 kB

  • Original 343.2 kB
  • After minification 342.8 kB
  • After compression 52.4 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.

Requests Breakdown

Number of requests can be reduced by 12 (18%)

Requests Now

67

After Optimization

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.

Accessibility Review

xlarge.jp accessibility score

81

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

ARIA IDs are not unique

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

xlarge.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

xlarge.jp SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    JA

  • Encoding

    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.

Social Sharing Optimization

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: