Website review, no card needed

livingdesert.org logo

livingdesert.org website review

Visit site (opens in a new tab)Reviewed 24 October 202635 issues · 89 checks

This review found 35 issues worth fixing on livingdesert.org, 17 of them high impact, across 89 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
1.8 s1.3 sMay 2Oct 171.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.6 s
May 9, 20261.6 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.5 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
248 ms100 msMay 2Oct 17231 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026127 ms
May 9, 2026129 ms
May 16, 2026125 ms
May 23, 2026121 ms
May 30, 2026118 ms
Jun 6, 2026117 ms
Jun 13, 2026121 ms
Jun 20, 2026128 ms
Jun 27, 2026133 ms
Jul 4, 2026141 ms
Jul 11, 2026145 ms
Jul 18, 2026146 ms
Jul 25, 2026151 ms
Aug 1, 2026161 ms
Aug 8, 2026175 ms
Aug 15, 2026195 ms
Aug 22, 2026204 ms
Aug 29, 2026212 ms
Sep 5, 2026211 ms
Sep 12, 2026209 ms
Sep 19, 2026214 ms
Sep 26, 2026220 ms
Oct 3, 2026223 ms
Oct 10, 2026229 ms
Oct 17, 2026231 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 livingdesert.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. livingdesert.org at 0.4 s0.4 s
  2. livingdesert.org at 0.8 s0.8 s
  3. livingdesert.org at 1.1 s1.1 s
  4. livingdesert.org at 1.5 s1.5 s
  5. livingdesert.org at 1.9 s1.9 s
  6. livingdesert.org at 2.3 s2.3 s
  7. livingdesert.org at 2.6 s2.6 s
  8. livingdesert.org at 3.0 s3.0 s

Speed

11 to fix44
  • Improve image delivery

    4.8 s · 2.2 MB

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

  • Render-blocking requests

    2.9 s

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

  • Reduce unused JavaScript

    1.8 s · 900 KiB

    About 900 KiB 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.

  • Mobile performance score: 44

    44/100

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

  • 3,565 HTML elements

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

  • 8 third-party services on the page

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

  • Reduce unused CSS

    600 ms · 135 KiB

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

  • Use efficient cache lifetimes

    350 ms · 384 KiB

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

  • Google Tag Manager adds 597 ms

    597 ms

    Google Tag Manager costs a phone 597 ms of main-thread work and 821 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.

  • Facebook adds 316 ms

    316 ms

    Facebook costs a phone 316 ms of main-thread work and 308 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: 3.3 s

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

  • 12 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 52 KiB

    Polyfills for old browsers add 52 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify CSS

    150 ms · 10 KiB

    10 KiB could be saved by minifying CSS.

  • Font display

    50 ms

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

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

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

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

  • Largest Contentful Paint: 22.1 s

    22.1 s

    Your largest element takes 22.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “More Than a Zoo Explore. Connect. Protect. Buy Tickets (Ope…”.

  • Time to Interactive: 22.9 s

    22.9 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Speed Index: 7.4 s

    7.4 s

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

  • Total Blocking Time: 604 ms

    604 ms

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

  • Real-user INP: 238 ms

    238 ms

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

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

    +80%

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

  • 15 images without width and height

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

6 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

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

    1.2 s

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

  • Real-user TTFB: 658 ms

    658 ms

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

  • Largest content (LCP) got 13% faster for real visitors

    -13%

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

  • Cumulative Layout Shift: 0.071

    0.071

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

Images and page weight

2 to fix55
  • Page weight: 24.6 MB in 203 requests

    24.6 MB

    Your homepage downloads 24.6 MB in 203 requests on a phone: media 19.2 MB (3), images 2.7 MB (50) and scripts 2.0 MB (57). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Foxpaws-768x495.png weighs 501 KiB. On a phone connection a single image that size takes seconds.

  • 3 images in older formats

    3 images (220 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.

  • 3 images below the first screen load straight away

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

  • About 7.0 g of CO₂ per visit

    6.96 g

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

5 to fixGoogle 9093
  • Elements must only use permitted ARIA attributes (7 elements)

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

  • Interactive controls must not be nested (7 elements)

    Interactive controls must not be nested: 7 elements on the page fail this check, rated serious by axe-core.

  • 2 text elements with low contrast

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

  • 1 link without text

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

  • ARIA role should be appropriate for the element (1 element)

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 41 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

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

SEO

1 to fixGoogle 9298
  • 9 links with vague text

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

  • 365 internal links, 33 external

    The homepage links to 365 pages on livingdesert.org and 33 external pages.

8 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “The Living Desert in Palm Springs, CA is a family-friendly zoo and garden rated 10 Best Zoos in the US, specializing in…”.

  • One H1 headline

    Your main headline reads: “Find Your Adventure”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “The Living Desert Zoo and Gardens in Palm Springs, CA”.

  • Canonical URL set

    The canonical URL is https://www.livingdesert.org/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, LocalBusiness, Organization and WebPage.

  • 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.livingdesert.org/sitemap_index.xml.

AI search readiness

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

    Your Organization JSON-LD is missing 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://www.livingdesert.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 (1,630 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix78
  • 2 pages share a title

    https://www.livingdesert.org/events/wild-at-heart-zoocamp-for-adults-2/2026-11-14 and https://www.livingdesert.org/events/dog-day/2026-10-30 all use the title “Events Calendar - The Living Desert Zoo and Gardens”. 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://www.livingdesert.org/events/wild-at-heart-zoocamp-for-adults-2/2026-11-14, https://www.livingdesert.org/events/dog-day/2026-10-30 and https://www.livingdesert.org/events have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.livingdesert.org/support/ways-to-give, whose canonical is https://www.livingdesert.org/support/give. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.livingdesert.org/plan-your-visit/oasis-splash-pad has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 10078
  • 4 broken images

    4 images failed to load on a phone, for example https://www.livingdesert.org/.

  • 2 JavaScript errors while loading

    2 errors were 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

    33 of 36 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No opening hours

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

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

    The homepage carries about 995 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Buy Tickets (Open Link in new window)”.

  • 35 calls to action

    The homepage has 35 calls to action, for example “Gift Shop”, “Buy Tickets” and “Zoo Map & Schedule”.

  • 1 short form

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

  • Social proof on the page

    Social proof on the homepage: 6 customer or partner logos, a star rating and “Over 12920 Reviews”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

  • Direct contact links

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

  • Phone number on the homepage

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

  • 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

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag and 3 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 17 cookies set on arrival

    17

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

  • 31 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 livingdesert.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
jQuery
Analytics
Google Tag Manager

Company

Founded
1970

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on livingdesert.org, including 20 speed issues and 1 SEO issue. 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