Tools & Wizards About Us
umaimon.net screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

umaimon.net

飛騨・高山のグルメや観光情報「高山うまいもんマップ」

Page Load Speed

5.5 sec in total

First Response

742 ms

Resources Loaded

4.3 sec

Page Rendered

504 ms

umaimon.net screenshot

About Website

Click here to check amazing Umaimon content for Japan. Otherwise, check out these important facts you probably never knew about umaimon.net

飛騨・高山のグルメと観光情報「高山うまいもんマップ」。飛騨牛・高山ラーメン・食べ歩き・郷土料理・地酒。おすすめの美味しいお店をご紹介。地元で人気の隠れ家的なお店も掲載。宮川朝市などの一押しスポットも！

Visit umaimon.net

Key Findings

We analyzed Umaimon.net page load time and found that the first response time was 742 ms and then it took 4.8 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

umaimon.net performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value20.6 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value1,630 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.266

46/100

15%

TTI (Time to Interactive)

Value25.7 s

0/100

10%

Network Requests Diagram

umaimon.net

742 ms

www.umaimon.net

27 ms

www.umaimon.net

1306 ms

reset.css

22 ms

jquery.bxslider.css

25 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 71% of them (60 requests) were addressed to the original Umaimon.net, 7% (6 requests) were made to Apis.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 (1.4 sec) relates to the external source Developers.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 119.9 kB (6%)

Content Size

2.1 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Umaimon.net main page is 2.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. 70% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 47.5 kB

  • Original 63.6 kB
  • After minification 62.0 kB
  • After compression 16.1 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 47.5 kB or 75% of the original size.

Image Optimization

-4%

Potential reduce by 62.1 kB

  • Original 1.7 MB
  • After minification 1.7 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. Umaimon images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 8.4 kB

  • Original 325.0 kB
  • After minification 324.9 kB
  • After compression 316.7 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

-20%

Potential reduce by 2.0 kB

  • Original 10.0 kB
  • After minification 9.6 kB
  • After compression 8.0 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. Umaimon.net needs all CSS files to be minified and compressed as it can save up to 2.0 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (38%)

Requests Now

77

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

umaimon.net

umaimon.net

742 ms

www.umaimon.net

www.umaimon.net

27 ms

www.umaimon.net

www.umaimon.net

1306 ms

reset.css

reset.css

22 ms

jquery.bxslider.css

jquery.bxslider.css

25 ms

common.css

common.css

26 ms

style.css

style.css

521 ms

js

js

80 ms

oxm8znn.js

oxm8znn.js

181 ms

respond.src.js

respond.src.js

496 ms

jquery-1.9.0.min.js

jquery-1.9.0.min.js

43 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

33 ms

instagram.min.js

instagram.min.js

32 ms

jquery.autopager-1.0.0.js

jquery.autopager-1.0.0.js

33 ms

common.js

common.js

43 ms

js

js

68 ms

platform.js

platform.js

38 ms

wpp.css

wpp.css

40 ms

jquery.js

jquery.js

49 ms

jquery-migrate.min.js

jquery-migrate.min.js

52 ms

jquery.sonar.min.js

jquery.sonar.min.js

610 ms

lazy-load.js

lazy-load.js

50 ms

wp-embed.min.js

wp-embed.min.js

610 ms

p.gif

p.gif

123 ms

munchkin.js

munchkin.js

97 ms

header_bg.png

header_bg.png

85 ms

logo.png

logo.png

84 ms

key_image_01-1-1600x800.jpg

key_image_01-1-1600x800.jpg

87 ms

banner_key.png

banner_key.png

84 ms

key_image_02-1600x800.jpg

key_image_02-1600x800.jpg

98 ms

key_image_03-1600x800.jpg

key_image_03-1600x800.jpg

99 ms

search_bg.gif

search_bg.gif

98 ms

fixed_logo.png

fixed_logo.png

97 ms

icon_select.png

icon_select.png

97 ms

icon_search.png

icon_search.png

144 ms

search_ttl_icon.png

search_ttl_icon.png

146 ms

map.png

map.png

147 ms

lead_inner_bg.png

lead_inner_bg.png

144 ms

lead_bg.gif

lead_bg.gif

587 ms

banner_sushi.png

banner_sushi.png

1066 ms

banner_hida.png

banner_hida.png

146 ms

banner_eat.png

banner_eat.png

147 ms

banner_local.png

banner_local.png

148 ms

banner_noodle.png

banner_noodle.png

179 ms

head_icon_left.png

head_icon_left.png

178 ms

head_icon_right.png

head_icon_right.png

178 ms

head_icon_bottom.png

head_icon_bottom.png

590 ms

column_renewal-1-1600x800.jpg

column_renewal-1-1600x800.jpg

183 ms

1x1.trans.gif

1x1.trans.gif

182 ms

footer_logo.png

footer_logo.png

181 ms

banner_hida_takayama.jpg

banner_hida_takayama.jpg

185 ms

banner_chita.gif

banner_chita.gif

183 ms

pagetop.png

pagetop.png

660 ms

icon_search_black.png

icon_search_black.png

180 ms

icon_ranking.png

icon_ranking.png

620 ms

icon_word.png

icon_word.png

626 ms

icon_newshop.png

icon_newshop.png

550 ms

separation.png

separation.png

1264 ms

map_icon_left.png

map_icon_left.png

563 ms

map_icon_right.png

map_icon_right.png

571 ms

map_ttl.png

map_ttl.png

1269 ms

icon_ins_black.png

icon_ins_black.png

590 ms

footer_bg.jpg

footer_bg.jpg

597 ms

AvenirNextLTPro-Demi.woff

AvenirNextLTPro-Demi.woff

1299 ms

widgets.js

widgets.js

165 ms

munchkin.js

munchkin.js

50 ms

sdk.js

sdk.js

82 ms

bx_loader.gif

bx_loader.gif

541 ms

controls.png

controls.png

547 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

21 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

21 ms

fastbutton

fastbutton

53 ms

visitWebPage

visitWebPage

103 ms

sdk.js

sdk.js

40 ms

postmessageRelay

postmessageRelay

83 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

61 ms

developers.google.com

developers.google.com

1353 ms

544727282-postmessagerelay.js

544727282-postmessagerelay.js

36 ms

rpc:shindig_random.js

rpc:shindig_random.js

8 ms

settings

settings

97 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

22 ms

embeds

embeds

36 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

32 ms

Accessibility Review

umaimon.net accessibility score

83

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

[aria-hidden="true"] elements contain focusable descendents

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

<frame> or <iframe> elements do not have a title

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

umaimon.net 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

umaimon.net SEO score

90

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

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 Umaimon.net 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 Umaimon.net 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

umaimon.net

Open Graph data is detected on the main page of Umaimon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: