11.2 sec in total
869 ms
10.1 sec
265 ms
Click here to check amazing Royal Host content for Japan. Otherwise, check out these important facts you probably never knew about royalhost.jp
“あんしん”だから“おいしい”。みんなにやさしいファミリーレストラン ロイヤルホストのホームページです。私たちは、おいしい料理と心地良いサービスでおもてなし致します。
Visit royalhost.jpWe analyzed Royalhost.jp page load time and found that the first response time was 869 ms and then it took 10.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
royalhost.jp performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value15.5 s
0/100
25%
Value9.9 s
10/100
10%
Value2,200 ms
6/100
30%
Value1.094
1/100
15%
Value9.9 s
27/100
10%
869 ms
502 ms
503 ms
689 ms
353 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 96% of them (90 requests) were addressed to the original Royalhost.jp, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ie7-js.googlecode.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Royalhost.jp.
Page size can be reduced by 258.4 kB (11%)
2.2 MB
2.0 MB
In fact, the total size of Royalhost.jp main page is 2.2 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. 30% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 11.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. This page needs HTML code to be minified as it can gain 2.0 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 11.0 kB or 72% of the original size.
Potential reduce by 1.1 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. Royal Host images are well optimized though.
Potential reduce by 122.7 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 122.7 kB or 70% of the original size.
Potential reduce by 123.6 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. Royalhost.jp needs all CSS files to be minified and compressed as it can save up to 123.6 kB or 85% of the original size.
Number of requests can be reduced by 34 (37%)
93
59
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Royal Host. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
royalhost.jp
869 ms
txt_m.css
502 ms
common.css
503 ms
content.css
689 ms
styleswitcher.js
353 ms
open.js
366 ms
smartRollover.js
632 ms
jquery.js
1536 ms
iepngfix_tilebg.js
902 ms
subMenu.js
818 ms
rollover.js
823 ms
navi.js
1022 ms
newyear.js
1028 ms
IE9.js
70 ms
common0609.css
1293 ms
slider2.css
1156 ms
jquery.min.js
30 ms
slider2.js
1233 ms
osusume.css
977 ms
menu.css
678 ms
add.css
1172 ms
0909.css
1302 ms
1208.css
1110 ms
0912.css
1179 ms
strawberry.css
1225 ms
ga.js
30 ms
txt_l.css
351 ms
__utm.gif
21 ms
back.jpg
322 ms
back120313.jpg
659 ms
logo.jpg
496 ms
head_kensaku_off.jpg
506 ms
head_con_off.jpg
351 ms
head_map_off.jpg
635 ms
head_press_off.jpg
638 ms
btm00_off.jpg
850 ms
btm01_off.jpg
1163 ms
btm02_off.jpg
1228 ms
btm03_off.jpg
1111 ms
btm04_off.jpg
1179 ms
btm05_off.jpg
1047 ms
contents_back.gif
1215 ms
01.jpg
2723 ms
selected.jpg
2686 ms
lunch.jpg
2744 ms
morning.jpg
2686 ms
01_off.jpg
2060 ms
02_off.jpg
2062 ms
03_off.jpg
2965 ms
under_box_back.gif
2446 ms
under_box_top.gif
2767 ms
img_2.gif
3210 ms
icon_2.gif
3053 ms
icon_3.gif
3055 ms
icon_1.gif
3093 ms
01_off.jpg
3750 ms
cowboy_off.jpg
3903 ms
100310_bnr_search_off.gif
3528 ms
banner03_off.jpg
3715 ms
banner_off.gif
3616 ms
100310_bnr_online_off.gif
3750 ms
banner02_off.jpg
4190 ms
mb.jpg
4164 ms
jcb.jpg
4043 ms
01.jpg
3920 ms
120110_bnr_jalcard.gif
3757 ms
100802_jafnavi_bnr0194.gif
3900 ms
bn_royal_2.jpg
4118 ms
bg_arrow_2.gif
3890 ms
under_box_under.gif
3905 ms
pagetop_1.gif
3933 ms
footer_back120313.jpg
3812 ms
navi.png
3697 ms
txt_s.css
367 ms
head_kensaku_on.jpg
320 ms
head_con_on.jpg
320 ms
head_map_on.jpg
331 ms
head_press_on.jpg
337 ms
btm00_on.jpg
525 ms
btm01_on.jpg
729 ms
btm02_on.jpg
991 ms
btm03_on.jpg
831 ms
btm04_on.jpg
858 ms
btm05_on.jpg
671 ms
01_on.jpg
1425 ms
02_on.jpg
1545 ms
03_on.jpg
1524 ms
01_on.jpg
1883 ms
cowboy_on.jpg
1580 ms
100310_bnr_search_on.gif
1333 ms
banner03_on.jpg
1970 ms
banner_on.gif
1950 ms
100310_bnr_online_on.gif
2028 ms
banner02_on.jpg
2305 ms
royalhost.jp accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
royalhost.jp 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
Browser errors were logged to the console
Page has valid source maps
royalhost.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Royalhost.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Royalhost.jp 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.
royalhost.jp
Open Graph description is not detected on the main page of Royal Host. 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: