7.4 sec in total
1.1 sec
6.2 sec
113 ms
Click here to check amazing G Beer content for Japan. Otherwise, check out these important facts you probably never knew about g-beer.jp
鳥取県・国立公園大山(だいせん)で、原料にこだわったビールと地酒造りをしています。すぐ近くには「平成の名水百選」にも選ばれた「地蔵滝の泉」と呼ばれる名水をはじめ、大山が育んだ伏流水が湧き出ています。原料も醸造所のすぐ近くで栽培。大山の自然を楽しんだ後は、直営レストラン【ガンバリウス】でビール・地酒をお楽しみください。
Visit g-beer.jpWe analyzed G-beer.jp page load time and found that the first response time was 1.1 sec and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
g-beer.jp performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value13.5 s
0/100
25%
Value10.9 s
6/100
10%
Value490 ms
59/100
30%
Value0.849
4/100
15%
Value10.4 s
24/100
10%
1107 ms
382 ms
581 ms
71 ms
929 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 50% of them (31 requests) were addressed to the original G-beer.jp, 34% (21 requests) were made to G-beer.sanin.jp and 6% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source G-beer.sanin.jp.
Page size can be reduced by 103.5 kB (10%)
1.0 MB
909.1 kB
In fact, the total size of G-beer.jp main page is 1.0 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. 25% of websites need less resources to load. Images take 875.6 kB which makes up the majority of the site volume.
Potential reduce by 17.9 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 17.9 kB or 79% of the original size.
Potential reduce by 9.7 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. G Beer images are well optimized though.
Potential reduce by 71.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 71.1 kB or 66% of the original size.
Potential reduce by 4.9 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. G-beer.jp needs all CSS files to be minified and compressed as it can save up to 4.9 kB or 75% of the original size.
Number of requests can be reduced by 23 (38%)
61
38
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of G Beer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
g-beer.jp
1107 ms
reset.css
382 ms
style.css
581 ms
js
71 ms
jquery-1.7.1.min.js
929 ms
original.js
554 ms
smoothscroll.js
572 ms
jquery.masonry.min.js
598 ms
171542293812290_box_l.jpg
1788 ms
171542499713702_box_m.jpg
914 ms
171542576614365_box_m.jpg
1131 ms
171542538214034_box_l.jpg
1330 ms
171774448430136_box_l.jpg
2895 ms
172173447514634_box_l.jpg
2820 ms
171542264512041_box_m.jpg
1306 ms
171542330912562_box_l.jpg
3401 ms
171542593814475_box_m.jpg
1680 ms
17217300868694_box_l.jpg
2508 ms
171946191012927_box_l.jpg
2083 ms
171542762415689_box_m.jpg
2156 ms
171653578524804_box_m.png
2809 ms
171542606614540_box_l.jpg
3381 ms
172173452914758_box_l.jpg
2867 ms
171542515413825_box_m.jpg
3018 ms
171542558414222_box_m.jpg
3169 ms
171868016627414_box_l.jpg
3477 ms
171542657914922_box_m.jpg
3569 ms
171542723915354_box_m.jpg
3202 ms
171575802111248_box_l.jpg
4349 ms
bg_01.gif
189 ms
icon_new_top.png
199 ms
tab_bg_w01.gif
199 ms
tab_bg_w02.png
198 ms
site_title.gif
181 ms
navi_top_03.gif
192 ms
navi_top_04.gif
362 ms
navi_top_05.gif
369 ms
navi_top_06.gif
383 ms
navi_top_07.gif
386 ms
tab_beer01.png
584 ms
tab_ganba01.png
934 ms
tab_kume01.png
721 ms
btn_mobile01.gif
550 ms
icon01.gif
578 ms
widgets.js
25 ms
like.php
521 ms
navi_top_03_over.gif
525 ms
navi_top_04_over.gif
675 ms
navi_top_05_over.gif
715 ms
navi_top_06_over.gif
718 ms
navi_top_07_over.gif
724 ms
tab_beer01_over.png
847 ms
tab_ganba01_over.png
1238 ms
tab_kume01_over.png
1047 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
29 ms
settings
97 ms
button.856debeac157d9669cf51e73a08fbc93.js
3 ms
embeds
30 ms
tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html
17 ms
7Sq0vGHTbTI.js
29 ms
FEppCFCt76d.png
28 ms
print_top.css
180 ms
g-beer.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
g-beer.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
g-beer.jp SEO score
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise G-beer.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 G-beer.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.
g-beer.jp
Open Graph data is detected on the main page of G Beer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: