Tools & Wizards About Us
okoku.jp screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

okoku.jp

買取王国　|　古着・おもちゃを売るのも買うのも買取王国　愛知名古屋 三重 岐阜 大阪 総合リユース・リサイクルショップ

Page Load Speed

6.8 sec in total

First Response

557 ms

Resources Loaded

6.1 sec

Page Rendered

146 ms

okoku.jp screenshot

About Website

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

買取王国は名古屋を中心に、愛知・岐阜・三重・大阪に展開しているリユース・リサイクルショップ。古着・おもちゃホビー・ブランド等の買取と販売。メンズファッション、レディースファッション、ホビー、ブランド品、高級時計、トレーディングカード、家具、家電、携帯電話、生活雑貨、お酒、貴金属、金券、工具、ゲーム、きもの、楽器など豊富なアイテムを取り揃えております。

Visit okoku.jp

Key Findings

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

Performance Metrics

okoku.jp performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value430 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.037

100/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

okoku.jp

557 ms

okoku.jp

744 ms

gtm.js

48 ms

base.css

241 ms

swiper.min.css

482 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 91% of them (49 requests) were addressed to the original Okoku.jp, 4% (2 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Okoku.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.3 MB (69%)

Content Size

4.8 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 25.4 kB

  • Original 30.1 kB
  • After minification 25.5 kB
  • After compression 4.7 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 4.6 kB, which is 15% 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 25.4 kB or 84% of the original size.

Image Optimization

-69%

Potential reduce by 3.3 MB

  • Original 4.7 MB
  • After minification 1.4 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, Okoku needs image optimization as it can save up to 3.3 MB or 69% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-18%

Potential reduce by 12.7 kB

  • Original 71.7 kB
  • After minification 71.7 kB
  • After compression 59.0 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 12.7 kB or 18% of the original size.

CSS Optimization

-29%

Potential reduce by 3.4 kB

  • Original 11.4 kB
  • After minification 11.4 kB
  • After compression 8.1 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. Okoku.jp needs all CSS files to be minified and compressed as it can save up to 3.4 kB or 29% of the original size.

Requests Breakdown

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

Requests Now

52

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 8 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

okoku.jp

okoku.jp

557 ms

okoku.jp

okoku.jp

744 ms

gtm.js

gtm.js

48 ms

base.css

base.css

241 ms

swiper.min.css

swiper.min.css

482 ms

index.css

index.css

605 ms

index_pc.css

index_pc.css

606 ms

intersection-observer.js

intersection-observer.js

640 ms

swiper.min.js

swiper.min.js

1043 ms

lozad.min.js

lozad.min.js

804 ms

base.js

base.js

805 ms

index.js

index.js

809 ms

ico_mv_anchor_pc.svg

ico_mv_anchor_pc.svg

1010 ms

clear.png

clear.png

1012 ms

ico_h_shop.svg

ico_h_shop.svg

1018 ms

logoH.svg

logoH.svg

1492 ms

ico_h_store.svg

ico_h_store.svg

1115 ms

ico_h_kaitori.svg

ico_h_kaitori.svg

1249 ms

ico_h_menu.png

ico_h_menu.png

1245 ms

mvbrand1.png

mvbrand1.png

1624 ms

mvhobby1.png

mvhobby1.png

1470 ms

mvfashion1.png

mvfashion1.png

2543 ms

mvhother1.png

mvhother1.png

2257 ms

ico_mv_2.png

ico_mv_2.png

1530 ms

imgBtnTakuhai.png

imgBtnTakuhai.png

1740 ms

icoBtnAbout.png

icoBtnAbout.png

2456 ms

IcoBtnShop.png

IcoBtnShop.png

2157 ms

fashion_okoku_202405_1.png

fashion_okoku_202405_1.png

2622 ms

hobby_okoku_202405_1.png

hobby_okoku_202405_1.png

2574 ms

hobby_okoku_202405_2.png

hobby_okoku_202405_2.png

3576 ms

hobby_okoku_202405_3.png

hobby_okoku_202405_3.png

4370 ms

hobby_okoku_202405_4.png

hobby_okoku_202405_4.png

4545 ms

brand_okoku_202405_1.png

brand_okoku_202405_1.png

4341 ms

brand_okoku_202405_2.png

brand_okoku_202405_2.png

2832 ms

osake_okoku_202405_1.png

osake_okoku_202405_1.png

4370 ms

kaden_okoku_202405_1.png

kaden_okoku_202405_1.png

3078 ms

kaden_okoku_202405_2.png

kaden_okoku_202405_2.png

3322 ms

kaden_okoku_202405_3.png

kaden_okoku_202405_3.png

3596 ms

bnrRec1.png

bnrRec1.png

4124 ms

js

js

63 ms

analytics.js

analytics.js

13 ms

collect

collect

80 ms

collect

collect

29 ms

bnrRec2.png

bnrRec2.png

3591 ms

bnrRec3.png

bnrRec3.png

3579 ms

bnr_other_1.png

bnr_other_1.png

3663 ms

bnr_other_7.png

bnr_other_7.png

3701 ms

bnr_other_3.png

bnr_other_3.png

3837 ms

monodone2.png

monodone2.png

3744 ms

bnr_other_4.png

bnr_other_4.png

3925 ms

food_loss.png

food_loss.png

3957 ms

bnr_other_6.png

bnr_other_6.png

3596 ms

logoF.svg

logoF.svg

3678 ms

saiyo_anchor.svg

saiyo_anchor.svg

3734 ms

Accessibility Review

okoku.jp accessibility score

77

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

High

Page has valid source maps

SEO Factors

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Okoku.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 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

okoku.jp

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