Website review, no card needed
alc.ca website review
Visit site (opens in a new tab)Reviewed 31 October 202657 issues · 97 checks
This review found 57 issues worth fixing on alc.ca, 18 of them high impact, across 97 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.2 s |
| May 16, 2026 | 4.2 s |
| May 23, 2026 | 4.3 s |
| May 30, 2026 | 4.4 s |
| Jun 6, 2026 | 4.5 s |
| Jun 13, 2026 | 4.6 s |
| Jun 20, 2026 | 4.6 s |
| Jun 27, 2026 | 4.6 s |
| Jul 4, 2026 | 4.7 s |
| Jul 11, 2026 | 4.8 s |
| Jul 18, 2026 | 5.0 s |
| Jul 25, 2026 | 5.1 s |
| Aug 1, 2026 | 5.1 s |
| Aug 8, 2026 | 5.1 s |
| Aug 15, 2026 | 5.0 s |
| Aug 22, 2026 | 4.9 s |
| Aug 29, 2026 | 4.8 s |
| Sep 5, 2026 | 4.7 s |
| Sep 12, 2026 | 4.6 s |
| Sep 19, 2026 | 4.5 s |
| Sep 26, 2026 | 4.5 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 4.3 s |
| Oct 17, 2026 | 4.2 s |
| Oct 24, 2026 | 4.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 204 ms |
| May 16, 2026 | 205 ms |
| May 23, 2026 | 207 ms |
| May 30, 2026 | 210 ms |
| Jun 6, 2026 | 209 ms |
| Jun 13, 2026 | 211 ms |
| Jun 20, 2026 | 211 ms |
| Jun 27, 2026 | 211 ms |
| Jul 4, 2026 | 216 ms |
| Jul 11, 2026 | 220 ms |
| Jul 18, 2026 | 224 ms |
| Jul 25, 2026 | 228 ms |
| Aug 1, 2026 | 229 ms |
| Aug 8, 2026 | 233 ms |
| Aug 15, 2026 | 237 ms |
| Aug 22, 2026 | 238 ms |
| Aug 29, 2026 | 240 ms |
| Sep 5, 2026 | 241 ms |
| Sep 12, 2026 | 238 ms |
| Sep 19, 2026 | 238 ms |
| Sep 26, 2026 | 237 ms |
| Oct 3, 2026 | 235 ms |
| Oct 10, 2026 | 233 ms |
| Oct 17, 2026 | 230 ms |
| Oct 24, 2026 | 229 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
Speed
Use efficient cache lifetimes
12.9 s · 4.5 MB153 files are served with short cache lifetimes, so returning visitors download them again (4.5 MB).
Render-blocking requests
8.7 s51 files block the first paint until they finish downloading. Deferring or inlining them could save about 8.7 s.
Reduce unused JavaScript
3.5 s · 904 KiBAbout 904 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.
Improve image delivery
1.4 s · 440 KiB13 images could be 440 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 45
45/100Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and reddit and others), adding 1.3 MB and 976 ms of main-thread time.
Reduce unused CSS
900 ms · 164 KiBAbout 164 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Google Tag Manager adds 421 ms
421 msGoogle Tag Manager costs a phone 421 ms of main-thread work and 668 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.
Legacy JavaScript
350 ms · 52 KiBPolyfills for old browsers add 52 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 384 ms. During a long task the page ignores taps.
Minify JavaScript
300 ms · 60 KiB60 KiB could be saved by minifying JavaScript.
1,519 HTML elements
The page has 1,519 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 49 ms
49 msYour server sent the HTML in 49 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 4.0 s
4.0 sReal visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
First Contentful Paint: 13.5 s
13.5 sThe first text or image appears after 13.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 29.2 s
29.2 sYour largest element takes 29.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Michael & Patricia Doiron Halifax, NS See all winners Winne…”.
Time to Interactive: 29.6 s
29.6 sThe page becomes fully interactive after 29.6 s. Good is under 3.8 s.
Speed Index: 13.5 s
13.5 sVisually, the page fills in at 13.5 s (Speed Index). Good is under 3.4 s.
Real-user INP: 253 ms
253 msReal visitors wait 253 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 416 ms
416 msScripts block taps and scrolling for 416 ms in total while the page loads. Good is under 200 ms.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 204 ms to 229 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.2 s to 4.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user TTFB: 780 ms
780 msReal visitors wait 780 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.024
0.024The layout barely moves while loading (CLS 0.024, good is under 0.1).
Images and page weight
Page weight: 6.7 MB in 257 requests
6.7 MBYour homepage downloads 6.7 MB in 257 requests on a phone: images 3.1 MB (89), scripts 2.6 MB (70) and fonts 665 KiB (8). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
1793393584617.png weighs 659 KiB. On a phone connection a single image that size takes seconds.
12 images in older formats
12 images (1.3 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.
5 images below the first screen load straight away
5 images further down the page (933 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
47 KiB1 image is downloaded at several times the size a phone draws it, for example safari_browser_icon.png at 300 px wide, shown at 40 px. Resized copies would save about 47 KiB.
About 1.9 g of CO₂ per visit
1.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.89 g of CO₂e: 227.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Interactive controls must not be nested (4 elements)
Interactive controls must not be nested: 4 elements on the page fail this check, rated serious 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.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 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 (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Main landmark should not be contained in another landmark (1 element)
Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3 and h1 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 55 images in the HTML carry an alt attribute.
46 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: 46 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (4 characters)
Your title is only 4 characters: “Home”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
5 H1 headlines
There are 5 <h1> headlines (“Are you a winner?”, “Giving Back” and “About Atlantic Lottery”). One clear main headline is easier for people and search engines.
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.
Invalid hreflang
Your hreflang tags are invalid, so Google may show the wrong language version.
223 internal links, 8 external
The homepage links to 223 pages on alc.ca and 8 external pages.
5 checks passed
Meta description: 131 characters
Your meta description is 131 characters: “Visit alc.ca today to buy lottery tickets online, get the latest winning numbers, play games and more. Safe, regulated,…”.
Canonical URL set
The canonical URL is https://www.alc.ca/content/alc/en.html.
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.alc.ca/sitemap.xml.
AI search readiness
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.alc.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 (833 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.alc.ca/content/alc/en.html and https://www.alc.ca/content/alc/en/play-online.html all use the title “Home”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.alc.ca/content/alc/en/referenced-content/external/help-redirect.html and https://www.alc.ca/content/alc/en/corporate/about-atlantic-lottery/contact-us.html have no meta description, so Google writes the search snippet from whatever text it finds.
11 links to non-canonical URLs
Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://www.alc.ca/content/alc/en/play-online.html, whose canonical is https://www.alc.ca/content/alc/en.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.alc.ca/content/alc/en/referenced-content/external/help-redirect.html has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.alc.ca/content/alc/en/referenced-content/external/help-redirect.html has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
5 pages slow to respond
https://www.alc.ca/content/alc/en/referenced-content/external/help-redirect.html, https://www.alc.ca/content/alc/en/play-online/lotto649.html, https://www.alc.ca/content/alc/en/play-online/dailygrand.html, https://www.alc.ca/content/alc/en/play-online/lotto.html and https://www.alc.ca/content/alc/en/play-online/casino.html took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 80 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.
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
1 broken image
1 image failed to load on a phone, for example https://www.alc.ca/content/alc/en/rewards.img.png.
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
47 of 52 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
About 352 words of copy
The homepage carries about 352 words of visible text.
4 checks passed
10 calls to action
The homepage has 10 calls to action, for example “Contact Us”, “Get your ticket” and “Learn More”.
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag and 5 mores (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.
26 cookies set on arrival
26Opening the homepage sets 26 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.
38 other companies contacted
Loading the homepage contacts 38 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 alc.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
- Vue.js
- Hosting
- Playsphere
Company
- Founded
- 1976
- Headquarters
- Moncton
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 57 issues on alc.ca, including 23 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.