Website review, no card needed

thewillowcentre.com logo

thewillowcentre.com website review

Visit site (opens in a new tab)Reviewed 3 November 202624 issues · 74 checks

This review found 24 issues worth fixing on thewillowcentre.com, 9 of them high impact, across 74 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

Full-page screenshot of thewillowcentre.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thewillowcentre.com at 0.4 s0.4 s
  2. thewillowcentre.com at 0.8 s0.8 s
  3. thewillowcentre.com at 1.1 s1.1 s
  4. thewillowcentre.com at 1.5 s1.5 s
  5. thewillowcentre.com at 1.9 s1.9 s
  6. thewillowcentre.com at 2.3 s2.3 s
  7. thewillowcentre.com at 2.6 s2.6 s
  8. thewillowcentre.com at 3.0 s3.0 s

Speed

3 to fix74
  • Improve image delivery

    2.6 s · 493 KiB

    2 images could be 493 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.

  • Render-blocking requests

    1.3 s

    13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.

  • Mobile performance score: 74

    74/100

    Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.

  • Minify CSS

    150 ms · 2 KiB

    2 KiB could be saved by minifying CSS.

  • Font display

    150 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Google Analytics and Cloudflare and others), adding 283 KiB and 86 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 72 ms. During a long task the page ignores taps.

  • Reduce unused JavaScript

    70 KiB

    About 70 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    20 KiB

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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.

2 checks passed
  • Main-thread work: 0.3 s

    A phone's processor spends 0.3 s on main-thread work while loading, 138 ms of it running JavaScript. That is comfortably low.

  • Server response: 35 ms

    35 ms

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

Core Web Vitals

4 to fix68
  • Largest Contentful Paint: 7.8 s

    7.8 s

    Your largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Willow Centre was founded in 1999 by Dr. Rex Collins, a…”.

  • Time to Interactive: 7.8 s

    7.8 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 1 image without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • Speed Index: 2.6 s

    2.6 s

    Visually, the page fills in at 2.6 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 22 ms

    22 ms

    Scripts block the page for only 22 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix90
  • 3 images in older formats

    3 images (781 KiB) 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.

  • About 0.4 g of CO₂ per visit

    0.39 g

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

3 checks passed
  • Page weight: 1.4 MB in 34 requests

    1.4 MB

    Your homepage downloads 1.4 MB in 34 requests on a phone: images 874 KiB (4), scripts 245 KiB (10) and fonts 218 KiB (6). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8891
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 14 text elements with low contrast

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

  • Links look like plain text

    3 links inside paragraphs rely on colour alone to stand out.

  • All page content should be contained by landmarks (4 elements)

    All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 2 images in the HTML carry an alt attribute.

  • 41 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: 41 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10083
  • Title is long (99 characters)

    Your title is 99 characters, so Google will cut it off around 60: “The Willow Centre | Toronto Infant, Child, Adolescent, and Adult Psychologists and Psycho…”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“The Willow Centre” and “Menu”). One clear main headline is easier for people and search engines.

  • Meta description is long (200 characters)

    Your meta description is 200 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 80 internal links, 4 external

    The homepage links to 80 pages on thewillowcentre.com and 4 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://www.thewillowcentre.com/.

  • Structured data in place

    Structured data found: Organization, WebPage and WebSite.

  • 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 http://www.thewillowcentre.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    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.

  • No llms.txt

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

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (712 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 65 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

3 to fixGoogle 10071
  • 1 broken image

    1 image failed to load on a phone, for example https://www.thewillowcentre.com/.

  • 10 small tap targets

    10 of 24 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: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 624 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Call Us – 416-250-1540” and “Contact Us”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Call Us – 416-250-1540”, “Book List” and “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 6 other companies contacted

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

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 thewillowcentre.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
Framework
jQuery
Analytics
Google Analytics
Hosting
Cloudflare

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on thewillowcentre.com, including 7 speed issues, 3 SEO issues and 2 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