6.7 sec in total
1.1 sec
5.2 sec
481 ms
Visit rlx.jp now to see the best up-to-date Rlx content for Japan and also check out these interesting facts you probably never knew about rlx.jp
ホテル・旅館の宿泊予約をするならRelux(リラックス)。全国から満足度の高いホテル・旅館を厳選してご紹介します。ご希望の日程や条件でお探しいただけます。早期割引や直前割引などお得な宿泊プランも掲載中。ご予約いただいた宿泊プランで最大6%のポイント還元など、お得に宿泊できます。宿泊予約にぜひReluxをご利用ください。
Visit rlx.jpWe analyzed Rlx.jp page load time and found that the first response time was 1.1 sec and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
rlx.jp performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value7.6 s
3/100
25%
Value9.7 s
11/100
10%
Value5,450 ms
0/100
30%
Value0.137
80/100
15%
Value21.5 s
1/100
10%
1061 ms
73 ms
149 ms
296 ms
443 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 46% of them (47 requests) were addressed to the original Rlx.jp, 14% (14 requests) were made to Scontent.xx.fbcdn.net and 12% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Rlx.jp.
Page size can be reduced by 685.5 kB (26%)
2.6 MB
1.9 MB
In fact, the total size of Rlx.jp main page is 2.6 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. 45% 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.6 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 7.1 kB, which is 15% 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 36.6 kB or 77% of the original size.
Potential reduce by 236.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. Obviously, Rlx needs image optimization as it can save up to 236.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 293.5 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 293.5 kB or 73% of the original size.
Potential reduce by 118.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. Rlx.jp needs all CSS files to be minified and compressed as it can save up to 118.8 kB or 84% of the original size.
Number of requests can be reduced by 53 (56%)
94
41
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rlx. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
rlx.jp
1061 ms
icon
73 ms
global.css
149 ms
global-header.css
296 ms
global-footer.css
443 ms
btn.css
445 ms
sub.css
446 ms
index.css
474 ms
searchbox.css
475 ms
calendar.css
475 ms
member.css
588 ms
font-awesome.min.css
589 ms
relux-sns-all.js
595 ms
relux-top-all.js
965 ms
ld.js
68 ms
jquery.autocomplete.loco.js
631 ms
moment.js
798 ms
hogan.js
733 ms
ReluxUtil.js
733 ms
ReluxCalender.js
735 ms
index.js
787 ms
s_retargeting.js
1138 ms
conversion.js
55 ms
oct.js
44 ms
facebook_like.js
876 ms
sdk.js
476 ms
fbds.js
152 ms
RP21006_1033.jpg
1140 ms
RP21890_1032.jpg
627 ms
RP24942_1003.jpg
952 ms
RP22637_1031.jpg
809 ms
RP27085_1005.jpg
757 ms
RP23423_1006.jpg
790 ms
logo-white.png
731 ms
icon-lang.png
161 ms
icon-merit-01.png
160 ms
icon-merit-02.png
158 ms
icon-merit-03.png
161 ms
banner-service-01.jpg
959 ms
banner-service-02.jpg
1181 ms
banner-service-03.jpg
888 ms
banner-service-04.jpg
1114 ms
btn-app.png
320 ms
btn-google.png
486 ms
icon_inbound_close.gif
644 ms
logo_footer.png
804 ms
icon-footer-facebook.png
876 ms
icon-footer-twitter.png
959 ms
icon-footer-google.png
1023 ms
icon-footer-instagram.png
1033 ms
close_mark.png
1113 ms
concept_popMsg.png
1743 ms
event
183 ms
gtm.js
157 ms
dc.js
183 ms
tracer.js
1158 ms
header_bg.png
1167 ms
header_bg_white.png
1256 ms
facepile.php
155 ms
mainvidulal-03.jpg
2018 ms
index-dot.png
1276 ms
popup_bg_b.png
1285 ms
conceptpop_bg.png
1285 ms
fontawesome-webfont.woff
1509 ms
113 ms
adsct
150 ms
adsct
167 ms
70 ms
xd_arbiter.php
451 ms
page.php
125 ms
14 ms
event
905 ms
53 ms
__utm.gif
28 ms
xPv7gOXb_eI.css
298 ms
gPLjjXw4kx2.css
368 ms
_rx8naC75Dy.js
502 ms
t-KLv3gqZy0.js
497 ms
uLtKx7ldlvR.js
633 ms
12743921_788395604599151_306468018272992085_n.jpg
417 ms
12715346_788393767932668_1728767664984580101_n.jpg
482 ms
10424249_516544795151178_6064333049867036373_n.jpg
553 ms
12241285_789332741193447_2579717266287855014_n.jpg
622 ms
12274425_594780510660239_8027528164394336699_n.jpg
679 ms
534513_381804435227669_1243953845_n.jpg
619 ms
10494837_477700539041447_1287650983275319880_n.jpg
643 ms
10408606_731792930267404_4402174665231693092_n.jpg
620 ms
12009723_10206513518230145_4758391535362940480_n.jpg
736 ms
486277_117523921745363_1651985111_n.jpg
693 ms
10460118_602780096501119_1597067102804580650_n.jpg
693 ms
12119060_427655604110742_6332418667600857393_n.jpg
693 ms
11149551_832266333518699_7218771625230718099_n.jpg
710 ms
12308553_802337659875627_1799215862690454532_n.jpg
744 ms
ZS8q378OQsF.png
71 ms
wL6VQj7Ab77.png
70 ms
CSXXCvknpgK.png
71 ms
criteohandler
57 ms
R9a_DtVRZgv.js
69 ms
cUDgRFxaoIk.js
70 ms
0JBr1QHp8Gi.js
71 ms
kDOzhTr2W91.js
71 ms
dis.aspx
713 ms
3 ms
rlx.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
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
rlx.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
rlx.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 Rlx.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 Rlx.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.
rlx.jp
Open Graph data is detected on the main page of Rlx. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: