Website review, no card needed
visionmondiale.ca website review
Visit site (opens in a new tab)Reviewed 17 November 202633 issues · 80 checks
This review found 33 issues worth fixing on visionmondiale.ca, 9 of them high impact, across 80 checks. The most urgent: fails Core Web Vitals for real visitors. 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
73C- #88,178 of 118,911 reviewed websitesbeats 22%
- #55,304 of 67,481 online storesbeats 15%
- #51,828 of 61,525 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.7 s |
| Jun 27, 2026 | 3.7 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.5 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 3.0 s |
| Oct 31, 2026 | 3.2 s |
| Nov 7, 2026 | 4.1 s |
| Nov 14, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 152 ms |
| Jun 6, 2026 | 152 ms |
| Jun 13, 2026 | 154 ms |
| Jun 20, 2026 | 151 ms |
| Jun 27, 2026 | 152 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 155 ms |
| Jul 18, 2026 | 153 ms |
| Jul 25, 2026 | 153 ms |
| Aug 1, 2026 | 149 ms |
| Aug 8, 2026 | 146 ms |
| Aug 15, 2026 | 147 ms |
| Aug 22, 2026 | 150 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 167 ms |
| Sep 12, 2026 | 178 ms |
| Sep 19, 2026 | 189 ms |
| Sep 26, 2026 | 197 ms |
| Oct 3, 2026 | 195 ms |
| Oct 10, 2026 | 192 ms |
| Oct 17, 2026 | 178 ms |
| Oct 24, 2026 | 163 ms |
| Oct 31, 2026 | 148 ms |
| Nov 7, 2026 | 140 ms |
| Nov 14, 2026 | 143 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.9 s
1.3 s
1.8 s
2.2 s
2.7 s
3.1 s
3.6 s
Speed
Use efficient cache lifetimes
200 ms · 1.7 MB26 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).
Reduce unused JavaScript
150 ms · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (talkdeskapp.com, Optanon and Kameleoon and others), adding 2.6 MB and 745 ms of main-thread time.
Mobile performance score: 74
74/100Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.
Document request latency
800 ms · 78 KiBThe HTML itself could arrive about 800 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce unused CSS
700 ms · 165 KiBAbout 165 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 700 ms faster on a phone.
Reduce initial server response time
824 msReduce initial server response time. Google estimates savings of 824 ms on a phone.
talkdeskapp.com adds 571 ms
571 mstalkdeskapp.com costs a phone 571 ms of main-thread work and 1.9 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.
Render-blocking requests
650 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Server response: 924 ms
924 msYour server takes 924 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
graphassets.com adds 0 ms
0 msgraphassets.com costs a phone 0 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 121 ms. During a long task the page ignores taps.
Improve image delivery
98 KiB5 images could be 98 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
34 KiBPolyfills for old browsers add 34 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.
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.
Real-user CLS: 0.78
0.78For real visitors the layout shifts by 0.78 (75th percentile). Good is under 0.1.
Time to Interactive: 25.0 s
25.0 sThe page becomes fully interactive after 25.0 s. Good is under 3.8 s.
Speed Index: 11.3 s
11.3 sVisually, the page fills in at 11.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.9 s
3.9 sReal visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 3.5 s
3.5 sYour largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Contribuez au changement. Un enfant à la fois.”.
Tap response (INP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 152 ms to 143 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 143 ms
143 msReal visitors wait 143 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 140 ms
140 msScripts block the page for only 140 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.0 MB in 158 requests
4.0 MBYour homepage downloads 4.0 MB in 158 requests on a phone: scripts 2.3 MB (104), fonts 847 KiB (12) and images 360 KiB (15). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (57 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.1 g of CO₂ per visit
1.13 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.13 g of CO₂e: 136.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 checks passed
Every image has alt text
All 20 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 1 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 long (216 characters)
Your meta description is 216 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.
34 internal links, 10 external
The homepage links to 34 pages on visionmondiale.ca and 10 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Contribuez au changement. Un enfant à la fois.”.
Title: 56 characters
Your title is a healthy 56 characters: “Vision Mondiale | Aide aux enfants | Lutte à la pauvreté”.
Canonical URL set
The canonical URL is https://www.worldvision.ca/fr.
Structured data in place
Structured data found: NGO and WebPage.
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://my.worldvision.ca/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.worldvision.ca/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 contact details; sameAs (social profiles) and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (598 words), so crawlers that don't run JavaScript still read it.
Other pages
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.worldvision.ca/ways-to-give/sponsor-a-child, whose canonical is https://www.worldvision.ca/en/ways-to-give/sponsor-a-child. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.worldvision.ca/ways-to-give/membership has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.worldvision.ca/campaigns/where-most-needed took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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.
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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
8 of 9 tappable elements near the top are at least 24 px.
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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 623 words of copy
The homepage carries about 623 words of visible text.
2 checks passed
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.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 visionmondiale.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Astro
- E-commerce
- Shopify;Shopify Plus
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on visionmondiale.ca, including 21 speed issues, 2 SEO issues and 5 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.