Website review, no card needed

tvolearn.com logo

tvolearn.com website review

Visit site (opens in a new tab)Reviewed 10 November 202638 issues · 83 checks

This review found 38 issues worth fixing on tvolearn.com, 13 of them high impact, across 83 checks. The most urgent: render-blocking requests. 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.2 s423 msMay 23Nov 7805 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026510 ms
May 30, 2026631 ms
Jun 6, 2026785 ms
Jun 13, 20261.0 s
Jun 20, 20261.1 s
Jun 27, 20261.0 s
Jul 4, 2026929 ms
Jul 11, 2026852 ms
Jul 18, 2026869 ms
Jul 25, 2026879 ms
Aug 1, 2026874 ms
Aug 8, 2026960 ms
Aug 15, 2026956 ms
Aug 22, 2026964 ms
Aug 29, 2026945 ms
Sep 5, 2026871 ms
Sep 12, 2026729 ms
Sep 19, 2026732 ms
Sep 26, 2026747 ms
Oct 3, 2026771 ms
Oct 10, 2026838 ms
Oct 17, 2026836 ms
Oct 24, 2026821 ms
Oct 31, 2026799 ms
Nov 7, 2026805 ms
Real-visitor tap response (INP)75th percentile, phones
118 ms92 msMay 23Nov 7104 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026101 ms
May 30, 2026101 ms
Jun 6, 2026104 ms
Jun 13, 2026105 ms
Jun 20, 2026106 ms
Jun 27, 2026109 ms
Jul 4, 2026110 ms
Jul 11, 2026108 ms
Jul 18, 2026112 ms
Jul 25, 2026113 ms
Aug 1, 2026112 ms
Aug 8, 2026115 ms
Aug 15, 2026113 ms
Aug 22, 2026112 ms
Aug 29, 2026108 ms
Sep 5, 2026103 ms
Sep 12, 202695 ms
Sep 19, 202696 ms
Sep 26, 202696 ms
Oct 3, 2026102 ms
Oct 10, 2026107 ms
Oct 17, 2026108 ms
Oct 24, 2026108 ms
Oct 31, 2026105 ms
Nov 7, 2026104 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 tvolearn.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tvolearn.com at 0.4 s0.4 s
  2. tvolearn.com at 0.9 s0.9 s
  3. tvolearn.com at 1.3 s1.3 s
  4. tvolearn.com at 1.8 s1.8 s
  5. tvolearn.com at 2.2 s2.2 s
  6. tvolearn.com at 2.7 s2.7 s
  7. tvolearn.com at 3.1 s3.1 s
  8. tvolearn.com at 3.6 s3.6 s

Speed

8 to fix66
  • Render-blocking requests

    2.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and shgcdn2.com and others), adding 1.6 MB and 1.1 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 692 KiB

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

  • Mobile performance score: 66

    66/100

    Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    500 ms · 107 KiB

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

  • Google CDN adds 360 ms

    360 ms

    Google CDN costs a phone 360 ms of main-thread work and 740 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.

  • Google Tag Manager adds 367 ms

    367 ms

    Google Tag Manager costs a phone 367 ms of main-thread work and 552 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.8 s

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

  • Reduce unused CSS

    150 ms · 57 KiB

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

  • Improve image delivery

    204 KiB

    2 images could be 204 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 9 long tasks on the main thread

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

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 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.

1 checks passed
  • Server response: 5 ms

    5 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 19.3 s

    19.3 s

    The page becomes fully interactive after 19.3 s. Good is under 3.8 s.

  • Largest Contentful Paint: 5.8 s

    5.8 s

    Your largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 6.9 s

    6.9 s

    Visually, the page fills in at 6.9 s (Speed Index). Good is under 3.4 s.

  • Largest content (LCP) got 41% slower for real visitors

    +41%

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

  • Total Blocking Time: 276 ms

    276 ms

    Scripts block taps and scrolling for 276 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) held steady for real visitors

    +3%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 101 ms to 104 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.1 s

    1.1 s

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

  • Real-user INP: 100 ms

    100 ms

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

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 323 ms

    323 ms

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.003

    0.003

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

Images and page weight

2 to fix75
  • Page weight: 3.8 MB in 180 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 180 requests on a phone: scripts 1.7 MB (53), other files 1.0 MB (90) and images 679 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    156 KiB

    2 images are downloaded at several times the size a phone draws them, for example lighter at 2,060 px wide, shown at 308 px. Resized copies would save about 156 KiB.

  • 1 image in older formats

    1 image (131 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.

  • About 1.1 g of CO₂ per visit

    1.07 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

9 to fixGoogle 7487
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • Positive tabindex

    2 elements have a tabindex above 0, which scrambles the keyboard order.

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • 4 links without text

    4 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 8594
  • Structured data has 1 problem

    Structured data found (EducationalOrganization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://tvolearn.com{{ routes.search_url }…”.

  • 5 links with vague text

    5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 66 internal links, 18 external

    The homepage links to 66 pages on tvolearn.com and 18 external pages.

7 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Support your child's learning with straightforward, engaging and free resources that align with the Ontario curriculum,…”.

  • One H1 headline

    Your main headline reads: “Learning Resources You Can Count On”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Learn at Home Resources for K to Grade 12 Students | TVO Learn”.

  • Canonical URL set

    The canonical URL is https://tvolearn.com/.

  • 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://tvolearn.com/sitemap.xml.

AI search readiness

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (906 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://tvolearn.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix81
  • 2 pages share a title

    https://tvolearn.com/pages/kindergarten and https://tvolearn.com/collections/courses all use the title “Activities | TVO Learn”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://tvolearn.com/pages/kindergarten and https://tvolearn.com/collections/courses use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://tvolearn.com/pages/kindergarten, whose canonical is https://tvolearn.com/collections/courses. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://tvolearn.com/pages/letter-recognition has no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 internal pages checked

    We fetched 14 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 14 pages we checked loaded without an error.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9291
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Swiper container not found.”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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.

  • A 8-field form

    Your longest form asks for 8 fields (0 required). Every extra field lowers completion.

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

    The homepage carries about 569 words of visible text.

2 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Learn More”, “Start Kindergarten Learning” and “Subscribe”.

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

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 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.

  • 23 other companies contacted

    Loading the homepage contacts 23 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 tvolearn.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Geolizr · weglot.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on tvolearn.com, including 14 speed issues, 2 SEO issues and 4 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