Website review, no card needed

fieldbar.co.za logo

fieldbar.co.za website review

Visit site (opens in a new tab)Reviewed 7 November 202652 issues · 90 checks

This review found 52 issues worth fixing on fieldbar.co.za, 20 of them high impact, across 90 checks. The most urgent: page weight: 25.0 MB in 400 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.9 s2.6 sMay 16Oct 313.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.8 s
May 23, 20262.9 s
May 30, 20263.0 s
Jun 6, 20263.2 s
Jun 13, 20263.2 s
Jun 20, 20263.4 s
Jun 27, 20263.4 s
Jul 4, 20263.5 s
Jul 11, 20263.5 s
Jul 18, 20263.6 s
Jul 25, 20263.6 s
Aug 1, 20263.5 s
Aug 8, 20263.5 s
Aug 15, 20263.5 s
Aug 22, 20263.5 s
Aug 29, 20263.6 s
Sep 5, 20263.7 s
Sep 12, 20263.7 s
Sep 19, 20263.8 s
Sep 26, 20263.7 s
Oct 3, 20263.7 s
Oct 10, 20263.7 s
Oct 17, 20263.6 s
Oct 24, 20263.6 s
Oct 31, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
476 ms171 msMay 16Oct 31361 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026206 ms
May 23, 2026229 ms
May 30, 2026256 ms
Jun 6, 2026290 ms
Jun 13, 2026313 ms
Jun 20, 2026330 ms
Jun 27, 2026353 ms
Jul 4, 2026374 ms
Jul 11, 2026397 ms
Jul 18, 2026438 ms
Jul 25, 2026441 ms
Aug 1, 2026431 ms
Aug 8, 2026431 ms
Aug 15, 2026415 ms
Aug 22, 2026416 ms
Aug 29, 2026420 ms
Sep 5, 2026421 ms
Sep 12, 2026406 ms
Sep 19, 2026393 ms
Sep 26, 2026369 ms
Oct 3, 2026351 ms
Oct 10, 2026344 ms
Oct 17, 2026346 ms
Oct 24, 2026358 ms
Oct 31, 2026361 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 fieldbar.co.za (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fieldbar.co.za at 0.8 s0.8 s
  2. fieldbar.co.za at 1.6 s1.6 s
  3. fieldbar.co.za at 2.3 s2.3 s
  4. fieldbar.co.za at 3.1 s3.1 s
  5. fieldbar.co.za at 3.9 s3.9 s
  6. fieldbar.co.za at 4.7 s4.7 s
  7. fieldbar.co.za at 5.5 s5.5 s
  8. fieldbar.co.za at 6.2 s6.2 s

Speed

11 to fix20
  • Mobile performance score: 20

    20/100

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

  • Main-thread work: 7.8 s

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

  • 3,786 HTML elements

    The page has 3,786 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 (Shopify, Google Tag Manager and Cloudflare CDN and others), adding 21.8 MB and 1.3 s of main-thread time.

  • Shopify adds 477 ms

    477 ms

    Shopify costs a phone 477 ms of main-thread work and 20.7 MB 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.

  • Improve image delivery

    650 ms · 698 KiB

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

  • Reduce unused JavaScript

    150 ms · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Render-blocking requests

    800 ms

    9 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

  • 18 long tasks on the main thread

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

  • Google Tag Manager adds 222 ms

    222 ms

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

  • rebuyengine.com adds 105 ms

    105 ms

    rebuyengine.com costs a phone 105 ms of main-thread work and 300 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.

  • Use efficient cache lifetimes

    200 ms · 209 KiB

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

  • Reduce unused CSS

    150 ms · 86 KiB

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

  • Legacy JavaScript

    64 KiB

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

  • Font display

    50 ms

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

  • 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

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 33 ms

    33 ms

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

Core Web Vitals

13 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: 5.1 s

    5.1 s

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

  • Real-user INP: 570 ms

    570 ms

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

  • Real-user CLS: 1.00

    1.00

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

  • Largest Contentful Paint: 10.6 s

    10.6 s

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

  • Time to Interactive: 32.3 s

    32.3 s

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

  • Cumulative Layout Shift: 1

    1

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

  • Speed Index: 9.7 s

    9.7 s

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

  • Total Blocking Time: 899 ms

    899 ms

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

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

    +65%

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

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

    +26%

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • 12 images without width and height

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

2 checks passed
  • Real-user TTFB: 727 ms

    727 ms

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

  • First Contentful Paint: 1.7 s

    1.7 s

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

Images and page weight

5 to fix18
  • Page weight: 25.0 MB in 400 requests

    25.0 MB

    Your homepage downloads 25.0 MB in 400 requests on a phone: media 18.0 MB (5), images 3.1 MB (74) and scripts 2.3 MB (128). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    1.6 MB

    6 images are downloaded at several times the size a phone draws them, for example WEB_ICONS_Delivery-EN.webp at 1,042 px wide, shown at 60 px. Resized copies would save about 1.6 MB.

  • 1 image over 500 KB

    PG-Towel01-Front1200x1600_result.webp weighs 491 KiB. On a phone connection a single image that size takes seconds.

  • 19 images in older formats

    19 images (4.0 MB) are 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.

  • 10 images below the first screen load straight away

    10 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 7.1 g of CO₂ per visit

    7.07 g

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

Accessibility

10 to fixGoogle 8488
  • Images must have alternative text (4 elements)

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

  • 14 text elements with low contrast

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

  • 8 tap targets too small

    8 tap targets are too small or too close together to hit reliably with a finger.

  • Form elements should have a visible label (2 elements)

    Form elements should have a visible label: 2 elements on the page fail this check, rated serious by axe-core.

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails 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.

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

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

1 checks passed
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 10 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 8581
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Handcrafted Cooler Boxes & Fine Outdoor Objects - The Fieldbar Co.”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Handcrafted Cooler Boxes & Fine Outdoor Goods.” and “Handcrafted Cooler Boxes & Fine Outdoor Goods.”). One clear main headline is easier for people and search engines.

  • Meta description is long (182 characters)

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

  • 4 links with vague text

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

  • 142 internal links, 2 external

    The homepage links to 142 pages on fieldbar.co.za and 2 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

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

AI search readiness

100
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: 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 (1,066 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://fieldbar.co.za/llms.txt (1 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix75
  • 8 pages without a title

    https://fieldbar.co.za/pages/fieldbar-wonderland, https://fieldbar.co.za/collections, https://fieldbar.co.za/collections/mini-bar, https://fieldbar.co.za/collections/field-bottles, https://fieldbar.co.za/collections/textiles and https://fieldbar.co.za/collections/collection/Signature-Shades and 2 others have no <title>, so Google invents the link text in results.

  • 8 pages without a meta description

    https://fieldbar.co.za/pages/fieldbar-wonderland, https://fieldbar.co.za/collections, https://fieldbar.co.za/collections/mini-bar, https://fieldbar.co.za/collections/field-bottles, https://fieldbar.co.za/collections/textiles and https://fieldbar.co.za/collections/collection/Signature-Shades and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://fieldbar.co.za/collections/all, https://fieldbar.co.za/pages/fieldbar-wonderland, https://fieldbar.co.za/collections, https://fieldbar.co.za/collections/mini-bar, https://fieldbar.co.za/collections/drinks-boxes and https://fieldbar.co.za/collections/gin-trunks and 9 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 65 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

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

Best practices

3 to fixGoogle 9285
  • 173 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://fieldbar.co.za/cdn/shop/t/67/assets/region-language-drawer.css?v=45542' because it…”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

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

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

    The homepage carries about 588 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP CATALOGUE”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Register A New Product”, “Order History” and “SHOP CATALOGUE”.

  • 2 short forms

    2 short forms (0 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 17 cookies set on arrival

    17

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

  • 44 other companies contacted

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

Apps on your store

Your storefront loads 12 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Selecty · Gift Card Hero All In One · Linkedoption · Yoast Seo · Powerful Form Builder · Judge Me Reviews · Forms · Selleasy · Essential Pre Order Presale · nfcube.com · rebuyengine.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on fieldbar.co.za, including 24 speed issues, 4 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