2.5 sec in total
326 ms
1.8 sec
335 ms
Click here to check amazing RIU content for Spain. Otherwise, check out these important facts you probably never knew about riu.net
Best hotel deals and offers in Aruba, Cancun, Miami, Jamaica, Mexico, Dominican Republic, Mauritius, Europe and much more
Visit riu.netWe analyzed Riu.net page load time and found that the first response time was 326 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
riu.net performance score
name
value
score
weighting
Value2.9 s
51/100
10%
Value31.7 s
0/100
25%
Value15.6 s
0/100
10%
Value11,120 ms
0/100
30%
Value0.179
67/100
15%
Value39.3 s
0/100
10%
326 ms
70 ms
179 ms
301 ms
50 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Riu.net, 79% (53 requests) were made to Riu.com and 3% (2 requests) were made to Cdn-eu.dynamicyield.com. The less responsive or slowest element that took the longest time to load (772 ms) relates to the external source Riu.com.
Page size can be reduced by 64.7 kB (9%)
753.5 kB
688.8 kB
In fact, the total size of Riu.net main page is 753.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 343.7 kB which makes up the majority of the site volume.
Potential reduce by 55.1 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 55.1 kB or 78% of the original size.
Potential reduce by 21 B
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. RIU images are well optimized though.
Potential reduce by 9.3 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. This website has mostly compressed JavaScripts.
Potential reduce by 286 B
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. Riu.net has all CSS files already compressed.
Number of requests can be reduced by 46 (77%)
60
14
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of RIU. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
riu.net
326 ms
www.riu.com
70 ms
www.riu.com
179 ms
home.jsp
301 ms
api_dynamic.js
50 ms
api_static.js
132 ms
platform.js
39 ms
client
156 ms
jwt-decode.js
130 ms
platform.js
46 ms
sdk.js
35 ms
bootstrap.min.css
156 ms
riucom_general.css
162 ms
riucom_home.css
148 ms
riucom_fonts.css
147 ms
animate.min.css
161 ms
jquery.min.js
192 ms
lodash.min.js
214 ms
bootstrap.min.js
224 ms
masonry.pkgd.min.js
203 ms
general.js
222 ms
home.js
229 ms
moment.js
230 ms
daterangepicker.js
242 ms
daterangepicker.css
235 ms
fuse.min.js
241 ms
riu-app-angular.css
247 ms
angular.min.js
247 ms
angular-local-storage.min.js
246 ms
angular-filter.min.js
246 ms
angular-sanitize.min.js
302 ms
angular-cookies.min.js
304 ms
angular-animate.min.js
303 ms
ng-map.min.js
304 ms
ui-bootstrap-tpls-2.1.2.min.js
302 ms
format.min.js
302 ms
riu.comun.min.js
305 ms
riuclass.comun.min.js
305 ms
riu.ngdialog.min.css
303 ms
ngDialog.min.js
345 ms
ng-table.min.js
346 ms
riu.home.min.js
347 ms
jwt-decode.js
120 ms
RIU.tealeaf-SaaS-prod.min.js
210 ms
cohorts_riu.js
201 ms
vcd15cbe7772f49c399c6a5babf22c1241717689176015
200 ms
bg-home-2020.jpg
643 ms
bg-riuclass-pattern-small.png
175 ms
mac.png
660 ms
bg-logo2018-riu.png
173 ms
bg-rsc.jpg
772 ms
riu-plaza.png
179 ms
riu-palace.png
205 ms
adults-only.png
185 ms
all-inclusive.png
213 ms
sdk.js
95 ms
btn-download-ios.png
231 ms
btn-download-playstore.png
223 ms
logo-aenor.png
217 ms
LivroEletronico.png
737 ms
logo-footer.png
741 ms
iconsRiu.svg
209 ms
iconsRiu.woff
756 ms
66 ms
logo2018-riucom-movil.png
471 ms
gtm.js
133 ms
gtm.js
190 ms
riu.net 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
button, link, and menuitem elements do not have accessible names.
[aria-*] attributes do not have valid values
ARIA IDs are not unique
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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.
riu.net 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
riu.net 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Riu.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Riu.net 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.
riu.net
Open Graph description is not detected on the main page of RIU. 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: