Website review, no card needed

exploriaresorts.com logo

exploriaresorts.com website review

Visit site (opens in a new tab)Reviewed 28 October 202643 issues · 86 checks

This review found 43 issues worth fixing on exploriaresorts.com, 21 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.5 s4.0 sMay 9Oct 244.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.2 s
May 16, 20264.2 s
May 23, 20264.2 s
May 30, 20264.3 s
Jun 6, 20264.4 s
Jun 13, 20264.4 s
Jun 20, 20264.5 s
Jun 27, 20264.4 s
Jul 4, 20264.3 s
Jul 11, 20264.2 s
Jul 18, 20264.2 s
Jul 25, 20264.2 s
Aug 1, 20264.3 s
Aug 8, 20264.2 s
Aug 15, 20264.2 s
Aug 22, 20264.1 s
Aug 29, 20264.1 s
Sep 5, 20264.2 s
Sep 12, 20264.2 s
Sep 19, 20264.2 s
Sep 26, 20264.3 s
Oct 3, 20264.2 s
Oct 10, 20264.2 s
Oct 17, 20264.3 s
Oct 24, 20264.3 s
Real-visitor tap response (INP)75th percentile, phones
275 ms241 msMay 9Oct 24271 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026270 ms
May 16, 2026263 ms
May 23, 2026268 ms
May 30, 2026264 ms
Jun 6, 2026262 ms
Jun 13, 2026264 ms
Jun 20, 2026257 ms
Jun 27, 2026259 ms
Jul 4, 2026254 ms
Jul 11, 2026254 ms
Jul 18, 2026255 ms
Jul 25, 2026254 ms
Aug 1, 2026253 ms
Aug 8, 2026245 ms
Aug 15, 2026252 ms
Aug 22, 2026246 ms
Aug 29, 2026252 ms
Sep 5, 2026262 ms
Sep 12, 2026253 ms
Sep 19, 2026258 ms
Sep 26, 2026261 ms
Oct 3, 2026258 ms
Oct 10, 2026255 ms
Oct 17, 2026263 ms
Oct 24, 2026271 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

Full-page screenshot of exploriaresorts.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. exploriaresorts.com at 0.5 s0.5 s
  2. exploriaresorts.com at 1.0 s1.0 s
  3. exploriaresorts.com at 1.5 s1.5 s
  4. exploriaresorts.com at 2.0 s2.0 s
  5. exploriaresorts.com at 2.4 s2.4 s
  6. exploriaresorts.com at 2.9 s2.9 s
  7. exploriaresorts.com at 3.4 s3.4 s
  8. exploriaresorts.com at 3.9 s3.9 s

Speed

12 to fix18
  • Use efficient cache lifetimes

    2.4 s · 593 KiB

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

  • Improve image delivery

    2.2 s · 475 KiB

    6 images could be 475 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.2 s faster on a phone.

  • Reduce unused JavaScript

    2.1 s · 503 KiB

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

  • Render-blocking requests

    1.7 s

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

  • Mobile performance score: 18

    18/100

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

  • Main-thread work: 4.3 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Other Google APIs/SDKs, Google Tag Manager and purechatcdn.com and others), adding 2.5 MB and 1.7 s of main-thread time.

  • Reduce unused CSS

    750 ms · 171 KiB

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

  • Other Google APIs/SDKs adds 600 ms

    600 ms

    Other Google APIs/SDKs costs a phone 600 ms of main-thread work and 1.3 MB 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 adds 351 ms

    351 ms

    Google Tag Manager costs a phone 351 ms of main-thread work and 288 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.

  • 8 long tasks on the main thread

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

  • purechatcdn.com adds 273 ms

    273 ms

    purechatcdn.com costs a phone 273 ms of main-thread work and 326 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

    150 ms · 30 KiB

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

  • Font display

    50 ms

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

  • 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.

  • Duplicated JavaScript

    4 KiB

    4 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 5 ms

    5 ms

    Your server sent the HTML in 5 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix0
  • 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 LCP: 4.3 s

    4.3 s

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

  • Real-user CLS: 0.69

    0.69

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

  • Largest Contentful Paint: 17.5 s

    17.5 s

    Your largest element takes 17.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Welcome to Exploria Resorts - where bringing families toget…”.

  • Time to Interactive: 21.4 s

    21.4 s

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

  • Cumulative Layout Shift: 0.579

    0.579

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

  • First Contentful Paint: 4.7 s

    4.7 s

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

  • Speed Index: 8.6 s

    8.6 s

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

  • Total Blocking Time: 759 ms

    759 ms

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

  • Real-user INP: 316 ms

    316 ms

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

  • 5 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

