3.4 sec in total
646 ms
2.5 sec
217 ms
Click here to check amazing Support Opentable content for United States. Otherwise, check out these important facts you probably never knew about support.opentable.com
Visit support.opentable.comWe analyzed Support.opentable.com page load time and found that the first response time was 646 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
support.opentable.com performance score
name
value
score
weighting
Value9.1 s
0/100
10%
Value12.3 s
0/100
25%
Value9.5 s
11/100
10%
Value520 ms
56/100
30%
Value0
100/100
15%
Value12.1 s
16/100
10%
646 ms
221 ms
66 ms
143 ms
203 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Support.opentable.com, 35% (14 requests) were made to Xihwk77754.i.lithium.com and 10% (4 requests) were made to . The less responsive or slowest element that took the longest time to load (815 ms) relates to the external source Community.opentable.com.
Page size can be reduced by 104.3 kB (33%)
318.2 kB
214.0 kB
In fact, the total size of Support.opentable.com main page is 318.2 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. 30% of websites need less resources to load. Images take 205.7 kB which makes up the majority of the site volume.
Potential reduce by 90.1 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 90.1 kB or 80% of the original size.
Potential reduce by 14.2 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. Support Opentable images are well optimized though.
Number of requests can be reduced by 10 (29%)
35
25
The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Support Opentable. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
OpenTable_Community_US
646 ms
new_opentable_diners_skin-2060154068.css
221 ms
dwh4rpg.js
66 ms
lia-scripts-head-min.js
143 ms
lia-scripts-common-min.js
203 ms
lia-scripts-body-min.js
110 ms
d
171 ms
open-table-logo.png
255 ms
arrow-rt.png
66 ms
hero_293_tables_1.jpg
588 ms
tap-sprite.png
307 ms
card_dinner_2.jpg
314 ms
card_dinner_1.jpg
313 ms
card_tables_1.jpg
311 ms
general-img.jpg
609 ms
card_gardener_1.jpg
598 ms
540 ms
scoopbanner.jpg
612 ms
footer-logo.png
542 ms
facebook-icon.jpg
771 ms
twitter-icon.jpg
770 ms
google-plus-icon.jpg
815 ms
arrow-down.png
44 ms
icon_list_separator_navigation.png
45 ms
button_fbconnect_secondary.png
45 ms
icon_help.png
45 ms
0%2C0%2C166%2C166
101 ms
message
101 ms
message
102 ms
message
102 ms
message
251 ms
AQYaZLAhhhpmuBFGGmW0MdJlGGuc8SaYaJLJppha9PNNM90MM80y2xxzzTPfAgststgSSy2z3AorrbLaGmuts94GG22y2RZbbQs1scNOu+y2x1777HfAQYccdsRRxxx3wkmnnHbGWedkOh+q6qJLLrviqmuuy3LDTbfcdsdd92S774EcuR565LE8TzyVHyrzuRdeeuW1N956978q9BeryJua
53 ms
P9Vob8A32GbuwAAAA==
53 ms
F8V+gPTCpuy
53 ms
8T0ONNA63TpUWfiddUxkyNdNcCy210lobbbXTXgcdddJZF111010PPfXSWx999dPfAAMNMtgQQw0z3AgjjTLaGGONM16WbBNMNMlkU0w1zXQzSn++mWaZbY655plvgYUWWWyJpZZZLscKK62y2hprrbPeBhttstkWW22z3Y5QE7vstsde++x3wEGHHHbEUcccd8JJp5x2xlnnnHfBRZdCVV1x1TXX3XDTLbluu+Oue+574KE8jzz2xFPP5HuuwAsvFYbKfO2Nt95574OPPv2vCv0FVomcAgAA
52 ms
sdk.js
66 ms
182 ms
xd_arbiter.php
53 ms
p.gif
127 ms
xd_arbiter.php
8 ms
support.opentable.com accessibility score
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
support.opentable.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
support.opentable.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Support.opentable.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Support.opentable.com 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.
support.opentable.com
Open Graph description is not detected on the main page of Support Opentable. 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: