Tools & Wizards About Us
reyesmex.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

reyesmex.com

Mexican Restaurant | Orlando, Fl | Reyes Mezcaleria

Page Load Speed

1 sec in total

First Response

124 ms

Resources Loaded

840 ms

Page Rendered

54 ms

reyesmex.com screenshot

About Website

Welcome to reyesmex.com homepage info - get ready to check Reyes Mex best content for United States right away, or after learning these important things about reyesmex.com

A regionally-inspired Mexican restaurant located in the vibrant North Quarter district of downtown Orlando, Fl. With over 150 agave selections, this Mezcaleria is open for lunch, happy hour and dinner...

Visit reyesmex.com

Key Findings

We analyzed Reyesmex.com page load time and found that the first response time was 124 ms and then it took 894 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

reyesmex.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value13.0 s

0/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value770 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

Network Requests Diagram

www.reyesmex.com

124 ms

minified.js

30 ms

focus-within-polyfill.js

29 ms

polyfill.min.js

29 ms

thunderbolt-commons.7700cd07.bundle.min.js

118 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Reyesmex.com, 49% (27 requests) were made to Static.wixstatic.com and 22% (12 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (438 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 341.6 kB (14%)

Content Size

2.5 MB

After Optimization

2.2 MB

  • Images
  • JavaScript

In fact, the total size of Reyesmex.com main page is 2.5 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. 40% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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. This web page is already compressed.

Image Optimization

-15%

Potential reduce by 338.0 kB

  • Original 2.2 MB
  • After minification 1.9 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. Obviously, Reyes Mex needs image optimization as it can save up to 338.0 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 3.6 kB

  • Original 259.0 kB
  • After minification 259.0 kB
  • After compression 255.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 10 (25%)

Requests Now

40

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.reyesmex.com

www.reyesmex.com

124 ms

minified.js

minified.js

30 ms

focus-within-polyfill.js

focus-within-polyfill.js

29 ms

polyfill.min.js

polyfill.min.js

29 ms

thunderbolt-commons.7700cd07.bundle.min.js

thunderbolt-commons.7700cd07.bundle.min.js

118 ms

main.16c08821.bundle.min.js

main.16c08821.bundle.min.js

118 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

117 ms

lodash.min.js

lodash.min.js

123 ms

react.production.min.js

react.production.min.js

134 ms

react-dom.production.min.js

react-dom.production.min.js

134 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

122 ms

0af4a5b2f5cd4d36a0a2bdef00ee6ad8.png

0af4a5b2f5cd4d36a0a2bdef00ee6ad8.png

92 ms

bundle.min.js

bundle.min.js

65 ms

Reyes_FINAL_white.png

Reyes_FINAL_white.png

191 ms

34ad14_5fc637859008407ab402f440c1e43ae2~mv2.jpg

34ad14_5fc637859008407ab402f440c1e43ae2~mv2.jpg

202 ms

Reyes_logo_white.png

Reyes_logo_white.png

273 ms

donkey_edited.png

donkey_edited.png

200 ms

Reyes-03717.jpg

Reyes-03717.jpg

197 ms

donkey_edited.png

donkey_edited.png

249 ms

e2d616_ed88bdfebb2148c580f2a05673a9f025~mv2.jpg

e2d616_ed88bdfebb2148c580f2a05673a9f025~mv2.jpg

323 ms

Parking%2520Directions_edited.jpg

Parking%2520Directions_edited.jpg

395 ms

e2d616_a93b7622e9234731b9f9d4c1c6156a4d~mv2.jpg

e2d616_a93b7622e9234731b9f9d4c1c6156a4d~mv2.jpg

208 ms

e2d616_e5c2b5eec72f4056b3f9854eae40745e~mv2.jpg

e2d616_e5c2b5eec72f4056b3f9854eae40745e~mv2.jpg

207 ms

e2d616_1f3def2d49c141af9074d420e8b6c4a6~mv2.jpg

e2d616_1f3def2d49c141af9074d420e8b6c4a6~mv2.jpg

214 ms

e2d616_39104f5d0dfd4711aa676592cf2e3cff~mv2.jpg

e2d616_39104f5d0dfd4711aa676592cf2e3cff~mv2.jpg

214 ms

e2d616_8cc763d7e8e14465b3d01719a6a3bc01~mv2.jpg

e2d616_8cc763d7e8e14465b3d01719a6a3bc01~mv2.jpg

223 ms

e2d616_11987404d3f24b88a14effb3a8b21211~mv2.png

e2d616_11987404d3f24b88a14effb3a8b21211~mv2.png

228 ms

e2d616_9aa67ea2a14745198bbf39b396c8b873~mv2.jpg

e2d616_9aa67ea2a14745198bbf39b396c8b873~mv2.jpg

230 ms

e2d616_dd38e9701958482fb4928c75ff0c74fc~mv2.png

e2d616_dd38e9701958482fb4928c75ff0c74fc~mv2.png

240 ms

e2d616_d263b6a5e92f4d90959cd8233e0d5499~mv2.jpg

e2d616_d263b6a5e92f4d90959cd8233e0d5499~mv2.jpg

237 ms

e2d616_521759fc57a6494d8bd4aa79cc3a95fb~mv2.jpg

e2d616_521759fc57a6494d8bd4aa79cc3a95fb~mv2.jpg

242 ms

e2d616_8089fbc7904f494484a6a1566c8083e8~mv2.jpg

e2d616_8089fbc7904f494484a6a1566c8083e8~mv2.jpg

257 ms

e2d616_19f0edf34f054054bafc321e9f041154~mv2.jpg

e2d616_19f0edf34f054054bafc321e9f041154~mv2.jpg

248 ms

e2d616_3f52ab7040814ab0944ee389cea52834~mv2.jpg

e2d616_3f52ab7040814ab0944ee389cea52834~mv2.jpg

253 ms

e2d616_d978e7b3e9984c999c4e793d030a00d2~mv2.jpg

e2d616_d978e7b3e9984c999c4e793d030a00d2~mv2.jpg

254 ms

agave_edited.png

agave_edited.png

361 ms

GS_logo_noBG_white%20(1).png

GS_logo_noBG_white%20(1).png

438 ms

102 ms

101 ms

100 ms

101 ms

99 ms

97 ms

124 ms

122 ms

122 ms

126 ms

121 ms

125 ms

file.woff

file.woff

99 ms

file.woff

file.woff

263 ms

deprecation-en.v5.html

deprecation-en.v5.html

5 ms

bolt-performance

bolt-performance

22 ms

deprecation-style.v5.css

deprecation-style.v5.css

6 ms

right-arrow.svg

right-arrow.svg

5 ms

Accessibility Review

reyesmex.com accessibility score

90

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

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

Buttons do not have an accessible name

Best Practices

reyesmex.com best practices score

92

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

Page has valid source maps

SEO Factors

reyesmex.com SEO score

100

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

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

reyesmex.com

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