Tools & Wizards About Us
ido-mizu.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

ido-mizu.com

【井戸掘り業者 家庭用・業務用・防災用】なら井戸生活へ。＜東京、埼玉対応＞

Page Load Speed

14 sec in total

First Response

1.5 sec

Resources Loaded

10.9 sec

Page Rendered

1.6 sec

ido-mizu.com screenshot

About Website

Visit ido-mizu.com now to see the best up-to-date Ido Mizu content for Japan and also check out these interesting facts you probably never knew about ido-mizu.com

災害に備え、あなたのお庭に井戸を掘りませんか？ 井戸掘り専門業者の「井戸生活」にお任せ ください！硬い地層でも対応可能。 寿命の長い井戸をご提供します。「リフォームローン」・「水質検査」もご用意しております。ご家庭の生活井戸・マンションの防災井戸に是非「井戸生活」へ！！

Visit ido-mizu.com

Key Findings

We analyzed Ido-mizu.com page load time and found that the first response time was 1.5 sec and then it took 12.4 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

ido-mizu.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.442

21/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

ido-mizu.com

1513 ms

font-awesome.min.css

5 ms

style.css

1042 ms

simplegallery.js

523 ms

jquery-1.2.6.pack.js

869 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 91% of them (101 requests) were addressed to the original Ido-mizu.com, 2% (2 requests) were made to Googleads.g.doubleclick.net and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Ido-mizu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 434.9 kB (13%)

Content Size

3.4 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ido-mizu.com main page is 3.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. 40% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 31.1 kB

  • Original 41.6 kB
  • After minification 39.1 kB
  • After compression 10.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. 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 31.1 kB or 75% of the original size.

Image Optimization

-7%

Potential reduce by 229.9 kB

  • Original 3.1 MB
  • After minification 2.9 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. Ido Mizu images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 118.3 kB

  • Original 224.3 kB
  • After minification 218.9 kB
  • After compression 106.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 118.3 kB or 53% of the original size.

CSS Optimization

-82%

Potential reduce by 55.7 kB

  • Original 68.0 kB
  • After minification 54.8 kB
  • After compression 12.4 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. Ido-mizu.com needs all CSS files to be minified and compressed as it can save up to 55.7 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

107

After Optimization

87

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ido-mizu.com

ido-mizu.com

1513 ms

font-awesome.min.css

font-awesome.min.css

5 ms

style.css

style.css

1042 ms

simplegallery.js

simplegallery.js

523 ms

jquery-1.2.6.pack.js

jquery-1.2.6.pack.js

869 ms

styles.css

styles.css

352 ms

lightbox.min.css

lightbox.min.css

372 ms

jquery.js

jquery.js

1387 ms

jquery-migrate.min.js

jquery-migrate.min.js

745 ms

s_retargeting.js

s_retargeting.js

589 ms

conversion.js

conversion.js

13 ms

jquery.form.min.js

jquery.form.min.js

530 ms

scripts.js

scripts.js

363 ms

jquery.touchwipe.min.js

jquery.touchwipe.min.js

401 ms

jquery.lightbox.min.js

jquery.lightbox.min.js

528 ms

bg80.jpg

bg80.jpg

539 ms

logo2.jpg

logo2.jpg

743 ms

tel1.png

tel1.png

700 ms

top_hl1.png

top_hl1.png

521 ms

lptop1_pic.png

lptop1_pic.png

1562 ms

lptop1_1.png

lptop1_1.png

181 ms

lptop1_2.png

lptop1_2.png

356 ms

top_hl6.png

top_hl6.png

702 ms

riyuu4.png

riyuu4.png

1214 ms

riyuu1.png

riyuu1.png

1076 ms

riyuu2.png

riyuu2.png

1046 ms

riyuu3.png

riyuu3.png

1221 ms

riyuu5.png

riyuu5.png

928 ms

riyuu6.png

riyuu6.png

1300 ms

top_bt1.png

top_bt1.png

1395 ms

top_bt2.png

top_bt2.png

1257 ms

top_bt3.png

top_bt3.png

1388 ms

lptop3_h2.png

lptop3_h2.png

1913 ms

lptop3_pic.png

lptop3_pic.png

1795 ms

sonae3.png

sonae3.png

1487 ms

lptop3_pic1.png

lptop3_pic1.png

1734 ms

lptop3_pic2.png

lptop3_pic2.png

1916 ms

lptop3_pic3.png

lptop3_pic3.png

1859 ms

sonae6.png

sonae6.png

2079 ms

top_hl3.png

top_hl3.png

2253 ms

yousui1.jpg

yousui1.jpg

2512 ms

lptop5_h2.png

lptop5_h2.png

2230 ms

lptop5_pic.png

lptop5_pic.png

2434 ms

top_hl7.png

top_hl7.png

2438 ms

step1.jpg

step1.jpg

2772 ms

top_hl5.png

top_hl5.png

2418 ms

shitumon1.png

shitumon1.png

2427 ms

shitumon2.png

shitumon2.png

2606 ms

top_hl8.png

top_hl8.png

2774 ms

staffttl01.png

staffttl01.png

3297 ms

staff01.png

staff01.png

3126 ms

109 ms

ga.js

ga.js

27 ms

27 ms

516 ms

__utm.gif

__utm.gif

12 ms

629 ms

collect

collect

55 ms

staff02.png

staff02.png

3414 ms

staff03.png

staff03.png

2813 ms

staffttl02.png

staffttl02.png

2778 ms

staff04.png

staff04.png

3110 ms

staff05.png

staff05.png

2793 ms

staff06.png

staff06.png

2837 ms

staff07.png

staff07.png

3079 ms

staff08.png

staff08.png

3068 ms

contact_01.png

contact_01.png

3141 ms

contact_btn.png

contact_btn.png

2839 ms

contact_02.png

contact_02.png

3362 ms

banner4.png

banner4.png

2946 ms

banner5.png

banner5.png

3083 ms

bunner.png

bunner.png

3727 ms

ryoukin.png

ryoukin.png

3302 ms

banner0312.png

banner0312.png

3987 ms

banner2.png

banner2.png

2875 ms

banner3.png

banner3.png

2957 ms

footer_logo.png

footer_logo.png

3151 ms

footer_h3img.png

footer_h3img.png

2896 ms

gloval_navi1.png

gloval_navi1.png

3236 ms

gloval_navi2.png

gloval_navi2.png

2954 ms

gloval_navi3.png

gloval_navi3.png

3122 ms

gloval_navi4.png

gloval_navi4.png

2962 ms

gloval_navi5.png

gloval_navi5.png

3002 ms

main.jpg

main.jpg

5014 ms

main2.png

main2.png

5122 ms

main3.png

main3.png

4690 ms

lptop1_bg1.png

lptop1_bg1.png

3047 ms

lptop1_bg2.png

lptop1_bg2.png

2973 ms

riyuubg4.png

riyuubg4.png

3561 ms

riyuubg1.png

riyuubg1.png

3503 ms

riyuubg2.jpg

riyuubg2.jpg

3621 ms

riyuubg3.jpg

riyuubg3.jpg

3993 ms

riyuubg5.jpg

riyuubg5.jpg

3498 ms

riyuubg6.png

riyuubg6.png

3583 ms

sonae2.png

sonae2.png

3688 ms

sonaebg.png

sonaebg.png

3626 ms

lptop5_check.png

lptop5_check.png

3461 ms

shitumonbg.png

shitumonbg.png

3737 ms

shitumonbg2.png

shitumonbg2.png

3533 ms

staff_bg.png

staff_bg.png

4735 ms

bg_title_h2.png

bg_title_h2.png

3478 ms

bg.jpg

bg.jpg

4256 ms

contact_bg.png

contact_bg.png

4495 ms

bg_title_side.png

bg_title_side.png

3288 ms

bg_side.jpg

bg_side.jpg

3634 ms

btn_side.gif

btn_side.gif

3291 ms

footer_li.png

footer_li.png

3356 ms

footer.jpg

footer.jpg

3465 ms

left.gif

left.gif

3322 ms

pause.gif

pause.gif

3308 ms

right.gif

right.gif

3378 ms

Accessibility Review

ido-mizu.com accessibility score

67

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

button, link, and menuitem elements do not have accessible names.

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

ido-mizu.com best practices score

58

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

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

ido-mizu.com SEO score

83

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

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

    N/A

  • Encoding

    UTF-8

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

ido-mizu.com

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