Website review, no card needed
caamanitoba.com website review
Visit site (opens in a new tab)Reviewed 23 October 202642 issues · 72 checks
This review found 42 issues worth fixing on caamanitoba.com, 16 of them high impact, across 72 checks. The most urgent: use efficient cache lifetimes. 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
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.1 s |
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 149 ms |
| May 9, 2026 | 148 ms |
| May 16, 2026 | 147 ms |
| May 23, 2026 | 145 ms |
| May 30, 2026 | 147 ms |
| Jun 6, 2026 | 148 ms |
| Jun 13, 2026 | 149 ms |
| Jun 20, 2026 | 148 ms |
| Jun 27, 2026 | 148 ms |
| Jul 4, 2026 | 155 ms |
| Jul 11, 2026 | 162 ms |
| Jul 18, 2026 | 165 ms |
| Jul 25, 2026 | 164 ms |
| Aug 1, 2026 | 162 ms |
| Aug 8, 2026 | 160 ms |
| Aug 15, 2026 | 166 ms |
| Aug 22, 2026 | 174 ms |
| Aug 29, 2026 | 176 ms |
| Sep 5, 2026 | 178 ms |
| Sep 12, 2026 | 174 ms |
| Sep 19, 2026 | 170 ms |
| Sep 26, 2026 | 174 ms |
| Oct 3, 2026 | 178 ms |
| Oct 10, 2026 | 175 ms |
| Oct 17, 2026 | 174 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
1.0 s
2.0 s
3.1 s
4.1 s
5.1 s
6.2 s
7.2 s
8.2 s
Speed
Use efficient cache lifetimes
8.8 s · 2.9 MB63 files are served with short cache lifetimes, so returning visitors download them again (2.9 MB).
Reduce unused JavaScript
6.5 s · 2.9 MBAbout 2.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.5 s faster on a phone.
Improve image delivery
2.6 s · 983 KiB10 images could be 983 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.
Google Tag Manager adds 2.2 s
2.2 sGoogle Tag Manager costs a phone 2.2 s of main-thread work and 2.5 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.
Render-blocking requests
1.5 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Reduce unused CSS
1.1 s · 218 KiBAbout 218 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
jQuery CDN adds 1.0 s
1.0 sjQuery CDN costs a phone 1.0 s of main-thread work and 30 KiB 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.
Mobile performance score: 31
31/100Your mobile performance score is 31 (desktop: 41). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.4 s
A phone's processor spends 7.4 s on main-thread work while loading, 5.1 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, jQuery CDN and Google CDN and others), adding 5.6 MB and 4.4 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.2 s. During a long task the page ignores taps.
Google CDN adds 489 ms
489 msGoogle CDN costs a phone 489 ms of main-thread work and 1.1 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.
Font display
500 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 500 ms).
YouTube adds 355 ms
355 msYouTube costs a phone 355 ms of main-thread work and 1,006 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.
Google Maps adds 108 ms
108 msGoogle Maps costs a phone 108 ms of main-thread work and 407 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.
Legacy JavaScript
24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need.
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: 177 ms
177 msYour server sent the HTML in 177 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: 22.7 s
22.7 sYour largest element takes 22.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “CAA tow truck operator helping on the side of the road.”.
Time to Interactive: 48.9 s
48.9 sThe page becomes fully interactive after 48.9 s. Good is under 3.8 s.
Total Blocking Time: 2.9 s
2.9 sScripts block taps and scrolling for 2.9 s in total while the page loads. Good is under 200 ms.
Speed Index: 10.3 s
10.3 sVisually, the page fills in at 10.3 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 911 ms
911 msReal visitors wait 911 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.119
0.119The layout shifts by 0.119 while loading, so content jumps under the reader's thumb. Good is under 0.1.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 149 ms to 174 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 162 ms
162 msReal visitors wait 162 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (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.
Images and page weight
Page weight: 9.6 MB in 208 requests
9.6 MBYour homepage downloads 9.6 MB in 208 requests on a phone: scripts 5.7 MB (74), images 2.4 MB (44) and other files 740 KiB (57). Under 2 MB keeps phones on slow connections fast.
About 2.7 g of CO₂ per visit
2.72 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.72 g of CO₂e: 325.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (3 elements).
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
5 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 8 WCAG 2.2 A/AA and best-practice rules on the phone render: 5 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (19 characters)
Your title is only 19 characters: “Home - CAA Manitoba”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (173 characters)
Your meta description is 173 characters; Google truncates after about 160, so the end of your pitch is cut.
No XML sitemap
No XML sitemap at https://www.caamanitoba.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at caamanitoba.com/robots.txt, the first file search crawlers ask for.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
216 internal links, 58 external
The homepage links to 216 pages on caamanitoba.com and 58 external pages.
3 checks passed
One H1 headline
Your main headline reads: “Driven by Good Neighbours”.
Canonical URL set
The canonical URL is https://www.caamanitoba.com/.
Structured data in place
Structured data found: Organization and WebSite.
AI search readiness
1 checks passed
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.
Other pages
Your server turned our page checks away
15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 1,314 words of copy
The homepage carries about 1,314 words of visible text.
3 checks passed
22 calls to action
The homepage has 22 calls to action, for example “Shop our eStore”, “Property Insurance Quote” and “Travel Insurance Quote”.
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 cookies set on arrival
3Opening the homepage sets 3 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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 caamanitoba.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Cogeco Peer 1;Oracle Cloud;Oracle Zenedge;Shopify Hosted;Cloudflare Hosting;Amazon
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on caamanitoba.com, including 25 speed issues, 6 SEO issues and 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.