Website review, no card needed

pixelpro.co.za logo

pixelpro.co.za website review

Visit site (opens in a new tab)Reviewed 7 November 202614 issues · 67 checks

This review found 14 issues worth fixing on pixelpro.co.za, 4 of them high impact, across 67 checks. The most urgent: 5 text elements with low contrast. 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

Full-page screenshot of pixelpro.co.za (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pixelpro.co.za at 0.4 s0.4 s
  2. pixelpro.co.za at 0.8 s0.8 s
  3. pixelpro.co.za at 1.1 s1.1 s
  4. pixelpro.co.za at 1.5 s1.5 s
  5. pixelpro.co.za at 1.9 s1.9 s
  6. pixelpro.co.za at 2.3 s2.3 s
  7. pixelpro.co.za at 2.6 s2.6 s
  8. pixelpro.co.za at 3.0 s3.0 s

Speed

3 to fix80
  • Improve image delivery

    150 ms · 1.5 MB

    12 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Mobile performance score: 80

    80/100

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

  • Render-blocking requests

    700 ms

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Google Fonts and others), adding 462 KiB and 212 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Reduce unused JavaScript

    159 KiB

    About 159 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    150 ms · 8 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (8 KiB).

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

2 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 455 ms of it running JavaScript. That is comfortably low.

  • Server response: 8 ms

    8 ms

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

Core Web Vitals

3 to fix77
  • Largest Contentful Paint: 4.6 s

    4.6 s

    Your largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Albert Bredenhann running a Pixel Pro Media AI workshop for…”.

  • Time to Interactive: 4.8 s

    4.8 s

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

  • Speed Index: 3.9 s

    3.9 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • 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.

  • Total Blocking Time: 147 ms

    147 ms

    Scripts block the page for only 147 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.021

    0.021

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

Images and page weight

4 to fix48
  • 13 images far larger than shown

    1.2 MB

    13 images are downloaded at several times the size a phone draws them, for example ws-capetown-07nov.jpg at 1,672 px wide, shown at 348 px. Resized copies would save about 1.2 MB.

  • Page weight: 3.4 MB in 44 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 44 requests on a phone: images 2.6 MB (16), scripts 431 KiB (13) and fonts 275 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 14 images in older formats

    14 images (2.6 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.

  • 12 images below the first screen load straight away

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

  • About 1.0 g of CO₂ per visit

    0.95 g

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

Accessibility

1 to fixGoogle 10098
  • 5 text elements with low contrast

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

2 checks passed
  • Every image has alt text

    All 14 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

Google 100100
  • 47 internal links, 5 external

    The homepage links to 47 pages on pixelpro.co.za and 5 external pages.

8 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “Pretoria AI marketing agency: branding, web design, social media management and practical AI training for South African…”.

  • One H1 headline

    Your main headline reads: “We build the brand, run the marketing and teach your team AI you can actually use.”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Pixel Pro Media | AI Marketing & Training Pretoria”.

  • Canonical URL set

    The canonical URL is https://www.pixelpro.co.za/.

  • Structured data in place

    Structured data found: LocalBusiness and Organization.

  • 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.pixelpro.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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

100
  • 3 pages slow to respond

    https://www.pixelpro.co.za/services/ai-training, https://www.pixelpro.co.za/training and https://www.pixelpro.co.za/workshops took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

    The homepage carries about 694 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book a free consult”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “Book a free consult” and “Book a consult call”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

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.

  • 9 other companies contacted

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

Apps on your store

No apps were seen in the code your storefront loads.

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
Tailwind CSS
E-commerce
Shopify
Analytics
Google Analytics
Hosting
Cloudflare

Company

Headquarters
Pretoria

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 14 issues on pixelpro.co.za, including 6 speed 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