7.1 sec in total
560 ms
6.2 sec
327 ms
Welcome to rubura.org homepage info - get ready to check Rubura best content for Japan right away, or after learning these important things about rubura.org
ホテルルブラ王山は地下鉄東山線池下駅下車2番出口より徒歩3分。11月オープンのジブリパークやバンテリンドーム ナゴヤ、東山動植物園、名古屋城などへの拠点にレジャーやビジネスにも便利です。
Visit rubura.orgWe analyzed Rubura.org page load time and found that the first response time was 560 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
rubura.org performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value10.6 s
0/100
25%
Value18.2 s
0/100
10%
Value360 ms
72/100
30%
Value0.197
62/100
15%
Value12.8 s
13/100
10%
560 ms
1245 ms
181 ms
541 ms
529 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 90% of them (80 requests) were addressed to the original Rubura.org, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Stats.wp.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Rubura.org.
Page size can be reduced by 163.8 kB (8%)
2.1 MB
2.0 MB
In fact, the total size of Rubura.org main page is 2.1 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. 55% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 62.4 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 17.3 kB, which is 24% 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 62.4 kB or 85% of the original size.
Potential reduce by 46.6 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. Rubura images are well optimized though.
Potential reduce by 46.0 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 46.0 kB or 29% of the original size.
Potential reduce by 8.8 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. Rubura.org needs all CSS files to be minified and compressed as it can save up to 8.8 kB or 24% of the original size.
Number of requests can be reduced by 20 (23%)
86
66
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rubura. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
rubura.org
560 ms
www.rubura.org
1245 ms
common.css
181 ms
jquery.min.js
541 ms
style.js
529 ms
jquery.tile.js
530 ms
jquery.bxslider.css
530 ms
jquery.bxslider.min.js
531 ms
top.ini.js
534 ms
analytics.js
30 ms
style.min.css
759 ms
jquery.fancybox.min.css
763 ms
jetpack.css
884 ms
css3_brown_glossy.css
763 ms
jquery.min.js
897 ms
jquery-migrate.min.js
763 ms
jquery.fancybox.min.js
939 ms
jquery.mousewheel.min.js
890 ms
wp-embed.min.js
937 ms
e-202422.js
26 ms
css
37 ms
wp-emoji-release.min.js
465 ms
collect
14 ms
js
48 ms
embed
327 ms
logo.png
183 ms
header_tel01.png
183 ms
header_access.png
178 ms
header_tel02.png
184 ms
header_contact.png
178 ms
header_btn01.png
203 ms
header_btn02.png
349 ms
btn_menu.png
353 ms
gnavi01.png
356 ms
gnavi02.png
355 ms
gnavi03.png
353 ms
gnavi04.png
374 ms
gnavi05.png
525 ms
gnavi06.png
529 ms
gnavi07.png
530 ms
gnavi08.png
532 ms
gnavi09.png
532 ms
slide01.jpg
1075 ms
R5.6-7.jpg
1050 ms
R5.6-1.jpg
1227 ms
2024.4-5-1.jpg
1231 ms
4d8164e45d522f086d173465a428cb64-1.jpg
888 ms
d19419db6be3a93346e77f582102007b-1.jpg
710 ms
4f70a0948dc563e74582dc8a4353e386-1.jpg
1067 ms
dbe7063a2229730968c26ec1ab6aeda5.jpg
1070 ms
27ff3c492eb26220836262fc1cee486c.jpg
1402 ms
6b35aca88c55b6dc02ea5ec728d247a8.jpg
1424 ms
bnr.jpg
1250 ms
nav_bg.png
1252 ms
noimage.png
1403 ms
IMG_7563-237x237.jpg
1408 ms
IMG_7611-237x237.jpg
1430 ms
509440-237x237.jpg
1429 ms
125885765_3459038020817318_1556660838096248166_o-237x237.jpg
1577 ms
e7778f04602dce5535f051b8142c3190-237x237.jpg
1473 ms
yYLl0h7WyfzTzI49.ttf
62 ms
509440-237x237-1-237x237.jpg
1479 ms
1f338.svg
38 ms
IMG_7302-237x237.jpg
1438 ms
IMG_7433-237x237.jpg
1441 ms
be4edc634618b7178a0d62a04e7d30da-237x237.jpg
1440 ms
IMG_0379-237x237.jpg
1585 ms
457b5e35ceb2f1d4329d00871f6111d8-237x237.jpg
1571 ms
77b871695f4216842455aaccd81fcf62-237x237.jpg
1576 ms
js
53 ms
bab96f91608f7af78b8c0872f3891f0d_s-1-237x237.jpg
1441 ms
IMG_8878-237x237.jpg
1441 ms
IMG_4375-237x237.jpg
1442 ms
IMG_4377-237x237.jpg
1584 ms
IMG_4382-237x237.jpg
1587 ms
image_bg.png
1577 ms
757066-660x495.jpg
1446 ms
M_gainfriends_2dbarcodes_GW-660x466.jpg
1443 ms
1704070860454-e1704072067659-660x576.jpg
1447 ms
ico_arrow02.png
1585 ms
pagetop.png
1587 ms
footer_logo.png
1414 ms
ico_fb.png
1257 ms
ico_tw.png
1098 ms
ico_ig.png
1084 ms
ico_line.png
1220 ms
bx_loader.gif
1222 ms
slide_prev.png
1075 ms
slide_next.png
1091 ms
rubura.org accessibility score
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.
rubura.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
rubura.org 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
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rubura.org 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 Rubura.org 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.
rubura.org
Open Graph data is detected on the main page of Rubura. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: