Tools & Wizards About Us
hashplayavista.com screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

hashplayavista.com

HASH | Breakfast Restaurant | Playa Vista, CA | Los Angeles

Page Load Speed

1.7 sec in total

First Response

88 ms

Resources Loaded

1.6 sec

Page Rendered

56 ms

hashplayavista.com screenshot

About Website

Visit hashplayavista.com now to see the best up-to-date HASH Playa Vista content and also check out these interesting facts you probably never knew about hashplayavista.com

HASH: Best Breakfast In Los Angeles! Belgian Waffles, Fluffy Pancakes, Eggs-traOrdinary Breakfast Options and more... Inspired by our love for breakfast, the best meal of the day.

Visit hashplayavista.com

Key Findings

We analyzed Hashplayavista.com page load time and found that the first response time was 88 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

hashplayavista.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value3.1 s

92/100

10%

TBT (Total Blocking Time)

Value1,400 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

www.hashrestaurant.com

88 ms

minified.js

30 ms

focus-within-polyfill.js

59 ms

polyfill.min.js

27 ms

adsbygoogle.js

106 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Hashplayavista.com, 14% (12 requests) were made to Pagead2.googlesyndication.com and 14% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (565 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

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

Content Size

1.7 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Hashplayavista.com main page is 1.7 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. 60% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 393.2 kB

  • Original 503.9 kB
  • After minification 502.1 kB
  • After compression 110.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 393.2 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 940 B

  • Original 29.8 kB
  • After minification 28.9 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. HASH Playa Vista images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 142.7 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 986.9 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 142.7 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (60%)

Requests Now

67

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.hashrestaurant.com

www.hashrestaurant.com

88 ms

minified.js

minified.js

30 ms

focus-within-polyfill.js

focus-within-polyfill.js

59 ms

polyfill.min.js

polyfill.min.js

27 ms

adsbygoogle.js

adsbygoogle.js

106 ms

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

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

90 ms

main.16c08821.bundle.min.js

main.16c08821.bundle.min.js

90 ms

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

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

89 ms

lodash.min.js

lodash.min.js

90 ms

react.production.min.js

react.production.min.js

90 ms

react-dom.production.min.js

react-dom.production.min.js

92 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

91 ms

widget.js

widget.js

180 ms

5b1880_b635ee6be5024fc49d2776af8b721ea3~mv2.png

5b1880_b635ee6be5024fc49d2776af8b721ea3~mv2.png

201 ms

bundle.min.js

bundle.min.js

90 ms

5b1880_308edbdb7ed544869ac70833b65b7ea9~mv2_d_1800_1200_s_2.jpg

5b1880_308edbdb7ed544869ac70833b65b7ea9~mv2_d_1800_1200_s_2.jpg

282 ms

Yogurt-Trifle-w-Mixed-Fruit-Homemade-Glu.jpg

Yogurt-Trifle-w-Mixed-Fruit-Homemade-Glu.jpg

282 ms

Philly-Crust-French-Toast-HASH-Breakfast.jpg

Philly-Crust-French-Toast-HASH-Breakfast.jpg

253 ms

Chocolate-Chip-Pancakes-Hash-Breakfast-R.jpg

Chocolate-Chip-Pancakes-Hash-Breakfast-R.jpg

300 ms

bebop%20bowl-hash-breakfast-800.jpg

bebop%20bowl-hash-breakfast-800.jpg

330 ms

Big-Papa-Breakfast-sandwich-HASH-Playa-V.jpg

Big-Papa-Breakfast-sandwich-HASH-Playa-V.jpg

324 ms

5b1880_f8e552b50f74490ba1141ac8b04c09ed~mv2.png

5b1880_f8e552b50f74490ba1141ac8b04c09ed~mv2.png

409 ms

5b1880_76f661c1bf6d4fa3a27bef1642f3b1c8~mv2.png

5b1880_76f661c1bf6d4fa3a27bef1642f3b1c8~mv2.png

432 ms

5b1880_aefcd1a5e3f34ae4bd313af046954bb4~mv2_d_1800_1200_s_2.jpg

5b1880_aefcd1a5e3f34ae4bd313af046954bb4~mv2_d_1800_1200_s_2.jpg

497 ms

show_ads_impl.js

show_ads_impl.js

149 ms

94 ms

95 ms

178 ms

177 ms

175 ms

172 ms

169 ms

167 ms

197 ms

188 ms

172 ms

169 ms

widget_app_base_1725874918757.js

widget_app_base_1725874918757.js

26 ms

80de9d5d-ab5f-40ce-911b-104e51e93d7c.woff

80de9d5d-ab5f-40ce-911b-104e51e93d7c.woff

9 ms

QkxXQ7hF5m

QkxXQ7hF5m

335 ms

zrt_lookup.html

zrt_lookup.html

30 ms

ads

ads

565 ms

en-US.json

en-US.json

7 ms

sodar

sodar

38 ms

deprecation-en.v5.html

deprecation-en.v5.html

12 ms

bolt-performance

bolt-performance

19 ms

reactive_library.js

reactive_library.js

64 ms

deprecation-style.v5.css

deprecation-style.v5.css

9 ms

right-arrow.svg

right-arrow.svg

22 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

4 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

8 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

4 ms

sodar2.js

sodar2.js

24 ms

runner.html

runner.html

16 ms

aframe

aframe

43 ms

gen_204

gen_204

19 ms

pixel

pixel

43 ms

dv3.js

dv3.js

29 ms

window_focus.js

window_focus.js

5 ms

qs_click_protection.js

qs_click_protection.js

10 ms

ufs_web_display.js

ufs_web_display.js

22 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

10 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

13 ms

pixel

pixel

40 ms

171001.js

171001.js

56 ms

gen_204

gen_204

37 ms

dFv_sHiz6Z5Qfnds41P-Qz-x_VXgV0A6IVrYWelEutw.js

dFv_sHiz6Z5Qfnds41P-Qz-x_VXgV0A6IVrYWelEutw.js

14 ms

ad

ad

50 ms

ad

ad

59 ms

pixel

pixel

57 ms

pixel

pixel

56 ms

remediation-tool-free.js

remediation-tool-free.js

129 ms

skeleton.js

skeleton.js

218 ms

9758598915904327472

9758598915904327472

217 ms

abg_lite.js

abg_lite.js

116 ms

omrhp.js

omrhp.js

117 ms

Q12zgMmT.js

Q12zgMmT.js

166 ms

body_wh.svg

body_wh.svg

197 ms

spin_wh.svg

spin_wh.svg

209 ms

icon.png

icon.png

166 ms

62bHydCX.html

62bHydCX.html

25 ms

activeview

activeview

87 ms

bounce

bounce

39 ms

rum

rum

37 ms

pixel

pixel

26 ms

pixel

pixel

25 ms

rum

rum

41 ms

Accessibility Review

hashplayavista.com accessibility score

89

Accessibility Issues

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

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

Best Practices

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

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

    EN

  • Encoding

    UTF-8

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

hashplayavista.com

Open Graph data is detected on the main page of HASH Playa Vista. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: