Website review, no card needed
lakeshore.edu website review
Visit site (opens in a new tab)Reviewed 1 November 202643 issues · 85 checks
This review found 43 issues worth fixing on lakeshore.edu, 16 of them high impact, across 85 checks. The most urgent: improve image delivery. 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
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.1 s |
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 91 ms |
| May 16, 2026 | 88 ms |
| May 23, 2026 | 89 ms |
| May 30, 2026 | 89 ms |
| Jun 6, 2026 | 88 ms |
| Jun 13, 2026 | 89 ms |
| Jun 20, 2026 | 87 ms |
| Jun 27, 2026 | 86 ms |
| Jul 4, 2026 | 86 ms |
| Jul 11, 2026 | 86 ms |
| Jul 18, 2026 | 87 ms |
| Jul 25, 2026 | 87 ms |
| Aug 1, 2026 | 89 ms |
| Aug 8, 2026 | 90 ms |
| Aug 15, 2026 | 91 ms |
| Aug 22, 2026 | 92 ms |
| Aug 29, 2026 | 95 ms |
| Sep 5, 2026 | 100 ms |
| Sep 12, 2026 | 103 ms |
| Sep 19, 2026 | 104 ms |
| Sep 26, 2026 | 106 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 105 ms |
| Oct 17, 2026 | 107 ms |
| Oct 24, 2026 | 111 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
Improve image delivery
4.0 s · 1.0 MB13 images could be 1.0 MB 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.
Use efficient cache lifetimes
3.7 s · 893 KiB195 files are served with short cache lifetimes, so returning visitors download them again (893 KiB).
Reduce unused JavaScript
3.6 s · 639 KiBAbout 639 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.
Mobile performance score: 33
33/100Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Render-blocking requests
800 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.7 MB and 533 ms of main-thread time.
Reduce unused CSS
450 ms · 93 KiBAbout 93 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Minify JavaScript
450 ms · 78 KiB78 KiB could be saved by minifying JavaScript.
Google Tag Manager adds 278 ms
278 msGoogle Tag Manager costs a phone 278 ms of main-thread work and 555 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.
eab.com adds 14 ms
14 mseab.com costs a phone 14 ms of main-thread work and 650 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 115 ms. During a long task the page ignores taps.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 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.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 801 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 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 CLS: 0.76
0.76For real visitors the layout shifts by 0.76 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 24.9 s
24.9 sYour largest element takes 24.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Apply Now It’s always a good day to come to Lakeshore APPLY…”.
Time to Interactive: 25.1 s
25.1 sThe page becomes fully interactive after 25.1 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.763
0.763The layout shifts by 0.763 while loading, so content jumps under the reader's thumb. Good is under 0.1.
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.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 91 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
20 images without width and height
20 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 134 ms
134 msReal visitors wait 134 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 745 ms
745 msReal visitors wait 745 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 185 ms
185 msScripts block the page for only 185 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.2 MB in 296 requests
4.2 MBYour homepage downloads 4.2 MB in 296 requests on a phone: scripts 2.0 MB (239), images 1.8 MB (29) and fonts 215 KiB (2). Under 2 MB keeps phones on slow connections fast.
6 images far larger than shown
611 KiB6 images are downloaded at several times the size a phone draws them, for example enrollment_banner_v3.webp at 3,840 px wide, shown at 390 px. Resized copies would save about 611 KiB.
An image on the first screen is lazy-loaded
enrollment_banner_v3.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
8 images in older formats
8 images (698 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.
3 images below the first screen load straight away
3 images further down the page (233 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.19 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.19 g of CO₂e: 143.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
1 checks passed
42 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: 42 passed and 2 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (17 characters)
Your title is only 17 characters: “Lakeshore College”. 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.
Meta description is long (180 characters)
Your meta description is 180 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
92 internal links, 14 external
The homepage links to 92 pages on lakeshore.edu and 14 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://lakeshore.edu/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://lakeshore.edu/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://lakeshore.edu/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 (512 words), so crawlers that don't run JavaScript still read it.
Other pages
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://lakeshore.edu/academics/descriptions/competency-based-education, whose canonical is https://lakeshore.edu/future-students/flexible-learning-options/competency-based-education. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://lakeshore.edu/lennys-leap has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 80 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.
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 15 pages that loaded have a <title>.
Best practices
7 small tap targets
7 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “$ is not a function”.
1 checks passed
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.
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: 1 trust badge. 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 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 381 words of copy
The homepage carries about 381 words of visible text.
5 checks passed
10 calls to action
The homepage has 10 calls to action, for example “Apply for Financial Aid”, “Contact Information” and “Apply Now”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics, Meta Pixel and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel 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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
26 other companies contacted
Loading the homepage contacts 26 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 lakeshore.edu, 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
- Framework
- jQuery
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- Fastly
Hiring
- Hiring
- 95 open roles
- Job board
- smartrecruiters
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on lakeshore.edu, including 19 speed issues, 6 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.