Website review, no card needed

adventurelanding.com logo

adventurelanding.com website review

Visit site (opens in a new tab)Reviewed 20 October 202633 issues · 79 checks

This review found 33 issues worth fixing on adventurelanding.com, 16 of them high impact, across 79 checks. The most urgent: render-blocking requests. 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
2.2 s1.7 sMay 2Sep 51.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.9 s
May 9, 20261.9 s
May 16, 20261.9 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.9 s
Jun 13, 20262.0 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20262.0 s
Jul 11, 20261.8 s
Jul 18, 20261.9 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.2 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.8 s
Sep 5, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
123 ms103 msMay 2Aug 1121 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026105 ms
May 16, 2026107 ms
May 23, 2026111 ms
May 30, 2026105 ms
Jun 13, 2026109 ms
Jun 27, 2026113 ms
Jul 4, 2026115 ms
Jul 18, 2026110 ms
Jul 25, 2026118 ms
Aug 1, 2026121 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 adventurelanding.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. adventurelanding.com at 0.8 s0.8 s
  2. adventurelanding.com at 1.6 s1.6 s
  3. adventurelanding.com at 2.4 s2.4 s
  4. adventurelanding.com at 3.1 s3.1 s
  5. adventurelanding.com at 3.9 s3.9 s
  6. adventurelanding.com at 4.7 s4.7 s
  7. adventurelanding.com at 5.5 s5.5 s
  8. adventurelanding.com at 6.3 s6.3 s

Speed

11 to fix35
  • Render-blocking requests

    2.0 s

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

  • Google Tag Manager adds 1.1 s

    1.1 s

    Google Tag Manager costs a phone 1.1 s of main-thread work and 819 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 7.2 s

    A phone's processor spends 7.2 s on main-thread work while loading, 3.1 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 (Google Tag Manager, Facebook and Google/Doubleclick Ads and others), adding 2.4 MB and 1.8 s of main-thread time.

  • Use efficient cache lifetimes

    350 ms · 1.3 MB

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

  • Reduce unused JavaScript

    900 ms · 782 KiB

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

  • 20 long tasks on the main thread

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

  • Facebook adds 290 ms

    290 ms

    Facebook costs a phone 290 ms of main-thread work and 152 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.

  • Reduce unused CSS

    260 KiB

    About 260 KiB of CSS is downloaded but never applied on this page.

  • Amazon Web Services adds 9 ms

    9 ms

    Amazon Web Services costs a phone 9 ms of main-thread work and 1.2 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.

  • Font display

    250 ms

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

  • Improve image delivery

    100 ms · 28 KiB

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

  • Legacy JavaScript

    58 KiB

    Polyfills for old browsers add 58 KiB JavaScript that modern phones do not need.

  • Phones get a much slower page than desktops

    Desktop scores 78 but mobile only 35. 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: 106 ms

    106 ms

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

Core Web Vitals

5 to fix42
  • Time to Interactive: 20.3 s

    20.3 s

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

  • Largest Contentful Paint: 6.5 s

    6.5 s

    Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Adventure Landing Family Entertainment Centers & Water Park…”.

  • Speed Index: 9.1 s

    9.1 s

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

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • First Contentful Paint: 4.3 s

    4.3 s

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

  • Tap response (INP) got 13% slower for real visitors

    +13%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

  • Not enough real-visitor data yet

    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.

1 checks passed
  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 3.4 MB in 232 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 232 requests on a phone: scripts 1.8 MB (104), images 1.1 MB (16) and fonts 232 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    0.97 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 8792
  • 14 text elements with low contrast

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

  • Links must have discernible text (3 elements)

    Links must have discernible text: 3 elements on the page fail this check, rated serious by axe-core.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10090
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 10 internal links, 10 external

    The homepage links to 10 pages on adventurelanding.com and 10 external pages.

7 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “With several locations across the US, Adventure Landing Family Entertainment Centers is THE place for fun family outing…”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “Adventure Landing Family Fun Entertainment Centers & Water Parks”.

  • Canonical URL set

    The canonical URL is https://www.adventurelanding.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage and WebSite.

  • 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.adventurelanding.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://www.adventurelanding.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 (272 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix78
  • 1 page points its canonical at the homepage

    https://www.adventurelanding.com/fun-happenings declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.adventurelanding.com/fun-happenings all use the title “Adventure Landing Family Fun Entertainment Centers & Water Parks”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without an H1

    https://www.adventurelanding.com/locations, https://www.adventurelanding.com/about-adventure-landing, https://www.adventurelanding.com/about-adventure-landing/sister-parks, https://www.adventurelanding.com/in-the-news, https://www.adventurelanding.com/adventure-landing-jacksonville-beach-announces-closure-after-30-years-of-family-fun and https://www.adventurelanding.com/adventure-landing-jacksonville-beach-will-remain-open-for-business-through-september-2024-delivering-on-commitment-to-family-entertainment-in-the-jacksonville-community and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 internal pages checked

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

4 checks passed
  • Linked pages load

    All 7 pages we checked loaded without an error.

  • Every page has a meta description

    All 7 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 7 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 6 small tap targets

    6 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'addAction')”.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Local business without LocalBusiness data

    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.

  • Thin social proof

    Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

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

  • No map or directions link

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

  • 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 252 words of copy

    The homepage carries about 252 words of visible text.

4 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 14 cookies set on arrival

    14

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

  • No consent tool detected

    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.

  • 14 other companies contacted

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

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on adventurelanding.com, including 16 speed issues, 1 SEO issue and 4 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