2 checks passed
  • Real-user FCP: 1.3 s

    1.3 s

    Real visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 603 ms

    603 ms

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

Images and page weight

4 to fix58
  • Page weight: 2.8 MB in 136 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 136 requests on a phone: scripts 1.6 MB (35), images 776 KiB (28) and fonts 189 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (820 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.

  • 1 image far larger than shown

    238 KiB

    1 image is downloaded at several times the size a phone draws it, for example b2cSk_cv8RHNejnuAj7SLy7XJ9G4p3NW3m_umLJYbVvC8lI24jRdHpWj0LVZ at 2,475 px wide, shown at 153 px. Resized copies would save about 238 KiB.

  • 7 images below the first screen load straight away

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

  • About 0.8 g of CO₂ per visit

    0.81 g

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

Accessibility

6 to fixGoogle 8591
  • 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.

  • Interactive controls must not be nested (16 elements)

    Interactive controls must not be nested: 16 elements on the page fail this check, rated serious by axe-core.

  • ARIA commands must have an accessible name (8 elements)

    ARIA commands must have an accessible name: 8 elements on the page fail this check, rated serious by axe-core.

  • 4 text elements with low contrast

    4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 5 links without text

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

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 5 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9289
  • No structured data

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

  • Meta description is long (290 characters)

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

  • 1 link with vague text

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 53 internal links, 5 external

    The homepage links to 53 pages on exploriaresorts.com and 5 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Exploria Resorts”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Exploria Resorts | Fun Family Vacation Experiences”.

  • Canonical URL set

    The canonical URL is https://www.exploriaresorts.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.exploriaresorts.com/sitemap.xml.

AI search readiness

2 to fix75
  • No Organization structured data

    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.

  • Some text only appears after JavaScript runs

    58%

    The HTML your server sends has 231 of the 399 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

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

1 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.

Other pages

1 to fix95
  • 10 pages without an H1

    https://www.exploriaresorts.com/florida, https://www.exploriaresorts.com/clermont-florida/summer-bay-orlando, https://www.exploriaresorts.com/clermont-florida/601-the-reserve, https://www.exploriaresorts.com/daytona-beach-florida/grand-seas, https://www.exploriaresorts.com/new-smyrna-beach-florida/new-smyrna-waves and https://www.exploriaresorts.com/pennsylvania and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 pages with very little text

    https://www.exploriaresorts.com/destinations, https://www.exploriaresorts.com/florida, https://www.exploriaresorts.com/clermont-florida/summer-bay-orlando, https://www.exploriaresorts.com/clermont-florida/601-the-reserve, https://www.exploriaresorts.com/daytona-beach-florida/grand-seas and https://www.exploriaresorts.com/new-smyrna-beach-florida/new-smyrna-waves and 7 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 25 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

2 to fixGoogle 10078
  • 8 broken images

    8 images failed to load on a phone, for example https://b.tile.openstreetmap.org/5/8/13.png.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

2 checks passed
  • Tap targets are thumb-sized

    54 of 56 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • No social proof

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No form on the homepage

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

  • No risk reducer

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

  • About 399 words of copy

    The homepage carries about 399 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Call Us” and “BOOK NOW”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “601 The Reserve | Orlando” and “Call”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Microsoft Clarity and HubSpot.

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 2 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.

  • 17 cookies set on arrival

    17

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

  • 57 other companies contacted

    Loading the homepage contacts 57 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 exploriaresorts.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Angular
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Google Cloud

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on exploriaresorts.com, including 23 speed issues, 3 SEO issues and 2 conversion gaps. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25