32 sec in total
3.3 sec
25.1 sec
3.6 sec
Visit 220restaurant.com now to see the best up-to-date 220 Restaurant content for United States and also check out these interesting facts you probably never knew about 220restaurant.com
Visit 220restaurant.comWe analyzed 220restaurant.com page load time and found that the first response time was 3.3 sec and then it took 28.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
220restaurant.com performance score
name
value
score
weighting
Value12.3 s
0/100
10%
Value37.9 s
0/100
25%
Value40.1 s
0/100
10%
Value3,620 ms
1/100
30%
Value0.745
6/100
15%
Value39.7 s
0/100
10%
3308 ms
85 ms
53 ms
57 ms
912 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 72% of them (108 requests) were addressed to the original 220restaurant.com, 11% (16 requests) were made to Scontent.cdninstagram.com and 4% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Secure.opentable.com.
Page size can be reduced by 1.1 MB (16%)
6.7 MB
5.7 MB
In fact, the total size of 220restaurant.com main page is 6.7 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. 85% 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 5.4 MB which makes up the majority of the site volume.
Potential reduce by 124.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. 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 124.0 kB or 80% of the original size.
Potential reduce by 44.6 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. 220 Restaurant images are well optimized though.
Potential reduce by 474.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 474.9 kB or 72% of the original size.
Potential reduce by 411.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. 220restaurant.com needs all CSS files to be minified and compressed as it can save up to 411.3 kB or 82% of the original size.
Number of requests can be reduced by 70 (57%)
123
53
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 220 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 38 to 1 for JavaScripts and from 34 to 1 for CSS and as a result speed up the page load time.
220restaurant.com
3308 ms
analytics.js
85 ms
wp-emoji-release.min.js
53 ms
gcc_custom.css
57 ms
sbi-styles.min.css
912 ms
wd_default_style.css
894 ms
styles.css
1913 ms
duplicate-page-and-post-admin.min.css
1913 ms
theme.css
91 ms
settings.css
108 ms
slick.css
103 ms
logo-showcase.css
114 ms
reset.css
124 ms
wordpress.css
124 ms
animation.css
140 ms
magnific-popup.css
139 ms
custom.css
167 ms
mediaelementplayer-legacy.min.css
155 ms
flexslider.css
170 ms
tooltipster.css
181 ms
odometer-theme-minimal.css
184 ms
hw-parallax.css
195 ms
screen.css
229 ms
font-awesome.min.css
224 ms
css
45 ms
css
48 ms
css
48 ms
addtoany.min.css
254 ms
220restaurant.com
1018 ms
css
49 ms
kirki-styles.css
254 ms
grid.css
283 ms
custom-css.php
1257 ms
gcc_ajax.js
900 ms
frontend.min.js
915 ms
jquery.js
976 ms
addtoany.min.js
929 ms
Popup.js
976 ms
PopupConfig.js
992 ms
PopupBuilder.js
1020 ms
jquery.themepunch.tools.min.js
1054 ms
loader
19674 ms
leadform.js
93 ms
loader
111 ms
linkid.js
23 ms
jquery.timepicker.css
992 ms
datepicker.css
998 ms
jquery.themepunch.revolution.min.js
1044 ms
collect
49 ms
collect
71 ms
sbi-scripts.min.js
962 ms
scripts.js
977 ms
jquery.magnific-popup.js
980 ms
jquery.easing.js
982 ms
waypoints.min.js
985 ms
jquery.isotope.js
986 ms
jquery.masory.js
972 ms
jquery.tooltipster.min.js
984 ms
hw-parallax.js
969 ms
jquery.stellar.min.js
958 ms
jquery.resizeimagetoparent.min.js
968 ms
custom_plugins.js
961 ms
custom.js
974 ms
wp-embed.min.js
958 ms
core.min.js
927 ms
datepicker.min.js
918 ms
custom-date.js
914 ms
jquery.timepicker.js
918 ms
custom-time.js
901 ms
jquery.validate.js
303 ms
custom_onepage.js
286 ms
page.js
257 ms
fbevents.js
261 ms
paper_bg.png
19622 ms
kirki-styles.css
147 ms
Top-Logo.png
131 ms
Top-Logo.png
136 ms
Untitled-design-11.jpg
301 ms
Untitled-design-12.jpg
216 ms
Untitled-design-16.jpg
192 ms
Untitled-design-20.jpg
301 ms
Untitled-design-18.jpg
301 ms
Untitled-design-21.jpg
300 ms
big1-min.jpg
304 ms
GC4A8193-X3-min.jpg
219 ms
Untitled-design-1-400x400.jpg
173 ms
pizza.jpg
464 ms
chickenparm.jpg
172 ms
Untitled-design-1-400x400.png
181 ms
GC4A8609-X3-min.jpg
259 ms
Untitled-design-9-400x400.jpg
173 ms
drn-7-400x400.jpg
176 ms
Untitled-design-8-400x400.jpg
180 ms
Untitled-design-2-400x400.png
215 ms
private-min.jpg
463 ms
maps.png
233 ms
placeholder.png
233 ms
WInners_Footer1-298x300.png
233 ms
220Merrill-logo-stackedglow200.png
256 ms
220_CoronaGuidelines_12x18_v3-1-min.jpg
255 ms
S6uyw4BMUTPHvxk.ttf
38 ms
S6uyw4BMUTPHjx4wWw.ttf
69 ms
S6u9w4BMUTPHh6UVew8.ttf
71 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
71 ms
fontawesome-webfont.woff
206 ms
identity.js
9 ms
424045878199302
127 ms
29 ms
10 ms
kirki-styles.css
39 ms
uK_y4ricdeU6zwdRCg.ttf
26 ms
uK_y4ricdeU6zwdhDRcX.ttf
27 ms
1f60d.svg
215 ms
revolution.extension.video.min.js
187 ms
revolution.extension.slideanims.min.js
192 ms
revolution.extension.navigation.min.js
193 ms
106544939_271104774123454_4073809385732173751_n.jpg
202 ms
drink2.jpg
272 ms
106229598_293641258496550_5911078068532145019_n.jpg
114 ms
106220988_138561484532009_6751071196582323016_n.jpg
194 ms
106398847_110070963982905_4335465028278336627_n.jpg
199 ms
106005944_939128223203029_5038536227401397586_n.jpg
196 ms
105944430_1665152490301823_4948363221143925944_n.jpg
198 ms
105568768_652179565336021_4031717859531807401_n.jpg
196 ms
105984498_2634068200193795_5889588920739433265_n.jpg
200 ms
104474121_2715052112065567_1148839037249908387_n.jpg
200 ms
104307121_2575391132560596_1468635292916831478_n.jpg
198 ms
103976608_313541593139349_2585916032065405455_n.jpg
201 ms
103997978_1116425808738213_8898198107194975270_n.jpg
201 ms
104112435_147304600232967_6370901004103396549_n.jpg
202 ms
104483299_267859081089759_8318504564419819073_n.jpg
202 ms
82517706_276940010123357_3120655429808905615_n.jpg
204 ms
103451565_337070460633940_4431250757282235528_n.jpg
203 ms
2728.svg
64 ms
106544939_271104774123454_4073809385732173751_nfull.jpg
100 ms
106229598_293641258496550_5911078068532145019_nfull.jpg
99 ms
106220988_138561484532009_6751071196582323016_nfull.jpg
75 ms
106005944_939128223203029_5038536227401397586_nfull.jpg
76 ms
105568768_652179565336021_4031717859531807401_nfull.jpg
74 ms
105944430_1665152490301823_4948363221143925944_nfull.jpg
94 ms
106398847_110070963982905_4335465028278336627_nfull.jpg
76 ms
104307121_2575391132560596_1468635292916831478_nfull.jpg
130 ms
104474121_2715052112065567_1148839037249908387_nfull.jpg
91 ms
105984498_2634068200193795_5889588920739433265_nfull.jpg
92 ms
103976608_313541593139349_2585916032065405455_nfull.jpg
129 ms
103997978_1116425808738213_8898198107194975270_nfull.jpg
119 ms
104112435_147304600232967_6370901004103396549_nfull.jpg
129 ms
104483299_267859081089759_8318504564419819073_nfull.jpg
128 ms
103451565_337070460633940_4431250757282235528_nfull.jpg
130 ms
82517706_276940010123357_3120655429808905615_nfull.jpg
167 ms
220restaurant.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.
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.
220restaurant.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
220restaurant.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 220restaurant.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 220restaurant.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.
220restaurant.com
Open Graph description is not detected on the main page of 220 Restaurant. 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: