Tools & Wizards About Us
vanah.co.jp screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

vanah.co.jp

富士山からの水素珪素天然水 VanaH

Page Load Speed

9.7 sec in total

First Response

557 ms

Resources Loaded

8.8 sec

Page Rendered

357 ms

vanah.co.jp screenshot

About Website

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

ようこそ、富士山天然水合同会社のホームページへ。水素珪素天然水VanaH（バナH,バナ エイチ）は、厚さ1000mにおよぶ富士山の玄武岩層が生んだ天然水です。一人でも多くの方に、安全な水を安心して飲んでいただきたいという思いから、徹底した品質管理を行っているVanaH第一生産工場から皆様のもとへお届けしています。

Visit vanah.co.jp

Key Findings

We analyzed Vanah.co.jp page load time and found that the first response time was 557 ms and then it took 9.1 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

vanah.co.jp performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value1,040 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.065

97/100

15%

TTI (Time to Interactive)

Value13.3 s

12/100

10%

Network Requests Diagram

vanah.co.jp

557 ms

www.vanah.co.jp

1293 ms

style.min.css

181 ms

style.css

360 ms

jquery.fancybox.min.css

512 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 89% of them (86 requests) were addressed to the original Vanah.co.jp, 3% (3 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Vanah.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 314.2 kB (4%)

Content Size

7.1 MB

After Optimization

6.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-87%

Potential reduce by 74.0 kB

  • Original 85.5 kB
  • After minification 52.6 kB
  • After compression 11.5 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 33.0 kB, which is 39% 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 74.0 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 101.5 kB

  • Original 6.4 MB
  • After minification 6.3 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. VanaH images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 90.0 kB

  • Original 482.3 kB
  • After minification 482.3 kB
  • After compression 392.3 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 90.0 kB or 19% of the original size.

CSS Optimization

-34%

Potential reduce by 48.7 kB

  • Original 143.9 kB
  • After minification 143.8 kB
  • After compression 95.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. Vanah.co.jp needs all CSS files to be minified and compressed as it can save up to 48.7 kB or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (51%)

Requests Now

92

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of VanaH. 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 18 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

vanah.co.jp

vanah.co.jp

557 ms

www.vanah.co.jp

www.vanah.co.jp

1293 ms

style.min.css

style.min.css

181 ms

style.css

style.css

360 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

512 ms

mtssb-front.css

mtssb-front.css

517 ms

jquery.min.js

jquery.min.js

691 ms

jquery-migrate.min.js

jquery-migrate.min.js

529 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

537 ms

underscore.min.js

underscore.min.js

548 ms

infinite-scroll.pkgd.min.js

infinite-scroll.pkgd.min.js

683 ms

front.js

front.js

689 ms

foundation.min.css

foundation.min.css

885 ms

animate.css

animate.css

726 ms

swiper.css

swiper.css

732 ms

slick.css

slick.css

853 ms

style.css

style.css

862 ms

common.css

common.css

864 ms

font-awesome.css

font-awesome.css

895 ms

jquery.simpleTicker.css

jquery.simpleTicker.css

914 ms

js

js

74 ms

js

js

128 ms

js

js

66 ms

js

js

83 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

1206 ms

bootstrap.js

bootstrap.js

1035 ms

jquery.simpleTicker.js

jquery.simpleTicker.js

1058 ms

vivus.js

vivus.js

39 ms

wow.min.js

wow.min.js

1070 ms

slick.min.js

slick.min.js

1096 ms

googlemap.js

googlemap.js

1192 ms

googlemap02.js

googlemap02.js

1207 ms

googlemap_en.js

googlemap_en.js

1235 ms

googlemap02_en.js

googlemap02_en.js

1248 ms

jquery.cookie.js

jquery.cookie.js

1280 ms

jquery.jmap.min.js

jquery.jmap.min.js

1362 ms

booking.js

booking.js

1376 ms

swiper.js

swiper.js

1561 ms

jquery-ui.min.js

jquery-ui.min.js

41 ms

raindrops.js

raindrops.js

1412 ms

top.js

top.js

1424 ms

nav.js

nav.js

1462 ms

common.js

common.js

1533 ms

add.css

add.css

694 ms

loader-1.css

loader-1.css

730 ms

factory.css

factory.css

747 ms

other.css

other.css

789 ms

bootstrap.css

bootstrap.css

177 ms

css

css

34 ms

js

js

192 ms

analytics.js

analytics.js

187 ms

logo.png

logo.png

285 ms

search_icon01.png

search_icon01.png

283 ms

mainslide01.png

mainslide01.png

797 ms

slide_main_img.png

slide_main_img.png

282 ms

mainslide00.jpg

mainslide00.jpg

617 ms

caption04_ph.png

caption04_ph.png

654 ms

mainslide06.png

mainslide06.png

1143 ms

caption01_ph.png

caption01_ph.png

1161 ms

mainslide02.png

mainslide02.png

1346 ms

caption02_ph.png

caption02_ph.png

959 ms

mainslide03.png

mainslide03.png

4298 ms

caption06_ph.png

caption06_ph.png

973 ms

mainslide04.png

mainslide04.png

1471 ms

caption03_ph.png

caption03_ph.png

1150 ms

mainslide05.png

mainslide05.png

1495 ms

caption05_ph.png

caption05_ph.png

1329 ms

top_banner01.png

top_banner01.png

1338 ms

top_banner_fuel.png

top_banner_fuel.png

1505 ms

top_banner_gas.png

top_banner_gas.png

1515 ms

arrow_icon02.png

arrow_icon02.png

1523 ms

sec01_ph01.png

sec01_ph01.png

1643 ms

sec01_ph02.png

sec01_ph02.png

1671 ms

sec02_bg__1.png

sec02_bg__1.png

1678 ms

sec02_bg__2.png

sec02_bg__2.png

1693 ms

sec02_ph01.jpg

sec02_ph01.jpg

1701 ms

sec02_ph02.jpg

sec02_ph02.jpg

1813 ms

sec02_ph03.jpg

sec02_ph03.jpg

1843 ms

sec02_ph04.jpg

sec02_ph04.jpg

1850 ms

sec02_ph05.jpg

sec02_ph05.jpg

1870 ms

main_bg_2x.png

main_bg_2x.png

2955 ms

sec03_ph02.png

sec03_ph02.png

1986 ms

sec03_ph01.png

sec03_ph01.png

2022 ms

sec03_ph03.png

sec03_ph03.png

2200 ms

arrow_icon01.png

arrow_icon01.png

2046 ms

sec03_ph04.png

sec03_ph04.png

2164 ms

ticker_bn01.png

ticker_bn01.png

2096 ms

AlZy_zVFtYP12Zncg2kRcn38fh4Dog.ttf

AlZy_zVFtYP12Zncg2kRcn38fh4Dog.ttf

66 ms

collect

collect

38 ms

fa-solid-900.woff

fa-solid-900.woff

1949 ms

fa-regular-400.woff

fa-regular-400.woff

2057 ms

ticker_bn02.png

ticker_bn02.png

2089 ms

ticker_bn03.png

ticker_bn03.png

1763 ms

ticker_bn04.jpg

ticker_bn04.jpg

2103 ms

arrow_icon03.png

arrow_icon03.png

1716 ms

arrow_icon04.png

arrow_icon04.png

1586 ms

privacy_mark_icon.png

privacy_mark_icon.png

1579 ms

Accessibility Review

vanah.co.jp accessibility score

72

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

vanah.co.jp SEO score

74

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

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

    JA

  • Encoding

    UTF-8

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

vanah.co.jp

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