Website review, no card needed

teppermans.com logo

teppermans.com website review

Visit site (opens in a new tab)Reviewed 31 October 202641 issues · 81 checks

This review found 41 issues worth fixing on teppermans.com, 18 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. 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
4.3 s3.7 sMay 9Oct 244.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.2 s
May 16, 20264.1 s
May 23, 20264.0 s
May 30, 20263.9 s
Jun 6, 20263.9 s
Jun 13, 20263.9 s
Jun 20, 20264.0 s
Jun 27, 20263.9 s
Jul 4, 20264.0 s
Jul 11, 20263.9 s
Jul 18, 20263.9 s
Jul 25, 20263.8 s
Aug 1, 20263.8 s
Aug 8, 20263.8 s
Aug 15, 20263.8 s
Aug 22, 20263.8 s
Aug 29, 20263.9 s
Sep 5, 20263.9 s
Sep 12, 20264.0 s
Sep 19, 20264.0 s
Sep 26, 20264.1 s
Oct 3, 20264.1 s
Oct 10, 20264.2 s
Oct 17, 20264.2 s
Oct 24, 20264.2 s
Real-visitor tap response (INP)75th percentile, phones
218 ms131 msMay 9Oct 24206 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026153 ms
May 16, 2026146 ms
May 23, 2026142 ms
May 30, 2026141 ms
Jun 6, 2026146 ms
Jun 13, 2026153 ms
Jun 20, 2026159 ms
Jun 27, 2026164 ms
Jul 4, 2026168 ms
Jul 11, 2026168 ms
Jul 18, 2026166 ms
Jul 25, 2026164 ms
Aug 1, 2026163 ms
Aug 8, 2026165 ms
Aug 15, 2026169 ms
Aug 22, 2026171 ms
Aug 29, 2026171 ms
Sep 5, 2026174 ms
Sep 12, 2026177 ms
Sep 19, 2026180 ms
Sep 26, 2026189 ms
Oct 3, 2026198 ms
Oct 10, 2026204 ms
Oct 17, 2026208 ms
Oct 24, 2026206 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 teppermans.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. teppermans.com at 0.5 s0.5 s
  2. teppermans.com at 1.0 s1.0 s
  3. teppermans.com at 1.4 s1.4 s
  4. teppermans.com at 1.9 s1.9 s
  5. teppermans.com at 2.4 s2.4 s
  6. teppermans.com at 2.9 s2.9 s
  7. teppermans.com at 3.3 s3.3 s
  8. teppermans.com at 3.8 s3.8 s

Speed

13 to fix6
  • Use efficient cache lifetimes

    7.7 s · 2.4 MB

    44 files are served with short cache lifetimes, so returning visitors download them again (2.4 MB).

  • Render-blocking requests

    7.5 s

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

  • Reduce unused JavaScript

    3.3 s · 1.6 MB

    About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.

  • Improve image delivery

    1.6 s · 509 KiB

    5 images could be 509 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

  • Reduce unused CSS

    1.1 s · 241 KiB

    About 241 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 6

    6/100

    Your mobile performance score is 6. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.4 s

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

  • 3,187 HTML elements

    The page has 3,187 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 (Google Tag Manager, Facebook and rlets.com and others), adding 1.3 MB and 1.5 s of main-thread time.

  • Google Tag Manager adds 622 ms

    622 ms

    Google Tag Manager costs a phone 622 ms of main-thread work and 680 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.

  • Facebook adds 322 ms

    322 ms

    Facebook costs a phone 322 ms of main-thread work and 311 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.

  • rlets.com adds 289 ms

    289 ms

    rlets.com costs a phone 289 ms of main-thread work and 108 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.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 251 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).

  • Legacy JavaScript

    34 KiB

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

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 30 ms

    30 ms

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

Core Web Vitals

14 to fix0
  • 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: 1.14

    1.14

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

  • First Contentful Paint: 7.8 s

    7.8 s

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

  • Largest Contentful Paint: 15.3 s

    15.3 s

    Your largest element takes 15.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner Oct W1a @1.5x”.

  • Time to Interactive: 24.6 s

    24.6 s

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

  • Cumulative Layout Shift: 1.125

    1.125

    The layout shifts by 1.125 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 9.0 s

    9.0 s

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

  • Total Blocking Time: 1.4 s

    1.4 s

    Scripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 3.9 s

    3.9 s

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

  • Real-user INP: 209 ms

    209 ms

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

  • Tap response (INP) got 38% slower for real visitors

    +38%

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

  • Real-user FCP: 2.9 s

    2.9 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) held steady for real visitors

    +1%

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

Images and page weight

1 to fix33
  • Page weight: 4.5 MB in 121 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 121 requests on a phone: scripts 2.4 MB (35), images 1.3 MB (32) and fonts 456 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • About 1.3 g of CO₂ per visit

    1.27 g

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

Accessibility

3 to fixGoogle 9588
  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (8 elements).

1 checks passed
  • 10 automated accessibility rules passed

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

SEO

2 to fixGoogle 10090
  • Title is long (74 characters)

    Your title is 74 characters, so Google will cut it off around 60: “Shop Furniture, Mattresses, Electronics & Appliances Ontario | Tepperman’s”.

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 395 internal links, 5 external

    The homepage links to 395 pages on teppermans.com and 5 external pages.

6 checks passed
  • Meta description: 133 characters

    Your meta description is 133 characters: “Tepperman’s offers furniture, mattresses & appliances across Ontario—Windsor, London, Chatham, Sarnia, Niagara, Hamilto…”.

  • One H1 headline

    Your main headline reads: “get home happy.”.

  • Canonical URL set

    The canonical URL is https://www.teppermans.com/.

  • Structured data in place

    Structured data found: FurnitureStore and WebSite.

  • 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.teppermans.com/sitemap_www.teppermans.com_Index.xml.

AI search readiness

1 to fix83
  • 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.

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.

  • llms.txt published

    The site publishes https://www.teppermans.com/llms.txt (3 KiB, 18 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.teppermans.com/financing, whose canonical is https://www.teppermans.com/financing-credit. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://www.teppermans.com/google-reviews and https://www.teppermans.com/blog/teppermans-your-trusted-canadian-retailer have 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 199 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

1 to fixGoogle 7396
  • 9 third-party cookies

    9 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

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

3 to fix71
  • 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.

  • About 1,741 words of copy

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

4 checks passed
  • 28 calls to action

    The homepage has 28 calls to action, for example “Register”, “| Shop Now |” and “| Learn More”.

  • 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: 1 testimonial or review block and a star rating.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (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

    7

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

  • 4 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
Akamai

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on teppermans.com, including 27 speed issues, 2 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

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