Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

o-ya.restaurant

"Expect a Brilliantly Non-Traditional Sushi Experience" - Eater NY | o ya in boston mexico city

Page Load Speed

2.5 sec in total

First Response

928 ms

Resources Loaded

1.4 sec

Page Rendered

195 ms

About Website

Welcome to o-ya.restaurant homepage info - get ready to check O Ya best content for United States right away, or after learning these important things about o-ya.restaurant

creative omakase riffing on flavors from the global culinary journeys of James Beard Award Winning Chef Tim Cushman and Advanced Sake Professional Nancy Cushman

Visit o-ya.restaurant

Key Findings

We analyzed O-ya.restaurant page load time and found that the first response time was 928 ms and then it took 1.6 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

o-ya.restaurant performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.8 s

35/100

10%

Network Requests Diagram

o-ya.restaurant

928 ms

css

14 ms

mll5sga.js

126 ms

style.css

12 ms

modernizr-2.8.3.min.js

49 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 55% of them (27 requests) were addressed to the original O-ya.restaurant, 18% (9 requests) were made to Use.typekit.net and 6% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (928 ms) belongs to the original domain O-ya.restaurant.

Page Optimization Overview & Recommendations

Page size can be reduced by 321.7 kB (13%)

Content Size

2.4 MB

After Optimization

2.1 MB

In fact, the total size of O-ya.restaurant main page is 2.4 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. 65% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 36.5 kB

  • Original 44.5 kB
  • After minification 42.0 kB
  • After compression 8.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 36.5 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 31.9 kB

  • Original 2.0 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. O Ya images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 158.0 kB

  • Original 290.1 kB
  • After minification 266.9 kB
  • After compression 132.1 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 158.0 kB or 54% of the original size.

CSS Optimization

-86%

Potential reduce by 95.3 kB

  • Original 110.8 kB
  • After minification 80.9 kB
  • After compression 15.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. O-ya.restaurant needs all CSS files to be minified and compressed as it can save up to 95.3 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

35

After Optimization

10

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

Accessibility Review

o-ya.restaurant accessibility score

98

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

Links do not have a discernible name

Best Practices

o-ya.restaurant 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

o-ya.restaurant 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 O-ya.restaurant 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 O-ya.restaurant 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 data is detected on the main page of O Ya. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: