Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

riu.net

RIU.com | Offers | Book the best vacation resorts and hotels

Page Load Speed

3.4 sec in total

First Response

314 ms

Resources Loaded

2.8 sec

Page Rendered

258 ms

riu.net screenshot

About Website

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.net

Key Findings

We analyzed Riu.net page load time and found that the first response time was 314 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

riu.net performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

48/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value8,400 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.17

70/100

15%

TTI (Time to Interactive)

Value26.0 s

0/100

10%

Network Requests Diagram

www.riu.com

314 ms

home.jsp

333 ms

tealeaf_W3C.min.js

27 ms

reset.css

41 ms

responsive-RIU.css

46 ms

Our browser made a total of 161 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Riu.net, 12% (19 requests) were made to Ajax.googleapis.com and 6% (10 requests) were made to Us-sonar.sociomantic.com. The less responsive or slowest element that took the longest time to load (471 ms) relates to the external source Track.adform.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (62%)

Content Size

2.9 MB

After Optimization

1.1 MB

In fact, the total size of Riu.net main page is 2.9 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. 80% 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 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 155.0 kB

  • Original 185.6 kB
  • After minification 161.9 kB
  • After compression 30.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 23.7 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 155.0 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 18.9 kB

  • Original 603.1 kB
  • After minification 584.2 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. RIU images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 1.5 MB

  • Original 1.9 MB
  • After minification 1.5 MB
  • After compression 470.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 1.5 MB or 76% of the original size.

CSS Optimization

-85%

Potential reduce by 203.1 kB

  • Original 240.2 kB
  • After minification 188.0 kB
  • After compression 37.1 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. Riu.net needs all CSS files to be minified and compressed as it can save up to 203.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 125 (86%)

Requests Now

146

After Optimization

21

The browser has sent 146 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 57 to 1 for JavaScripts and from 33 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

riu.net accessibility score

58

Accessibility Issues

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

High

button, link, and menuitem elements do not have accessible names.

High

[aria-*] attributes do not have valid values

High

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

riu.net best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

riu.net SEO score

80

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: