masterteacher.com website review

Your mobile performance score is 64 (desktop: 63). Pages that score under 90 lose visitors before the first paint.

10 images could be 195 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.

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

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

The page has 1,661 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

LiveChat costs a phone 65 ms of main-thread work and 366 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.

8 third-party services load with your homepage (Klaviyo, LiveChat and Shopify and others), adding 747 KiB and 250 ms of main-thread time.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

About 23 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need.

6 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

The first text or image appears after 2.3 s on a phone. Good is under 1.8 s.

Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 105 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 9.6 MB in 303 requests on a phone: media 6.2 MB (1), scripts 1,017 KiB (109) and other files 951 KiB (129). Under 2 MB keeps phones on slow connections fast.

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

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.

Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

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

Your meta description is 230 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (WebSite) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected token ',', ..."rteacher",,"https:\/"... is not va)”.

The homepage links to 98 pages on masterteacher.com and 22 external pages.

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.

https://www.masterteacher.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.masterteacher.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.masterteacher.com/customer_authentication/redirect, https://www.masterteacher.com/products/teacher-pd-bundle, https://www.masterteacher.com/products/paraeducator-online-courses, https://www.masterteacher.com/products/the-master-teacher-weekly-pd-program, https://www.masterteacher.com/products/behavior-bundle and https://www.masterteacher.com/products/teacher-elearning-bundle and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.masterteacher.com/pages/elearning-webinar, https://www.masterteacher.com/pages/ctepathway and https://www.masterteacher.com/collections/autism use the same meta description. A description written for each page earns more clicks.

https://www.masterteacher.com/customer_authentication/redirect, https://www.masterteacher.com/pages/ctepathway and https://www.masterteacher.com/collections/autism have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.

10 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,810 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and LinkedIn Insight and 3 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.

Opening the homepage sets 19 cookies, 4 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.