Website review, no card needed

americandream.com logo

americandream.com website review

Visit site (opens in a new tab)Reviewed 18 November 202651 issues · 86 checks

This review found 51 issues worth fixing on americandream.com, 24 of them high impact, across 86 checks. The most urgent: google Tag Manager adds 6.6 s. 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
3.7 s3.1 sMay 30Nov 143.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.2 s
Jun 6, 20263.3 s
Jun 13, 20263.4 s
Jun 20, 20263.5 s
Jun 27, 20263.5 s
Jul 4, 20263.5 s
Jul 11, 20263.5 s
Jul 18, 20263.5 s
Jul 25, 20263.4 s
Aug 1, 20263.4 s
Aug 8, 20263.3 s
Aug 15, 20263.3 s
Aug 22, 20263.2 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Sep 12, 20263.2 s
Sep 19, 20263.3 s
Sep 26, 20263.4 s
Oct 3, 20263.6 s
Oct 10, 20263.7 s
Oct 17, 20263.6 s
Oct 24, 20263.6 s
Oct 31, 20263.5 s
Nov 7, 20263.5 s
Nov 14, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
270 ms215 msMay 30Nov 14253 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026221 ms
Jun 6, 2026227 ms
Jun 13, 2026228 ms
Jun 20, 2026229 ms
Jun 27, 2026229 ms
Jul 4, 2026233 ms
Jul 11, 2026241 ms
Jul 18, 2026245 ms
Jul 25, 2026252 ms
Aug 1, 2026254 ms
Aug 8, 2026254 ms
Aug 15, 2026257 ms
Aug 22, 2026254 ms
Aug 29, 2026251 ms
Sep 5, 2026247 ms
Sep 12, 2026246 ms
Sep 19, 2026252 ms
Sep 26, 2026257 ms
Oct 3, 2026262 ms
Oct 10, 2026264 ms
Oct 17, 2026263 ms
Oct 24, 2026264 ms
Oct 31, 2026262 ms
Nov 7, 2026255 ms
Nov 14, 2026253 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 americandream.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. americandream.com at 4.2 s4.2 s
  2. americandream.com at 8.3 s8.3 s
  3. americandream.com at 12.5 s12.5 s
  4. americandream.com at 16.6 s16.6 s
  5. americandream.com at 20.8 s20.8 s
  6. americandream.com at 25.0 s25.0 s
  7. americandream.com at 29.1 s29.1 s
  8. americandream.com at 33.3 s33.3 s

Speed

14 to fix5
  • Google Tag Manager adds 6.6 s

    6.6 s

    Google Tag Manager costs a phone 6.6 s of main-thread work and 1.7 MB 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.

  • Render-blocking requests

    5.4 s

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

  • Reduce unused JavaScript

    1.8 s · 1.8 MB

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

  • Main-thread work: 33.9 s

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

  • Stripe adds 1.1 s

    1.1 s

    Stripe costs a phone 1.1 s of main-thread work and 305 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.

  • Facebook adds 1.0 s

    1.0 s

    Facebook costs a phone 1.0 s of main-thread work and 333 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: 5

    5/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Stripe and Facebook and others), adding 2.9 MB and 10.6 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Use efficient cache lifetimes

    885 KiB

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

  • Reduce unused CSS

    610 ms · 162 KiB

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

  • Snapchat adds 456 ms

    456 ms

    Snapchat costs a phone 456 ms of main-thread work and 53 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.

  • Other Google APIs/SDKs adds 430 ms

    430 ms

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

  • Improve image delivery

    274 KiB

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

  • Font display

    250 ms

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

  • Legacy JavaScript

    64 KiB

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

  • Minify JavaScript

    10 KiB

    10 KiB could be saved by minifying JavaScript.

  • Document request latency

    7 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 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: 1 ms

    1 ms

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

Core Web Vitals

12 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 CLS: 0.45

    0.45

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

  • First Contentful Paint: 8.4 s

    8.4 s

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

  • Speed Index: 44.2 s

    44.2 s

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

  • Total Blocking Time: 13.0 s

    13.0 s

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

  • Time to Interactive: 54.4 s

    54.4 s

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

  • Largest Contentful Paint: 8.4 s

    8.4 s

    Your largest element takes 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies (and other similar technologies) to collect …”. Most of its time is element render delay (12.4 s).

  • Cumulative Layout Shift: 0.488

    0.488

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

  • Real-user LCP: 3.7 s

    3.7 s

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

  • Real-user INP: 282 ms

    282 ms

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • 13 images without width and height

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

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

    +13%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

1 checks passed
  • Real-user TTFB: 565 ms

    565 ms

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

Images and page weight

1 to fix70
  • Page weight: 12.8 MB in 436 requests

    12.8 MB

    Your homepage downloads 12.8 MB in 436 requests on a phone: scripts 4.9 MB (86), media 3.2 MB (3) and images 2.6 MB (133). Under 2 MB keeps phones on slow connections fast.

  • About 3.6 g of CO₂ per visit

    3.63 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.63 g of CO₂e: 435.8 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

8 to fixGoogle 7987
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (40 elements)

    All page content should be contained by landmarks: 40 elements on the page fail this check, rated moderate by axe-core.

  • Zoom is disabled

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

  • 6 links without text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

1 checks passed
  • 34 automated accessibility rules passed

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

SEO

7 to fixGoogle 9264
  • No H1 headline

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

  • Title is long (75 characters)

    Your title is 75 characters, so Google will cut it off around 60: “Best Indoor Amusement Park NY Metro - Water Park & Luxury Shopping Near NYC”.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (169 characters)

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

  • No XML sitemap

    No XML sitemap at https://www.americandream.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at americandream.com/robots.txt, the first file search crawlers ask for.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No X (Twitter) card tag

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

2 checks passed
  • Structured data in place

    Structured data found: EntertainmentBusiness.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

1 to fix75
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 203 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • No llms.txt

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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, sameAs (social profiles) and contact details; logo and description would complete it.

Best practices

3 to fixGoogle 7376
  • 5 broken images

    5 images failed to load on a phone, for example https://cdnjs.cloudflare.com/ajax/libs/flag-icon-css/4.1.4/flags/4x3/us.svg.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    9 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • 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.

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

  • Only about 203 words

    The homepage has only about 203 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

  • No form on the homepage

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

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book Tickets”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 14 trackers load before any consent

    14

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

  • 30 cookies set on arrival

    30

    Opening the homepage sets 30 cookies, 2 of them by other companies (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.

  • 68 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager

Company

Founded
2004

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 51 issues on americandream.com, including 26 speed issues, 7 SEO issues 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