Website review, no card needed

ccdi.ca logo

ccdi.ca website review

Visit site (opens in a new tab)Reviewed 24 October 202633 issues · 65 checks

This review found 33 issues worth fixing on ccdi.ca, 15 of them high impact, across 65 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
3.0 s2.2 sJul 25Oct 172.8 s
Show as table
DateReal-visitor load time (LCP)
Jul 25, 20262.4 s
Aug 1, 20262.9 s
Aug 8, 20262.8 s
Aug 15, 20262.7 s
Aug 22, 20262.6 s
Aug 29, 20262.4 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
122 ms95 msAug 8Oct 17118 ms
Show as table
DateReal-visitor tap response (INP)
Aug 8, 2026105 ms
Aug 15, 2026104 ms
Aug 22, 2026115 ms
Aug 29, 2026115 ms
Sep 5, 2026115 ms
Sep 12, 2026119 ms
Sep 19, 202698 ms
Sep 26, 202698 ms
Oct 3, 2026106 ms
Oct 10, 2026107 ms
Oct 17, 2026118 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 ccdi.ca (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ccdi.ca at 0.7 s0.7 s
  2. ccdi.ca at 1.3 s1.3 s
  3. ccdi.ca at 2.0 s2.0 s
  4. ccdi.ca at 2.6 s2.6 s
  5. ccdi.ca at 3.3 s3.3 s
  6. ccdi.ca at 3.9 s3.9 s
  7. ccdi.ca at 4.6 s4.6 s
  8. ccdi.ca at 5.2 s5.2 s

Speed

8 to fix30
  • Improve image delivery

    10.6 s · 3.7 MB

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

  • Reduce unused JavaScript

    1.5 s · 468 KiB

    About 468 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Mobile performance score: 30

    30/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Accessibe Accessibility Overlay and others), adding 1.0 MB and 969 ms of main-thread time.

  • Use efficient cache lifetimes

    450 ms · 279 KiB

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

  • Render-blocking requests

    600 ms

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

  • Google Tag Manager adds 422 ms

    422 ms

    Google Tag Manager costs a phone 422 ms of main-thread work and 462 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.4 s

    A phone's processor spends 3.4 s on main-thread work while loading, 1.7 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 241 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    150 ms · 37 KiB

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

  • Reduce unused CSS

    32 KiB

    About 32 KiB of CSS is downloaded but never applied on this page.

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

1 checks passed
  • Server response: 31 ms

    31 ms

    Your server sent the HTML in 31 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix33
  • 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: 1.00

    1.00

    For real visitors the layout shifts by 1.00 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 20.7 s

    20.7 s

    Your largest element takes 20.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BUILDING A MORE INCLUSIVE CANADA Advancing diversity, equit…”.

  • Time to Interactive: 27.8 s

    27.8 s

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

  • Cumulative Layout Shift: 0.95

    0.95

    The layout shifts by 0.95 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 10.5 s

    10.5 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Total Blocking Time: 426 ms

    426 ms

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

  • Tap response (INP) held steady for real visitors

    +8%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

3 checks passed
  • Real-user INP: 111 ms

    111 ms

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

  • Real-user TTFB: 677 ms

    677 ms

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

Images and page weight

5 to fix28
  • Page weight: 20.0 MB in 117 requests

    20.0 MB

    Your homepage downloads 20.0 MB in 117 requests on a phone: media 11.7 MB (3), images 5.8 MB (23) and scripts 1.3 MB (32). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    7141414-6a2c1bbd24ab0.png weighs 598 KiB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (598 KiB) is 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.

  • 1 image far larger than shown

    328 KiB

    1 image is downloaded at several times the size a phone draws it, for example 7141414-6a2c1bbd24ab0.png at 1,384 px wide, shown at 310 px. Resized copies would save about 328 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (598 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 5.7 g of CO₂ per visit

    5.66 g

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

Accessibility

1 to fixGoogle 10099
  • 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 checks passed
  • 42 automated accessibility rules passed

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

SEO

4 to fixGoogle 9283
  • No H1 headline

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 3 links with vague text

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

6 checks passed
  • Meta description: 120 characters

    Your meta description is 120 characters: “Building a more inclusive Canada through DEIA, working with organizations in the public, private and non-profit sectors.”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Building a more inclusive Canada through DEIA”.

  • Canonical URL set

    The canonical URL is https://ccdi.ca/en.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://ccdi.ca/sitemap.xml.

AI search readiness

1 to fix75
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 525 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • No llms.txt

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

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.

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

Best practices

2 to fixGoogle 9687
  • 34 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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.

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 525 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Join the mission”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 8 cookies set on arrival

    8

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

  • 19 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 ccdi.ca, 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
Next.js
Analytics
Google Tag Manager

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 ccdi.ca, including 17 speed issues, 4 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

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