Website review, no card needed

buschgardens.com logo

buschgardens.com website review

Visit site (opens in a new tab)Reviewed 12 October 202634 issues · 81 checks

This review found 34 issues worth fixing on buschgardens.com, 15 of them high impact, across 81 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
2.1 s1.5 sApr 18Oct 31.7 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.7 s
Apr 25, 20261.7 s
May 2, 20261.7 s
May 9, 20261.6 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.7 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
188 ms160 msApr 18Oct 3185 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026169 ms
Apr 25, 2026169 ms
May 2, 2026169 ms
May 9, 2026168 ms
May 16, 2026164 ms
May 23, 2026163 ms
May 30, 2026165 ms
Jun 6, 2026167 ms
Jun 13, 2026170 ms
Jun 20, 2026170 ms
Jun 27, 2026171 ms
Jul 4, 2026171 ms
Jul 11, 2026172 ms
Jul 18, 2026174 ms
Jul 25, 2026177 ms
Aug 1, 2026177 ms
Aug 8, 2026177 ms
Aug 15, 2026178 ms
Aug 22, 2026179 ms
Aug 29, 2026179 ms
Sep 5, 2026180 ms
Sep 12, 2026179 ms
Sep 19, 2026180 ms
Sep 26, 2026183 ms
Oct 3, 2026185 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 buschgardens.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. buschgardens.com at 0.5 s0.5 s
  2. buschgardens.com at 1.0 s1.0 s
  3. buschgardens.com at 1.5 s1.5 s
  4. buschgardens.com at 2.0 s2.0 s
  5. buschgardens.com at 2.5 s2.5 s
  6. buschgardens.com at 3.0 s3.0 s
  7. buschgardens.com at 3.6 s3.6 s
  8. buschgardens.com at 4.1 s4.1 s

Speed

11 to fix34
  • Use efficient cache lifetimes

    4.0 s · 2.2 MB

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

  • Google Tag Manager adds 2.3 s

    2.3 s

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

  • Reduce unused JavaScript

    1.3 s · 802 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 34

    34/100

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

  • Main-thread work: 6.2 s

    A phone's processor spends 6.2 s on main-thread work while loading, 4.3 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 Quantum Metric and others), adding 2.1 MB and 3.2 s of main-thread time.

  • Improve image delivery

    600 ms · 1.2 MB

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

  • Reduce unused CSS

    750 ms · 142 KiB

    About 142 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.

  • Facebook adds 300 ms

    300 ms

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

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    12 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 65 but mobile only 34. 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.

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 16.2 s

    16.2 s

    Your largest element takes 16.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 28.0 s

    28.0 s

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

  • Total Blocking Time: 1.9 s

    1.9 s

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

  • Speed Index: 8.4 s

    8.4 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Real-user TTFB: 840 ms

    840 ms

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

  • Tap response (INP) held steady for real visitors

    +9%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 169 ms to 185 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-03, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 129 ms

    129 ms

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

  • Real-user CLS: 0.00

    0.00

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

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 15.9 MB in 242 requests

    15.9 MB

    Your homepage downloads 15.9 MB in 242 requests on a phone: media 11.5 MB (1), scripts 2.5 MB (106) and images 1.6 MB (33). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (108 KiB) is 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.

  • About 4.5 g of CO₂ per visit

    4.50 g

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

2 checks passed
  • 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

3 to fixGoogle 9697
  • All page content should be contained by landmarks (1 element)

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 44 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

4 to fixGoogle 8589
  • No structured data

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

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

  • 18 internal links, 18 external

    The homepage links to 18 pages on buschgardens.com and 18 external pages.

6 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Experience our animal attractions and educational series with spectacular rides and events happening daily. Visit your …”.

  • One H1 headline

    Your main headline reads: “Busch Gardens Theme Parks: Thrill Rides & Animal Adventures in Tampa Bay and Williamsburg”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Explore Theme Parks, Animals & Attractions - Busch Gardens”.

  • Canonical URL set

    The canonical URL is https://buschgardens.com/.

  • 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://buschgardens.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://buschgardens.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 (212 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 9 internal pages checked

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

7 checks passed
  • Linked pages load

    All 9 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 9 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7376
  • 1 broken image

    1 image failed to load on a phone, for example https://www.facebook.com/tr/?id=581588089464037&ev=CookieSync&dl=https%3A%2F%2Fbuschgardens.com%2F&ud%5Bexternal_id%5D=0cc2c465a0f578ce346460afedc461fcbab3d472eef379a737c69f0e652790c5&dpo=LDU&dpoco=0&.

  • 1 third-party cookie

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

  • 6 JavaScript errors while loading

    6 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

    22 of 23 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 247 words

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

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

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Shop tickets & passes” and “Learn more”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, LinkedIn Insight, Meta Pixel and The Trade Desk (measured from a US location before any click). A consent tool (TrustArc) is installed; check it blocks these until visitors agree where the law requires it.

  • 20 cookies set on arrival

    20

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

  • 24 other companies contacted

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

1 checks passed
  • Consent tool: TrustArc

    A consent management tool (TrustArc) 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 buschgardens.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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on buschgardens.com, including 18 speed issues, 4 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