Website review, no card needed
lambtoncollege.ca website review
Visit site (opens in a new tab)Reviewed 19 November 202635 issues · 87 checks
This review found 35 issues worth fixing on lambtoncollege.ca, 9 of them high impact, across 87 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
88BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.4 s |
| Nov 7, 2026 | 1.3 s |
| Nov 14, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 142 ms |
| Jun 6, 2026 | 145 ms |
| Jun 13, 2026 | 149 ms |
| Jun 20, 2026 | 150 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 147 ms |
| Jul 11, 2026 | 144 ms |
| Jul 18, 2026 | 146 ms |
| Jul 25, 2026 | 152 ms |
| Aug 1, 2026 | 159 ms |
| Aug 8, 2026 | 163 ms |
| Aug 15, 2026 | 171 ms |
| Aug 22, 2026 | 170 ms |
| Aug 29, 2026 | 169 ms |
| Sep 5, 2026 | 165 ms |
| Sep 12, 2026 | 156 ms |
| Sep 19, 2026 | 158 ms |
| Sep 26, 2026 | 163 ms |
| Oct 3, 2026 | 178 ms |
| Oct 10, 2026 | 191 ms |
| Oct 17, 2026 | 196 ms |
| Oct 24, 2026 | 188 ms |
| Oct 31, 2026 | 178 ms |
| Nov 7, 2026 | 171 ms |
| Nov 14, 2026 | 166 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Use efficient cache lifetimes
1.4 s · 845 KiB32 files are served with short cache lifetimes, so returning visitors download them again (845 KiB).
Render-blocking requests
1.0 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 895 KiB and 1.2 s of main-thread time.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
977 KiB6 images could be 977 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
540 ms · 379 KiBAbout 379 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 540 ms faster on a phone.
Google Tag Manager adds 502 ms
502 msGoogle Tag Manager costs a phone 502 ms of main-thread work and 365 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
420 ms · 72 KiBAbout 72 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 420 ms faster on a phone.
Facebook adds 282 ms
282 msFacebook costs a phone 282 ms of main-thread work and 222 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.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 267 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 8 KiB8 KiB could be saved by minifying JavaScript.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 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.
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: 45 ms
45 msYour server sent the HTML in 45 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 16.4 s
16.4 sThe page becomes fully interactive after 16.4 s. Good is under 3.8 s.
First Contentful Paint: 4.4 s
4.4 sThe first text or image appears after 4.4 s on a phone. Good is under 1.8 s.
Speed Index: 7.6 s
7.6 sVisually, the page fills in at 7.6 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.4 s
4.4 sYour largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies on this site to enhance your user experience…”. Most of its time is element render delay (2.4 s).
Total Blocking Time: 403 ms
403 msScripts block taps and scrolling for 403 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 142 ms to 166 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 160 ms
160 msReal visitors wait 160 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 656 ms
656 msReal visitors wait 656 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 21.4 MB in 85 requests
21.4 MBYour homepage downloads 21.4 MB in 85 requests on a phone: media 18.4 MB (1), images 1.5 MB (17) and scripts 1.0 MB (23). Under 2 MB keeps phones on slow connections fast.
9 images far larger than shown
1.1 MB9 images are downloaded at several times the size a phone draws them, for example d-person.webp at 5,760 px wide, shown at 390 px. Resized copies would save about 1.1 MB.
9 images below the first screen load straight away
9 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
6 images in older formats
6 images (414 KiB) 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.
About 6.1 g of CO₂ per visit
6.07 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.07 g of CO₂e: 728.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 25 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
99 internal links, 8 external
The homepage links to 99 pages on lambtoncollege.ca and 8 external pages.
8 checks passed
Meta description: 119 characters
Your meta description is 119 characters: “Discover hands-on programs, career-driven learning, and a supportive community to help you prepare for what comes next.”.
One H1 headline
Your main headline reads: “Discover what's possible”.
Title: 42 characters
Your title is a healthy 42 characters: “Your Path to What's Next | Lambton College”.
Canonical URL set
The canonical URL is https://www.lambtoncollege.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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.lambtoncollege.ca/sitemap/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.lambtoncollege.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 (641 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.lambtoncollege.ca/international is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages share 2 titles
https://www.lambtoncollege.ca/programs/programs and https://www.lambtoncollege.ca/programs/program-options all use the title “Program Options and Credentials to Fit Your Goals | Lambton College”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.lambtoncollege.ca/event-calendar/event/2026/12/09/default-calendar/application-night-dec-2026 has no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://www.lambtoncollege.ca/programs/programs and https://www.lambtoncollege.ca/programs/program-options use the same meta description. A description written for each page earns more clicks.
8 links to non-canonical URLs
Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://www.lambtoncollege.ca/privacy-policy, whose canonical is https://www.lambtoncollege.ca/about-lambton-college/policies/details/2000-7-1-confidentiality-privacy-of-information-records. 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 91 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.
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
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
23 of 25 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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: 4 testimonial or review blocks. 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.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 395 words of copy
The homepage carries about 395 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Join us for Application Night on Dec 9”.
8 calls to action
The homepage has 8 calls to action, for example “Apply”, “Join us for Application Night on Dec 9” and “Request Information”.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 2 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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
18 other companies contacted
Loading the homepage contacts 18 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 lambtoncollege.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
- Hosting
- Lambton College of Applied Arts and Technology
Company
- Founded
- 1969
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on lambtoncollege.ca, including 17 speed 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.