Website review, no card needed

torgaoptical.co.za logo

torgaoptical.co.za website review

Visit site (opens in a new tab)Reviewed 6 November 202632 issues · 80 checks

This review found 32 issues worth fixing on torgaoptical.co.za, 9 of them high impact, across 80 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
5.2 s2.3 sMay 16Oct 312.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.3 s
May 23, 20264.5 s
May 30, 20264.6 s
Jun 6, 20264.8 s
Jun 13, 20264.8 s
Jun 20, 20264.7 s
Jun 27, 20264.6 s
Jul 4, 20264.2 s
Jul 11, 20264.0 s
Jul 18, 20263.8 s
Jul 25, 20263.7 s
Aug 1, 20263.5 s
Aug 8, 20263.4 s
Aug 15, 20263.3 s
Aug 22, 20263.3 s
Aug 29, 20263.3 s
Sep 5, 20263.4 s
Sep 12, 20263.4 s
Sep 19, 20263.3 s
Sep 26, 20263.3 s
Oct 3, 20263.0 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Oct 24, 20262.7 s
Oct 31, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
319 ms206 msMay 16Oct 31272 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026247 ms
May 23, 2026241 ms
May 30, 2026240 ms
Jun 6, 2026244 ms
Jun 13, 2026238 ms
Jun 20, 2026229 ms
Jun 27, 2026225 ms
Jul 4, 2026219 ms
Jul 11, 2026223 ms
Jul 18, 2026231 ms
Jul 25, 2026235 ms
Aug 1, 2026239 ms
Aug 8, 2026248 ms
Aug 15, 2026255 ms
Aug 22, 2026272 ms
Aug 29, 2026287 ms
Sep 5, 2026293 ms
Sep 12, 2026295 ms
Sep 19, 2026295 ms
Sep 26, 2026306 ms
Oct 3, 2026306 ms
Oct 10, 2026302 ms
Oct 17, 2026303 ms
Oct 24, 2026283 ms
Oct 31, 2026272 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 torgaoptical.co.za (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. torgaoptical.co.za at 0.8 s0.8 s
  2. torgaoptical.co.za at 1.7 s1.7 s
  3. torgaoptical.co.za at 2.5 s2.5 s
  4. torgaoptical.co.za at 3.4 s3.4 s
  5. torgaoptical.co.za at 4.2 s4.2 s
  6. torgaoptical.co.za at 5.1 s5.1 s
  7. torgaoptical.co.za at 5.9 s5.9 s
  8. torgaoptical.co.za at 6.8 s6.8 s

Speed

10 to fix72
  • Use efficient cache lifetimes

    1.0 s · 857 KiB

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

  • Render-blocking requests

    1.1 s

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

  • 3,805 HTML elements

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

  • Reduce unused JavaScript

    750 ms · 582 KiB

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

  • Mobile performance score: 72

    72/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.1 MB and 785 ms of main-thread time.

  • Improve image delivery

    350 ms · 511 KiB

    11 images could be 511 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.

  • Reduce unused CSS

    450 ms · 91 KiB

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

  • Google Tag Manager adds 388 ms

    388 ms

    Google Tag Manager costs a phone 388 ms of main-thread work and 585 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.2 s

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

  • 10 long tasks on the main thread

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

  • Legacy JavaScript

    100 ms · 31 KiB

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

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

    31 ms

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

Core Web Vitals

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

  • Time to Interactive: 11.9 s

    11.9 s

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

  • Largest Contentful Paint: 4.5 s

    4.5 s

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user INP: 306 ms

    306 ms

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

  • Real-user FCP: 2.6 s

    2.6 s

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

  • Real-user TTFB: 1.8 s

    1.8 s

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

  • Total Blocking Time: 432 ms

    432 ms

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

  • 2 images without width and height

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

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

    +14%

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

5 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Largest content (LCP) got 39% faster for real visitors

    -39%

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

  • Speed Index: 3.2 s

    3.2 s

    Visually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.5 s

    1.5 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.3 MB in 65 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 65 requests on a phone: scripts 1.2 MB (16), images 846 KiB (29) and stylesheets 116 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (163 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 0.6 g of CO₂ per visit

    0.64 g

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

2 checks passed
  • Images load when needed

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

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

  • 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 (18 elements)

    All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 465 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

1 to fixGoogle 10097
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 644 internal links, 8 external

    The homepage links to 644 pages on torgaoptical.co.za and 8 external pages.

7 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Book an eye test online at a store near you. Frames we design and make, German precision lenses from our own lab, and E…”.

  • One H1 headline

    Your main headline reads: “Glasses FOR MORE OCCASIONS”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Optometrists & Glasses in South Africa | Torga Optical”.

  • Canonical URL set

    The canonical URL is https://torgaoptical.co.za/.

  • Structured data in place

    Structured data found: Organization 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://torgaoptical.co.za/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://torgaoptical.co.za/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.

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

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

  • Text is in the HTML

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

Other pages

3 to fix67
  • 1 linked page is broken

    Your homepage links to https://torgaoptical.co.za/uv420-blue-light-protection-voucher, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 linked page hidden from search

    https://torgaoptical.co.za/wishlist is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a meta description

    https://torgaoptical.co.za/wishlist and https://torgaoptical.co.za/book-appointment use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

5 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 14 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.doofinder.com/livelayer/1.8.211/css/2/common.css' from origin 'https://torgaop…”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • About 707 words of copy

    The homepage carries about 707 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 now” and “CONTACT LENSES”.

  • 35 calls to action

    The homepage has 35 calls to action, for example “Shop now”, “Contact Lenses” and “Book Appointment”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

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

  • 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
  • 2 trackers load before any consent

    2

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

  • 6 other companies contacted

    Loading the homepage contacts 6 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 torgaoptical.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
nopCommerce
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on torgaoptical.co.za, including 19 speed issues, 1 SEO issue and 1 conversion gap. 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