Tools & Wizards About Us
opentable.jp screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 96% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

opentable.jp

レストラン情報とネット予約 | OpenTable

Page Load Speed

3.2 sec in total

First Response

257 ms

Resources Loaded

2.6 sec

Page Rendered

337 ms

opentable.jp screenshot

About Website

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

レストランのネット予約や口コミのチェックは OpenTable で！ポイント貯めて次のお食事に使ったり、高級レストランを即時予約できます。

Visit opentable.jp

Key Findings

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

Performance Metrics

opentable.jp performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value22.5 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value4,070 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

www.opentable.jp

257 ms

default.aspx

90 ms

home

145 ms

app-728a02b6d05de92d718d5fb3129132fc.css._gz

52 ms

home-988e8d0ad6aedf3da8d3b3118c5e621f.css._gz

42 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Opentable.jp, 20% (14 requests) were made to Media.otstatic.com and 9% (6 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (457 ms) relates to the external source Widget.as.criteo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 973.6 kB (61%)

Content Size

1.6 MB

After Optimization

629.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Opentable.jp main page is 1.6 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. 65% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 65.9 kB

  • Original 86.7 kB
  • After minification 86.3 kB
  • After compression 20.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. 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 65.9 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 3.3 kB

  • Original 193.7 kB
  • After minification 190.4 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. Open Table images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 677.3 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 361.5 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 677.3 kB or 65% of the original size.

CSS Optimization

-80%

Potential reduce by 227.1 kB

  • Original 283.3 kB
  • After minification 281.7 kB
  • After compression 56.3 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. Opentable.jp needs all CSS files to be minified and compressed as it can save up to 227.1 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (69%)

Requests Now

54

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.opentable.jp

www.opentable.jp

257 ms

default.aspx

default.aspx

90 ms

home

home

145 ms

app-728a02b6d05de92d718d5fb3129132fc.css._gz

app-728a02b6d05de92d718d5fb3129132fc.css._gz

52 ms

home-988e8d0ad6aedf3da8d3b3118c5e621f.css._gz

home-988e8d0ad6aedf3da8d3b3118c5e621f.css._gz

42 ms

bundle_head.js

bundle_head.js

83 ms

280966806.js

280966806.js

172 ms

dtp.js

dtp.js

36 ms

bundle_common.js

bundle_common.js

46 ms

application-b00b8d294654c40b46bc02b4cc2ae430.js._gz

application-b00b8d294654c40b46bc02b4cc2ae430.js._gz

36 ms

homeController-56798756fd909a8c24c5bfa4c6eacced.js._gz

homeController-56798756fd909a8c24c5bfa4c6eacced.js._gz

309 ms

jp-tokyo-b6f75de4439fcae007942dbb6cfd5ab8.png

jp-tokyo-b6f75de4439fcae007942dbb6cfd5ab8.png

17 ms

jp-hyogo-359dc6b3632a65636951e5eae8c1c468.png

jp-hyogo-359dc6b3632a65636951e5eae8c1c468.png

9 ms

jp-kanagawa-a2f141e67c23d3c109afc95dd6e261e0.png

jp-kanagawa-a2f141e67c23d3c109afc95dd6e261e0.png

18 ms

jp-kyoto-1480590ccf4bc4107190e31f94c2e7fe.png

jp-kyoto-1480590ccf4bc4107190e31f94c2e7fe.png

32 ms

jp-osaka-df49fe33a867d206289ce990203807cf.png

jp-osaka-df49fe33a867d206289ce990203807cf.png

22 ms

jp-hawaii-206d6704ecc64f7d06ba96a3b2f313b9.png

jp-hawaii-206d6704ecc64f7d06ba96a3b2f313b9.png

37 ms

food-ba33685c5a52b59dd47a5d93a096a96b.jpg

food-ba33685c5a52b59dd47a5d93a096a96b.jpg

42 ms

gpt.js

gpt.js

122 ms

event

event

61 ms

www.opentable.jp

www.opentable.jp

160 ms

pubads_impl_82.js

pubads_impl_82.js

50 ms

container.html

container.html

10 ms

aksb.min.js

aksb.min.js

14 ms

logo-7cd459fb1da36ae8f2030a77aa098c2a.png

logo-7cd459fb1da36ae8f2030a77aa098c2a.png

63 ms

szUnz7JNc6gl-e3W7djvQG_-HM09uhfCmn-o6PrAa2IffFpAEN32IgCjMKM2HMIt294MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff

szUnz7JNc6gl-e3W7djvQG_-HM09uhfCmn-o6PrAa2IffFpAEN32IgCjMKM2HMIt294MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff

34 ms

QGIOMjZGZehFDCJLQ1s-ZeF2M89QilUpbxg6K1RsiL3ffFKAEN32IgCjMKM2HMIt2q4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff

QGIOMjZGZehFDCJLQ1s-ZeF2M89QilUpbxg6K1RsiL3ffFKAEN32IgCjMKM2HMIt2q4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff

153 ms

uIj_dRTnzpkaqxs4MzQRUM4RT9DgotJa3_jcIOAcRbjffF-AEN32IgCjMKM2HMItMX4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff

uIj_dRTnzpkaqxs4MzQRUM4RT9DgotJa3_jcIOAcRbjffF-AEN32IgCjMKM2HMItMX4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff

213 ms

txOCIlQLR4HZ9WM6GUhBISTykN0Fgr39_jPHnzk1JvvffFcAEN32IgCjMKM2HMItgI4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff

txOCIlQLR4HZ9WM6GUhBISTykN0Fgr39_jPHnzk1JvvffFcAEN32IgCjMKM2HMItgI4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff

282 ms

nCDHTzypxIou1_79fuif0SzrrCKtVATUFivNbS5_7H6ffF7AEN32IgCjMKM2HMItgq4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff

nCDHTzypxIou1_79fuif0SzrrCKtVATUFivNbS5_7H6ffF7AEN32IgCjMKM2HMItgq4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff

283 ms

icons-bfc13198e8dedc4fb8d494144088b529.woff

icons-bfc13198e8dedc4fb8d494144088b529.woff

32 ms

affiliate_logos-e2f289ddcf0858ad42b32a863ee7bfa7.png

affiliate_logos-e2f289ddcf0858ad42b32a863ee7bfa7.png

117 ms

tag.js

tag.js

18 ms

s_code.js

s_code.js

155 ms

tag

tag

28 ms

p.gif

p.gif

168 ms

s21791255786083

s21791255786083

12 ms

quant.js

quant.js

16 ms

conversion_async.js

conversion_async.js

39 ms

pixel;r=40574939;a=p-_W1qFnnaA1ucH;labels=;fpan=1;fpa=P0-574858829-1458137498706;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458137498705;tzo=-180;ref=;url=http%3A%2F%2Fwww.opentable.jp%2Fstart%2Fhome;ogl=image.%2F%2Fcomponents%252Eotstatic%252Ecom%2Fcomponents%2Ffavicon%2F1%252E0%252E4%2Ffavicon%2Fapple-touch-icon-152x

pixel;r=40574939;a=p-_W1qFnnaA1ucH;labels=;fpan=1;fpa=P0-574858829-1458137498706;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458137498705;tzo=-180;ref=;url=http%3A%2F%2Fwww.opentable.jp%2Fstart%2Fhome;ogl=image.%2F%2Fcomponents%252Eotstatic%252Ecom%2Fcomponents%2Ffavicon%2F1%252E0%252E4%2Ffavicon%2Fapple-touch-icon-152x

13 ms

beacon

beacon

71 ms

mone.84fdbb44f5e_1340.js

mone.84fdbb44f5e_1340.js

166 ms

74 ms

63 ms

41 ms

32 ms

42 ms

55 ms

50 ms

46 ms

63 ms

54 ms

ld.js

ld.js

27 ms

activityi;src=4334009;type=fl2GT-;cat=homep001;ord=9487383819650.86

activityi;src=4334009;type=fl2GT-;cat=homep001;ord=9487383819650.86

121 ms

activityi;src=4334009;type=fl2GT-;cat=opent001;ord=7576016620732.844

activityi;src=4334009;type=fl2GT-;cat=opent001;ord=7576016620732.844

135 ms

pixel

pixel

86 ms

set.html

set.html

72 ms

332 ms

event

event

457 ms

cs

cs

15 ms

cs

cs

52 ms

lb

lb

222 ms

lb

lb

206 ms

js

js

41 ms

i.js

i.js

61 ms

cs

cs

9 ms

83 ms

js

js

42 ms

img

img

31 ms

Accessibility Review

opentable.jp accessibility score

99

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

opentable.jp SEO score

100

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

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

opentable.jp

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