Tools & Wizards About Us
le-bernardin.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

le-bernardin.com

Le Bernardin by Eric Ripert | Home

Page Load Speed

1.7 sec in total

First Response

27 ms

Resources Loaded

1.6 sec

Page Rendered

59 ms

le-bernardin.com screenshot

About Website

Welcome to le-bernardin.com homepage info - get ready to check Le Bernardin best content for United States right away, or after learning these important things about le-bernardin.com

Le Bernardin, Zagat's top pick for 2012, and awarded the Michelin Guide's coveted 3-stars as well as The New York Times' highest rating of 4-stars, has maintained its status of excellence for 20 years...

Visit le-bernardin.com

Key Findings

We analyzed Le-bernardin.com page load time and found that the first response time was 27 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

le-bernardin.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value13.3 s

0/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value1,940 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

le-bernardin.com

27 ms

www.le-bernardin.com

443 ms

spin.js

34 ms

modernizr.min.js

50 ms

js

73 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 38% of them (5 requests) were addressed to the original Le-bernardin.com, 15% (2 requests) were made to Cdnjs.cloudflare.com and 15% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Le-bernardin.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 188.9 kB (32%)

Content Size

595.5 kB

After Optimization

406.5 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Le-bernardin.com main page is 595.5 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. 25% of websites need less resources to load. Javascripts take 419.5 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 113.8 kB

  • Original 157.1 kB
  • After minification 157.1 kB
  • After compression 43.4 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 113.8 kB or 72% of the original size.

JavaScript Optimization

-17%

Potential reduce by 70.0 kB

  • Original 419.5 kB
  • After minification 419.5 kB
  • After compression 349.5 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 70.0 kB or 17% of the original size.

CSS Optimization

-27%

Potential reduce by 5.2 kB

  • Original 18.8 kB
  • After minification 18.8 kB
  • After compression 13.6 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. Le-bernardin.com needs all CSS files to be minified and compressed as it can save up to 5.2 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (64%)

Requests Now

11

After Optimization

4

  • AJAX
  • JavaScript
  • CSS

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

Network Requests Diagram

le-bernardin.com

le-bernardin.com

27 ms

www.le-bernardin.com

www.le-bernardin.com

443 ms

spin.js

spin.js

34 ms

modernizr.min.js

modernizr.min.js

50 ms

js

js

73 ms

respond.matchmedia.addListener.min.js

respond.matchmedia.addListener.min.js

18 ms

main.min.css

main.min.css

96 ms

embed.js

embed.js

21 ms

main.min.js

main.min.js

1059 ms

analytics.js

analytics.js

22 ms

collect

collect

12 ms

collect

collect

30 ms

js

js

50 ms

Accessibility Review

le-bernardin.com accessibility score

60

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

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

le-bernardin.com best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

le-bernardin.com SEO score

85

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Le-bernardin.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Le-bernardin.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

le-bernardin.com

Open Graph description is not detected on the main page of Le Bernardin. 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: