Tools & Wizards About Us
kingfamily.co.jp screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

kingfamily.co.jp

キングファミリー｜古着のリサイクルショップ

Page Load Speed

14.3 sec in total

First Response

952 ms

Resources Loaded

12.8 sec

Page Rendered

496 ms

kingfamily.co.jp screenshot

About Website

Click here to check amazing Kingfamily content for Japan. Otherwise, check out these important facts you probably never knew about kingfamily.co.jp

キングファミリーはいらなくなった服をぜんぶまるごと買取いたします。ノンブランドでもなんでも、もったいないを新たな楽しみに繋げるリサイクルショップを目指します。

Visit kingfamily.co.jp

Key Findings

We analyzed Kingfamily.co.jp page load time and found that the first response time was 952 ms and then it took 13.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

kingfamily.co.jp performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value35.3 s

0/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0.249

50/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

www.kingfamily.co.jp

952 ms

sbc.css

349 ms

pagenavi-css.css

371 ms

bootstrap.min.css

1312 ms

bootstrap_custom.css

1365 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 74% of them (73 requests) were addressed to the original Kingfamily.co.jp, 4% (4 requests) were made to Googletagmanager.com and 4% (4 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (6.5 sec) belongs to the original domain Kingfamily.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 631.7 kB (22%)

Content Size

2.9 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kingfamily.co.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. 40% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 31.0 kB

  • Original 39.6 kB
  • After minification 35.6 kB
  • After compression 8.6 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 31.0 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 95.9 kB

  • Original 2.0 MB
  • After minification 1.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. Kingfamily images are well optimized though.

JavaScript Optimization

-37%

Potential reduce by 185.0 kB

  • Original 493.8 kB
  • After minification 490.9 kB
  • After compression 308.7 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 185.0 kB or 37% of the original size.

CSS Optimization

-86%

Potential reduce by 319.8 kB

  • Original 371.3 kB
  • After minification 320.3 kB
  • After compression 51.5 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. Kingfamily.co.jp needs all CSS files to be minified and compressed as it can save up to 319.8 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (43%)

Requests Now

91

After Optimization

52

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.kingfamily.co.jp

www.kingfamily.co.jp

952 ms

sbc.css

sbc.css

349 ms

pagenavi-css.css

pagenavi-css.css

371 ms

bootstrap.min.css

bootstrap.min.css

1312 ms

bootstrap_custom.css

bootstrap_custom.css

1365 ms

style.css

style.css

393 ms

masterslider.main.css

masterslider.main.css

1125 ms

custom.css

custom.css

722 ms

jquery.js

jquery.js

1496 ms

jquery-migrate.min.js

jquery-migrate.min.js

784 ms

sbc.js

sbc.js

1071 ms

api.js

api.js

24 ms

home.css

home.css

1152 ms

underscore.min.js

underscore.min.js

1430 ms

bootstrap.min.js

bootstrap.min.js

1524 ms

hover_top_btn.js

hover_top_btn.js

1326 ms

shop_news.js

shop_news.js

1493 ms

wp-embed.min.js

wp-embed.min.js

1566 ms

jquery.easing.min.js

jquery.easing.min.js

2018 ms

masterslider.min.js

masterslider.min.js

2246 ms

marketing.js

marketing.js

1801 ms

css

css

21 ms

recaptcha__en.js

recaptcha__en.js

29 ms

reset.css

reset.css

528 ms

common.css

common.css

553 ms

gtm.js

gtm.js

46 ms

bg.png

bg.png

420 ms

logo.png

logo.png

422 ms

smart_logo.png

smart_logo.png

421 ms

btn01_smart.jpg

btn01_smart.jpg

564 ms

btn02_smart.jpg

btn02_smart.jpg

488 ms

btn03_smart.jpg

btn03_smart.jpg

749 ms

top_img01.jpg

top_img01.jpg

1498 ms

btn01.png

btn01.png

749 ms

top_img02.jpg

top_img02.jpg

1742 ms

btn02.png

btn02.png

881 ms

top_img03.jpg

top_img03.jpg

2817 ms

btn03.png

btn03.png

1300 ms

top_pu_bg.gif

top_pu_bg.gif

6498 ms

blank.gif

blank.gif

1234 ms

btn_omoi.gif

btn_omoi.gif

1601 ms

btn_tanoshimu.gif

btn_tanoshimu.gif

1674 ms

btn_gakusei.gif

btn_gakusei.gif

1870 ms

mirai.jpg

mirai.jpg

2160 ms

top_180329.png

top_180329.png

2416 ms

bnr_rec-permit.jpg

bnr_rec-permit.jpg

2269 ms

topics_title_smart.png

topics_title_smart.png

2739 ms

topics_title.png

topics_title.png

3333 ms

topics_douga.jpg

topics_douga.jpg

2826 ms

topics_meyasu.jpg

topics_meyasu.jpg

2977 ms

topics_yukue.jpg

topics_yukue.jpg

3300 ms

topics_teian.jpg

topics_teian.jpg

3338 ms

topics_ecopro.jpg

topics_ecopro.jpg

3352 ms

topics_blog.jpg

topics_blog.jpg

3502 ms

topics_manga.jpg

topics_manga.jpg

3824 ms

topics_chuui.jpg

topics_chuui.jpg

3890 ms

title_omoi_smart.png

title_omoi_smart.png

3734 ms

title_omoi.png

title_omoi.png

3743 ms

btn_omoi_smart.gif

btn_omoi_smart.gif

3893 ms

btn_omoi.gif

btn_omoi.gif

4075 ms

gtm.js

gtm.js

72 ms

js

js

12 ms

analytics.js

analytics.js

7 ms

kd20th_banner.png

kd20th_banner.png

6506 ms

js

js

58 ms

collect

collect

32 ms

collect

collect

108 ms

segmentation.js

segmentation.js

115 ms

news

news

3861 ms

thumbnails.png

thumbnails.png

3844 ms

btn_pagetop.png

btn_pagetop.png

3871 ms

footer_logo.png

footer_logo.png

4081 ms

topcontents_bg.png

topcontents_bg.png

4148 ms

cnt

cnt

760 ms

bg_omoi.gif

bg_omoi.gif

4066 ms

footer_bg.jpg

footer_bg.jpg

4575 ms

ico_footer_arrow.png

ico_footer_arrow.png

4149 ms

btn_fc_owner.jpg

btn_fc_owner.jpg

4306 ms

loading-2.gif

loading-2.gif

3789 ms

img_main_think_kf-754x227.jpg

img_main_think_kf-754x227.jpg

4572 ms

ss_picture1.jpg

ss_picture1.jpg

1137 ms

ss_picture1.jpg

ss_picture1.jpg

1258 ms

ss_picture1.jpg

ss_picture1.jpg

1414 ms

img_main_feature1-754x227.jpg

img_main_feature1-754x227.jpg

1213 ms

beacon.html

beacon.html

46 ms

pixel

pixel

55 ms

tap.php

tap.php

50 ms

Pug

Pug

49 ms

set

set

314 ms

pixel

pixel

62 ms

img_main_student-754x227.jpg

img_main_student-754x227.jpg

1390 ms

pixel

pixel

21 ms

bounce

bounce

8 ms

sd

sd

7 ms

pixel

pixel

21 ms

sync

sync

757 ms

report

report

781 ms

sync

sync

314 ms

Accessibility Review

kingfamily.co.jp accessibility score

77

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

Links do not have a discernible name

Best Practices

kingfamily.co.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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

kingfamily.co.jp SEO score

91

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 Kingfamily.co.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 Kingfamily.co.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

kingfamily.co.jp

Open Graph data is detected on the main page of Kingfamily. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: