2.5 sec in total
928 ms
1.4 sec
195 ms
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.restaurantWe 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.
o-ya.restaurant performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value5.3 s
22/100
25%
Value6.3 s
42/100
10%
Value410 ms
67/100
30%
Value0
100/100
15%
Value8.8 s
35/100
10%
928 ms
14 ms
126 ms
12 ms
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 size can be reduced by 289.8 kB (12%)
2.4 MB
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.
Potential reduce by 36.5 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.
Potential reduce by 31.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. O Ya images are well optimized though.
Potential reduce by 126.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 126.1 kB or 49% of the original size.
Potential reduce by 95.3 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.
Number of requests can be reduced by 25 (71%)
35
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.
o-ya.restaurant
928 ms
css
14 ms
mll5sga.js
126 ms
style.css
12 ms
modernizr-2.8.3.min.js
49 ms
jquery.vegas.css
37 ms
jquery.js
26 ms
jquery-migrate.min.js
37 ms
mll5sga.js
133 ms
jquery.min.js
12 ms
plugins.js
52 ms
main.js
52 ms
otw-datepicker.css
41 ms
open-table-widget.css
41 ms
selectric.css
43 ms
jquery.vegas.js
43 ms
wp-embed.min.js
43 ms
open-table-widget.js
43 ms
datepicker.js
47 ms
jquery.selectric.js
49 ms
main.css
5 ms
media-queries.css
7 ms
normalize.css
8 ms
wp-emoji-release.min.js
153 ms
analytics.js
138 ms
fbevents.js
167 ms
analytics.js
137 ms
accordian.png
28 ms
texture.jpg
26 ms
jbf-award-winner-o-ya.png
57 ms
close.png
27 ms
Amy-Braga-Photography-2008-026.jpg
49 ms
p.gif
100 ms
p-22-johnston-underground-1361501764-webfont.woff
25 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
33 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
37 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
46 ms
ACaslonPro-Italic.otf
24 ms
d
33 ms
d
37 ms
d
45 ms
d
46 ms
d
46 ms
d
45 ms
d
45 ms
collect
15 ms
collect
45 ms
1890336161289389
44 ms
63 ms
o-ya.restaurant accessibility score
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
Links do not have a discernible name
o-ya.restaurant best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
o-ya.restaurant SEO score
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
Document uses legible font sizes
EN
N/A
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.
o-ya.restaurant
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: