Tools & Wizards About Us
s-grow.co.jp screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

s-grow.co.jp

通販EC物流・越境ECなら株式会社エスグロー

Page Load Speed

7.4 sec in total

First Response

852 ms

Resources Loaded

5.4 sec

Page Rendered

1.1 sec

s-grow.co.jp screenshot

About Website

Welcome to s-grow.co.jp homepage info - get ready to check S Grow best content right away, or after learning these important things about s-grow.co.jp

通販・EC物流、越境ECなら株式会社エスグローにお任せ下さい！変動費にこだわり多品種が得意な関西の物流会社。ネクストエンジン・Ship&co・shopifyも連携可能。

Visit s-grow.co.jp

Key Findings

We analyzed S-grow.co.jp page load time and found that the first response time was 852 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

s-grow.co.jp performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value290 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.125

83/100

15%

TTI (Time to Interactive)

Value7.2 s

51/100

10%

Network Requests Diagram

www.s-grow.co.jp

852 ms

notosansjapanese.css

38 ms

style.css

356 ms

swiper.css

357 ms

css

58 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 94% of them (88 requests) were addressed to the original S-grow.co.jp, 3% (3 requests) were made to Fonts.googleapis.com and 1% (1 request) were made to Kit.fontawesome.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain S-grow.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 479.8 kB (11%)

Content Size

4.4 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of S-grow.co.jp main page is 4.4 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. 45% of websites need less resources to load. Images take 4.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 44.1 kB

  • Original 56.4 kB
  • After minification 54.4 kB
  • After compression 12.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 44.1 kB or 78% of the original size.

Image Optimization

-9%

Potential reduce by 385.1 kB

  • Original 4.1 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. S Grow images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 26.6 kB

  • Original 130.1 kB
  • After minification 129.8 kB
  • After compression 103.5 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 26.6 kB or 20% of the original size.

CSS Optimization

-33%

Potential reduce by 24.1 kB

  • Original 72.3 kB
  • After minification 72.2 kB
  • After compression 48.2 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. S-grow.co.jp needs all CSS files to be minified and compressed as it can save up to 24.1 kB or 33% of the original size.

Requests Breakdown

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

Requests Now

59

After Optimization

38

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.s-grow.co.jp

www.s-grow.co.jp

852 ms

notosansjapanese.css

notosansjapanese.css

38 ms

style.css

style.css

356 ms

swiper.css

swiper.css

357 ms

css

css

58 ms

css

css

65 ms

0aa60be6c9.js

0aa60be6c9.js

63 ms

style_pp.min.css

style_pp.min.css

362 ms

js

js

72 ms

style.min.css

style.min.css

360 ms

styles.css

styles.css

364 ms

styles.css

styles.css

376 ms

style.css

style.css

533 ms

jquery.min.js

jquery.min.js

534 ms

jquery-migrate.min.js

jquery-migrate.min.js

548 ms

lazysizes.min.js

lazysizes.min.js

554 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

27 ms

pp_slider.js

pp_slider.js

560 ms

scripts.js

scripts.js

710 ms

jquery.form.min.js

jquery.form.min.js

542 ms

scripts.js

scripts.js

552 ms

navigation.js

navigation.js

563 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

563 ms

style.css

style.css

909 ms

swiper.css

swiper.css

744 ms

style.min.css

style.min.css

933 ms

style_pp.min.css

style_pp.min.css

746 ms

styles.css

styles.css

744 ms

styles.css

styles.css

736 ms

style.css

style.css

933 ms

jquery.min.js

jquery.min.js

940 ms

jquery-migrate.min.js

jquery-migrate.min.js

744 ms

swiper.js

swiper.js

1227 ms

lazysizes.min.js

lazysizes.min.js

888 ms

pp_slider.js

pp_slider.js

914 ms

scripts.js

scripts.js

765 ms

jquery.form.min.js

jquery.form.min.js

905 ms

scripts.js

scripts.js

921 ms

navigation.js

navigation.js

917 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

921 ms

device.css

device.css

399 ms

header_bg.png

header_bg.png

188 ms

tab_icon.png

tab_icon.png

184 ms

mitsumori_icon.png

mitsumori_icon.png

181 ms

contact_icon.png

contact_icon.png

185 ms

top_main1.jpg

top_main1.jpg

730 ms

top_main2.jpg

top_main2.jpg

731 ms

top_main3.jpg

top_main3.jpg

718 ms

top_main4.jpg

top_main4.jpg

1096 ms

top_main5.jpg

top_main5.jpg

1481 ms

midashi_w.png

midashi_w.png

186 ms

midashi_bk.png

midashi_bk.png

185 ms

banner_02.jpg

banner_02.jpg

555 ms

linkTab01.png

linkTab01.png

181 ms

linkTab02.png

linkTab02.png

182 ms

linkTab03.png

linkTab03.png

180 ms

banner_co01.png

banner_co01.png

187 ms

banner_co02.png

banner_co02.png

359 ms

banner_co03.png

banner_co03.png

358 ms

banner_co04.png

banner_co04.png

361 ms

banner_co05.png

banner_co05.png

368 ms

banner_co06.png

banner_co06.png

367 ms

banner_co07.png

banner_co07.png

370 ms

banner_co08.png

banner_co08.png

536 ms

banner_co09.png

banner_co09.png

536 ms

banner_04.jpg

banner_04.jpg

1676 ms

banner_01.jpg

banner_01.jpg

1074 ms

banner_03.jpg

banner_03.jpg

1093 ms

top_ec_bnr.png

top_ec_bnr.png

539 ms

top_ec_bnr_sp.svg

top_ec_bnr_sp.svg

549 ms

company_banner.jpg

company_banner.jpg

916 ms

message_banner.jpg

message_banner.jpg

1101 ms

base_banner.jpg

base_banner.jpg

1258 ms

recruit_banner.jpg

recruit_banner.jpg

1280 ms

icon_tab_black.svg

icon_tab_black.svg

1276 ms

contact_tel_box.png

contact_tel_box.png

1591 ms

contact_tel.png

contact_tel.png

476 ms

linkTab03.png

linkTab03.png

1262 ms

linkTab01.png

linkTab01.png

1282 ms

linkTab02.png

linkTab02.png

1285 ms

midashi_bk.png

midashi_bk.png

1437 ms

midashi_w.png

midashi_w.png

1461 ms

banner_co01.png

banner_co01.png

1463 ms

banner_co03.png

banner_co03.png

1306 ms

banner_co02.png

banner_co02.png

1443 ms

banner_co04.png

banner_co04.png

1469 ms

banner_co06.png

banner_co06.png

1464 ms

banner_co05.png

banner_co05.png

1481 ms

banner_co07.png

banner_co07.png

1479 ms

banner_co08.png

banner_co08.png

1327 ms

banner_co09.png

banner_co09.png

1444 ms

top_ec_bnr.png

top_ec_bnr.png

1474 ms

top_ec_bnr_sp.svg

top_ec_bnr_sp.svg

1467 ms

contact_tel.png

contact_tel.png

1481 ms

Accessibility Review

s-grow.co.jp accessibility score

61

Accessibility Issues

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

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

s-grow.co.jp best practices score

67

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

s-grow.co.jp SEO score

84

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

Links do not have descriptive text

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 S-grow.co.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 S-grow.co.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

s-grow.co.jp

Open Graph data is detected on the main page of S Grow. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: