Report Summary

  • 2

    Performance

    Renders faster than
    19% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

400olive.com

400 Olive - Downtown St. Louis Restaurant by Hilton Dining

Page Load Speed

23.9 sec in total

First Response

150 ms

Resources Loaded

22.5 sec

Page Rendered

1.2 sec

400olive.com screenshot

About Website

Welcome to 400olive.com homepage info - get ready to check 400 Olive best content right away, or after learning these important things about 400olive.com

Our downtown St. Louis restaurant 400 Olive is a modern American Bistro, the perfect spot for a casual dinner, business meeting or romantic rendezvous.

Visit 400olive.com

Key Findings

We analyzed 400olive.com page load time and found that the first response time was 150 ms and then it took 23.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

400olive.com performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value10,840 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.629

9/100

15%

TTI (Time to Interactive)

Value31.5 s

0/100

10%

Network Requests Diagram

400olive.com

150 ms

400-olive.html

10081 ms

926 ms

dt-jSoVLlm8Db1J9D3k4nN05QFUuoFH90

171 ms

ruxitagentjs_ICA237Vfghjoqrtux_10249220905100923.js

81 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original 400olive.com, 91% (43 requests) were made to Hilton.com and 2% (1 request) were made to Www3.hilton.com. The less responsive or slowest element that took the longest time to load (10.1 sec) relates to the external source Www3.hilton.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 211.5 kB (69%)

Content Size

305.9 kB

After Optimization

94.4 kB

In fact, the total size of 400olive.com main page is 305.9 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. 75% 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. HTML takes 201.0 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 146.3 kB

  • Original 201.0 kB
  • After minification 200.9 kB
  • After compression 54.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 146.3 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 19.0 kB
  • After minification 19.0 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. 400 Olive images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 65.2 kB

  • Original 85.8 kB
  • After minification 85.8 kB
  • After compression 20.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 65.2 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (67%)

Requests Now

36

After Optimization

12

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 400 Olive. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

400olive.com accessibility score

100

Accessibility Issues

Best Practices

400olive.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

400olive.com SEO score

98

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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 400olive.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 400olive.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 400 Olive. 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: