Report Summary

  • 1

    Performance

    Renders faster than
    19% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

220restaurant.com

220 Restaurant – Birmingham’s Premier Dining Destination – Nice people serving nice people

Page Load Speed

32 sec in total

First Response

3.3 sec

Resources Loaded

25.1 sec

Page Rendered

3.6 sec

220restaurant.com screenshot

About Website

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

Key Findings

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

Performance Metrics

220restaurant.com performance score

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value37.9 s

0/100

25%

SI (Speed Index)

Value40.1 s

0/100

10%

TBT (Total Blocking Time)

Value3,620 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.745

6/100

15%

TTI (Time to Interactive)

Value39.7 s

0/100

10%

Network Requests Diagram

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

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 Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (16%)

Content Size

6.7 MB

After Optimization

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.

HTML Optimization

-80%

Potential reduce by 124.0 kB

  • Original 155.6 kB
  • After minification 147.3 kB
  • After compression 31.6 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.

Image Optimization

-1%

Potential reduce by 44.6 kB

  • Original 5.4 MB
  • After minification 5.3 MB

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.

JavaScript Optimization

-72%

Potential reduce by 474.9 kB

  • Original 662.7 kB
  • After minification 605.4 kB
  • After compression 187.7 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.

CSS Optimization

-82%

Potential reduce by 411.3 kB

  • Original 502.3 kB
  • After minification 441.9 kB
  • After compression 91.0 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.

Requests Breakdown

Number of requests can be reduced by 70 (57%)

Requests Now

123

After Optimization

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.

Accessibility Review

220restaurant.com accessibility score

83

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

220restaurant.com 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

Page has valid source maps

SEO Factors

220restaurant.com SEO score

86

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: