swandolphin.com website review

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

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

7 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

6 long tasks block the main thread while loading, the longest for 1.5 s. During a long task the page ignores taps.

Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.

10 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

3 third-party services load with your homepage (Cookiebot, weglot.com and Google Tag Manager), adding 647 KiB and 586 ms of main-thread time.

Cookiebot costs a phone 586 ms of main-thread work and 450 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.

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

About 85 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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.

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

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

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

Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

4 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-31, real Chrome visitors' tap response (inp) went from 116 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 37.1 MB in 50 requests on a phone: media 33.7 MB (12), images 2.5 MB (11) and scripts 721 KiB (16). Under 2 MB keeps phones on slow connections fast.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Your title is 68 characters, so Google will cut it off around 60: “Disney Hotels - Official site for Walt Disney World Swan and Dolphin”.

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

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

The homepage links to 194 pages on swandolphin.com and 25 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), 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.

There is no https://swandolphin.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.

/ and https://swandolphin.com/accommodations all use the title “Disney Hotels - Official site for Walt Disney World Swan and Dolphin”. Search engines can't tell which page to show for a search, so each competes with the others.

https://swandolphin.com/activities/events-all, https://swandolphin.com/our-resorts, https://swandolphin.com/our-resorts/swan, https://swandolphin.com/our-resorts/dolphin, https://swandolphin.com/our-resorts/swan-reserve and https://swandolphin.com/location and 4 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://swandolphin.com/our-resorts/gallery, whose canonical is https://swandolphin.com/gallery. 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 113 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

Opening the homepage sets 1 cookie (measured from a US location before any click).

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