Tools & Wizards About Us
procable.jp screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

procable.jp

PRO CABLE - プロ用オーディオケーブル・最強のアンプ・オーディオ電源 ケーブル -

Page Load Speed

5 sec in total

First Response

541 ms

Resources Loaded

3.6 sec

Page Rendered

918 ms

procable.jp screenshot

About Website

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

最高峰のプロ用ケーブル、最強オーディオアンプ、オーディオ電源トランス、スピーカー等、オーディオで良い音を出す為、オーディオに驚くほど役に立つ商品を安価に提供します。自宅のオーディオで至上の音を出されてください。

Visit procable.jp

Key Findings

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

procable.jp performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

18/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value420 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value7.8 s

45/100

10%

Network Requests Diagram

procable.jp

541 ms

procable.jp

1140 ms

js

75 ms

jquery-1.10.1.min.js

689 ms

pagetop.js

532 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 68% of them (43 requests) were addressed to the original Procable.jp, 10% (6 requests) were made to S.w.org and 6% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Procable.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 228.3 kB (35%)

Content Size

646.5 kB

After Optimization

418.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Procable.jp main page is 646.5 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. 45% of websites need less resources to load. Images take 294.3 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 161.0 kB

  • Original 200.7 kB
  • After minification 195.6 kB
  • After compression 39.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. 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 161.0 kB or 80% of the original size.

Image Optimization

-9%

Potential reduce by 26.5 kB

  • Original 294.3 kB
  • After minification 267.8 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. PRO CABLE images are well optimized though.

JavaScript Optimization

-29%

Potential reduce by 40.1 kB

  • Original 137.5 kB
  • After minification 137.5 kB
  • After compression 97.4 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 40.1 kB or 29% of the original size.

CSS Optimization

-5%

Potential reduce by 707 B

  • Original 14.0 kB
  • After minification 14.0 kB
  • After compression 13.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. Procable.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 27 (45%)

Requests Now

60

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

procable.jp

procable.jp

541 ms

procable.jp

procable.jp

1140 ms

js

js

75 ms

jquery-1.10.1.min.js

jquery-1.10.1.min.js

689 ms

pagetop.js

pagetop.js

532 ms

prototype.js

prototype.js

32 ms

recommend.js

recommend.js

685 ms

base.css

base.css

528 ms

clearfix.css

clearfix.css

528 ms

analytics.js

analytics.js

36 ms

style.min.css

style.min.css

758 ms

classic-themes.min.css

classic-themes.min.css

542 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

302 ms

collect

collect

50 ms

blank.gif

blank.gif

296 ms

p.gif

p.gif

295 ms

top_title.gif

top_title.gif

295 ms

design_x_r1_c1.gif

design_x_r1_c1.gif

295 ms

design_x_r1_c3.gif

design_x_r1_c3.gif

294 ms

side-login.png

side-login.png

363 ms

side-cart.png

side-cart.png

1455 ms

side-favorite.png

side-favorite.png

453 ms

top_bnr_AmazonPay2.png

top_bnr_AmazonPay2.png

446 ms

rakutenp.jpg

rakutenp.jpg

623 ms

df4b94657c1c4c5b23dd096bf2684f74.png

df4b94657c1c4c5b23dd096bf2684f74.png

625 ms

xone96-catch-200x225.jpg

xone96-catch-200x225.jpg

579 ms

20150717_113127-200x251.jpg

20150717_113127-200x251.jpg

625 ms

vital_vam265_1-200x250.jpg

vital_vam265_1-200x250.jpg

635 ms

20171213_150139-200x270.jpg

20171213_150139-200x270.jpg

747 ms

we_jumper_pin-200x250.jpg

we_jumper_pin-200x250.jpg

806 ms

belden_8460_china-200x250.jpg

belden_8460_china-200x250.jpg

804 ms

belden_88760_china-200x250.gif

belden_88760_china-200x250.gif

807 ms

belden_88760_2-200x250.jpg

belden_88760_2-200x250.jpg

817 ms

20171205_160941-200x282.jpg

20171205_160941-200x282.jpg

932 ms

20171213_133103-200x282.jpg

20171213_133103-200x282.jpg

980 ms

20171121_164943-200x294.jpg

20171121_164943-200x294.jpg

985 ms

20171212_165817-200x306.jpg

20171212_165817-200x306.jpg

987 ms

belden_8412_1-200x250.jpg

belden_8412_1-200x250.jpg

997 ms

we_14ga_replica-200x250.jpg

we_14ga_replica-200x250.jpg

1125 ms

we_16ga_replica-200x250.jpg

we_16ga_replica-200x250.jpg

1158 ms

we_18ga_replica-200x250.jpg

we_18ga_replica-200x250.jpg

1166 ms

20171212_144200-200x254.jpg

20171212_144200-200x254.jpg

1168 ms

we_16ga-200x250.jpg

we_16ga-200x250.jpg

1180 ms

design_x_r6_c1.gif

design_x_r6_c1.gif

1311 ms

design_x_r6_c3.gif

design_x_r6_c3.gif

1339 ms

f-btn-pagetop.png

f-btn-pagetop.png

1347 ms

all.js

all.js

88 ms

design_x_r2_c1.gif

design_x_r2_c1.gif

1319 ms

arrow.gif

arrow.gif

1331 ms

widgets.js

widgets.js

199 ms

all.js

all.js

21 ms

1f537.svg

1f537.svg

99 ms

2b55.svg

2b55.svg

88 ms

1f534.svg

1f534.svg

86 ms

26ab.svg

26ab.svg

89 ms

2757.svg

2757.svg

86 ms

2753.svg

2753.svg

85 ms

88 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

70 ms

settings

settings

96 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

22 ms

embeds

embeds

47 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

40 ms

Accessibility Review

procable.jp accessibility score

77

Accessibility Issues

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

procable.jp best practices score

58

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

procable.jp SEO score

86

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

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

procable.jp

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