9.5 sec in total
1.5 sec
7.4 sec
637 ms
Click here to check amazing As Restaurant content for United States. Otherwise, check out these important facts you probably never knew about asrestaurant.com
Mister A's restaurant San Diego is perched atop the Manchester Building, and features stunning 180 degree views of San Diego's iconic skyline.
Visit asrestaurant.comWe analyzed Asrestaurant.com page load time and found that the first response time was 1.5 sec and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
asrestaurant.com performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value10.7 s
0/100
25%
Value11.7 s
4/100
10%
Value3,920 ms
1/100
30%
Value0.019
100/100
15%
Value11.4 s
19/100
10%
1509 ms
115 ms
79 ms
149 ms
452 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 31% of them (38 requests) were addressed to the original Asrestaurant.com, 14% (17 requests) were made to Fonts.gstatic.com and 12% (15 requests) were made to Secure.opentable.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Asrestaurant.com.
Page size can be reduced by 2.3 MB (46%)
5.0 MB
2.7 MB
In fact, the total size of Asrestaurant.com main page is 5.0 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 2.0 MB which makes up the majority of the site volume.
Potential reduce by 50.7 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 50.7 kB or 82% of the original size.
Potential reduce by 33.8 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. As Restaurant images are well optimized though.
Potential reduce by 1.3 MB
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 1.3 MB or 69% of the original size.
Potential reduce by 951.1 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. Asrestaurant.com needs all CSS files to be minified and compressed as it can save up to 951.1 kB or 90% of the original size.
Number of requests can be reduced by 62 (61%)
101
39
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of As Restaurant. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
www.asrestaurant.com
1509 ms
wp-emoji-release.min.js
115 ms
style.css
79 ms
open-table-widget.min.css
149 ms
js_composer.css
452 ms
jquery.js
182 ms
jquery-migrate.min.js
97 ms
datepicker.min.js
147 ms
open-table-widget.min.js
166 ms
jquery.js
283 ms
ie10-viewport-bug-workaround.js
214 ms
dc_social_icons.css
44 ms
default.aspx
158 ms
jquery.vide.js
200 ms
bootstrap.min.js
251 ms
custom.js
233 ms
wp-embed.min.js
267 ms
js_composer_front.js
298 ms
waypoints.min.js
301 ms
script-min.js
371 ms
css
61 ms
css
75 ms
css
87 ms
font-awesome.css
307 ms
responsive.min.css
421 ms
default.css
305 ms
custom.css
309 ms
custom-responsive.css
419 ms
ga.js
117 ms
main-banner-final-2015-2.jpg
724 ms
fb.png
63 ms
twitter.png
64 ms
linkedin.png
190 ms
logo.png
189 ms
timeline-img.png
613 ms
newsimg-home.png
613 ms
ot_wide.css
32 ms
facebook-dice.png
117 ms
widgets.js
362 ms
embed
300 ms
none
2991 ms
timelinebg.jpg
459 ms
icons_final_dark.png
269 ms
downarrow_gray.gif
284 ms
ot_btn_red.png
289 ms
twitter-dice.png
263 ms
google_plus-dice.png
266 ms
linkedin-dice.png
267 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
296 ms
zJY4gsxBiSo5L7tNutxFNg.ttf
346 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
400 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
399 ms
4cKlrioa77J2iqTqBgkRWg.ttf
436 ms
4A-myfZX6oDr9CtSTkTGig.ttf
426 ms
rapsGf8n-DpRu9kcmAAciA.ttf
454 ms
fontawesome-webfont.woff
453 ms
9MkijrV-dEJ0-_NWV7E6N218GKU_F_kIyfK-gGC-Yzs.ttf
435 ms
n7G4PqJvFP2Kubl0VBLDEGewmj-_04VMEgCJvu_4mtU.ttf
454 ms
n7G4PqJvFP2Kubl0VBLDEG8w0mKJnD4ozU8DBImj2X0.ttf
453 ms
2NBgzUtEeyB-Xtpr9bm1Cczai8e7xzqnKiVb1EwOy0E.ttf
454 ms
UC3ZEjagJi85gF9qFaBgIETamuWRjOQSPxoOXgdYd7c.ttf
454 ms
UC3ZEjagJi85gF9qFaBgIA0DQt4XpTxu2mZR8niJHm4.ttf
455 ms
__utm.gif
287 ms
iframe_api
266 ms
jquery-ui-1.8.11.custom.min.js
255 ms
thickbox.js
77 ms
thickbox.css
61 ms
jquery-ui-1.8.5.custom.css
57 ms
bertrand.gif
3516 ms
bertrand.jpg
339 ms
bertrand.jpeg
3804 ms
bertrand.png
3832 ms
pressbg-m875xhjhrn3fdfiuuuii6e7zxyjbqtxzu2wxmf0ybg.png
1117 ms
contactbg2-m875njezfrgw9paws0df0uodf8cdn7go63m0riignc.jpeg
915 ms
js
201 ms
init_embed.js
197 ms
loading-animation.gif
115 ms
ba-postmessage.js
112 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
194 ms
s14931421973742
90 ms
www-widgetapi.js
88 ms
CookieCheck.aspx
118 ms
jquery.scrollTo-min.js
12 ms
ui-bg_flat_75_ffffff_40x100.png
24 ms
common.js
23 ms
util.js
40 ms
streetview.js
40 ms
google_white4.png
20 ms
marker.js
37 ms
syndication
214 ms
544357898361372672
228 ms
ScriptHandler.ashx
223 ms
imagery_viewer.js
56 ms
controls.js
9 ms
GeoPhotoService.GetMetadata
167 ms
transparent.png
140 ms
css
139 ms
geocoder.js
62 ms
sv4.png
130 ms
openhand_8_8.cur
129 ms
mapcnt6.png
182 ms
tmapctrl.png
183 ms
cbk
105 ms
GeoPhotoService.GetMetadata
100 ms
CookieCheck.aspx
351 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
62 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
58 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
61 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
62 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
42 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
202 ms
cbk
433 ms
cbk
434 ms
crFs9TO7_normal.jpeg
432 ms
cbk
430 ms
cbk
426 ms
lrP19J_P_normal.jpeg
438 ms
CdZGx-TXIAEWCnb.jpg:small
655 ms
Cc-ceB6UUAAXVDN.jpg:small
654 ms
cbk
320 ms
cbk
52 ms
cbk
310 ms
cbk
312 ms
jot
44 ms
asrestaurant.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
asrestaurant.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
asrestaurant.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Asrestaurant.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Asrestaurant.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.
asrestaurant.com
Open Graph data is detected on the main page of As Restaurant. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: