Tools & Wizards About Us
gremz-pwater.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

gremz-pwater.co.jp

ウォーターサーバーのレンタル・宅配の「グリムスプレミアムウォーター」

Page Load Speed

5.2 sec in total

First Response

919 ms

Resources Loaded

3.9 sec

Page Rendered

354 ms

gremz-pwater.co.jp screenshot

About Website

Click here to check amazing Gremz Pwater content. Otherwise, check out these important facts you probably never knew about gremz-pwater.co.jp

プレミアムフジは、ウォーターサーバーをレンタルし、ご自宅までお水を宅配（定期配送）するサービスです。重いお水を買いに行ったり、お湯を沸かす手間が省け、美味しい天然水をいつでも使うことができます。

Visit gremz-pwater.co.jp

Key Findings

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

Performance Metrics

gremz-pwater.co.jp performance score

0

Network Requests Diagram

gremz-pwater.co.jp

919 ms

style.css

488 ms

ga.js

57 ms

img_main.jpg

1464 ms

img_price.jpg

815 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 84% of them (21 requests) were addressed to the original Gremz-pwater.co.jp, 16% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Gremz-pwater.co.jp.

Page Optimization Overview & Recommendations

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

Content Size

920.1 kB

After Optimization

884.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gremz-pwater.co.jp main page is 920.1 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. 15% of websites need less resources to load. Images take 864.7 kB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 6.5 kB

  • Original 10.9 kB
  • After minification 10.3 kB
  • After compression 4.4 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 6.5 kB or 60% of the original size.

Image Optimization

-3%

Potential reduce by 23.9 kB

  • Original 864.7 kB
  • After minification 840.8 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. Gremz Pwater images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 84 B

  • Original 38.2 kB
  • After minification 38.2 kB
  • After compression 38.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-76%

Potential reduce by 4.8 kB

  • Original 6.4 kB
  • After minification 4.3 kB
  • After compression 1.6 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. Gremz-pwater.co.jp needs all CSS files to be minified and compressed as it can save up to 4.8 kB or 76% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

24

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gremz-pwater.co.jp

gremz-pwater.co.jp

919 ms

style.css

style.css

488 ms

ga.js

ga.js

57 ms

img_main.jpg

img_main.jpg

1464 ms

img_price.jpg

img_price.jpg

815 ms

img_buy.gif

img_buy.gif

810 ms

info-box-line.gif

info-box-line.gif

352 ms

subtitle_info.gif

subtitle_info.gif

534 ms

title_kodawari.gif

title_kodawari.gif

763 ms

subtitle_kodawari01.gif

subtitle_kodawari01.gif

527 ms

img_kodawari01.jpg

img_kodawari01.jpg

1967 ms

subtitle_kodawari02.gif

subtitle_kodawari02.gif

711 ms

ctitle_panagium.gif

ctitle_panagium.gif

890 ms

ctitle_aen.gif

ctitle_aen.gif

954 ms

title_server.gif

title_server.gif

1130 ms

bg_s01.jpg

bg_s01.jpg

1139 ms

ctitle_s01.gif

ctitle_s01.gif

1066 ms

bg_s02.jpg

bg_s02.jpg

1526 ms

ctitle_s02.gif

ctitle_s02.gif

1243 ms

bg_s03.jpg

bg_s03.jpg

1619 ms

ctitle_s03.gif

ctitle_s03.gif

1302 ms

img_6color.jpg

img_6color.jpg

2843 ms

analytics.js

analytics.js

19 ms

__utm.gif

__utm.gif

24 ms

collect

collect

34 ms

SEO Factors

gremz-pwater.co.jp SEO score

0

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 Gremz-pwater.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 Gremz-pwater.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

gremz-pwater.co.jp

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