Website review, no card needed

enchantchristmas.com logo

enchantchristmas.com website review

Visit site (opens in a new tab)Reviewed 31 October 202641 issues · 84 checks

This review found 41 issues worth fixing on enchantchristmas.com, 15 of them high impact, across 84 checks. The most urgent: improve image delivery. 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.9 s1.3 sMay 9Oct 242.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.6 s
May 16, 20261.7 s
May 23, 20261.8 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20261.5 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20262.3 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.6 s
Aug 8, 20262.6 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.7 s
Sep 5, 20262.5 s
Sep 12, 20262.3 s
Sep 19, 20262.2 s
Sep 26, 20262.0 s
Oct 3, 20262.1 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
106 ms74 msMay 16Oct 2480 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026101 ms
May 23, 202697 ms
May 30, 2026101 ms
Jun 6, 202694 ms
Jun 13, 202696 ms
Jun 20, 2026100 ms
Jun 27, 2026102 ms
Jul 4, 2026102 ms
Jul 11, 202696 ms
Jul 18, 202692 ms
Jul 25, 202694 ms
Aug 1, 202694 ms
Aug 8, 202692 ms
Aug 15, 202693 ms
Aug 22, 202693 ms
Aug 29, 202688 ms
Sep 5, 202687 ms
Sep 12, 202683 ms
Sep 19, 202679 ms
Sep 26, 202678 ms
Oct 3, 202678 ms
Oct 10, 202678 ms
Oct 17, 202679 ms
Oct 24, 202680 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 enchantchristmas.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. enchantchristmas.com at 0.5 s0.5 s
  2. enchantchristmas.com at 1.0 s1.0 s
  3. enchantchristmas.com at 1.4 s1.4 s
  4. enchantchristmas.com at 1.9 s1.9 s
  5. enchantchristmas.com at 2.4 s2.4 s
  6. enchantchristmas.com at 2.9 s2.9 s
  7. enchantchristmas.com at 3.3 s3.3 s
  8. enchantchristmas.com at 3.8 s3.8 s

Speed

11 to fix31
  • Improve image delivery

    12.9 s · 7.3 MB

    20 images could be 7.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 12.9 s faster on a phone.

  • Render-blocking requests

    2.3 s

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

  • Mobile performance score: 31

    31/100

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

  • Use efficient cache lifetimes

    550 ms · 324 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Cookiebot, Facebook and Google Tag Manager and others), adding 921 KiB and 598 ms of main-thread time.

  • Reduce unused JavaScript

    300 ms · 358 KiB

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

  • Reduce unused CSS

    450 ms · 99 KiB

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

  • 8 long tasks on the main thread

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

  • Cookiebot adds 253 ms

    253 ms

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

  • Main-thread work: 2.5 s

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

  • 2,419 HTML elements

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

  • Minify JavaScript

    150 ms · 53 KiB

    53 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

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

  • Legacy JavaScript

    28 KiB

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

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

    6 ms

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

Core Web Vitals

10 to fix67
  • 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: 1.94

    1.94

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

  • Largest Contentful Paint: 47.8 s

    47.8 s

    Your largest element takes 47.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”.

  • Time to Interactive: 58.3 s

    58.3 s

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

  • Speed Index: 13.9 s

    13.9 s

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

  • Cumulative Layout Shift: 1

    1

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

  • Largest content (LCP) got 32% slower for real visitors

    +32%

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • 24 images without width and height

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

  • Total Blocking Time: 273 ms

    273 ms

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

5 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 76 ms

    76 ms

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 499 ms

    499 ms

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

  • Tap response (INP) got 20% faster for real visitors

    -20%

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

Images and page weight

4 to fix28
  • Page weight: 24.0 MB in 155 requests

    24.0 MB

    Your homepage downloads 24.0 MB in 155 requests on a phone: images 14.2 MB (38), media 7.5 MB (5) and scripts 1.7 MB (69). Under 2 MB keeps phones on slow connections fast.

  • 10 images over 500 KB

    10 images weigh 7.5 MB together. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    1.1 MB

    2 images are downloaded at several times the size a phone draws them, for example Village.png at 1,277 px wide, shown at 291 px. Resized copies would save about 1.1 MB.

  • 23 images below the first screen load straight away

    23 images further down the page (10.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.8 g of CO₂ per visit

    6.79 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

7 to fixGoogle 8893
  • All page content should be contained by landmarks (25 elements)

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

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

  • 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 links without text

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

2 checks passed
  • Every image has alt text

    All 68 images in the HTML carry an alt attribute.

  • 45 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: 45 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

1 to fixGoogle 10090
  • No H1 headline

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

  • 30 internal links, 27 external

    The homepage links to 30 pages on enchantchristmas.com and 27 external pages.

7 checks passed
  • Meta description: 114 characters

    Your meta description is 114 characters: “Welcome to Enchant Christmas! We are the creators of the World's Largest Christmas Light Maze. Come see the magic!”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Enchant Christmas is coming back in 2026.”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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.enchantchristmas.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.enchantchristmas.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 (740 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 3 pages without a meta description

    https://www.enchantchristmas.com/locations, https://www.enchantchristmas.com/news-and-blog and https://www.enchantchristmas.com/privacy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.enchantchristmas.com/locations, https://www.enchantchristmas.com/las-vegas, https://www.enchantchristmas.com/los-angeles, https://www.enchantchristmas.com/st-petersburg, https://www.enchantchristmas.com/washington-dc and https://www.enchantchristmas.com/get-involved and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.enchantchristmas.com/influencer-opportunities has 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 16 found) and read each the way a search engine does.

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

  • 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

1 to fixGoogle 9693
  • 1 JavaScript error while loading

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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 social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 589 words of visible text.

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Book a Party” and “Subscribe”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

Privacy and tracking

  • 1 cookie set on arrival

    1

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

  • 6 other companies contacted

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

2 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 enchantchristmas.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
Analytics
Segment
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on enchantchristmas.com, including 21 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