Website review, no card needed
calgaryzoo.com website review
Visit site (opens in a new tab)Reviewed 29 October 202622 issues · 74 checks
This review found 22 issues worth fixing on calgaryzoo.com, 7 of them high impact, across 74 checks. The most urgent: 1 image over 500 KB. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
88BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 122 ms |
| May 16, 2026 | 121 ms |
| May 23, 2026 | 121 ms |
| May 30, 2026 | 121 ms |
| Jun 6, 2026 | 121 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 121 ms |
| Jul 4, 2026 | 121 ms |
| Jul 11, 2026 | 122 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 123 ms |
| Aug 1, 2026 | 126 ms |
| Aug 8, 2026 | 127 ms |
| Aug 15, 2026 | 128 ms |
| Aug 22, 2026 | 129 ms |
| Aug 29, 2026 | 129 ms |
| Sep 5, 2026 | 129 ms |
| Sep 12, 2026 | 130 ms |
| Sep 19, 2026 | 130 ms |
| Sep 26, 2026 | 129 ms |
| Oct 3, 2026 | 128 ms |
| Oct 10, 2026 | 127 ms |
| Oct 17, 2026 | 125 ms |
| Oct 24, 2026 | 127 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
1.4 s · 412 KiBAbout 412 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, wordfly.com and cdn-cookieyes.com and others), adding 1.1 MB and 628 ms of main-thread time.
Google Tag Manager adds 528 ms
528 msGoogle Tag Manager costs a phone 528 ms of main-thread work and 855 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.
Reduce unused CSS
150 ms · 33 KiBAbout 33 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
150 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 130 ms. During a long task the page ignores taps.
Improve image delivery
125 KiB1 image could be 125 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
37 KiB3 files are served with short cache lifetimes, so returning visitors download them again (37 KiB).
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.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 671 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 10.4 s
10.4 sYour largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 12.0 s
12.0 sThe page becomes fully interactive after 12.0 s. Good is under 3.8 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user TTFB: 897 ms
897 msReal visitors wait 897 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 268 ms
268 msScripts block taps and scrolling for 268 ms in total while the page loads. Good is under 200 ms.
18 images without width and height
18 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 122 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 153 ms
153 msReal visitors wait 153 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Speed Index: 3.0 s
3.0 sVisually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.025
0.025The layout barely moves while loading (CLS 0.025, good is under 0.1).
Images and page weight
1 image over 500 KB
IA_Now-Open-Banner_P2-1.gif weighs 65.4 MB. On a phone connection a single image that size takes seconds.
2 images far larger than shown
51.2 MB2 images are downloaded at several times the size a phone draws them, for example IA_Now-Open-Banner_P2-1.gif at 2,500 px wide, shown at 390 px. Resized copies would save about 51.2 MB.
8 images in older formats
8 images (66.4 MB) 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.
Page weight: 2.3 MB in 62 requests
2.3 MBYour homepage downloads 2.3 MB in 62 requests on a phone: images 1.1 MB (20), scripts 1.0 MB (16) and fonts 105 KiB (3). Under 2 MB keeps phones on slow connections fast.
About 0.7 g of CO₂ per visit
0.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.66 g of CO₂e: 79.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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
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 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 29 images in the HTML carry an alt attribute.
49 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: 49 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
Meta description is short (46 characters)
Your meta description is only 46 characters: “Welcome to the Wilder Institute's Calgary Zoo.”. 70 to 160 characters is enough to sell the click.
Structured data has 3 problems
Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 3 problems, for example “WebSite: url is not an absolute URL ("/")”.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
79 internal links, 19 external
The homepage links to 79 pages on calgaryzoo.com and 19 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Wildlife And Human Life, Together.”.
Title: 48 characters
Your title is a healthy 48 characters: “The Calgary Zoo - Wilder Institute's Calgary Zoo”.
Canonical URL set
The canonical URL is https://www.calgaryzoo.com/.
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.calgaryzoo.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.calgaryzoo.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.
3 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,315 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 61 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 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 15 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://chat.satis.fi/embedder/styles/satisfipopup.1.0.141.css' from origin 'https://www.c…”.
2 checks passed
Tap targets are thumb-sized
88 of 90 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 805 words of copy
The homepage carries about 805 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Eat, Shop, Play” and “Buy Tickets”.
14 calls to action
The homepage has 14 calls to action, for example “Eat, Shop, Play”, “Buy Tickets” and “Learn More”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
12 other companies contacted
Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) 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 calgaryzoo.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
- Analytics
- Google Tag Manager
- Hosting
- Fastly
Company
- Employees
- 904
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 22 issues on calgaryzoo.com, including 11 speed issues, 3 SEO issues and 1 conversion gap. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.