Tools & Wizards About Us
hotpepper.jp screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

hotpepper.jp

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

Page Load Speed

7.2 sec in total

First Response

554 ms

Resources Loaded

6.1 sec

Page Rendered

614 ms

hotpepper.jp screenshot

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！（2025年6月調査時点(株)東京商工リサーチ調べ）人気の特集や季節のおすすめ情報から簡単お店検索！ネット予約なら24時間利用可能でポイントもたまります！

Visit hotpepper.jp

Key Findings

We analyzed Hotpepper.jp page load time and found that the first response time was 554 ms and then it took 6.7 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

hotpepper.jp performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value3,370 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value34.0 s

0/100

10%

Network Requests Diagram

hotpepper.jp

554 ms

hotpepper.jp

760 ms

www.hotpepper.jp

1449 ms

PTP01000.css

283 ms

abtest.config.js

416 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 11% of them (11 requests) were addressed to the original Hotpepper.jp, 34% (33 requests) were made to Imgfp.hotp.jp and 22% (22 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Code.usergram.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 285.1 kB (26%)

Content Size

1.1 MB

After Optimization

819.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hotpepper.jp main page is 1.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. 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. Images take 622.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 89.9 kB

  • Original 112.9 kB
  • After minification 96.6 kB
  • After compression 23.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 16.3 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 89.9 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 26.3 kB

  • Original 622.2 kB
  • After minification 595.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. Hotpepper images are well optimized though.

JavaScript Optimization

-44%

Potential reduce by 154.4 kB

  • Original 351.3 kB
  • After minification 350.8 kB
  • After compression 196.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 154.4 kB or 44% of the original size.

CSS Optimization

-80%

Potential reduce by 14.5 kB

  • Original 18.1 kB
  • After minification 15.4 kB
  • After compression 3.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. Hotpepper.jp needs all CSS files to be minified and compressed as it can save up to 14.5 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 58 (61%)

Requests Now

95

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 95 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 44 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

hotpepper.jp

hotpepper.jp

554 ms

hotpepper.jp

hotpepper.jp

760 ms

www.hotpepper.jp

www.hotpepper.jp

1449 ms

PTP01000.css

PTP01000.css

283 ms

abtest.config.js

abtest.config.js

416 ms

s_code_diff.js

s_code_diff.js

377 ms

s_code.js

s_code.js

725 ms

logTeam.js

logTeam.js

719 ms

tgmn.js

tgmn.js

542 ms

jquery-1.10.1.min.js

jquery-1.10.1.min.js

375 ms

PTP01000.min.js

PTP01000.min.js

169 ms

bnr_season_90x90@2x.png

bnr_season_90x90@2x.png

1058 ms

bnr_beauty_437x80.png

bnr_beauty_437x80.png

383 ms

townwork.jpg

townwork.jpg

966 ms

store_number_no1.svg

store_number_no1.svg

161 ms

hotpepper_220x42.svg

hotpepper_220x42.svg

169 ms

kv_globaltop_01@2x.jpg

kv_globaltop_01@2x.jpg

178 ms

kv_globaltop_02@2x.jpg

kv_globaltop_02@2x.jpg

177 ms

kv_globaltop_03@2x.jpg

kv_globaltop_03@2x.jpg

174 ms

map_red_24x26@2x.png

map_red_24x26@2x.png

176 ms

search_red_24x30@2x.png

search_red_24x30@2x.png

179 ms

arrow_down_11x7.png

arrow_down_11x7.png

174 ms

map_18x18.png

map_18x18.png

332 ms

genre_14x14.png

genre_14x14.png

178 ms

yen_12x14.png

yen_12x14.png

178 ms

search_white_12x15.png

search_white_12x15.png

258 ms

bnr_point_plus_180x180@2x.png

bnr_point_plus_180x180@2x.png

181 ms

bnr_girlsparty_90x90.png

bnr_girlsparty_90x90.png

181 ms

bnr_birthday_90x90.png

bnr_birthday_90x90.png

180 ms

bnr_buffet_90x90.png

bnr_buffet_90x90.png

181 ms

bnr_premium_90x90.png

bnr_premium_90x90.png

340 ms

bnr_afterwedding_90x90.png

bnr_afterwedding_90x90.png

187 ms

bnr_local_90x90.png

bnr_local_90x90.png

187 ms

bnr_point_65x65.png

bnr_point_65x65.png

187 ms

bnr_kanji_65x65.png

bnr_kanji_65x65.png

271 ms

bnr_karaoke_65x65.png

bnr_karaoke_65x65.png

195 ms

bnr_application_65x65.png

bnr_application_65x65.png

193 ms

bnr_chouseikun_65x65.png

bnr_chouseikun_65x65.png

200 ms

bnr_labo_65x65.png

bnr_labo_65x65.png

201 ms

bnr_kanjimanual_65x65.png

bnr_kanjimanual_65x65.png

285 ms

bnr_report_65x65.png

bnr_report_65x65.png

357 ms

qr_smartphone_65x65.gif

qr_smartphone_65x65.gif

260 ms

recruit_100x26.png

recruit_100x26.png

261 ms

bt_course_pagetop_bg.png

bt_course_pagetop_bg.png

263 ms

gtm.js

gtm.js

95 ms

datadog-rum-v3.js

datadog-rum-v3.js

38 ms

ytag.js

ytag.js

1454 ms

vclp.js

vclp.js

213 ms

destination

destination

41 ms

destination

destination

115 ms

destination

destination

216 ms

destination

destination

260 ms

destination

destination

114 ms

destination

destination

349 ms

uwt.js

uwt.js

350 ms

destination

destination

304 ms

destination

destination

347 ms

destination

destination

346 ms

destination

destination

348 ms

destination

destination

347 ms

destination

destination

641 ms

destination

destination

644 ms

destination

destination

645 ms

destination

destination

642 ms

destination

destination

645 ms

destination

destination

646 ms

bat.js

bat.js

341 ms

destination

destination

645 ms

analytics.js

analytics.js

336 ms

fbevents.js

fbevents.js

334 ms

pixel.js

pixel.js

334 ms

default.js

default.js

1422 ms

conversion.js

conversion.js

333 ms

usergram.js

usergram.js

1468 ms

adsct

adsct

937 ms

adsct

adsct

936 ms

p

p

1268 ms

smallest.png

smallest.png

597 ms

adsct

adsct

545 ms

adsct

adsct

792 ms

adsct

adsct

792 ms

adsct

adsct

792 ms

adsct

adsct

792 ms

adsct

adsct

542 ms

linkid.js

linkid.js

418 ms

collect

collect

18 ms

collect

collect

53 ms

js

js

40 ms

ga-audiences

ga-audiences

251 ms

js

js

45 ms

js

js

92 ms

cv

cv

170 ms

bf.png

bf.png

884 ms

116 ms

config.js

config.js

105 ms

20 ms

_usergram.png

_usergram.png

709 ms

170 ms

Accessibility Review

hotpepper.jp accessibility score

81

Accessibility Issues

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

hotpepper.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

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

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 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: