Tools & Wizards About Us

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

spinns.jp

SPINNS WEB STORE | SPINNS (スピンズ) 公式通販

Page Load Speed

9.9 sec in total

First Response

569 ms

Resources Loaded

8.9 sec

Page Rendered

418 ms

About Website

Visit spinns.jp now to see the best up-to-date SPINNS content for Japan and also check out these interesting facts you probably never knew about spinns.jp

SPINNS（スピンズ）公式通販サイト。『変われるってムテキ！』をコンセプトに、メンズ・レディースのアパレル・雑貨・ブランドアイテムや、ハイクォリティー古着を取り扱うファッション通販サイトです。 毎週更新の新作アイテムや、通販限定のSALEなども開催中！最短翌日発送。お支払いは、コンビニ決済/クレジットカード/あと払いなども可。

Visit spinns.jp

Key Findings

We analyzed Spinns.jp page load time and found that the first response time was 569 ms and then it took 9.3 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

spinns.jp performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value23.5 s

0/100

25%

SI (Speed Index)

Value14.5 s

1/100

10%

TBT (Total Blocking Time)

Value2,520 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.511

15/100

15%

TTI (Time to Interactive)

Value16.8 s

5/100

10%

Network Requests Diagram

spinns.jp

569 ms

www.spinns.jp

727 ms

r_system_preset.css

351 ms

system_DesignSettings.css

521 ms

system_SizeColorSettings.css

356 ms

Our browser made a total of 185 requests to load all elements on the main page. We found that 89% of them (164 requests) were addressed to the original Spinns.jp, 5% (10 requests) were made to Dev.doomgroup.jp and 2% (4 requests) were made to R2.future-shop.jp. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Spinns.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 286.0 kB (10%)

Content Size

2.9 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Spinns.jp main page is 2.9 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 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 77.5 kB

  • Original 88.6 kB
  • After minification 73.1 kB
  • After compression 11.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 15.5 kB, which is 17% 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 77.5 kB or 87% of the original size.

Image Optimization

-3%

Potential reduce by 66.8 kB

  • Original 2.6 MB
  • After minification 2.5 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. SPINNS images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 5.1 kB

  • Original 58.0 kB
  • After minification 55.6 kB
  • After compression 52.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-88%

Potential reduce by 136.6 kB

  • Original 156.0 kB
  • After minification 88.1 kB
  • After compression 19.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. Spinns.jp needs all CSS files to be minified and compressed as it can save up to 136.6 kB or 88% of the original size.

Requests Breakdown

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

Requests Now

182

After Optimization

164

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

spinns.jp accessibility score

74

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-hidden="true"] elements contain focusable descendents

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

Image elements do not have [alt] attributes

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

spinns.jp best practices score

83

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

spinns.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 Spinns.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 Spinns.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 SPINNS. 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: