Access hotpepper.jp. ホットペッパーグルメ【ネット予約可能店舗数No.1】

Report Summary

About Website

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

ホットペッパーグルメはネット予約可能店舗数・ネット予約利用者数・ネット予約満足度でNo.1！（2023年6月調査時点(株)東京商工リサーチ調べ）人気の特集や季節のおすすめ情報から簡単お店検索！ネット予約なら24時間利用可能でポイントもたまります！

Visit hotpepper.jp

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value3,570 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.0 s

2/100

10%

hotpepper.jp

518 ms

www.hotpepper.jp

369 ms

top_design.css

175 ms

abutils.js

345 ms

squilla.min.js

346 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 95% of them (60 requests) were addressed to the original Hotpepper.jp, 2% (1 request) were made to C.tgknt.com and 2% (1 request) were made to Recruit.112.2o7.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Hotpepper.jp.

Content Size

913.0 kB

After Optimization

470.9 kB

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

HTML Optimization

-81%

Potential reduce by 54.4 kB

Original 67.3 kB
After minification 57.7 kB
After compression 13.0 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 9.6 kB, which is 14% 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 54.4 kB or 81% of the original size.

Image Optimization

-15%

Potential reduce by 65.3 kB

Original 423.2 kB
After minification 357.9 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. Obviously, Hotpepper needs image optimization as it can save up to 65.3 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 269.2 kB

Original 361.9 kB
After minification 300.0 kB
After compression 92.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 269.2 kB or 74% of the original size.

CSS Optimization

-88%

Potential reduce by 53.1 kB

Original 60.5 kB
After minification 52.7 kB
After compression 7.4 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. Hotpepper.jp needs all CSS files to be minified and compressed as it can save up to 53.1 kB or 88% of the original size.

Requests Now

After Optimization

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

Search Engine Optimization Advices

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

High

Links are not crawlable

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/).

High

Document doesn't use 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 Hotpepper.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 Hotpepper.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

hotpepper.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

ホットペッパーグルメ 【ネット予約可能店舗数No.1】

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)