Report Summary

  • 5

    Performance

    Renders faster than
    20% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

sanwa.co.jp

サンワサプライ株式会社 - パソコン・タブレット周辺機器メーカー

Page Load Speed

14.7 sec in total

First Response

1.4 sec

Resources Loaded

13.1 sec

Page Rendered

199 ms

sanwa.co.jp screenshot

About Website

Welcome to sanwa.co.jp homepage info - get ready to check Sanwa best content for Japan right away, or after learning these important things about sanwa.co.jp

パソコン周辺機器などのサンワサプライのサイト。パソコンラック、パソコンデスク、キャリングバッグなどの情報が満載です。

Visit sanwa.co.jp

Key Findings

We analyzed Sanwa.co.jp page load time and found that the first response time was 1.4 sec and then it took 13.3 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

sanwa.co.jp performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

1/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value4,150 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.53

14/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

sanwa.co.jp

1412 ms

base_new.css

396 ms

jquery-ui.css

788 ms

home.css

598 ms

page_top.css

401 ms

Our browser made a total of 328 requests to load all elements on the main page. We found that 94% of them (308 requests) were addressed to the original Sanwa.co.jp, 1% (3 requests) were made to R2.snva.jp and 1% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Sanwa.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.4 MB (35%)

Content Size

6.8 MB

After Optimization

4.4 MB

In fact, the total size of Sanwa.co.jp main page is 6.8 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. 85% 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. Images take 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 85.7 kB

  • Original 106.0 kB
  • After minification 98.6 kB
  • After compression 20.3 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 85.7 kB or 81% of the original size.

Image Optimization

-6%

Potential reduce by 215.2 kB

  • Original 3.9 MB
  • After minification 3.7 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. Sanwa images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 1.7 MB

  • Original 2.3 MB
  • After minification 2.1 MB
  • After compression 642.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 1.7 MB or 72% of the original size.

CSS Optimization

-90%

Potential reduce by 414.3 kB

  • Original 462.6 kB
  • After minification 415.6 kB
  • After compression 48.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. Sanwa.co.jp needs all CSS files to be minified and compressed as it can save up to 414.3 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (20%)

Requests Now

324

After Optimization

258

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

Accessibility Review

sanwa.co.jp accessibility score

61

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

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

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

sanwa.co.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

sanwa.co.jp SEO score

92

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

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

    N/A

  • Encoding

    SHIFT_JIS

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

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