Website review, no card needed

mytfgworld.com logo

mytfgworld.com website review

Visit site (opens in a new tab)Reviewed 2 November 202660 issues · 95 checks

This review found 60 issues worth fixing on mytfgworld.com, 32 of them high impact, across 95 checks. The most urgent: improve image delivery. 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.0 s3.3 sMay 16Oct 313.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.9 s
May 23, 20263.8 s
May 30, 20263.6 s
Jun 6, 20263.6 s
Jun 13, 20263.7 s
Jun 20, 20263.8 s
Jun 27, 20263.9 s
Jul 4, 20263.9 s
Jul 11, 20263.9 s
Jul 18, 20263.8 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.7 s
Sep 5, 20263.7 s
Sep 12, 20263.6 s
Sep 19, 20263.5 s
Sep 26, 20263.4 s
Oct 3, 20263.4 s
Oct 10, 20263.4 s
Oct 17, 20263.5 s
Oct 24, 20263.5 s
Oct 31, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
345 ms284 msMay 16Oct 31324 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026297 ms
May 23, 2026291 ms
May 30, 2026293 ms
Jun 6, 2026295 ms
Jun 13, 2026300 ms
Jun 20, 2026308 ms
Jun 27, 2026314 ms
Jul 4, 2026317 ms
Jul 11, 2026319 ms
Jul 18, 2026318 ms
Jul 25, 2026320 ms
Aug 1, 2026323 ms
Aug 8, 2026327 ms
Aug 15, 2026329 ms
Aug 22, 2026332 ms
Aug 29, 2026338 ms
Sep 5, 2026338 ms
Sep 12, 2026337 ms
Sep 19, 2026335 ms
Sep 26, 2026331 ms
Oct 3, 2026329 ms
Oct 10, 2026328 ms
Oct 17, 2026325 ms
Oct 24, 2026322 ms
Oct 31, 2026324 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 mytfgworld.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mytfgworld.com at 0.9 s0.9 s
  2. mytfgworld.com at 1.8 s1.8 s
  3. mytfgworld.com at 2.6 s2.6 s
  4. mytfgworld.com at 3.5 s3.5 s
  5. mytfgworld.com at 4.4 s4.4 s
  6. mytfgworld.com at 5.3 s5.3 s
  7. mytfgworld.com at 6.2 s6.2 s
  8. mytfgworld.com at 7.0 s7.0 s

Speed

12 to fix37
  • Improve image delivery

    24.8 s · 6.7 MB

    41 images could be 6.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 24.8 s faster on a phone.

  • Use efficient cache lifetimes

    20.8 s · 4.1 MB

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

  • Render-blocking requests

    7.2 s

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

  • Reduce unused JavaScript

    5.4 s · 1.3 MB

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

  • Reduce unused CSS

    1.0 s · 160 KiB

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

  • Mobile performance score: 37

    37/100

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

  • Main-thread work: 4.7 s

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

  • 4,486 HTML elements

    The page has 4,486 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 (vtexassets.com, Google Tag Manager and Google CDN and others), adding 3.0 MB and 2.3 s of main-thread time.

  • vtexassets.com adds 893 ms

    893 ms

    vtexassets.com costs a phone 893 ms of main-thread work and 946 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 762 ms

    762 ms

    Google Tag Manager costs a phone 762 ms of main-thread work and 919 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 340 ms

    340 ms

    Google CDN costs a phone 340 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.

  • Legacy JavaScript

    250 ms · 90 KiB

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

  • 19 long tasks on the main thread

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

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

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 21 ms

    21 ms

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

Core Web Vitals

12 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 LCP: 8.3 s

    8.3 s

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

  • Real-user CLS: 0.34

    0.34

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

  • Real-user FCP: 3.4 s

    3.4 s

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

  • First Contentful Paint: 12.9 s

    12.9 s

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

  • Largest Contentful Paint: 42.0 s

    42.0 s

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

  • Time to Interactive: 42.0 s

    42.0 s

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

  • Speed Index: 12.9 s

    12.9 s

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

  • Total Blocking Time: 764 ms

    764 ms

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

  • Real-user INP: 459 ms

    459 ms

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • 35 images without width and height

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

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

    +10%

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

2 checks passed
  • Largest content (LCP) got 10% faster for real visitors

    -10%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix38
  • Page weight: 12.2 MB in 220 requests

    12.2 MB

    Your homepage downloads 12.2 MB in 220 requests on a phone: images 8.3 MB (90), scripts 3.0 MB (65) and other files 450 KiB (56). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    SF_26_homepage_square_3_e953be7bd1.gif weighs 4.7 MB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (4.7 MB) 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.

  • 7 images below the first screen load straight away

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

  • About 3.5 g of CO₂ per visit

    3.45 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

16 to fixGoogle 6281
  • 8 buttons without a name

    8 buttons have no accessible name, so screen readers announce just “button”.

  • Images must have alternative text (3 elements)

    Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.

  • Hidden but focusable

    48 elements hidden from screen readers can still receive keyboard focus.

  • Orphan list items

    Some list items are not inside a list.

  • 4 text elements with low contrast

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

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • No main landmark

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

  • Zoom is disabled

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

  • 67 links without text

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

  • 7 form fields without a label

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

  • Headings should not be empty (14 elements)

    Headings should not be empty: 14 elements on the page fail this check, rated minor by axe-core.

  • ARIA role should be appropriate for the element (13 elements)

    ARIA role should be appropriate for the element: 13 elements on the page fail this check, rated minor by axe-core.

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

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

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

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

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

4 to fixGoogle 8576
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (78 characters)

    Your title is 78 characters, so Google will cut it off around 60: “Bash: Online Shopping - Shop Clothing, Sports, Home & Electronics Online in SA”.

  • Structured data has 1 problem

    Structured data found (Organization, WebPage and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

    No Open Graph image, 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.

  • 754 internal links, 1 external

    The homepage links to 754 pages on mytfgworld.com and 1 external page.

4 checks passed
  • Meta description: 144 characters

    Your meta description is 144 characters: “Bash is a fashion and lifestyle shopping platform in South Africa offering over 200 of the world’s best brands and 2000…”.

  • Canonical URL set

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

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

AI search readiness

100
  • No llms.txt

    There is no https://bash.com/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: 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,458 words), so crawlers that don't run JavaScript still read it.

Other pages

6 to fix38
  • 1 linked page is broken

    Your homepage links to https://bash.com/s, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages without a title

    https://bash.com/sale and https://bash.com/homewarestore have no <title>, so Google invents the link text in results.

  • 2 pages share a title

    https://bash.com/?redirect=mytfgworld.com and https://bash.com/brands all use the title “Bash: Online Shopping - Shop Clothing, Sports, Home & Electronics Onl…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://bash.com/homewarestore has 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://bash.com/vas/gift-card, whose canonical is https://bash.com/department/vouchers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://bash.com/black-friday and https://bash.com/brands 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 194 found) and read each the way a search engine does.

1 checks passed
  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187084580&tm=gtm002&Ver=2&mid=ad1ceb02-2188-45e6-8be6-6bc7c13c5094&bo=1&sid=18ea9b20d67e11f1bde8c7844fa6f745&vid=18eacc90d67e11f1a9074b8cfae1b29e&vids=1&msclkid=N&pi=9.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 410 ()”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    83 of 88 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 394 words of visible text.

2 checks passed
  • 75 calls to action

    The homepage has 75 calls to action, for example “Track your order”, “Shop All Womens Clothing” and “Shop All Womens Shoes”.

  • Analytics in place

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

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 35 cookies set on arrival

    35

    Opening the homepage sets 35 cookies, 2 of them by other companies (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.

  • 32 other companies contacted

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

Upkeep, stack and company

Stack

Framework
React
Analytics
Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 60 issues on mytfgworld.com, including 24 speed issues, 4 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