mickeyworldtravel.com website review

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

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

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

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

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

16 images could be 267 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

Other Google APIs/SDKs costs a phone 0 ms of main-thread work and 587 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.

6 third-party services load with your homepage (Google Tag Manager, elementor.com and trustindex.io and others), adding 921 KiB and 185 ms of main-thread time.

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

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

Desktop scores 87 but mobile only 56. 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.

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

4 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

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

Your largest element takes 15.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Mickey World Travel Making Memories That Last A Lifetime RE…”.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.1 MB in 194 requests on a phone: images 1.6 MB (71), scripts 672 KiB (42) and fonts 490 KiB (12). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example AABkmLfhYkrU07IUyyFQb2dv_YVOdzXTibo4VGW2P3XDwU3bYTdxgHRMGNzy at 512 px wide, shown at 80 px. Resized copies would save about 260 KiB.

4 images (363 KiB) 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.

4 images further down the page (131 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 0.89 g of CO₂e: 107.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

Your title is only 23 characters: “disney vacation planner”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Mickey World Travel” and “For the opportunity to plan your trip!”). One clear main headline is easier for people and search engines.

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

Structured data found (ImageObject, Organization, Product and TravelAgency) but with 1 problem, for example “Product: no offers (price) block”.

The homepage links to 42 pages on mickeyworldtravel.com and 46 external pages.

https://mickeyworldtravel.com/meet-our-team has no <h1> headline, so visitors and search engines get no clear main topic.

https://mickeyworldtravel.com/disney-cruise-line-quote-request took over 3 s to send its HTML from our server.

We fetched 10 pages linked from your homepage and read each the way a search engine does.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 2,708 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 2 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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