zooborns.com website review

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

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

YouTube costs a phone 1.9 s of main-thread work and 3.9 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.

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

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and Other Google APIs/SDKs and others), adding 9.0 MB and 2.1 s of main-thread time.

WordPress costs a phone 9 ms of main-thread work and 4.7 MB 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.

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

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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.

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

Your largest element takes 41.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “ZooBorns Logo”.

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

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

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

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

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

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

Your homepage downloads 9.2 MB in 84 requests on a phone: images 4.7 MB (14), scripts 3.6 MB (25) and HTML 345 KiB (5). Under 2 MB keeps phones on slow connections fast.

7 images weigh 4.0 MB together. On a phone connection a single image that size takes seconds.

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

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

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

Main 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 main landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is 76 characters, so Google will cut it off around 60: “ZooBorns - The Newest, Cutest Baby Animals from the World's Zoos & Aquariums”.

Your meta description is only 65 characters: “The Newest, Cutest Baby Animals from the World's Zoos & Aquariums”. 70 to 160 characters is enough to sell the click.

The homepage links to 54 pages on zooborns.com and 24 external pages.

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.

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

https://zooborns.com/category/elephant, https://zooborns.com/category/lion, https://zooborns.com/category/zsl-whipsnade-zoo, https://zooborns.com/category/tapir, https://zooborns.com/category/point-defiance-zoo-aquarium and https://zooborns.com/category/bioparc-valencia and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://zooborns.com/2025/08/26/pairi-daiza-celebrates-the-birth-of-a-second-asian-elephant-calf-in-2025, https://zooborns.com/2025/03/19/pride-and-joy-for-whipsnade-zoo-as-second-north-african-lioness-gives-birth, https://zooborns.com/2025/03/06/endangered-malayan-tapir-calf-born, https://zooborns.com/2025/02/26/a-chimpanzee-born-at-bioparc-valencia-from-a-critically-endangered-subspecies, https://zooborns.com/2024/12/19/three-northern-african-lion-cubs-born-at-whipsnade-zoo and https://zooborns.com/2024/12/17/meet-kayemba-the-rare-okapi-calf-born-at-marwell-zoo have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 2,745 words of visible text.

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

Opening the homepage sets 3 cookies, 1 of them by other companies (measured from a US location before any click).

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.

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