Website review, no card needed
celebritycruises.com website review
Visit site (opens in a new tab)Reviewed 12 October 202649 issues · 97 checks
This review found 49 issues worth fixing on celebritycruises.com, 22 of them high impact, across 97 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
65DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 3.8 s |
| Apr 25, 2026 | 3.8 s |
| May 2, 2026 | 3.8 s |
| May 9, 2026 | 3.8 s |
| May 16, 2026 | 3.9 s |
| May 23, 2026 | 3.9 s |
| May 30, 2026 | 3.9 s |
| Jun 6, 2026 | 3.9 s |
| Jun 13, 2026 | 3.8 s |
| Jun 20, 2026 | 3.7 s |
| Jun 27, 2026 | 3.7 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 3.6 s |
| Jul 25, 2026 | 3.6 s |
| Aug 1, 2026 | 3.6 s |
| Aug 8, 2026 | 3.6 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.6 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 272 ms |
| Apr 25, 2026 | 270 ms |
| May 2, 2026 | 264 ms |
| May 9, 2026 | 263 ms |
| May 16, 2026 | 262 ms |
| May 23, 2026 | 265 ms |
| May 30, 2026 | 271 ms |
| Jun 6, 2026 | 278 ms |
| Jun 13, 2026 | 286 ms |
| Jun 20, 2026 | 289 ms |
| Jun 27, 2026 | 295 ms |
| Jul 4, 2026 | 297 ms |
| Jul 11, 2026 | 296 ms |
| Jul 18, 2026 | 295 ms |
| Jul 25, 2026 | 296 ms |
| Aug 1, 2026 | 298 ms |
| Aug 8, 2026 | 303 ms |
| Aug 15, 2026 | 311 ms |
| Aug 22, 2026 | 314 ms |
| Aug 29, 2026 | 320 ms |
| Sep 5, 2026 | 323 ms |
| Sep 12, 2026 | 326 ms |
| Sep 19, 2026 | 327 ms |
| Sep 26, 2026 | 328 ms |
| Oct 3, 2026 | 330 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.1 s
2.2 s
3.3 s
4.5 s
5.6 s
6.7 s
7.8 s
8.9 s
Speed
Reduce unused JavaScript
5.5 s · 2.1 MBAbout 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.5 s faster on a phone.
Use efficient cache lifetimes
4.0 s · 1.9 MB125 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).
Render-blocking requests
3.0 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.
Main-thread work: 15.6 s
A phone's processor spends 15.6 s on main-thread work while loading, 9.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
1.1 s · 252 KiBAbout 252 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 19
19/100Your mobile performance score is 19 (desktop: 58). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,836 HTML elements
The page has 4,836 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (ContentSquare, Tealium and LivePerson and others), adding 1.6 MB and 1.9 s of main-thread time.
Improve image delivery
700 ms · 148 KiB7 images could be 148 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.
ContentSquare adds 639 ms
639 msContentSquare costs a phone 639 ms of main-thread work and 193 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 533 ms. During a long task the page ignores taps.
Tealium adds 479 ms
479 msTealium costs a phone 479 ms of main-thread work and 283 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.
Legacy JavaScript
350 ms · 74 KiBPolyfills for old browsers add 74 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
LivePerson adds 198 ms
198 msLivePerson costs a phone 198 ms of main-thread work and 606 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.
Minify JavaScript
150 ms · 7 KiB7 KiB could be saved by minifying JavaScript.
Phones get a much slower page than desktops
Desktop scores 58 but mobile only 19. A gap that wide usually means heavy scripts and images that hit phones hardest.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 40 ms
40 msYour server sent the HTML in 40 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Real-user CLS: 0.32
0.32For real visitors the layout shifts by 0.32 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 23.5 s
23.5 sYour largest element takes 23.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Xcel in Malta 2560x1440”.
Speed Index: 17.4 s
17.4 sVisually, the page fills in at 17.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 48.0 s
48.0 sThe page becomes fully interactive after 48.0 s. Good is under 3.8 s.
Total Blocking Time: 2.9 s
2.9 sScripts block taps and scrolling for 2.9 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 4.6 s
4.6 sThe first text or image appears after 4.6 s on a phone. Good is under 1.8 s.
Real-user INP: 353 ms
353 msReal visitors wait 353 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 272 ms to 330 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.184
0.184The layout shifts by 0.184 while loading, so content jumps under the reader's thumb. Good is under 0.1.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 776 ms
776 msReal visitors wait 776 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 3.8 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 12.5 MB in 446 requests
12.5 MBYour homepage downloads 12.5 MB in 446 requests on a phone: other files 5.7 MB (165), scripts 4.3 MB (142) and images 1.5 MB (91). Under 2 MB keeps phones on slow connections fast.
4 images far larger than shown
54 KiB4 images are downloaded at several times the size a phone draws them, for example homepage-hero-australia-deployment-2560x1440 at 1,280 px wide, shown at 390 px. Resized copies would save about 54 KiB.
4 images below the first screen load straight away
4 images further down the page (329 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.5 g of CO₂ per visit
3.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.54 g of CO₂e: 424.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
23 text elements with low contrast
23 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links must have discernible text (2 elements)
Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (59 elements)
All page content should be contained by landmarks: 59 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (4 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 4 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (19 elements)
ARIA role should be appropriate for the element: 19 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 11 failed. 7 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 8 problems
Structured data found (Organization, VideoObject and WebSite) but with 8 problems, for example “VideoObject: url is not an absolute URL ("https://assets.dm.rccl.com/is/content/RoyalCaribbeanCruis…”.
14 links with vague text
14 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
372 internal links, 16 external
The homepage links to 372 pages on celebritycruises.com and 16 external pages.
7 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Discover our cruises to the Caribbean, Mediterranean, Alaska & more. Voted best premium Cruise Line 14 years running. B…”.
One H1 headline
Your main headline reads: “MOST POPULAR CRUISES”.
Title: 62 characters
Your title is a healthy 62 characters: “Cruises: Award-Winning Premium Cruise Line | Celebrity Cruises”.
Canonical URL set
The canonical URL is https://www.celebritycruises.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.celebritycruises.com/sitemap/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.celebritycruises.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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (2,528 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without an H1
https://www.celebritycruises.com/cruises and https://www.celebritycruises.com/river have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://www.celebritycruises.com/destinations/european-cruises/croatia-cruises and https://www.celebritycruises.com/river took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 183 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://www.celebritycruises.com/.
16 small tap targets
16 of 50 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “ERROR NotSupportedError: Failed to execute 'define' on 'CustomElementRegistry': the name "cel-recommended-itineraries" …”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
About 1,568 words of copy
The homepage carries about 1,568 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book now” and “Shop Now”.
22 calls to action
The homepage has 22 calls to action, for example “signup”, “Learn More” and “Call”.
1 short form
A short form (3 fields at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 5 testimonial or review blocks and 3 customer or partner logos.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
13 trackers load before any consent
13Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 8 mores (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.
82 cookies set on arrival
82Opening the homepage sets 82 cookies, 1 of them by other companies (measured from a US location before any click).
69 other companies contacted
Loading the homepage contacts 69 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at celebritycruises.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on celebritycruises.com, including 25 speed issues, 2 SEO issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.