Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

gnavi.co.jp

ぐるなび - レストラン・宴会予約 グルメ情報サイト

Page Load Speed

7.2 sec in total

First Response

350 ms

Resources Loaded

5.8 sec

Page Rendered

984 ms

gnavi.co.jp screenshot

About Website

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

レストラン予約サイト【ぐるなび】なら、ネット予約で楽天ポイントが貯まる!エリア、駅名、予算などの条件から希望のお店をスピーディに検索、予約ができます。お得なクーポン情報や最新レストラン情報も満載なので、歓送迎会・宴会のお店探しにもオススメ!

Visit gnavi.co.jp

Key Findings

We analyzed Gnavi.co.jp page load time and found that the first response time was 350 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

gnavi.co.jp performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value20.9 s

0/100

25%

SI (Speed Index)

Value16.1 s

0/100

10%

TBT (Total Blocking Time)

Value10,670 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value42.9 s

0/100

10%

Network Requests Diagram

gnavi.co.jp

350 ms

www.gnavi.co.jp

350 ms

www.gnavi.co.jp

1352 ms

optimize.js

114 ms

ga_meta_sc_page-1.0.0.js

893 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 11% of them (14 requests) were addressed to the original Gnavi.co.jp, 25% (31 requests) were made to D1o79rcslrm1j.cloudfront.net and 21% (26 requests) were made to Rimage.gnst.jp. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Questant.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (45%)

Content Size

3.2 MB

After Optimization

1.7 MB

In fact, the total size of Gnavi.co.jp main page is 3.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 133.7 kB

  • Original 153.5 kB
  • After minification 129.4 kB
  • After compression 19.7 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 24.1 kB, which is 16% 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 133.7 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 306 B

  • Original 942.3 kB
  • After minification 942.0 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. Gnavi images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 855.9 kB

  • Original 1.5 MB
  • After minification 1.4 MB
  • After compression 681.9 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 855.9 kB or 56% of the original size.

CSS Optimization

-83%

Potential reduce by 448.3 kB

  • Original 538.9 kB
  • After minification 444.9 kB
  • After compression 90.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. Gnavi.co.jp needs all CSS files to be minified and compressed as it can save up to 448.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 67 (60%)

Requests Now

111

After Optimization

44

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

Accessibility Review

gnavi.co.jp accessibility score

71

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-*] attributes do not match their roles

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

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

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

gnavi.co.jp best practices score

75

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

Missing source maps for large first-party JavaScript

SEO Factors

gnavi.co.jp SEO score

99

Search Engine Optimization Advices

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

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