Tools & Wizards About Us
scrap.co.jp screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

scrap.co.jp

株式会社潮来工機

Page Load Speed

5.2 sec in total

First Response

1 sec

Resources Loaded

4.1 sec

Page Rendered

93 ms

scrap.co.jp screenshot

About Website

Click here to check amazing Scrap content. Otherwise, check out these important facts you probably never knew about scrap.co.jp

金属リサイクル 非鉄リサイクル 家電リサイクル 鉄屑 産業廃棄物処理に関する事なら社潮来工機へおまかせ下さい。

Visit scrap.co.jp

Key Findings

We analyzed Scrap.co.jp page load time and found that the first response time was 1 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

scrap.co.jp performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

98/100

10%

LCP (Largest Contentful Paint)

Value12.7 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value930 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

scrap.co.jp

1027 ms

spacer.gif

471 ms

shadow.gif

471 ms

index_01.jpg

669 ms

index_02.jpg

471 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 69% of them (31 requests) were addressed to the original Scrap.co.jp, 13% (6 requests) were made to Youtube.com and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Scrap.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 17.5 kB (6%)

Content Size

290.8 kB

After Optimization

273.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Scrap.co.jp main page is 290.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 157.6 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 15.0 kB

  • Original 18.2 kB
  • After minification 13.3 kB
  • After compression 3.2 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.9 kB, which is 27% 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 15.0 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 79 B

  • Original 56.2 kB
  • After minification 56.1 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. Scrap images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 2.5 kB

  • Original 157.6 kB
  • After minification 157.6 kB
  • After compression 155.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 58.8 kB
  • After minification 58.8 kB
  • After compression 58.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. Scrap.co.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (50%)

Requests Now

42

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

scrap.co.jp

scrap.co.jp

1027 ms

spacer.gif

spacer.gif

471 ms

shadow.gif

shadow.gif

471 ms

index_01.jpg

index_01.jpg

669 ms

index_02.jpg

index_02.jpg

471 ms

index_03.gif

index_03.gif

480 ms

piPqZcv2UFs

piPqZcv2UFs

127 ms

top_ob_04.jpg

top_ob_04.jpg

3562 ms

index_20.gif

index_20.gif

1288 ms

index_21.gif

index_21.gif

534 ms

www-player.css

www-player.css

7 ms

www-embed-player.js

www-embed-player.js

36 ms

base.js

base.js

63 ms

ad_status.js

ad_status.js

184 ms

wAFWjcG1j0S59k6y9gmRkscrkcYt8sjUn-04af-yL2Q.js

wAFWjcG1j0S59k6y9gmRkscrkcYt8sjUn-04af-yL2Q.js

128 ms

embed.js

embed.js

53 ms

nph-count

nph-count

551 ms

index_24.gif

index_24.gif

185 ms

index_25.gif

index_25.gif

182 ms

index_27.gif

index_27.gif

226 ms

index_30.gif

index_30.gif

423 ms

point.gif

point.gif

424 ms

index_29.gif

index_29.gif

423 ms

index_34.gif

index_34.gif

423 ms

index_06.gif

index_06.gif

524 ms

index_14.gif

index_14.gif

534 ms

home.gif

home.gif

542 ms

company1.gif

company1.gif

568 ms

dott_line.gif

dott_line.gif

691 ms

ninka1.gif

ninka1.gif

712 ms

kankyou1.gif

kankyou1.gif

721 ms

goiken1.gif

goiken1.gif

735 ms

index_15.gif

index_15.gif

857 ms

index_16.gif

index_16.gif

888 ms

index_17.gif

index_17.gif

900 ms

index_18.gif

index_18.gif

906 ms

index_36.gif

index_36.gif

973 ms

index_37.gif

index_37.gif

1025 ms

index_39.gif

index_39.gif

1252 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

38 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

44 ms

id

id

25 ms

Create

Create

19 ms

GenerateIT

GenerateIT

13 ms

log_event

log_event

22 ms

Accessibility Review

scrap.co.jp accessibility score

60

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

scrap.co.jp best practices score

75

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

scrap.co.jp SEO score

67

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

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

scrap.co.jp

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