Tools & Wizards About Us
gerogle.jp screenshot

Report Summary

  • 85

    Performance

    Renders faster than
    89% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

gerogle.jp

下呂温泉ぐるっと案内 - げろぐる -｜下呂温泉周辺のグルメを中心に、旅館・温泉・観光などの情報を発信

Page Load Speed

10.9 sec in total

First Response

3.3 sec

Resources Loaded

6.9 sec

Page Rendered

731 ms

gerogle.jp screenshot

About Website

Click here to check amazing Gerogle content for Japan. Otherwise, check out these important facts you probably never knew about gerogle.jp

下呂商工会公式ホームページ―下呂温泉周辺のグルメを中心に、旅館・温泉・観光などの情報を発信します。

Visit gerogle.jp

Key Findings

We analyzed Gerogle.jp page load time and found that the first response time was 3.3 sec and then it took 7.6 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

gerogle.jp performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

98/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.32

36/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

gerogle.jp

3292 ms

style.css

535 ms

lightbox.css

374 ms

AC_RunActiveContent.js

379 ms

jsapi

19 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 77% of them (57 requests) were addressed to the original Gerogle.jp, 7% (5 requests) were made to Google.com and 5% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Gerogle.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 133.0 kB (5%)

Content Size

2.8 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 22.1 kB

  • Original 28.9 kB
  • After minification 22.7 kB
  • After compression 6.8 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 6.2 kB, which is 21% 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 22.1 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 77.1 kB

  • Original 2.7 MB
  • After minification 2.6 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. Gerogle images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 7.0 kB

  • Original 26.1 kB
  • After minification 23.1 kB
  • After compression 19.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 7.0 kB or 27% of the original size.

CSS Optimization

-85%

Potential reduce by 26.8 kB

  • Original 31.7 kB
  • After minification 26.1 kB
  • After compression 4.8 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. Gerogle.jp needs all CSS files to be minified and compressed as it can save up to 26.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (44%)

Requests Now

73

After Optimization

41

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gerogle.jp

gerogle.jp

3292 ms

style.css

style.css

535 ms

lightbox.css

lightbox.css

374 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

379 ms

jsapi

jsapi

19 ms

blog_news.js

blog_news.js

591 ms

bg.gif

bg.gif

194 ms

bg_header.jpg

bg_header.jpg

529 ms

ar-r_sq.gif

ar-r_sq.gif

184 ms

gm.jpg

gm.jpg

378 ms

gerogle_kun.jpg

gerogle_kun.jpg

558 ms

panf_banner.jpg

panf_banner.jpg

937 ms

bnr_gg-gl.jpg

bnr_gg-gl.jpg

557 ms

bnr_madein_g.jpg

bnr_madein_g.jpg

569 ms

bnr_gero_business.jpg

bnr_gero_business.jpg

556 ms

blog.jpg

blog.jpg

928 ms

qr.php

qr.php

932 ms

banner02.gif

banner02.gif

932 ms

active_200x40.jpg

active_200x40.jpg

932 ms

bnr_link.jpg

bnr_link.jpg

930 ms

bnr_sem.jpg

bnr_sem.jpg

1174 ms

jigyosha_info.jpg

jigyosha_info.jpg

1199 ms

43.jpg

43.jpg

2232 ms

13.jpg

13.jpg

2732 ms

3.jpg

3.jpg

1389 ms

9.jpg

9.jpg

1583 ms

94.jpg

94.jpg

1524 ms

1.jpg

1.jpg

1964 ms

3.jpg

3.jpg

1578 ms

74.jpg

74.jpg

2057 ms

k-img01.jpg

k-img01.jpg

1763 ms

k-img02.jpg

k-img02.jpg

1766 ms

k-img03.jpg

k-img03.jpg

1948 ms

kensaku-btn.jpg

kensaku-btn.jpg

1950 ms

widgets.js

widgets.js

6 ms

btn_map.jpg

btn_map.jpg

2093 ms

btn_fanclub.jpg

btn_fanclub.jpg

2277 ms

st-bg_mobile.gif

st-bg_mobile.gif

2103 ms

mt-bg_new.jpg

mt-bg_new.jpg

2129 ms

mt-bg_pickup.jpg

mt-bg_pickup.jpg

2231 ms

ar-r_cr.gif

ar-r_cr.gif

2239 ms

th_g-g.gif

th_g-g.gif

2304 ms

th_g-s.jpg

th_g-s.jpg

2295 ms

th_g-n.jpg

th_g-n.jpg

2344 ms

th_g-e.jpg

th_g-e.jpg

2355 ms

13 ms

default+en.css

default+en.css

4 ms

default+en.I.js

default+en.I.js

11 ms

ga.js

ga.js

7 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

31 ms

__utm.gif

__utm.gif

46 ms

syndication

syndication

92 ms

345336479914008578

345336479914008578

270 ms

th_hotel.gif

th_hotel.gif

2168 ms

th_miyage.gif

th_miyage.gif

2063 ms

th_madeing.gif

th_madeing.gif

2051 ms

th_kigyo.gif

th_kigyo.gif

2154 ms

th_ryokumi.jpg

th_ryokumi.jpg

2169 ms

box01_top.gif

box01_top.gif

2172 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

3 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

6 ms

75b9b946f5104d7922189790eb53d027_normal.jpeg

75b9b946f5104d7922189790eb53d027_normal.jpeg

260 ms

buo0MsoO_normal.jpeg

buo0MsoO_normal.jpeg

260 ms

box01_middle.gif

box01_middle.gif

1828 ms

kensaku_midashi.gif

kensaku_midashi.gif

1856 ms

kensaku_tokubetsu.gif

kensaku_tokubetsu.gif

1961 ms

kensaku_janru.gif

kensaku_janru.gif

1978 ms

kensaku_syokuzai.gif

kensaku_syokuzai.gif

1982 ms

kensaku_time.gif

kensaku_time.gif

1993 ms

jot

jot

24 ms

box01_bottom.gif

box01_bottom.gif

1756 ms

bg_footer.gif

bg_footer.gif

1771 ms

ar-r.gif

ar-r.gif

1688 ms

Gfeeds

Gfeeds

178 ms

Accessibility Review

gerogle.jp accessibility score

76

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

gerogle.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

gerogle.jp SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gerogle.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 Gerogle.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

gerogle.jp

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