Website review, no card needed
gotyme.co.za website review
Visit site (opens in a new tab)Reviewed 30 October 202640 issues · 82 checks
This review found 40 issues worth fixing on gotyme.co.za, 11 of them high impact, across 82 checks. The most urgent: render-blocking 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.5 s |
| May 16, 2026 | 4.5 s |
| May 23, 2026 | 4.3 s |
| May 30, 2026 | 4.1 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 4.2 s |
| Jun 20, 2026 | 4.3 s |
| Jun 27, 2026 | 4.6 s |
| Jul 4, 2026 | 4.6 s |
| Jul 11, 2026 | 4.4 s |
| Jul 18, 2026 | 4.3 s |
| Jul 25, 2026 | 4.2 s |
| Aug 1, 2026 | 4.1 s |
| Aug 8, 2026 | 4.1 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 3.9 s |
| Aug 29, 2026 | 3.9 s |
| Sep 5, 2026 | 3.8 s |
| Sep 12, 2026 | 3.8 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 3.8 s |
| Oct 3, 2026 | 3.9 s |
| Oct 10, 2026 | 3.9 s |
| Oct 17, 2026 | 3.9 s |
| Oct 24, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 245 ms |
| May 16, 2026 | 247 ms |
| May 23, 2026 | 250 ms |
| May 30, 2026 | 245 ms |
| Jun 6, 2026 | 243 ms |
| Jun 13, 2026 | 240 ms |
| Jun 20, 2026 | 239 ms |
| Jun 27, 2026 | 240 ms |
| Jul 4, 2026 | 241 ms |
| Jul 11, 2026 | 243 ms |
| Jul 18, 2026 | 250 ms |
| Jul 25, 2026 | 269 ms |
| Aug 1, 2026 | 284 ms |
| Aug 8, 2026 | 292 ms |
| Aug 15, 2026 | 291 ms |
| Aug 22, 2026 | 281 ms |
| Aug 29, 2026 | 279 ms |
| Sep 5, 2026 | 275 ms |
| Sep 12, 2026 | 275 ms |
| Sep 19, 2026 | 276 ms |
| Sep 26, 2026 | 274 ms |
| Oct 3, 2026 | 272 ms |
| Oct 10, 2026 | 270 ms |
| Oct 17, 2026 | 267 ms |
| Oct 24, 2026 | 266 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
Speed
Render-blocking requests
2.0 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, cdn-cookieyes.com and JSDelivr CDN and others), adding 462 KiB and 859 ms of main-thread time.
Google Tag Manager adds 708 ms
708 msGoogle Tag Manager costs a phone 708 ms of main-thread work and 335 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 CSS
450 ms · 106 KiBAbout 106 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.
Improve image delivery
522 KiB5 images could be 522 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 397 ms. During a long task the page ignores taps.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
Reduce unused JavaScript
264 KiBAbout 264 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 799 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify CSS
150 ms · 15 KiB15 KiB could be saved by minifying CSS.
Document request latency
89 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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.
Use efficient cache lifetimes
1 KiB1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).
1 checks passed
Server response: 235 ms
235 msYour server sent the HTML in 235 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.
Real-user LCP: 4.6 s
4.6 sReal visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.7 s
4.7 sReal visitors see the first content after 4.7 s (75th percentile). Good is under 1.8 s.
Time to Interactive: 11.5 s
11.5 sThe page becomes fully interactive after 11.5 s. Good is under 3.8 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user INP: 257 ms
257 msReal visitors wait 257 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 473 ms
473 msScripts block taps and scrolling for 473 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 3.2 s
3.2 sYour largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Important Notice: The Old TymeBank app has been discontinue…”. Most of its time is element render delay (1.9 s).
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 245 ms to 266 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.5 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.8 MB in 77 requests
7.8 MBYour homepage downloads 7.8 MB in 77 requests on a phone: media 3.8 MB (2), images 2.5 MB (17) and scripts 646 KiB (23). Under 2 MB keeps phones on slow connections fast.
5 images below the first screen load straight away
5 images further down the page (579 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
160 KiB2 images are downloaded at several times the size a phone draws them, for example footer-logo-2.png at 3,971 px wide, shown at 154 px. Resized copies would save about 160 KiB.
2 images in older formats
2 images (164 KiB) 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.
About 2.2 g of CO₂ per visit
2.22 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.22 g of CO₂e: 266.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (16 elements)
All page content should be contained by landmarks: 16 elements on the page fail 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.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
37 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: 37 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Move Money Instantly & Free” and “It's Tyme to move to GoTyme Bank”). One clear main headline is easier for people and search engines.
No XML sitemap
No XML sitemap at https://gotyme.co.za/sitemap.xml, so Google discovers your pages only by following links.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
48 internal links, 16 external
The homepage links to 48 pages on gotyme.co.za and 16 external pages.
6 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Open a free bank account in South Africa with GoTyme Bank. Enjoy high savings interest rates on GoalSave with zero mont…”.
Title: 54 characters
Your title is a healthy 54 characters: “Free Bank Account and High Savings Rates | GoTyme Bank”.
Canonical URL set
The canonical URL is https://gotyme.co.za/.
Structured data in place
Structured data found: BankOrCreditUnion, FAQPage, 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.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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.
Text is in the HTML
Your server sends the page's text in the HTML (971 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://gotyme.co.za/llms.txt (21 KiB, 60 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://gotyme.co.za/personal declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://gotyme.co.za/personal all use the title “Free Bank Account and High Savings Rates | GoTyme Bank”. Search engines can't tell which page to show for a search, so each competes with the others.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 36 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
4 small tap targets
4 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 644 words of copy
The homepage carries about 644 words of visible text.
3 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Contact Us”, “Shop” and “Download the App”.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
8 other companies contacted
Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
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 gotyme.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
- Framework
- jQuery
- Hosting
- CloudFront
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on gotyme.co.za, including 21 speed issues, 3 SEO issues and 4 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.