Website review, no card needed

vizcaya.org logo

vizcaya.org website review

Visit site (opens in a new tab)Reviewed 19 October 202639 issues · 82 checks

This review found 39 issues worth fixing on vizcaya.org, 10 of them high impact, across 82 checks. The most urgent: page weight: 13.2 MB in 353 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
2.8 s2.2 sMay 2Oct 172.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.5 s
May 9, 20262.4 s
May 16, 20262.3 s
May 23, 20262.4 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.7 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20262.7 s
Aug 15, 20262.6 s
Aug 22, 20262.3 s
Aug 29, 20262.4 s
Sep 5, 20262.3 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Oct 17, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
180 ms94 msMay 2Oct 17170 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026112 ms
May 9, 2026106 ms
May 16, 2026104 ms
May 23, 2026112 ms
May 30, 2026121 ms
Jun 6, 2026136 ms
Jun 13, 2026148 ms
Jun 20, 2026154 ms
Jun 27, 2026161 ms
Jul 4, 2026170 ms
Jul 11, 2026170 ms
Jul 18, 2026170 ms
Jul 25, 2026164 ms
Aug 1, 2026161 ms
Aug 8, 2026155 ms
Aug 15, 2026155 ms
Aug 22, 2026155 ms
Aug 29, 2026156 ms
Sep 5, 2026160 ms
Sep 12, 2026160 ms
Sep 19, 2026162 ms
Sep 26, 2026163 ms
Oct 3, 2026166 ms
Oct 10, 2026166 ms
Oct 17, 2026170 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 vizcaya.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. vizcaya.org at 0.9 s0.9 s
  2. vizcaya.org at 1.8 s1.8 s
  3. vizcaya.org at 2.7 s2.7 s
  4. vizcaya.org at 3.7 s3.7 s
  5. vizcaya.org at 4.6 s4.6 s
  6. vizcaya.org at 5.5 s5.5 s
  7. vizcaya.org at 6.4 s6.4 s
  8. vizcaya.org at 7.3 s7.3 s

Speed

5 to fix
  • Google Tag Manager adds 1.1 s

    1.1 s

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

  • Main-thread work: 7.5 s

    A phone's processor spends 7.5 s on main-thread work while loading, 2.6 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 Maps and others), adding 1.8 MB and 1.6 s of main-thread time.

  • Facebook adds 292 ms

    292 ms

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

  • 2,080 HTML elements

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

  • Font display

    50 ms

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

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

    26 ms

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

Core Web Vitals

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

  • First Contentful Paint: 12.9 s

    12.9 s

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

  • Speed Index: 20.1 s

    20.1 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user INP: 220 ms

    220 ms

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

  • Real-user CLS: 0.25

    0.25

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

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

    +54%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Cumulative Layout Shift: 0.16

    0.16

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

  • 4 images without width and height

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

  • 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 2.5 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

1 checks passed
  • Real-user TTFB: 483 ms

    483 ms

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

Images and page weight

2 to fix63
  • Page weight: 13.2 MB in 353 requests

    13.2 MB

    Your homepage downloads 13.2 MB in 353 requests on a phone: images 8.4 MB (27), scripts 3.7 MB (161) and stylesheets 521 KiB (143). Under 2 MB keeps phones on slow connections fast.

  • 4 images below the first screen load straight away

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

  • 5 images in older formats

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

  • About 3.7 g of CO₂ per visit

    3.74 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

9 to fixGoogle 8888
  • Elements must only use permitted ARIA attributes (3 elements)

    Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • ARIA role should be appropriate for the element (9 elements)

    ARIA role should be appropriate for the element: 9 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h5, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 51 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 9290
  • Meta description is long (161 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 10 links with vague text

    10 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 105 internal links, 49 external

    The homepage links to 105 pages on vizcaya.org and 49 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Vizcaya Museum and Gardens in Miami, Florida”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Vizcaya Museum and Gardens | Historic Miami Landmark & Gardens”.

  • Canonical URL set

    The canonical URL is https://vizcaya.org/.

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and WebPage.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://vizcaya.org/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

Other pages

4 to fix81
  • 8 pages share 3 titles

    /, https://vizcaya.org/es, https://vizcaya.org/fr and https://vizcaya.org/pt all use the title “Vizcaya Museum and Gardens | Historic Miami Landmark & Gardens”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://vizcaya.org/welcome, https://vizcaya.org/visit/hours-and-admission and https://vizcaya.org/corporate-executive-events have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages share a meta description

    https://vizcaya.org/es, https://vizcaya.org/fr and https://vizcaya.org/pt use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://vizcaya.org/join-and-support/become-a-member, whose canonical is https://vizcaya.org/become-a-member. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page slow to respond

    https://vizcaya.org/fr took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 73 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 24 small tap targets

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

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • No social proof

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

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

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

    The homepage carries about 854 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Subscribe” and “Learn More”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “Buy Tickets”, “Cafe and Shop” and “Contact Us”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Hotjar.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 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.

  • 17 other companies contacted

    Loading the homepage contacts 17 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 vizcaya.org, 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
React
Analytics
Google Analytics | Google Tag Manager | Hotjar

Company

Founded
1914

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on vizcaya.org, including 15 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