princess.com website review

61 files are served with short cache lifetimes, so returning visitors download them again (5.2 MB).

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

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

About 279 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.

Your mobile performance score is 38 (desktop: 49). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

The page has 6,533 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

7 third-party services load with your homepage (mPulse, Adobe Tag Manager and osano.com and others), adding 1.1 MB and 650 ms of main-thread time.

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

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

coveo.com costs a phone 21 ms of main-thread work and 449 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.

Polyfills for old browsers add 38 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

3 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

Your largest element takes 36.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

Real visitors wait 392 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

The layout shifts by 0.124 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 36.6 MB in 199 requests on a phone: media 25.3 MB (2), images 8.1 MB (54) and scripts 1.9 MB (92). Under 2 MB keeps phones on slow connections fast.

10 images are downloaded at several times the size a phone draws them, for example naples-view2-princess-cruises-1:2x3-Portrait at 1,220 px wide, shown at 390 px. Resized copies would save about 1.1 MB.

9 images further down the page (2.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

8 images (1.6 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.

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

69 images have no alt text, which hurts accessibility and image search.

58 visible links have no text or label, so screen readers cannot say where they go.

Your title is 66 characters, so Google will cut it off around 60: “Princess Cruises: Award-Winning Cruises & Deals - Princess Cruises”.

28 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 396 pages on princess.com and 45 external pages.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.princess.com/cruise-destinations/european-cruises/mediterranean-and-greek-isles, whose canonical is https://www.princess.com/cruise-destinations/mediterranean-cruises. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 1,268 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Opening the homepage sets 18 cookies (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.