Website review, no card needed

alberta.ca logo

alberta.ca website review

Visit site (opens in a new tab)Reviewed 18 October 202626 issues · 73 checks

This review found 26 issues worth fixing on alberta.ca, 10 of them high impact, across 73 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
1.4 s992 msApr 25Oct 101.3 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.2 s
May 2, 20261.2 s
May 9, 20261.2 s
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.3 s
Jun 6, 20261.2 s
Jun 13, 20261.3 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.0 s
Jul 11, 20261.0 s
Jul 18, 20261.0 s
Jul 25, 20261.1 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
301 ms188 msApr 25Oct 10271 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026203 ms
May 2, 2026203 ms
May 9, 2026203 ms
May 16, 2026203 ms
May 23, 2026203 ms
May 30, 2026202 ms
Jun 6, 2026202 ms
Jun 13, 2026201 ms
Jun 20, 2026202 ms
Jun 27, 2026201 ms
Jul 4, 2026214 ms
Jul 11, 2026219 ms
Jul 18, 2026220 ms
Jul 25, 2026222 ms
Aug 1, 2026221 ms
Aug 8, 2026221 ms
Aug 15, 2026226 ms
Aug 22, 2026236 ms
Aug 29, 2026247 ms
Sep 5, 2026264 ms
Sep 12, 2026281 ms
Sep 19, 2026287 ms
Sep 26, 2026288 ms
Oct 3, 2026282 ms
Oct 10, 2026271 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 alberta.ca (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix55
  • Improve image delivery

    4.0 s · 810 KiB

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

  • Render-blocking requests

    2.9 s

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

  • Google Tag Manager adds 1.1 s

    1.1 s

    Google Tag Manager costs a phone 1.1 s of main-thread work and 989 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 8 third-party services on the page

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

  • Reduce unused JavaScript

    600 ms · 443 KiB

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

  • Mobile performance score: 55

    55/100

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

  • Reduce unused CSS

    750 ms · 156 KiB

    About 156 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • 10 long tasks on the main thread

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

  • Main-thread work: 2.1 s

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

  • Font display

    50 ms

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

  • Use efficient cache lifetimes

    19 KiB

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

  • Phones get a much slower page than desktops

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

  • Legacy JavaScript

    8 KiB

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

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 10.5 s

    10.5 s

    Your largest element takes 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Tariff-related resources for Alberta businesses Submit your…”.

  • Time to Interactive: 15.5 s

    15.5 s

    The page becomes fully interactive after 15.5 s. Good is under 3.8 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.

  • Real-user INP: 242 ms

    242 ms

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

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

    +36%

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

  • Total Blocking Time: 561 ms

    561 ms

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

6 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

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

  • 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: 1.1 s

    1.1 s

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

  • Real-user TTFB: 554 ms

    554 ms

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

  • Speed Index: 3.2 s

    3.2 s

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

  • Cumulative Layout Shift: 0.036

    0.036

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

Images and page weight

1 to fix85
  • Page weight: 2.5 MB in 37 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 37 requests on a phone: images 1.2 MB (6), scripts 1.1 MB (13) and stylesheets 174 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (159 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 below the first screen load straight away

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

  • About 0.7 g of CO₂ per visit

    0.71 g

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

1 checks passed
  • 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 9899
  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 7 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 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 10095
  • Meta description is short (49 characters)

    Your meta description is only 49 characters: “Find Alberta government services and information.”. 70 to 160 characters is enough to sell the click.

  • 65 internal links, 9 external

    The homepage links to 65 pages on alberta.ca and 9 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Tariff-related resources for Alberta businesses”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “Government of Alberta | Alberta.ca”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: 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 https://www.alberta.ca/sitemap.xml.

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.alberta.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 (495 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix83
  • 1 page points its canonical at the homepage

    https://www.alberta.ca/government-of-alberta declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.alberta.ca/government-of-alberta all use the title “Government of Alberta | Alberta.ca”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    31 of 31 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage carries about 349 words of visible text.

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact government” and “Download the app”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

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 Microsoft Clarity (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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies, 1 of them by other companies (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.

  • 16 other companies contacted

    Loading the homepage contacts 16 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 alberta.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
Drupal
Analytics
Google Tag Manager

Company

Founded
1905
Headquarters
Edmonton

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on alberta.ca, including 16 speed issues, 1 SEO issue 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