Tools & Wizards About Us
suzukin.jp screenshot

Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

suzukin.jp

鈴木金属 埼玉桶川 [高価買取] 鉄クズ 金属スクラップ アルミ 銅 電線 雑品 非鉄 相場 中古機械 フライス盤 工作機 プレス機 発電機 溶接機 東京,埼玉,千葉,群馬

Page Load Speed

8.8 sec in total

First Response

804 ms

Resources Loaded

7.9 sec

Page Rendered

133 ms

suzukin.jp screenshot

About Website

Welcome to suzukin.jp homepage info - get ready to check Suzukin best content right away, or after learning these important things about suzukin.jp

現金高価買取の鈴木金属では鉄くず,スクラップ,非鉄金属,アルミ,ステンレス,銅,真鍮,電線,雑品,特殊金属,中古機械,フライス盤,工作機,プレス機,発電機,溶接機等を買取/処分。産業廃棄物収集運搬や不用品回収・無料処分サービスも実施

Visit suzukin.jp

Key Findings

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

Performance Metrics

suzukin.jp performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value3.5 s

92/100

10%

Network Requests Diagram

suzukin.jp

804 ms

newstyle.css

460 ms

common.js

330 ms

news.php

5766 ms

back.jpg

158 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 93% of them (39 requests) were addressed to the original Suzukin.jp, 5% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Hi-power.jp. The less responsive or slowest element that took the longest time to load (5.8 sec) relates to the external source Hi-power.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.9 kB (9%)

Content Size

230.7 kB

After Optimization

210.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 7.5 kB

  • Original 10.1 kB
  • After minification 9.0 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 1.2 kB, which is 12% 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 7.5 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 188.6 kB
  • After minification 188.6 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. Suzukin images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 1.2 kB

  • Original 19.3 kB
  • After minification 19.1 kB
  • After compression 18.0 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

-88%

Potential reduce by 11.2 kB

  • Original 12.8 kB
  • After minification 12.2 kB
  • After compression 1.6 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. Suzukin.jp needs all CSS files to be minified and compressed as it can save up to 11.2 kB or 88% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

37

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Suzukin. According to our analytics all requests are already optimized.

Network Requests Diagram

suzukin.jp

suzukin.jp

804 ms

newstyle.css

newstyle.css

460 ms

common.js

common.js

330 ms

news.php

news.php

5766 ms

back.jpg

back.jpg

158 ms

header_bar.jpg

header_bar.jpg

155 ms

menu_r1_c8.jpg

menu_r1_c8.jpg

165 ms

header.jpg

header.jpg

462 ms

menu_r3_c2.jpg

menu_r3_c2.jpg

310 ms

menu_r3_c3.jpg

menu_r3_c3.jpg

314 ms

menu_r3_c5.jpg

menu_r3_c5.jpg

330 ms

menu_r3_c6.jpg

menu_r3_c6.jpg

342 ms

menu_r3_c7.jpg

menu_r3_c7.jpg

366 ms

menu_r3_c9.jpg

menu_r3_c9.jpg

463 ms

top_visual.jpg

top_visual.jpg

782 ms

tp_r1_c1.jpg

tp_r1_c1.jpg

657 ms

tp_r2_c5.jpg

tp_r2_c5.jpg

513 ms

3d.jpg

3d.jpg

905 ms

menu_r6_c2.jpg

menu_r6_c2.jpg

620 ms

menu_r7_c2.jpg

menu_r7_c2.jpg

619 ms

jirei.jpg

jirei.jpg

684 ms

menu_r8_c2.jpg

menu_r8_c2.jpg

775 ms

tp_r4_c5.jpg

tp_r4_c5.jpg

774 ms

tp_r10_c5.jpg

tp_r10_c5.jpg

820 ms

sv_r1_c1.jpg

sv_r1_c1.jpg

855 ms

sv_r1_c3.jpg

sv_r1_c3.jpg

927 ms

sv_r1_c5.jpg

sv_r1_c5.jpg

927 ms

footer.jpg

footer.jpg

940 ms

ga.js

ga.js

13 ms

__utm.gif

__utm.gif

13 ms

newstyle.css

newstyle.css

680 ms

common.js

common.js

536 ms

back.jpg

back.jpg

170 ms

null.jpg

null.jpg

158 ms

top_25_over.gif

top_25_over.gif

155 ms

menu_r1_c8_f2.jpg

menu_r1_c8_f2.jpg

166 ms

menu_r3_c2_f2.jpg

menu_r3_c2_f2.jpg

184 ms

menu_r3_c3_f2.jpg

menu_r3_c3_f2.jpg

155 ms

menu_r3_c5_f2.jpg

menu_r3_c5_f2.jpg

173 ms

menu_r3_c6_f2.jpg

menu_r3_c6_f2.jpg

308 ms

menu_r3_c7_f2.jpg

menu_r3_c7_f2.jpg

309 ms

menu_r3_c9_f2.jpg

menu_r3_c9_f2.jpg

312 ms

Accessibility Review

suzukin.jp accessibility score

54

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

suzukin.jp best practices score

67

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

Browser errors were logged to the console

SEO Factors

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Suzukin.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 Suzukin.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

suzukin.jp

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