Website review, no card needed
conceiveplus.co.za website review
Visit site (opens in a new tab)Reviewed 7 November 202631 issues · 80 checks
This review found 31 issues worth fixing on conceiveplus.co.za, 10 of them high impact, across 80 checks. The most urgent: page weight: 10.3 MB in 184 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
84B- #21,349 of 118,576 reviewed websitesbeats 77%
- #13,879 of 67,354 online storesbeats 73%
- #13,472 of 61,413 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.4 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.7 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 4.0 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 3.9 s |
| Aug 1, 2026 | 3.6 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.5 s |
| Oct 31, 2026 | 3.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 178 ms |
| May 23, 2026 | 165 ms |
| May 30, 2026 | 165 ms |
| Jun 6, 2026 | 173 ms |
| Jun 13, 2026 | 178 ms |
| Jun 20, 2026 | 206 ms |
| Jun 27, 2026 | 228 ms |
| Jul 4, 2026 | 247 ms |
| Jul 11, 2026 | 295 ms |
| Jul 18, 2026 | 296 ms |
| Jul 25, 2026 | 314 ms |
| Aug 1, 2026 | 281 ms |
| Aug 8, 2026 | 221 ms |
| Aug 15, 2026 | 213 ms |
| Aug 22, 2026 | 197 ms |
| Aug 29, 2026 | 187 ms |
| Sep 5, 2026 | 178 ms |
| Sep 12, 2026 | 174 ms |
| Sep 19, 2026 | 169 ms |
| Sep 26, 2026 | 173 ms |
| Oct 3, 2026 | 179 ms |
| Oct 10, 2026 | 179 ms |
| Oct 17, 2026 | 195 ms |
| Oct 24, 2026 | 183 ms |
| Oct 31, 2026 | 184 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
How it loaded on a phone
0.5 s
0.9 s
1.4 s
1.8 s
2.3 s
2.8 s
3.2 s
3.7 s
Speed
Main-thread work: 6.6 s
A phone's processor spends 6.6 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,673 HTML elements
The page has 4,673 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, negate.io and Google Tag Manager and others), adding 769 KiB and 970 ms of main-thread time.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
850 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Shopify adds 354 ms
354 msShopify costs a phone 354 ms of main-thread work and 408 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.
negate.io adds 342 ms
342 msnegate.io costs a phone 342 ms of main-thread work and 40 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.
Reduce unused JavaScript
328 KiBAbout 328 KiB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 274 ms
274 msGoogle Tag Manager costs a phone 274 ms of main-thread work and 170 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 276 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
150 ms · 53 KiB8 files are served with short cache lifetimes, so returning visitors download them again (53 KiB).
Reduce unused CSS
150 ms · 24 KiBAbout 24 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.
Improve image delivery
29 KiB3 images could be 29 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 9.2 s
9.2 sThe page becomes fully interactive after 9.2 s. Good is under 3.8 s.
Largest Contentful Paint: 4.5 s
4.5 sYour 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 element shown below.
Total Blocking Time: 755 ms
755 msScripts block taps and scrolling for 755 ms in total while the page loads. Good is under 200 ms.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 178 ms to 184 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.4 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 593 ms
593 msReal visitors wait 593 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 10.3 MB in 184 requests
10.3 MBYour homepage downloads 10.3 MB in 184 requests on a phone: media 8.1 MB (2), scripts 939 KiB (65) and other files 617 KiB (64). Under 2 MB keeps phones on slow connections fast.
About 2.9 g of CO₂ per visit
2.93 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.93 g of CO₂e: 351.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (87 characters)
Your title is 87 characters, so Google will cut it off around 60: “Conceive Plus South Africa | Fertility Vitamins & Fertility Lubricants – Conceive Plus®”.
Meta description is long (270 characters)
Your meta description is 270 characters; Google truncates after about 160, so the end of your pitch is cut.
One H1 headline
Your <h1> is empty.
131 internal links, 15 external
The homepage links to 131 pages on conceiveplus.co.za and 15 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://conceiveplus.co.za/.
Structured data in place
Structured data found: BreadcrumbList, Organization, Store 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://conceiveplus.co.za/sitemap.xml.
AI search readiness
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 (2,127 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://conceiveplus.co.za/llms.txt (17 KiB, 94 links), a plain-text guide to the site for AI tools.
Other pages
1 page without an H1
https://conceiveplus.co.za/tools/tracking has 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 44 found) and read each the way a search engine does.
6 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.
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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
34 of 41 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 12 testimonial or review blocks. 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 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,017 words of copy
The homepage carries about 1,017 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: “SHOP NOW” and “SHOP BESTSELLERS”.
35 calls to action
The homepage has 35 calls to action, for example “SHOP”, “SHOP BESTSELLERS” and “SHOP BUNDLES”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and TikTok Pixel.
Opening hours shown
Your opening hours are on the homepage.
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
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Klaviyo (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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
12 other companies contacted
Loading the homepage contacts 12 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 conceiveplus.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 16 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Uppromote Affiliate · Popsixle · Okendo · Simprosys Google Shopping Feed · Tinyseo Ai Seo Speed · Hreflang Manager · Elevar Conversion Tracking · Klaviyo Email Marketing Sms · Sami Wholesale · Seal Subscriptions · Gdpr Cookie Consent · Orbe Geolocation · Affliate By Secomapp · Section Factory · cloudfront.net
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 | Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on conceiveplus.co.za, including 16 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.