Website review, no card needed

smu.ca logo

smu.ca website review

Visit site (opens in a new tab)Reviewed 1 November 202627 issues · 77 checks

This review found 27 issues worth fixing on smu.ca, 6 of them high impact, across 77 checks. The most urgent: hidden but focusable. 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
1.5 s934 msMay 9Oct 241.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 2026994 ms
May 16, 2026997 ms
May 23, 2026994 ms
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.2 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.2 s
Aug 15, 20261.3 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.3 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
208 ms98 msMay 9Oct 24137 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026169 ms
May 16, 2026166 ms
May 23, 2026161 ms
May 30, 2026162 ms
Jun 6, 2026162 ms
Jun 13, 2026164 ms
Jun 20, 2026166 ms
Jun 27, 2026170 ms
Jul 4, 2026173 ms
Jul 11, 2026183 ms
Jul 18, 2026195 ms
Jul 25, 2026195 ms
Aug 1, 2026182 ms
Aug 8, 2026159 ms
Aug 15, 2026134 ms
Aug 22, 2026119 ms
Aug 29, 2026111 ms
Sep 5, 2026113 ms
Sep 12, 2026116 ms
Sep 19, 2026119 ms
Sep 26, 2026127 ms
Oct 3, 2026128 ms
Oct 10, 2026131 ms
Oct 17, 2026137 ms
Oct 24, 2026137 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 smu.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix69
  • Reduce unused JavaScript

    770 ms · 535 KiB

    About 535 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 770 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Snapchat and others), adding 1.7 MB and 1.1 s of main-thread time.

  • Mobile performance score: 69

    69/100

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

  • Google Tag Manager adds 747 ms

    747 ms

    Google Tag Manager costs a phone 747 ms of main-thread work and 885 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.

  • Improve image delivery

    400 ms · 56 KiB

    2 images could be 56 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

  • Use efficient cache lifetimes

    343 KiB

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

  • FontAwesome CDN adds 25 ms

    25 ms

    FontAwesome CDN costs a phone 25 ms of main-thread work and 304 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 · 155 KiB

    About 155 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.

  • 9 long tasks on the main thread

    9 long tasks block the main thread while loading, the longest for 230 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    72 KiB

    Polyfills for old browsers add 72 KiB JavaScript that modern phones do not need.

  • Font display

    50 ms

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

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.8 s

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

  • Server response: 19 ms

    19 ms

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

Core Web Vitals

3 to fix100
  • Time to Interactive: 17.2 s

    17.2 s

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

  • Largest Contentful Paint: 4.8 s

    4.8 s

    Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Two students examine equipment in a lab.”.

  • Total Blocking Time: 522 ms

    522 ms

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

  • Largest content (LCP) got 14% slower for real visitors

    +14%

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

10 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.3 s

    1.3 s

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

  • Real-user INP: 129 ms

    129 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 756 ms

    756 ms

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

  • Tap response (INP) got 18% faster for real visitors

    -18%

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

  • Cumulative Layout Shift: 0.037

    0.037

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

  • First Contentful Paint: 0.9 s

    0.9 s

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

  • Speed Index: 1.5 s

    1.5 s

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

Images and page weight

2 to fix81
  • Page weight: 2.3 MB in 102 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 102 requests on a phone: scripts 1.5 MB (27), fonts 379 KiB (14) and images 321 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Studentgrouphub.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.7 g of CO₂ per visit

    0.66 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.66 g of CO₂e: 78.8 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

1 to fixGoogle 9698
  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 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

1 to fixGoogle 10096
  • No XML sitemap

    No XML sitemap at https://www.smu.ca/sitemap.xml, so Google discovers your pages only by following links.

  • 129 internal links, 38 external

    The homepage links to 129 pages on smu.ca and 38 external pages.

7 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Saint Mary's offers a range of undergraduate, graduate and professional development programs and conducts research with…”.

  • One H1 headline

    Your main headline reads: “Saint Mary's University”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Saint Mary's University in Halifax, Nova Scotia, Canada”.

  • Canonical URL set

    The canonical URL is https://www.smu.ca/.

  • Structured data in place

    Structured data found: CollegeOrUniversity.

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

AI search readiness

1 to fix83
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

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

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

Other pages

4 to fix68
  • 1 page without a title

    https://www.smu.ca/phonebooknetworkcheck has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.smu.ca/phonebooknetworkcheck is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 6 pages without a meta description

    https://www.smu.ca/academics/the-patrick-power-library.html, https://www.smu.ca/phonebooknetworkcheck, https://www.smu.ca/about, https://www.smu.ca/future-students/soe-programs, https://www.smu.ca/gradstudies and https://www.smu.ca/sobey/graduateprograms have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.smu.ca/alert, whose canonical is https://www.smu.ca/alert/index.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 73 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

Best practices

3 to fixGoogle 7385
  • 9 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://in.getclicky.com/in.php?site_id=101446761&href=%2F&title=Saint%20Mary%27s%20University%20in…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix67
  • 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 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.

  • Only about 86 words

    The homepage has only about 86 words of visible text; thin pages give Google and first-time buyers little to go on.

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

5 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Apply Now”, “Apply to Saint Mary's” and “Register for Courses”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Reddit Pixel and 1 more (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.

  • 12 cookies set on arrival

    12

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

  • 31 other companies contacted

    Loading the homepage contacts 31 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 smu.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
jQuery
Analytics
Google Tag Manager
Hosting
AWS

Company

Employees
3,055
Founded
1840

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on smu.ca, including 10 speed issues, 1 SEO issue and 4 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