Website review, no card needed

albertahealthservices.ca logo

albertahealthservices.ca website review

Visit site (opens in a new tab)Reviewed 18 October 202640 issues · 89 checks

This review found 40 issues worth fixing on albertahealthservices.ca, 11 of them high impact, across 89 checks. The most urgent: render-blocking requests. 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
990 ms896 msApr 25Oct 10972 ms
Show as table
DateReal-visitor load time (LCP)
Apr 25, 2026907 ms
May 2, 2026917 ms
May 9, 2026925 ms
May 16, 2026932 ms
May 23, 2026934 ms
May 30, 2026935 ms
Jun 6, 2026939 ms
Jun 13, 2026941 ms
Jun 20, 2026943 ms
Jun 27, 2026952 ms
Jul 4, 2026955 ms
Jul 11, 2026957 ms
Jul 18, 2026963 ms
Jul 25, 2026963 ms
Aug 1, 2026973 ms
Aug 8, 2026977 ms
Aug 15, 2026974 ms
Aug 22, 2026979 ms
Aug 29, 2026964 ms
Sep 5, 2026964 ms
Sep 12, 2026964 ms
Sep 19, 2026957 ms
Sep 26, 2026965 ms
Oct 3, 2026968 ms
Oct 10, 2026972 ms
Real-visitor tap response (INP)75th percentile, phones
89 ms87 msApr 25Oct 1088 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202687 ms
May 2, 202687 ms
May 9, 202687 ms
May 16, 202688 ms
May 23, 202688 ms
May 30, 202688 ms
Jun 6, 202688 ms
Jun 13, 202688 ms
Jun 20, 202688 ms
Jun 27, 202688 ms
Jul 4, 202688 ms
Jul 11, 202688 ms
Jul 18, 202688 ms
Jul 25, 202689 ms
Aug 1, 202689 ms
Aug 8, 202689 ms
Aug 15, 202689 ms
Aug 22, 202689 ms
Aug 29, 202688 ms
Sep 5, 202689 ms
Sep 12, 202689 ms
Sep 19, 202688 ms
Sep 26, 202688 ms
Oct 3, 202688 ms
Oct 10, 202688 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 albertahealthservices.ca (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. albertahealthservices.ca at 0.5 s0.5 s
  2. albertahealthservices.ca at 1.1 s1.1 s
  3. albertahealthservices.ca at 1.6 s1.6 s
  4. albertahealthservices.ca at 2.2 s2.2 s
  5. albertahealthservices.ca at 2.7 s2.7 s
  6. albertahealthservices.ca at 3.3 s3.3 s
  7. albertahealthservices.ca at 3.8 s3.8 s
  8. albertahealthservices.ca at 4.4 s4.4 s

Speed

6 to fix64
  • Render-blocking requests

    1.0 s

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

  • Use efficient cache lifetimes

    700 ms · 1.4 MB

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

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64 (desktop: 90). Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    624 KiB

    3 images could be 624 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Font display

    600 ms

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

  • Google Tag Manager adds 174 ms

    174 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, FontAwesome CDN and Google Analytics and others), adding 668 KiB and 303 ms of main-thread time.

  • Reduce unused JavaScript

    191 KiB

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

  • Reduce unused CSS

    149 KiB

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

  • 2 long tasks on the main thread

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

  • Document request latency

    64 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Phones get a much slower page than desktops

    Desktop scores 90 but mobile only 64. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.0 s

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

  • Server response: 241 ms

    241 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 11.4 s

    11.4 s

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

  • Speed Index: 6.9 s

    6.9 s

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

  • Largest Contentful Paint: 4.5 s

    4.5 s

    Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Always here for you. Always caring for you.”. Most of its time is element render delay (3.3 s).

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Cumulative Layout Shift: 0.182

    0.182

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

  • 12 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

7 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.0 s

    1.0 s

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

  • Real-user INP: 105 ms

    105 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 524 ms

    524 ms

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

  • Total Blocking Time: 36 ms

    36 ms

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

Images and page weight

4 to fix58
  • Page weight: 2.2 MB in 91 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 91 requests on a phone: images 1.2 MB (41), scripts 466 KiB (16) and other files 211 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (1.0 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.

  • 2 images below the first screen load straight away

    2 images further down the page (688 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    109 KiB

    1 image is downloaded at several times the size a phone draws it, for example Reserved_ImageAttachment_Popular_Health_Topics_Section.jpg at 1,254 px wide, shown at 355 px. Resized copies would save about 109 KiB.

  • About 0.6 g of CO₂ per visit

    0.63 g

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

Accessibility

9 to fixGoogle 7789
  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 3 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 16 images without alt text

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

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

    All page content should be contained by landmarks: 3 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.

  • 5 links without text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Headings skip levels

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

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

7 to fixGoogle 6772
  • No meta description

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“Alberta Health Services” and “Always here for you. Always caring for you.”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

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

  • 7 links crawlers can't follow

    7 links have no real href, so search engines can't follow them.

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

  • 138 internal links, 42 external

    The homepage links to 138 pages on albertahealthservices.ca and 42 external pages.

3 checks passed
  • Title: 30 characters

    Your title is a healthy 30 characters: “Home | Alberta Health Services”.

  • Structured data in place

    Structured data found: WebSite.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

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

  • Text is in the HTML

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

Other pages

1 to fix93
  • 1 linked page hidden from search

    https://www.albertahealthservices.ca/info/Page12657.aspx is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 15 internal pages checked

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9691
  • 14 small tap targets

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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: 8 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 600 words of visible text.

6 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Book an appointment”, “Join our online community” and “Contact a health inspector”.

  • 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: 4 phone links and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

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

  • 6 cookies set on arrival

    6

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

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

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 albertahealthservices.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 Analytics | Google Tag Manager

Company

Employees
124,465
Founded
2008
Headquarters
Edmonton

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on albertahealthservices.ca, including 12 speed issues, 7 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