Website review, no card needed

tafelberg.co.za logo

tafelberg.co.za website review

Visit site (opens in a new tab)Reviewed 18 November 202654 issues · 105 checks

This review found 54 issues worth fixing on tafelberg.co.za, 21 of them high impact, across 105 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
3.5 s2.2 sMay 30Nov 143.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.7 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.6 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.5 s
Aug 29, 20262.7 s
Sep 5, 20262.9 s
Sep 12, 20263.1 s
Sep 19, 20263.3 s
Sep 26, 20263.3 s
Oct 3, 20263.4 s
Oct 10, 20263.4 s
Oct 17, 20263.3 s
Oct 24, 20263.2 s
Oct 31, 20263.1 s
Nov 7, 20263.0 s
Nov 14, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
223 ms96 msMay 30Nov 14113 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026194 ms
Jun 6, 2026197 ms
Jun 13, 2026206 ms
Jun 20, 2026208 ms
Jun 27, 2026206 ms
Jul 4, 2026204 ms
Jul 11, 2026196 ms
Jul 18, 2026191 ms
Jul 25, 2026190 ms
Aug 1, 2026190 ms
Aug 8, 2026196 ms
Aug 15, 2026206 ms
Aug 22, 2026204 ms
Aug 29, 2026185 ms
Sep 5, 2026158 ms
Sep 12, 2026126 ms
Sep 19, 2026113 ms
Sep 26, 2026116 ms
Oct 3, 2026118 ms
Oct 10, 2026118 ms
Oct 17, 2026115 ms
Oct 24, 2026112 ms
Oct 31, 2026111 ms
Nov 7, 2026112 ms
Nov 14, 2026113 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 tafelberg.co.za (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tafelberg.co.za at 0.9 s0.9 s
  2. tafelberg.co.za at 1.9 s1.9 s
  3. tafelberg.co.za at 2.8 s2.8 s
  4. tafelberg.co.za at 3.7 s3.7 s
  5. tafelberg.co.za at 4.6 s4.6 s
  6. tafelberg.co.za at 5.5 s5.5 s
  7. tafelberg.co.za at 6.5 s6.5 s
  8. tafelberg.co.za at 7.4 s7.4 s

Speed

14 to fix40
  • Render-blocking requests

    6.2 s

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

  • Reduce unused JavaScript

    4.3 s · 1.2 MB

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

  • Use efficient cache lifetimes

    2.7 s · 539 KiB

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

  • Mobile performance score: 40

    40/100

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

  • 6,040 HTML elements

    The page has 6,040 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 (jQuery CDN, Google Tag Manager and ZenDesk and others), adding 2.7 MB and 1.4 s of main-thread time.

  • Improve image delivery

    750 ms · 340 KiB

    8 images could be 340 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

  • Reduce unused CSS

    640 ms · 126 KiB

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

  • Main-thread work: 3.8 s

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

  • jQuery CDN adds 365 ms

    365 ms

    jQuery CDN costs a phone 365 ms of main-thread work and 39 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 271 ms

    271 ms

    Google Tag Manager costs a phone 271 ms of main-thread work and 599 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 CDN adds 230 ms

    230 ms

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

  • ZenDesk adds 244 ms

    244 ms

    ZenDesk costs a phone 244 ms of main-thread work and 477 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 Maps adds 111 ms

    111 ms

    Google Maps costs a phone 111 ms of main-thread work and 418 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.

  • Legacy JavaScript

    150 ms · 27 KiB

    Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 12 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Minify JavaScript

    6 KiB

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

1 checks passed
  • Server response: 512 ms

    512 ms

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

Core Web Vitals

12 to fix33
  • 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.

  • Largest Contentful Paint: 16.4 s

    16.4 s

    Your largest element takes 16.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “LG ELECTRONICS Shop LG”.

  • Time to Interactive: 27.3 s

    27.3 s

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

  • First Contentful Paint: 6.9 s

    6.9 s

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

  • Speed Index: 9.2 s

    9.2 s

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

  • Real-user LCP: 3.7 s

    3.7 s

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

  • Real-user CLS: 0.16

    0.16

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

  • 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: 942 ms

    942 ms

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

  • Cumulative Layout Shift: 0.2

    0.2

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

  • Total Blocking Time: 322 ms

    322 ms

    Scripts block taps and scrolling for 322 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.

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

    +17%

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

2 checks passed
  • Real-user INP: 152 ms

    152 ms

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

  • Tap response (INP) got 42% faster for real visitors

    -42%

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

Images and page weight

3 to fix60
  • Page weight: 5.1 MB in 184 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 184 requests on a phone: scripts 2.5 MB (62), images 986 KiB (73) and fonts 819 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    snomaster-5-in-1-slushie-machine-smic-18-01_yx6i.png 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).

  • 2 images far larger than shown

    137 KiB

    2 images are downloaded at several times the size a phone draws them, for example 1070x375-promo-site-banner-l1ujvl.jpg at 2,000 px wide, shown at 360 px. Resized copies would save about 137 KiB.

  • 5 images below the first screen load straight away

    5 images further down the page (219 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.5 g of CO₂ per visit

    1.46 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.46 g of CO₂e: 174.9 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

15 to fixGoogle 7182
  • Invalid ARIA attributes

    2 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (2 elements)

    Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

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

  • ARIA input fields must have an accessible name (7 elements)

    ARIA input fields must have an accessible name: 7 elements on the page fail this check, rated serious by axe-core.

  • 7 text elements with low contrast

    7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Interactive controls must not be nested (7 elements)

    Interactive controls must not be nested: 7 elements on the page fail this check, rated serious by axe-core.

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (8 elements)

    All page content should be contained by landmarks: 8 elements on the page fail 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 9 form fields without a label

    9 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4, h1 → h3 and h2 → h4), 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. (1 element).

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("//media.tafelberg.co.za/stores/za.co.storefront7.tafelb…”.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 658 internal links, 6 external

    The homepage links to 658 pages on tafelberg.co.za and 6 external pages.

7 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “Tafelberg Furniture Stores (Pty) Ltd. is the largest independent furniture and appliance retailer in the Western Cape, …”.

  • One H1 headline

    Your main headline reads: “Tafelberg Furnishers”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Furniture and Appliance Retailer | Tafelberg Furnishers”.

  • Canonical URL set

    The canonical URL is https://www.tafelberg.co.za/home.

  • 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://www.tafelberg.co.za/sitemap.xml.

AI search readiness

100
  • Opted out of AI training for 3 crawlers

    robots.txt blocks GPTBot, ClaudeBot and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.tafelberg.co.za/llms.txt (2 KiB, 6 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix85
  • 3 pages without a meta description

    https://www.tafelberg.co.za/blog, https://www.tafelberg.co.za/faq and https://www.tafelberg.co.za/find-a-store have no meta description, so Google writes the search snippet from whatever text it finds.

  • 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.tafelberg.co.za/general-enquiries, whose canonical is https://www.tafelberg.co.za/contact. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 9 pages without an H1

    https://www.tafelberg.co.za/find-a-store, https://www.tafelberg.co.za/major-appliances, https://www.tafelberg.co.za/major-appliances/laundry, https://www.tafelberg.co.za/major-appliances/laundry/washing-machines, https://www.tafelberg.co.za/major-appliances/laundry/washing-machines/front-loaders and https://www.tafelberg.co.za/major-appliances/laundry/washing-machines/top-loaders and 3 others 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 197 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7791
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://media.tafelberg.co.za/stores/za.co.storefront7.tafelberg/themes/Chronos/81c4a778-f…”.

2 checks passed
  • Tap targets are thumb-sized

    294 of 303 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • 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 1,155 words of copy

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop by Category” and “CONTACT”.

  • 25 calls to action

    The homepage has 25 calls to action, for example “Contact”, “Shop by Category” and “LG ELECTRONICS Shop LG”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and 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.

  • 5 cookies set on arrival

    5

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

  • 25 other companies contacted

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

Upkeep, stack and company

Stack

CMS
OrderEazi CMS
Framework
jQuery
Analytics
Google Tag Manager
Hosting
InMotion Hosting, Inc.

Hiring

Hiring
4 open roles
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 54 issues on tafelberg.co.za, including 26 speed issues, 2 SEO issues and 2 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