Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

royalcaribbean.no

Cruise – Fantastiske cruise og cruisetilbud | Royal Caribbean Norge

Page Load Speed

2.1 sec in total

First Response

140 ms

Resources Loaded

1.8 sec

Page Rendered

215 ms

royalcaribbean.no screenshot

About Website

Welcome to royalcaribbean.no homepage info - get ready to check Royal Caribbean best content for Norway right away, or after learning these important things about royalcaribbean.no

Cruise til uforglemmelige destinasjoner med Royal Caribbean. Sikre gode priser til vakre Karibien og Middelhavet. Utforsk spennende cruisedestinasjoner som Mexico, Stillehavsområdet eller cruise fra k...

Visit royalcaribbean.no

Key Findings

We analyzed Royalcaribbean.no page load time and found that the first response time was 140 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

royalcaribbean.no performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value23.8 s

0/100

25%

SI (Speed Index)

Value18.7 s

0/100

10%

TBT (Total Blocking Time)

Value16,990 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.083

93/100

15%

TTI (Time to Interactive)

Value36.8 s

0/100

10%

Network Requests Diagram

no

140 ms

icon

51 ms

clientlib-all.css

81 ms

clientlib-structure-base.css

59 ms

jquery.js

316 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Royalcaribbean.no, 28% (27 requests) were made to Assets.dm.rccl.com and 6% (6 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Assets.dm.rccl.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 450.4 kB (39%)

Content Size

1.2 MB

After Optimization

703.5 kB

In fact, the total size of Royalcaribbean.no main page is 1.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. 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 531.5 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 302.5 kB

  • Original 342.9 kB
  • After minification 295.1 kB
  • After compression 40.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 47.8 kB, which is 14% 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 302.5 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 270.9 kB
  • After minification 270.9 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 Caribbean images are well optimized though.

JavaScript Optimization

-28%

Potential reduce by 146.3 kB

  • Original 531.5 kB
  • After minification 530.7 kB
  • After compression 385.2 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 146.3 kB or 28% of the original size.

CSS Optimization

-19%

Potential reduce by 1.6 kB

  • Original 8.7 kB
  • After minification 8.2 kB
  • After compression 7.0 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. Royalcaribbean.no needs all CSS files to be minified and compressed as it can save up to 1.6 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (56%)

Requests Now

94

After Optimization

41

The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Royal Caribbean. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

royalcaribbean.no accessibility score

85

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

royalcaribbean.no 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

royalcaribbean.no SEO score

86

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    NO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Royalcaribbean.no can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Norwegian language. Our system also found out that Royalcaribbean.no 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 data is detected on the main page of Royal Caribbean. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: