rci.com website review

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.

About 795 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

57 files are served with short cache lifetimes, so returning visitors download them again (584 KiB).

8 third-party services load with your homepage (Dynatrace, Google Tag Manager and Optanon and others), adding 1.4 MB and 922 ms of main-thread time.

Your mobile performance score is 52 (desktop: 79). Pages that score under 90 lose visitors before the first paint.

4 images could be 827 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

105 KiB could be saved by minifying JavaScript.

About 97 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

Dynatrace costs a phone 349 ms of main-thread work and 141 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Google Tag Manager costs a phone 303 ms of main-thread work and 217 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

A phone's processor spends 3.1 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Vimeo costs a phone 29 ms of main-thread work and 527 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

15 long tasks block the main thread while loading, the longest for 159 ms. During a long task the page ignores taps.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

Polyfills for old browsers add 31 KiB JavaScript that modern phones do not need.

Desktop scores 79 but mobile only 52. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

The page becomes fully interactive after 27.2 s. Good is under 3.8 s.

Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A hand resting on a pink suitcase handle with a passport an…”.

The first text or image appears after 4.8 s on a phone. Good is under 1.8 s.

Visually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.

For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.

Real visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.

Scripts block taps and scrolling for 398 ms in total while the page loads. Good is under 200 ms.

3 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 194 ms to 212 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.7 MB in 167 requests on a phone: images 3.5 MB (91), scripts 1.7 MB (32) and fonts 219 KiB (4). Under 2 MB keeps phones on slow connections fast.

11 images (3.3 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

3 images further down the page (504 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 1.60 g of CO₂e: 192.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 frame has no title, so screen-reader users cannot tell what it contains.

1 link inside paragraphs relies on colour alone to stand out.

7 form fields have no label, so screen readers announce an empty box and autofill guesses.

Your title is 76 characters, so Google will cut it off around 60: “RCI - Reshaping The World of Travel With An All-New Travel Network | RCI.com”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 3 <h1> headlines (“MORE WAYS TO VACATION THAN EVER BEFORE”, “Best Cruise Lines For First-Time Cruisers” and “RCI Cruise Best Value Guarantee”). One clear main headline is easier for people and search engines.

Your meta description is 181 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

3 links have no real href, so search engines can't follow them.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 134 pages on rci.com and 33 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.rci.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

We fetched 15 pages linked from your homepage (of 68 found) and read each the way a search engine does.

3 of 7 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'frames')”.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

The homepage carries about 363 words of visible text.

Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 35 cookies, 2 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.