Tools & Wizards About Us
fashion-okoku.jp screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

fashion-okoku.jp

古着買取王国 ｜ ジャケット、ウエア、Tシャツ、スニーカーの買取なら！

Page Load Speed

15.4 sec in total

First Response

574 ms

Resources Loaded

13.8 sec

Page Rendered

1 sec

fashion-okoku.jp screenshot

About Website

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

メンズウエア、レディースウエアやブーツ、スニーカーなどシューズの買取なら古着買取王国へ！ブランドバッグ、サングラス、財布などの小物も高価買取しています。古着の買取はお任せください！

Visit fashion-okoku.jp

Key Findings

We analyzed Fashion-okoku.jp page load time and found that the first response time was 574 ms and then it took 14.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

fashion-okoku.jp performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value21.6 s

0/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value2,160 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.103

89/100

15%

TTI (Time to Interactive)

Value21.3 s

1/100

10%

Network Requests Diagram

fashion-okoku.jp

574 ms

fashion-okoku.jp

1014 ms

gtm.js

74 ms

style.css

495 ms

jquery-1.11.1.min.js

669 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 92% of them (82 requests) were addressed to the original Fashion-okoku.jp, 4% (4 requests) were made to Cdn.jsdelivr.net and 2% (2 requests) were made to Statics.a8.net. The less responsive or slowest element that took the longest time to load (6.7 sec) belongs to the original domain Fashion-okoku.jp.

Page Optimization Overview & Recommendations

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

Content Size

5.1 MB

After Optimization

4.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fashion-okoku.jp main page is 5.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. 50% of websites need less resources to load. Images take 4.9 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 43.0 kB

  • Original 54.0 kB
  • After minification 45.4 kB
  • After compression 11.0 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 8.6 kB, which is 16% 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 43.0 kB or 80% of the original size.

Image Optimization

-8%

Potential reduce by 411.2 kB

  • Original 4.9 MB
  • After minification 4.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. Fashion Okoku images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 30.8 kB

  • Original 100.3 kB
  • After minification 100.1 kB
  • After compression 69.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 30.8 kB or 31% of the original size.

CSS Optimization

-26%

Potential reduce by 7.9 kB

  • Original 30.2 kB
  • After minification 30.2 kB
  • After compression 22.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. Fashion-okoku.jp needs all CSS files to be minified and compressed as it can save up to 7.9 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (37%)

Requests Now

86

After Optimization

54

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fashion-okoku.jp

fashion-okoku.jp

574 ms

fashion-okoku.jp

fashion-okoku.jp

1014 ms

gtm.js

gtm.js

74 ms

style.css

style.css

495 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

669 ms

ie.js

ie.js

597 ms

updnWatermark.js

updnWatermark.js

601 ms

jquery.insetborder.js

jquery.insetborder.js

615 ms

collapse.js

collapse.js

698 ms

jquery.tile.min.js

jquery.tile.min.js

1187 ms

function.js

function.js

1193 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

1161 ms

login_form.js

login_form.js

1206 ms

pc_func.js

pc_func.js

1229 ms

sbi-styles.min.css

sbi-styles.min.css

1211 ms

style.min.css

style.min.css

1675 ms

a8sales.js

a8sales.js

22 ms

a8crossDomain.js

a8crossDomain.js

24 ms

lozad.min.js

lozad.min.js

1783 ms

intersection-observer.js

intersection-observer.js

1789 ms

topr.css

topr.css

1816 ms

slick-theme.css

slick-theme.css

1821 ms

slick.css

slick.css

1839 ms

slick.js

slick.js

2355 ms

Array.prototype.forEach.js

Array.prototype.forEach.js

30 ms

es6-promise.auto.min.js

es6-promise.auto.min.js

60 ms

vue.min.js

vue.min.js

50 ms

axios.min.js

axios.min.js

61 ms

main.js

main.js

2283 ms

wp-embed.min.js

wp-embed.min.js

2460 ms

logo.png

logo.png

821 ms

icon_company.png

icon_company.png

673 ms

icon_faq.png

icon_faq.png

699 ms

icon_map.png

icon_map.png

1107 ms

twitter.png

twitter.png

1076 ms

close.png

close.png

1138 ms

top_key_pc.png

top_key_pc.png

2821 ms

campaign_banner_next_pc_ver3.png

campaign_banner_next_pc_ver3.png

1306 ms

campaign_banner_next_pc.png

campaign_banner_next_pc.png

1839 ms

gshockBanner.png

gshockBanner.png

2275 ms

zippoBanner.png

zippoBanner.png

2303 ms

c_ban5.png

c_ban5.png

2360 ms

c_spring.png

c_spring.png

2538 ms

c_autumn.png

c_autumn.png

3263 ms

c_ban1.png

c_ban1.png

3160 ms

c_ban3.png

c_ban3.png

3654 ms

c_ban4.png

c_ban4.png

3521 ms

icon_1.png

icon_1.png

3131 ms

icon_2.png

icon_2.png

3313 ms

icon_3.png

icon_3.png

3729 ms

icon_4.png

icon_4.png

3775 ms

detail_1.png

detail_1.png

4289 ms

detail_2.png

detail_2.png

3925 ms

detail_3.png

detail_3.png

4590 ms

detail_4.png

detail_4.png

4332 ms

flow_top_1.png

flow_top_1.png

4630 ms

flow_top_2.png

flow_top_2.png

4752 ms

flow_top_3.png

flow_top_3.png

4914 ms

flow_top_4.png

flow_top_4.png

5183 ms

wo_exban7.png

wo_exban7.png

5453 ms

wo_exban8.png

wo_exban8.png

5626 ms

wo_exban9.png

wo_exban9.png

5948 ms

wo_exban10.png

wo_exban10.png

5935 ms

wo_exban11.png

wo_exban11.png

5606 ms

wo_exban12.png

wo_exban12.png

5744 ms

m_exban7.png

m_exban7.png

6034 ms

m_exban8.png

m_exban8.png

5963 ms

m_exban9.png

m_exban9.png

6471 ms

m_exban10.png

m_exban10.png

6175 ms

m_exban11.png

m_exban11.png

6245 ms

m_exban12.png

m_exban12.png

6516 ms

b_exban7.png

b_exban7.png

6706 ms

b_exban8.png

b_exban8.png

6425 ms

b_exban9.png

b_exban9.png

5977 ms

b_exban10.png

b_exban10.png

6123 ms

b_exban11.png

b_exban11.png

5875 ms

b_exban12.png

b_exban12.png

6160 ms

amecasu-1.png

amecasu-1.png

6420 ms

mf-z-link-0.png

mf-z-link-0.png

6182 ms

brand-banner-rich.png

brand-banner-rich.png

5705 ms

hermes-banner-rich.png

hermes-banner-rich.png

6004 ms

priload_img.png

priload_img.png

5727 ms

flow1.png

flow1.png

6429 ms

footer_logo.png

footer_logo.png

5993 ms

top_btn.png

top_btn.png

5829 ms

search_brand.png

search_brand.png

6042 ms

features_line.png

features_line.png

5839 ms

ajax-loader.gif

ajax-loader.gif

617 ms

slick.woff

slick.woff

616 ms

Accessibility Review

fashion-okoku.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

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.

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

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

fashion-okoku.jp best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

fashion-okoku.jp SEO score

89

Search Engine Optimization Advices

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fashion-okoku.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 Fashion-okoku.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

fashion-okoku.jp

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