Tools & Wizards About Us

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

src.ne.jp

株式会社エスアールシー(SRC)【コーポレートサイト】

Page Load Speed

15.1 sec in total

First Response

989 ms

Resources Loaded

13.7 sec

Page Rendered

428 ms

About Website

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

金属リサイクル、貴金属買取／販売のK.G.B.神戸ゴールドバンク、歯科金属・金パラ買取のシカキン、超硬スクラップ買取の超硬ドットコム、アンティーク家具・雑貨の神戸アンティークウェアハウスなど、様々なリサイクル＆リユース事業を展開しています。

Visit src.ne.jp

Key Findings

We analyzed Src.ne.jp page load time and found that the first response time was 989 ms and then it took 14.1 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

src.ne.jp performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value39.4 s

0/100

25%

SI (Speed Index)

Value18.7 s

0/100

10%

TBT (Total Blocking Time)

Value1,380 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

Network Requests Diagram

src.ne.jp

989 ms

import_131224.css

345 ms

rollover.js

356 ms

jquery.js

1941 ms

scroll.js

356 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 98% of them (107 requests) were addressed to the original Src.ne.jp, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Src.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 239.5 kB (10%)

Content Size

2.3 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 19.5 kB

  • Original 25.6 kB
  • After minification 22.4 kB
  • After compression 6.1 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 3.2 kB, which is 13% 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 19.5 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 16.1 kB

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

JavaScript Optimization

-66%

Potential reduce by 158.5 kB

  • Original 241.1 kB
  • After minification 214.8 kB
  • After compression 82.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 158.5 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 45.5 kB

  • Original 55.0 kB
  • After minification 42.3 kB
  • After compression 9.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. Src.ne.jp needs all CSS files to be minified and compressed as it can save up to 45.5 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

107

After Optimization

80

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

src.ne.jp accessibility score

83

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

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

src.ne.jp best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

src.ne.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 Src.ne.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 Src.ne.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

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