Tools & Wizards About Us
locations.eatnpark.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

locations.eatnpark.com

Page Load Speed

1.4 sec in total

First Response

73 ms

Resources Loaded

910 ms

Page Rendered

445 ms

locations.eatnpark.com screenshot

About Website

Welcome to locations.eatnpark.com homepage info - get ready to check Locations Eatnpark best content for United States right away, or after learning these important things about locations.eatnpark.com

Use our convenient Eat'n Park location finder to find a family restaurant near you! We offer full takeout & pick up meal services.

Visit locations.eatnpark.com

Key Findings

We analyzed Locations.eatnpark.com page load time and found that the first response time was 73 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

locations.eatnpark.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value1,140 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.683

7/100

15%

TTI (Time to Interactive)

Value10.3 s

25/100

10%

Network Requests Diagram

locations.eatnpark.com

73 ms

locations.eatnpark.com

49 ms

css

62 ms

client-bootstrap.css

80 ms

client-hamburger.css

74 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 6% of them (3 requests) were addressed to the original Locations.eatnpark.com, 53% (25 requests) were made to Assets.locations.eatnpark.com and 9% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (605 ms) relates to the external source Eatnpark.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.4 MB (63%)

Content Size

3.9 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Locations.eatnpark.com main page is 3.9 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. 70% of websites need less resources to load. HTML takes 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-96%

Potential reduce by 2.4 MB

  • Original 2.5 MB
  • After minification 2.5 MB
  • After compression 110.0 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 2.4 MB or 96% of the original size.

Image Optimization

-1%

Potential reduce by 10.4 kB

  • Original 954.0 kB
  • After minification 943.6 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. Locations Eatnpark images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 4.7 kB

  • Original 318.7 kB
  • After minification 318.7 kB
  • After compression 314.0 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.

CSS Optimization

-7%

Potential reduce by 3.6 kB

  • Original 53.2 kB
  • After minification 53.2 kB
  • After compression 49.5 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. Locations.eatnpark.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (50%)

Requests Now

40

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

locations.eatnpark.com

locations.eatnpark.com

73 ms

locations.eatnpark.com

locations.eatnpark.com

49 ms

css

css

62 ms

client-bootstrap.css

client-bootstrap.css

80 ms

client-hamburger.css

client-hamburger.css

74 ms

client-main.css

client-main.css

75 ms

styles.min.css

styles.min.css

90 ms

pollyfill.min.js

pollyfill.min.js

88 ms

js

js

428 ms

js

js

432 ms

leaflet.js

leaflet.js

87 ms

js

js

432 ms

Leaflet.GoogleMutant.js

Leaflet.GoogleMutant.js

87 ms

page.js

page.js

334 ms

locator.js

locator.js

384 ms

scripts.min.js

scripts.min.js

363 ms

logo_desktop.svg

logo_desktop.svg

605 ms

6715_49_24ENP6755_Web_RioSEO_Panels.jpg

6715_49_24ENP6755_Web_RioSEO_Panels.jpg

480 ms

logo_mobile.svg

logo_mobile.svg

458 ms

logo-dark.png

logo-dark.png

431 ms

logo-mobile.png

logo-mobile.png

227 ms

logo-mini.png

logo-mini.png

227 ms

browse-background.jpg

browse-background.jpg

242 ms

arrow-right.svg

arrow-right.svg

224 ms

app-store-img.png

app-store-img.png

227 ms

google-play-img.png

google-play-img.png

225 ms

6715_47_24ENP6755_Web_RioSEO_Panels2.jpg

6715_47_24ENP6755_Web_RioSEO_Panels2.jpg

254 ms

6715_48_24ENP6755_Web_RioSEO_Panels3.jpg

6715_48_24ENP6755_Web_RioSEO_Panels3.jpg

254 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

254 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

295 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

296 ms

getAutocompleteData

getAutocompleteData

120 ms

getAsyncLocations

getAsyncLocations

280 ms

fetridge-webfont.woff

fetridge-webfont.woff

119 ms

icomoon.ttf

icomoon.ttf

106 ms

js

js

109 ms

analytics.js

analytics.js

80 ms

js

js

100 ms

collect

collect

71 ms

collect

collect

76 ms

map-pin.svg

map-pin.svg

15 ms

filter-icon.svg

filter-icon.svg

40 ms

close-mobile.svg

close-mobile.svg

35 ms

dropdown-arrow.svg

dropdown-arrow.svg

11 ms

phone.svg

phone.svg

14 ms

details.svg

details.svg

13 ms

service-check.svg

service-check.svg

14 ms

Accessibility Review

locations.eatnpark.com accessibility score

91

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

[aria-*] attributes do not match their roles

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.

Best Practices

locations.eatnpark.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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

Page has valid source maps

SEO Factors

locations.eatnpark.com SEO score

91

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Locations.eatnpark.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Locations.eatnpark.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

locations.eatnpark.com

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