Tools & Wizards About Us
souko-hikaku.com screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

souko-hikaku.com

物流倉庫や物流代行サービス業者を探すなら倉庫比較ドットコム

Page Load Speed

10.8 sec in total

First Response

701 ms

Resources Loaded

9.7 sec

Page Rendered

384 ms

souko-hikaku.com screenshot

About Website

Welcome to souko-hikaku.com homepage info - get ready to check Souko Hikaku best content right away, or after learning these important things about souko-hikaku.com

物流倉庫や物流代行サービスをお探しなら、専門業者を1度のお問い合わせで90社以上の中からお客様のニーズに沿って探せる倉庫比較ドットコムへ。

Visit souko-hikaku.com

Key Findings

We analyzed Souko-hikaku.com page load time and found that the first response time was 701 ms and then it took 10.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

souko-hikaku.com performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

36/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value3.5 s

89/100

10%

TBT (Total Blocking Time)

Value150 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value3.8 s

90/100

10%

Network Requests Diagram

souko-hikaku.com

701 ms

base.css

182 ms

style.css

317 ms

check.js

332 ms

jquery.min.js

339 ms

Our browser made a total of 201 requests to load all elements on the main page. We found that 14% of them (29 requests) were addressed to the original Souko-hikaku.com, 86% (172 requests) were made to Ikkatsu.jp. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Ikkatsu.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 128.7 kB (47%)

Content Size

273.7 kB

After Optimization

144.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Souko-hikaku.com main page is 273.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. 45% of websites need less resources to load. Images take 166.5 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 37.7 kB

  • Original 45.0 kB
  • After minification 37.9 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 7.1 kB, which is 16% 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 37.7 kB or 84% of the original size.

Image Optimization

-23%

Potential reduce by 38.5 kB

  • Original 166.5 kB
  • After minification 128.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. Obviously, Souko Hikaku needs image optimization as it can save up to 38.5 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-76%

Potential reduce by 973 B

  • Original 1.3 kB
  • After minification 863 B
  • After compression 310 B

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 973 B or 76% of the original size.

CSS Optimization

-85%

Potential reduce by 51.6 kB

  • Original 60.8 kB
  • After minification 45.0 kB
  • After compression 9.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. Souko-hikaku.com needs all CSS files to be minified and compressed as it can save up to 51.6 kB or 85% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

193

After Optimization

193

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

souko-hikaku.com

souko-hikaku.com

701 ms

base.css

base.css

182 ms

style.css

style.css

317 ms

check.js

check.js

332 ms

jquery.min.js

jquery.min.js

339 ms

jquery.selectnav.js

jquery.selectnav.js

342 ms

custom.js

custom.js

364 ms

jquery-2.0.2.min.js

jquery-2.0.2.min.js

348 ms

Chart.js

Chart.js

475 ms

ga.js

ga.js

539 ms

hasegawa.gif

hasegawa.gif

304 ms

core.gif

core.gif

293 ms

logi.gif

logi.gif

295 ms

adjust.gif

adjust.gif

295 ms

daikyo.gif

daikyo.gif

297 ms

wakasu.gif

wakasu.gif

300 ms

shibusawa.gif

shibusawa.gif

564 ms

s_grow.gif

s_grow.gif

584 ms

good.gif

good.gif

586 ms

makino.gif

makino.gif

591 ms

nippack.gif

nippack.gif

593 ms

fesm.gif

fesm.gif

589 ms

citi.gif

citi.gif

853 ms

dai.gif

dai.gif

875 ms

address.gif

address.gif

877 ms

mahalo.gif

mahalo.gif

882 ms

value.gif

value.gif

880 ms

ognis.gif

ognis.gif

884 ms

proud.gif

proud.gif

1142 ms

spal.gif

spal.gif

1164 ms

toyo.gif

toyo.gif

1166 ms

hachi.gif

hachi.gif

1168 ms

kuri.gif

kuri.gif

1169 ms

tanaka.gif

tanaka.gif

1174 ms

seiwa.gif

seiwa.gif

1436 ms

3s.gif

3s.gif

1452 ms

spool.gif

spool.gif

1455 ms

zest.gif

zest.gif

1457 ms

pro-c.gif

pro-c.gif

1457 ms

taika.gif

taika.gif

1462 ms

g-homes.gif

g-homes.gif

1726 ms

ngsm.gif

ngsm.gif

1742 ms

wl.gif

wl.gif

1744 ms

jpr.gif

jpr.gif

1747 ms

alpha.gif

alpha.gif

1746 ms

bln.gif

bln.gif

1755 ms

logo.png

logo.png

236 ms

inquiry1.png

inquiry1.png

253 ms

freedial.png

freedial.png

227 ms

01_14.png

01_14.png

219 ms

01_18.png

01_18.png

385 ms

inquiry2.png

inquiry2.png

237 ms

01_28.png

01_28.png

389 ms

01_30.png

01_30.png

392 ms

01_34.png

01_34.png

402 ms

01_38.png

01_38.png

583 ms

01_56.png

01_56.png

438 ms

01_43.png

01_43.png

550 ms

01_47.png

01_47.png

891 ms

01_49.png

01_49.png

546 ms

01_53.png

01_53.png

566 ms

inquiry3.png

inquiry3.png

640 ms

01_62.png

01_62.png

713 ms

65_62.png

65_62.png

714 ms

69_69_92.png

69_69_92.png

735 ms

tlm.gif

tlm.gif

1751 ms

no.gif

no.gif

1748 ms

neo.gif

neo.gif

1748 ms

kamotsu.gif

kamotsu.gif

1748 ms

kentaku.gif

kentaku.gif

1749 ms

aishow.gif

aishow.gif

1755 ms

ymk.gif

ymk.gif

1750 ms

mynavi.gif

mynavi.gif

1745 ms

ktzw.gif

ktzw.gif

1751 ms

kshin.gif

kshin.gif

1743 ms

tsk.gif

tsk.gif

1744 ms

tsn.gif

tsn.gif

1752 ms

covered.gif

covered.gif

1750 ms

krt.gif

krt.gif

1745 ms

kohu.gif

kohu.gif

1748 ms

sus.gif

sus.gif

1745 ms

mori.gif

mori.gif

1744 ms

xrs.gif

xrs.gif

1751 ms

idb.gif

idb.gif

1750 ms

ktmt.gif

ktmt.gif

1748 ms

nmt.gif

nmt.gif

1748 ms

ksn.gif

ksn.gif

1746 ms

fnd.gif

fnd.gif

1753 ms

showa.gif

showa.gif

1750 ms

oct.gif

oct.gif

1747 ms

iuc.gif

iuc.gif

1749 ms

ksp.gif

ksp.gif

1749 ms

ras.gif

ras.gif

1748 ms

mrs.gif

mrs.gif

1756 ms

psl.gif

psl.gif

1756 ms

digo.gif

digo.gif

1747 ms

ses.gif

ses.gif

1749 ms

liner.gif

liner.gif

1749 ms

craft.gif

craft.gif

1746 ms

tws.gif

tws.gif

1755 ms

ktrg.gif

ktrg.gif

1753 ms

tele.gif

tele.gif

1748 ms

ace.gif

ace.gif

1749 ms

kmym.gif

kmym.gif

1749 ms

fline.gif

fline.gif

1747 ms

snl.gif

snl.gif

1763 ms

tcom.gif

tcom.gif

1753 ms

dais.gif

dais.gif

1749 ms

arr.gif

arr.gif

1749 ms

tdkr.gif

tdkr.gif

1746 ms

mitsuba.gif

mitsuba.gif

1747 ms

tome.gif

tome.gif

1763 ms

ybsk.gif

ybsk.gif

1760 ms

best.gif

best.gif

1749 ms

nw.gif

nw.gif

1749 ms

wm.gif

wm.gif

1746 ms

hira.gif

hira.gif

1745 ms

ams.gif

ams.gif

1762 ms

glg.gif

glg.gif

1760 ms

nhs.gif

nhs.gif

1757 ms

ths.gif

ths.gif

1744 ms

sze.gif

sze.gif

1745 ms

knt.gif

knt.gif

1745 ms

nis.gif

nis.gif

1756 ms

swel.gif

swel.gif

1768 ms

osaki.gif

osaki.gif

1756 ms

dsp.gif

dsp.gif

1745 ms

azm.gif

azm.gif

1748 ms

knd.gif

knd.gif

1747 ms

no.gif

no.gif

1754 ms

no.gif

no.gif

1763 ms

hun.gif

hun.gif

1763 ms

no.gif

no.gif

1746 ms

no.gif

no.gif

1749 ms

no.gif

no.gif

1750 ms

aggs.gif

aggs.gif

1754 ms

no.gif

no.gif

1763 ms

no.gif

no.gif

1763 ms

no.gif

no.gif

1747 ms

no.gif

no.gif

1750 ms

no.gif

no.gif

1750 ms

no.gif

no.gif

1748 ms

no.gif

no.gif

1760 ms

no.gif

no.gif

1763 ms

no.gif

no.gif

1749 ms

no.gif

no.gif

1758 ms

no.gif

no.gif

1755 ms

no.gif

no.gif

1746 ms

no.gif

no.gif

1763 ms

no.gif

no.gif

1764 ms

no.gif

no.gif

1754 ms

no.gif

no.gif

1760 ms

no.gif

no.gif

1763 ms

no.gif

no.gif

1747 ms

no.gif

no.gif

1772 ms

no.gif

no.gif

1756 ms

no.gif

no.gif

1763 ms

no.gif

no.gif

1767 ms

no.gif

no.gif

1766 ms

no.gif

no.gif

1750 ms

no.gif

no.gif

1764 ms

no.gif

no.gif

1756 ms

no.gif

no.gif

1768 ms

no.gif

no.gif

1762 ms

no.gif

no.gif

1762 ms

no.gif

no.gif

1748 ms

no.gif

no.gif

1763 ms

no.gif

no.gif

1751 ms

no.gif

no.gif

1767 ms

no.gif

no.gif

1761 ms

no.gif

no.gif

1760 ms

no.gif

no.gif

1750 ms

no.gif

no.gif

1762 ms

no.gif

no.gif

1751 ms

no.gif

no.gif

1768 ms

no.gif

no.gif

1764 ms

no.gif

no.gif

1766 ms

no.gif

no.gif

1758 ms

no.gif

no.gif

1772 ms

no.gif

no.gif

1749 ms

no.gif

no.gif

1769 ms

no.gif

no.gif

1758 ms

no.gif

no.gif

1758 ms

no.gif

no.gif

1759 ms

no.gif

no.gif

1764 ms

no.gif

no.gif

1754 ms

no.gif

no.gif

1763 ms

no.gif

no.gif

1755 ms

no.gif

no.gif

1751 ms

no.gif

no.gif

1758 ms

no.gif

no.gif

1755 ms

no.gif

no.gif

1763 ms

no.gif

no.gif

1756 ms

no.gif

no.gif

1751 ms

no.gif

no.gif

1757 ms

no.gif

no.gif

1757 ms

no.gif

no.gif

1763 ms

no.gif

no.gif

1771 ms

no.gif

no.gif

1752 ms

no.gif

no.gif

1753 ms

no.gif

no.gif

1758 ms

Accessibility Review

souko-hikaku.com accessibility score

86

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

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

Best Practices

souko-hikaku.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

souko-hikaku.com SEO score

100

Search Engine Optimization Advices

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

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 Souko-hikaku.com 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 Souko-hikaku.com 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

souko-hikaku.com

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