o-ya.restaurant Website Information
Daily Unique Visits: 996
Daily Page Views: 1,992
Income Per Day: $6
Estimated Value: $1,440
o-ya.restaurant is registered under .RESTAURANT top-level domain. Please check other sites in .RESTAURANT zone.
No name server records were found.
and is probably hosted by AMAZON-AES - Amazon.com, Inc., US. See the full list of other websites hosted by AMAZON-AES - Amazon.com, Inc., US.
The highest website o-ya.restaurant position in Alexa rank database was 63088 and the lowest rank position was 998342. Current position of o-ya.restaurant in Alexa rank database is 720114.
Desktop speed score of o-ya.restaurant (91/100) shows that the page is performing great on desktop computers.
Mobile usability score of o-ya.restaurant (92/100) is better than the results of 33.5% of other sites and means that the page is mobile-friendly.
Mobile speed score of o-ya.restaurant (57/100) is better than the results of 48.04% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
o-ya.restaurant Alexa Rank
The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.
o-ya.restaurant whois
WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.
o-ya.restaurant server information
Servers Location
o-ya.restaurant desktop page speed rank
Last tested: 2016-05-24
o-ya.restaurant Desktop Speed Test Quick Summary
priority - 9Reduce server response time
o-ya.restaurant Desktop Resource Breakdown
| Total Resources | 4 |
| Number of Hosts | 3 |
| Static Resources | 2 |
o-ya.restaurant mobile page speed rank
Last tested: 2019-12-26
o-ya.restaurant Mobile Speed Test Quick Summary
priority - 64Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
https://assets-cdn-refresh.getbento.com/stylesheet…58dc0923d23782108.scss
priority - 14Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 132.6KiB (23% reduction).
Compressing https://images.getbento.com/0HRyvuENSJmAh86ZNXOg_Oya_logo.png could save 4.8KiB (14% reduction).
priority - 1Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://www.google-analytics.com/analytics.js (2 hours)
priority - 0Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 963B (13% reduction).
o-ya.restaurant Mobile Resource Breakdown
| Total Resources | 30 |
| Number of Hosts | 11 |
| Static Resources | 24 |
| JavaScript Resources | 6 |
| CSS Resources | 2 |
o-ya.restaurant mobile page usability
Last tested: 2019-12-26
o-ya.restaurant Mobile Usability Test Quick Summary
priority - 7Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
<button type="button" class="arrow-btn arro…ft slick-arrow">Previous Slide</button> and 1 others are close to other tap targets.<button type="button" class="arrow-btn arro…ft slick-arrow">Previous Slide</button> and 1 others are close to other tap targets.<a href="https://goo.gl…s/fUL6RAYL7aS2">9 east streetboston, ma 02111</a> and 7 others are close to other tap targets.<a href="/location/o-ya-boston/" class="btn btn-brand">Learn More</a> is close to 1 other tap targets.<a href="/reservations/" class="btn btn-brand-alt btn-block">Reservations</a> and 1 others are close to other tap targets.o-ya.restaurant HTML validation
Errors
Almost standards mode doctype. Expected “<!DOCTYPE html>”.
"...<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html..."
Bad value “<? bloginfo('url'); ?>/wp-content/themes/o-ya-restaurant/favicon.ico” for attribute “href” on element “link”: Illegal character in path segment: “<” is not allowed.
"... <link rel="shortcut icon" href="<? bloginfo('url'); ?>/wp-content/themes/o-ya-restaurant/favicon.ico" /> ..."
Bad value “https://api.w.org/” for attribute “rel” on element “link”: The string “https://api.w.org/” is not a registered keyword.
"...</script> <link rel='https://api.w.org/' href='https://o-ya.restaurant/wp-json/' /> <link..."
Bad start tag in “img” in “head”.
"...oscript> <img height="1" width="1" src="https://www.facebook.com/tr?id=1890336161289389&ev=PageView &noscript=1"/> </nosc..."
Bad value “https://www.facebook.com/tr?id=1890336161289389&ev=PageView &noscript=1” for attribute “src” on element “img”: Tab, new line or carriage return found.
"...oscript> <img height="1" width="1" src="https://www.facebook.com/tr?id=1890336161289389&ev=PageView &noscript=1"/> </nosc..."
An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
"...oscript> <img height="1" width="1" src="https://www.facebook.com/tr?id=1890336161289389&ev=PageView &noscript=1"/> </nosc..."
Stray end tag “noscript”.
"...ript=1"/> </noscript> <!-- ..."
Element “style” not allowed as child of element “body” in this context. (Suppressing further errors from this subtree.)
"...l Code --><style type="text/css" id="simple-css-output">/*@med..."
Stray end tag “head”.
"... --> </head> <..."
Start tag “body” seen but an element of the same type was already open.
"...head> <body class="home blog"> ..."
Cannot recover after last error. Any further errors will be ignored.
"...head> <body class="home blog"> ..."
o-ya.restaurant similar domains
www.o-ya.net
www.o-ya.org
www.o-ya.info
www.o-ya.biz
www.o-ya.us
www.o-ya.mobi
www.-ya.restaurant
www.o-ya.restaurant
www.i-ya.restaurant
www.oi-ya.restaurant
www.io-ya.restaurant
www.k-ya.restaurant
www.ok-ya.restaurant
www.ko-ya.restaurant
www.l-ya.restaurant
www.ol-ya.restaurant
www.lo-ya.restaurant
www.p-ya.restaurant
www.op-ya.restaurant
www.po-ya.restaurant
www.oya.restaurant
www.o-a.restaurant
www.o-ta.restaurant
www.o-yta.restaurant
www.o-tya.restaurant
www.o-ga.restaurant
www.o-yga.restaurant
www.o-gya.restaurant
www.o-ha.restaurant
www.o-yha.restaurant
www.o-hya.restaurant
www.o-ua.restaurant
www.o-yua.restaurant
www.o-uya.restaurant
www.o-y.restaurant
www.o-yq.restaurant
www.o-yaq.restaurant
www.o-yqa.restaurant
www.o-yw.restaurant
www.o-yaw.restaurant
www.o-ywa.restaurant
www.o-ys.restaurant
www.o-yas.restaurant
www.o-ysa.restaurant
www.o-yz.restaurant
www.o-yaz.restaurant
www.o-yza.restaurant
o-ya.restaurant Ping
Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.
o-ya.restaurant TRACEROUTE
Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.