Tools & Wizards About Us
kendepot.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

kendepot.jp

東リタイルカーペットの通販なら！建デポオンラインショップ

Page Load Speed

5 sec in total

First Response

624 ms

Resources Loaded

3.6 sec

Page Rendered

842 ms

kendepot.jp screenshot

About Website

Click here to check amazing Kendepot content. Otherwise, check out these important facts you probably never knew about kendepot.jp

東リ タイルカーペットの卸売通販サイトです。株式会社建デポが運営する、法人・個人事業主様を対象とした、全国の建デポプロ店舗も含め40万人以上の会員様にご利用いただいています。豊富な品揃えで、3,000円以上のご注文は送料無料となります。

Visit kendepot.jp

Key Findings

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

Performance Metrics

kendepot.jp performance score

0

Network Requests Diagram

kendepot.jp

624 ms

www.kendepot.jp

896 ms

default.css

623 ms

pcsmpflg.js

498 ms

dc.js

219 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 58% of them (14 requests) were addressed to the original Kendepot.jp, 25% (6 requests) were made to Image1.shopserve.jp and 8% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Image1.shopserve.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 111.7 kB (25%)

Content Size

438.1 kB

After Optimization

326.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kendepot.jp main page is 438.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 344.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 35.3 kB

  • Original 43.8 kB
  • After minification 40.2 kB
  • After compression 8.4 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 35.3 kB or 81% of the original size.

Image Optimization

-14%

Potential reduce by 49.6 kB

  • Original 344.9 kB
  • After minification 295.3 kB

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, Kendepot needs image optimization as it can save up to 49.6 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

-16%

Potential reduce by 3.6 kB

  • Original 22.5 kB
  • After minification 20.9 kB
  • After compression 18.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 3.6 kB or 16% of the original size.

CSS Optimization

-86%

Potential reduce by 23.1 kB

  • Original 26.9 kB
  • After minification 17.4 kB
  • After compression 3.8 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. Kendepot.jp needs all CSS files to be minified and compressed as it can save up to 23.1 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

22

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kendepot.jp

kendepot.jp

624 ms

www.kendepot.jp

www.kendepot.jp

896 ms

default.css

default.css

623 ms

pcsmpflg.js

pcsmpflg.js

498 ms

dc.js

dc.js

219 ms

kendepot_logo.jpg

kendepot_logo.jpg

434 ms

04992219046558.jpg

04992219046558.jpg

1228 ms

rss.gif

rss.gif

202 ms

spacer.gif

spacer.gif

423 ms

1505tori.jpg

1505tori.jpg

1595 ms

icon_pickup.gif

icon_pickup.gif

431 ms

card_all.gif

card_all.gif

476 ms

04992219041522.jpg

04992219041522.jpg

1645 ms

04992219057523.jpg

04992219057523.jpg

1465 ms

02222222229475.jpg

02222222229475.jpg

646 ms

04992219065511.jpg

04992219065511.jpg

1001 ms

04992219065481.jpg

04992219065481.jpg

1082 ms

1505haisou3000.jpg

1505haisou3000.jpg

443 ms

headnavi_bg.gif

headnavi_bg.gif

582 ms

icon_eye01.gif

icon_eye01.gif

739 ms

title_bar01.gif

title_bar01.gif

765 ms

tracking.php

tracking.php

1006 ms

inpage_linkid.js

inpage_linkid.js

32 ms

__utm.gif

__utm.gif

54 ms

SEO Factors

kendepot.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kendepot.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 Kendepot.jp main page’s claimed encoding is euc-jp. 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

kendepot.jp

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