Website review, no card needed

alphacollege.ca logo

alphacollege.ca website review

Visit site (opens in a new tab)Reviewed 18 November 202642 issues · 85 checks

This review found 42 issues worth fixing on alphacollege.ca, 19 of them high impact, across 85 checks. The most urgent: use efficient cache lifetimes. 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
7.9 s4.0 sMay 30Nov 146.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20265.0 s
Jun 6, 20264.7 s
Jun 13, 20264.9 s
Jun 20, 20265.5 s
Jun 27, 20265.6 s
Jul 4, 20265.5 s
Jul 11, 20265.3 s
Jul 18, 20264.9 s
Jul 25, 20264.5 s
Aug 1, 20264.7 s
Aug 8, 20264.8 s
Aug 15, 20265.0 s
Aug 22, 20265.4 s
Aug 29, 20265.7 s
Sep 5, 20266.2 s
Sep 12, 20266.0 s
Sep 19, 20266.4 s
Sep 26, 20266.8 s
Oct 3, 20266.8 s
Oct 10, 20267.4 s
Oct 17, 20266.9 s
Oct 24, 20265.8 s
Oct 31, 20265.7 s
Nov 7, 20265.4 s
Nov 14, 20266.1 s
Real-visitor tap response (INP)75th percentile, phones
212 ms89 msMay 30Nov 14191 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026128 ms
Jun 6, 2026120 ms
Jun 13, 2026122 ms
Jun 20, 2026128 ms
Jun 27, 2026130 ms
Jul 4, 2026130 ms
Jul 11, 2026117 ms
Jul 18, 2026109 ms
Jul 25, 2026103 ms
Aug 29, 2026125 ms
Sep 5, 2026133 ms
Sep 12, 2026147 ms
Sep 19, 2026169 ms
Sep 26, 2026195 ms
Oct 3, 2026188 ms
Oct 10, 2026196 ms
Oct 17, 2026198 ms
Oct 24, 2026178 ms
Oct 31, 2026192 ms
Nov 7, 2026190 ms
Nov 14, 2026191 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 alphacollege.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alphacollege.ca at 4.4 s4.4 s
  2. alphacollege.ca at 8.7 s8.7 s
  3. alphacollege.ca at 13.1 s13.1 s
  4. alphacollege.ca at 17.5 s17.5 s
  5. alphacollege.ca at 21.9 s21.9 s
  6. alphacollege.ca at 26.2 s26.2 s
  7. alphacollege.ca at 30.6 s30.6 s
  8. alphacollege.ca at 35.0 s35.0 s

Speed

10 to fix53
  • Use efficient cache lifetimes

    14.3 s · 5.6 MB

    125 files are served with short cache lifetimes, so returning visitors download them again (5.6 MB).

  • Render-blocking requests

    5.8 s

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

  • Improve image delivery

    2.2 s · 1.6 MB

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

  • Reduce unused CSS

    2.9 s · 596 KiB

    About 596 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.9 s faster on a phone.

  • Reduce unused JavaScript

    1.4 s · 915 KiB

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

  • Mobile performance score: 53

    53/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, buttonizer.io and reddit and others), adding 1.7 MB and 632 ms of main-thread time.

  • Google Tag Manager adds 580 ms

    580 ms

    Google Tag Manager costs a phone 580 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.

  • Minify JavaScript

    300 ms · 69 KiB

    69 KiB could be saved by minifying JavaScript.

  • Main-thread work: 2.4 s

    A phone's processor spends 2.4 s on main-thread work while loading, 998 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Legacy JavaScript

    200 ms · 43 KiB

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

  • Minify CSS

    150 ms · 20 KiB

    20 KiB could be saved by minifying CSS.

  • 7 long tasks on the main thread

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

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 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.

1 checks passed
  • Server response: 48 ms

    48 ms

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

Core Web Vitals

10 to fix67
  • 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 LCP: 6.1 s

    6.1 s

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

  • Real-user FCP: 5.4 s

    5.4 s

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

  • Real-user TTFB: 3.4 s

    3.4 s

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

  • Largest Contentful Paint: 20.6 s

    20.6 s

    Your largest element takes 20.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FEATURED CAREER-FOCUSED PROGRAMS Discover diploma and certi…”.

  • Speed Index: 20.0 s

    20.0 s

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

  • First Contentful Paint: 7.1 s

    7.1 s

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

  • Time to Interactive: 22.2 s

    22.2 s

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

  • Tap response (INP) got 54% slower for real visitors

    +54%

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

  • 7 images without width and height

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

  • 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 5.0 s to 6.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user INP: 192 ms

    192 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Total Blocking Time: 160 ms

    160 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix43
  • Page weight: 7.2 MB in 164 requests

    7.2 MB

    Your homepage downloads 7.2 MB in 164 requests on a phone: images 3.6 MB (19), scripts 2.1 MB (66) and stylesheets 783 KiB (50). Under 2 MB keeps phones on slow connections fast.

  • 10 images in older formats

    10 images (1.6 MB) 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.

  • 8 images below the first screen load straight away

    8 images further down the page (1.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 6 images far larger than shown

    216 KiB

    6 images are downloaded at several times the size a phone draws them, for example Alpha-College-campus-Mississauga-sq.jpg at 1,155 px wide, shown at 330 px. Resized copies would save about 216 KiB.

  • About 2.1 g of CO₂ per visit

    2.05 g

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

Accessibility

6 to fixGoogle 8791
  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

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

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

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

  • Headings skip levels

    Headings skip levels (h3 → h5, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

4 to fixGoogle 8580
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • 3 H1 headlines

    There are 3 <h1> headlines (“Build Your Future withALPHA COLLEGE”, “Build Your Future withALPHA COLLEGE” and “Start a RewardingCareer in Care”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 5 links with vague text

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

  • 103 internal links, 17 external

    The homepage links to 103 pages on alphacollege.ca and 17 external pages.

5 checks passed
  • Title: 52 characters

    Your title is a healthy 52 characters: “Home 2026 - Alpha College of Business and Technology”.

  • Canonical URL set

    The canonical URL is https://alphacollege.ca/.

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person 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://alphacollege.ca/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://alphacollege.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 sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://alphacollege.ca/career-college-policies, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page without a meta description

    https://alphacollege.ca/personal-support-worker-program has no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://alphacollege.ca/calendar-important-dates, https://alphacollege.ca/faq, https://alphacollege.ca/contact-us and https://alphacollege.ca/important-dates have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://alphacollege.ca/contact-us took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 9 small tap targets

    9 of 14 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 “Function snaptr not implemented.”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • 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.

  • Thin social proof

    Social proof on the homepage: 27 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 688 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: “Learn More” and “Apply Now”.

  • 23 calls to action

    The homepage has 23 calls to action, for example “Learn More”, “Apply Now” and “Contact Us”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 alphacollege.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
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager
Hosting
IONOS

Company

Employees
63
Headquarters
Toronto

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 alphacollege.ca, including 20 speed issues, 4 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