Report Summary

  • 66

    Performance

    Renders faster than
    80% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 86

    SEO

    Google-friendlier than
    61% 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 50% of websites can load faster.

Performance Metrics

opentable.jp performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value7.1 s

52/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 959.9 kB (61%)

Content Size

1.6 MB

After Optimization

611.9 kB

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

-66%

Potential reduce by 663.6 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 344.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 663.6 kB or 66% 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

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.

Accessibility Review

opentable.jp accessibility score

100

Accessibility Issues

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

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

opentable.jp SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

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

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: