Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

jamtrading.jp

【古着通販】古着屋JAM(ジャム)公式オンラインショップ

Page Load Speed

12.8 sec in total

First Response

993 ms

Resources Loaded

10.8 sec

Page Rendered

1.1 sec

About Website

Welcome to jamtrading.jp homepage info - get ready to check Jamtrading best content for Japan right away, or after learning these important things about jamtrading.jp

古着屋JAMの公式通販・オンラインショップ。メンズ・レディース・ヴィンテージのスウェットやTシャツ、ラルフローレンなど人気ブランドの古着を販売。古着初心者からヴィンテージマニアまで、誰もが楽しめる日本最大級のインポート古着専門店です。

Visit jamtrading.jp

Key Findings

We analyzed Jamtrading.jp page load time and found that the first response time was 993 ms and then it took 11.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

jamtrading.jp performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value15.5 s

0/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.673

8/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

jamtrading.jp

993 ms

r_system_preset.css

573 ms

system_DesignSettings.css

586 ms

system_SizeColorSettings.css

397 ms

system_LayoutSettings.css

400 ms

Our browser made a total of 378 requests to load all elements on the main page. We found that 57% of them (217 requests) were addressed to the original Jamtrading.jp, 17% (63 requests) were made to Thumbnail.image.rakuten.co.jp and 13% (51 requests) were made to Image.rakuten.co.jp. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Thumbnail.image.rakuten.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (25%)

Content Size

4.1 MB

After Optimization

3.1 MB

In fact, the total size of Jamtrading.jp main page is 4.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 151.6 kB

  • Original 178.1 kB
  • After minification 141.3 kB
  • After compression 26.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. This page needs HTML code to be minified as it can gain 36.8 kB, which is 21% 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 151.6 kB or 85% of the original size.

Image Optimization

-14%

Potential reduce by 448.0 kB

  • Original 3.3 MB
  • After minification 2.9 MB

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. Obviously, Jamtrading needs image optimization as it can save up to 448.0 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-60%

Potential reduce by 253.8 kB

  • Original 426.1 kB
  • After minification 418.0 kB
  • After compression 172.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 253.8 kB or 60% of the original size.

CSS Optimization

-87%

Potential reduce by 195.0 kB

  • Original 223.6 kB
  • After minification 148.7 kB
  • After compression 28.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. Jamtrading.jp needs all CSS files to be minified and compressed as it can save up to 195.0 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (16%)

Requests Now

372

After Optimization

313

The browser has sent 372 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jamtrading. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

jamtrading.jp accessibility score

73

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

<input type="image"> elements do not have [alt] text

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

jamtrading.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

jamtrading.jp SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT-JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jamtrading.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 Jamtrading.jp main page’s claimed encoding is shift-jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Jamtrading. 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: