Report Summary

  • 57

    Performance

    Renders faster than
    74% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

mockingbirdrestaurant.com

Miraval Ballroom - Wedding & Special event venue

Page Load Speed

3.3 sec in total

First Response

165 ms

Resources Loaded

1.9 sec

Page Rendered

1.2 sec

mockingbirdrestaurant.com screenshot

About Website

Click here to check amazing Mockingbirdrestaurant content. Otherwise, check out these important facts you probably never knew about mockingbirdrestaurant.com

Visit mockingbirdrestaurant.com

Key Findings

We analyzed Mockingbirdrestaurant.com page load time and found that the first response time was 165 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

mockingbirdrestaurant.com performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value21.4 s

0/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value6.9 s

53/100

10%

Network Requests Diagram

mockingbirdrestaurant.com

165 ms

mockingbirdrestaurant.com

255 ms

www.miravalballroom.com

320 ms

css2

27 ms

style.css

113 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Mockingbirdrestaurant.com, 90% (65 requests) were made to Miravalballroom.com and 6% (4 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (900 ms) relates to the external source Miravalballroom.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 548.1 kB (5%)

Content Size

10.8 MB

After Optimization

10.2 MB

In fact, the total size of Mockingbirdrestaurant.com main page is 10.8 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 10.4 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 18.7 kB

  • Original 23.3 kB
  • After minification 21.9 kB
  • After compression 4.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 18.7 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 188.9 kB

  • Original 10.4 MB
  • After minification 10.2 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. Mockingbirdrestaurant images are well optimized though.

JavaScript Optimization

-81%

Potential reduce by 154.1 kB

  • Original 189.5 kB
  • After minification 143.3 kB
  • After compression 35.4 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 154.1 kB or 81% of the original size.

CSS Optimization

-97%

Potential reduce by 186.3 kB

  • Original 191.9 kB
  • After minification 26.6 kB
  • After compression 5.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. Mockingbirdrestaurant.com needs all CSS files to be minified and compressed as it can save up to 186.3 kB or 97% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (18%)

Requests Now

68

After Optimization

56

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

Accessibility Review

mockingbirdrestaurant.com accessibility score

81

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

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

mockingbirdrestaurant.com SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mockingbirdrestaurant.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 Mockingbirdrestaurant.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 Mockingbirdrestaurant. 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: