Website review, no card needed
lakeshorelearning.com website review
Visit site (opens in a new tab)Reviewed 3 November 202646 issues · 88 checks
This review found 46 issues worth fixing on lakeshorelearning.com, 19 of them high impact, across 88 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 147 ms |
| May 23, 2026 | 154 ms |
| May 30, 2026 | 159 ms |
| Jun 6, 2026 | 163 ms |
| Jun 13, 2026 | 163 ms |
| Jun 20, 2026 | 163 ms |
| Jun 27, 2026 | 162 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 160 ms |
| Jul 18, 2026 | 158 ms |
| Jul 25, 2026 | 161 ms |
| Aug 1, 2026 | 162 ms |
| Aug 8, 2026 | 162 ms |
| Aug 15, 2026 | 161 ms |
| Aug 22, 2026 | 160 ms |
| Aug 29, 2026 | 160 ms |
| Sep 5, 2026 | 161 ms |
| Sep 12, 2026 | 164 ms |
| Sep 19, 2026 | 169 ms |
| Sep 26, 2026 | 169 ms |
| Oct 3, 2026 | 164 ms |
| Oct 10, 2026 | 162 ms |
| Oct 17, 2026 | 160 ms |
| Oct 24, 2026 | 158 ms |
| Oct 31, 2026 | 156 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.5 s
1.0 s
1.5 s
2.0 s
2.4 s
2.9 s
3.4 s
3.9 s
Speed
Use efficient cache lifetimes
2.2 s · 731 KiB43 files are served with short cache lifetimes, so returning visitors download them again (731 KiB).
audioeye.com adds 1.8 s
1.8 saudioeye.com costs a phone 1.8 s of main-thread work and 310 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.
Render-blocking requests
1.6 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Reduce unused JavaScript
1.1 s · 364 KiBAbout 364 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Main-thread work: 5.0 s
A phone's processor spends 5.0 s on main-thread work while loading, 3.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,654 HTML elements
The page has 3,654 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (audioeye.com, Dynamic Yield and Optanon and others), adding 934 KiB and 2.1 s of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
740 ms · 190 KiBAbout 190 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 740 ms faster on a phone.
Improve image delivery
350 ms · 354 KiB7 images could be 354 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Legacy JavaScript
500 ms · 46 KiBPolyfills for old browsers add 46 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 500 ms faster on a phone.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 171 ms. During a long task the page ignores taps.
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
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.27
0.27For real visitors the layout shifts by 0.27 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 12.9 s
12.9 sYour largest element takes 12.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Our website uses third-party technology for targeted advert…”.
Time to Interactive: 14.8 s
14.8 sThe page becomes fully interactive after 14.8 s. Good is under 3.8 s.
Speed Index: 9.6 s
9.6 sVisually, the page fills in at 9.6 s (Speed Index). Good is under 3.4 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 352 ms
352 msScripts block taps and scrolling for 352 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.125
0.125The layout shifts by 0.125 while loading, so content jumps under the reader's thumb. Good is under 0.1.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 147 ms to 156 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 184 ms
184 msReal visitors wait 184 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.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 2.4 MB in 133 requests
2.4 MBYour homepage downloads 2.4 MB in 133 requests on a phone: scripts 1.1 MB (59), images 728 KiB (35) and stylesheets 199 KiB (9). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
10203574_P02_BOGO50off_XSHeroBanShrt_X1_DK 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).
3 images far larger than shown
162 KiB3 images are downloaded at several times the size a phone draws them, for example 10203574_P06_GiftsWonder_XSHero_Slider1_X4_EW at 1,500 px wide, shown at 390 px. Resized copies would save about 162 KiB.
1 image below the first screen load straight away
1 image further down the page (114 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.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.67 g of CO₂e: 80.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Invalid ARIA attributes
2 elements use ARIA attributes their role does not allow, which confuses screen readers.
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
ARIA commands must have an accessible name (1 element)
ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 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.
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.
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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 17 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 9 failed. 2 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 long (77 characters)
Your title is 77 characters, so Google will cut it off around 60: “Teacher Supply Store | Top-Quality Learning Products & Furniture | Lakeshore®”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image, 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.
243 internal links, 2 external
The homepage links to 243 pages on lakeshorelearning.com and 2 external pages.
4 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Your one-stop teacher supply store! Shop high-quality learning products & teaching resources—plus premium classroom fur…”.
Canonical URL set
The canonical URL is https://www.lakeshorelearning.com/.
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.lakeshorelearning.com/sitemap-index.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.lakeshorelearning.com/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,092 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://www.lakeshorelearning.com/quick-order 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 linked pages hidden from search
https://www.lakeshorelearning.com/rewards and https://www.lakeshorelearning.com/shopping-cart are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
1 page without a meta description
https://www.lakeshorelearning.com/products/gift-cards/N/3910126112 has no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://www.lakeshorelearning.com/furniture, https://www.lakeshorelearning.com/stores/locator, https://www.lakeshorelearning.com/resources/free-resources, https://www.lakeshorelearning.com/services, https://www.lakeshorelearning.com/registries and https://www.lakeshorelearning.com/shopping-lists and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages with very little text
https://www.lakeshorelearning.com/furniture, https://www.lakeshorelearning.com/stores/locator, https://www.lakeshorelearning.com/resources/free-resources, https://www.lakeshorelearning.com/services, https://www.lakeshorelearning.com/registries and https://www.lakeshorelearning.com/shopping-lists have 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.
7 pages slow to respond
https://www.lakeshorelearning.com/stores/locator, https://www.lakeshorelearning.com/resources/free-resources, https://www.lakeshorelearning.com/services, https://www.lakeshorelearning.com/registries, https://www.lakeshorelearning.com/products/gift-cards/N/3910126112 and https://www.lakeshorelearning.com/products/blocks-manipulatives/N/1784882785 and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 198 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.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
9 small tap targets
9 of 39 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
8 low-resolution images
8 images are served at too low a resolution for sharp phone screens.
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
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 260 words of copy
The homepage carries about 260 words of visible text.
3 checks passed
12 calls to action
The homepage has 12 calls to action, for example “Shop All”, “Shop By Category” and “Shop by Age”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 4 customer or partner logos and 1 trust badge.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Tag Manager, Meta Pixel, Microsoft Ads and TikTok Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
20 cookies set on arrival
20Opening the homepage sets 20 cookies (measured from a US location before any click).
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.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 lakeshorelearning.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- FullStory
- Hosting
- Level 3 Parent, LLC
Company
- Employees
- 3,939
- Founded
- 1954
- Headquarters
- Carson
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on lakeshorelearning.com, including 20 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.