Website review, no card needed
1strate.co.za website review
Visit site (opens in a new tab)Reviewed 4 November 202642 issues · 85 checks
This review found 42 issues worth fixing on 1strate.co.za, 16 of them high impact, across 85 checks. The most urgent: improve image delivery. 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 sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.2 s
1.6 s
2.0 s
2.4 s
2.8 s
3.1 s
Speed
Improve image delivery
1.3 s · 439 KiB14 images could be 439 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.
Render-blocking requests
1.4 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Use efficient cache lifetimes
900 ms · 241 KiB20 files are served with short cache lifetimes, so returning visitors download them again (241 KiB).
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
Avoid multiple page redirects
751 msThe page goes through 1 redirect before it starts loading, costing about 751 ms. Link and advertise the final URL directly.
8 third-party services on the page
8 third-party services load with your homepage (ESM>CDN, Hubspot and jQuery CDN and others), adding 1.2 MB and 369 ms of main-thread time.
Document request latency
400 msThe HTML itself could arrive about 400 ms sooner: redirects, a slow server response or missing compression delay everything after it.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 275 ms. During a long task the page ignores taps.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
cloudfront.net adds 45 ms
45 mscloudfront.net costs a phone 45 ms of main-thread work and 924 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
150 ms · 203 KiBAbout 203 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Duplicated JavaScript
150 ms · 14 KiB14 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page.
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: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 4.9 s
4.9 sYour largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “1st Rate Properties | Hero Image 1”.
Time to Interactive: 7.6 s
7.6 sThe page becomes fully interactive after 7.6 s. Good is under 3.8 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Total Blocking Time: 416 ms
416 msScripts block taps and scrolling for 416 ms in total while the page loads. Good is under 200 ms.
Speed Index: 4.5 s
4.5 sVisually, the page fills in at 4.5 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
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.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
3 images below the first screen load straight away
3 images further down the page (100 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.4 g of CO₂ per visit
0.40 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.40 g of CO₂e: 47.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.4 MB in 60 requests
1.4 MBYour homepage downloads 1.4 MB in 60 requests on a phone: images 758 KiB (23), scripts 568 KiB (25) and fonts 60 KiB (2). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
2 elements use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
ARIA attributes must conform to valid values (2 elements)
ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (2 elements)
ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
Interactive controls must not be nested (2 elements)
Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
Form elements should have a visible label (1 element)
Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (18 elements)
All page content should be contained by landmarks: 18 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.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Elements marked as presentational should be consistently ignored (2 elements)
Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.
1 checks passed
40 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: 40 passed and 15 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No XML sitemap
No XML sitemap at https://www.1strate.co.za/residential-for-sale/sitemap.txt, 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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
50 internal links, 4 external
The homepage links to 50 pages on 1strate.co.za and 4 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Welcome”.
Title: 39 characters
Your title is a healthy 39 characters: “1st Class Service | 1st Rate Properties”.
Canonical URL set
The canonical URL is https://www.1strate.co.za/.
Structured data in place
Structured data found: 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.
No llms.txt
There is no https://www.1strate.co.za/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.
2 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 (960 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.1strate.co.za/results/residential/to-let/sandton/sandown/apartment/1432036 and https://www.1strate.co.za/results/residential/to-let/sandton/sandown/apartment/1431589 all use the title “2 Bedroom Apartment To Let in Sandown | 1st Rate Properties”. 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://www.1strate.co.za/list-your-property has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.1strate.co.za/results/residential/to-let/sandton/sandown/apartment/1432036 and https://www.1strate.co.za/results/residential/to-let/sandton/sandown/apartment/1431589 use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.1strate.co.za/results/commercial/to-let, whose canonical is https://www.1strate.co.za/results/commercial/to-let/sandton/parkmore/business/406792. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages with very little text
https://www.1strate.co.za/list-your-property and https://www.1strate.co.za/agents have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 28 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.
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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
15 of 15 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: 7 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
About 995 words of copy
The homepage carries about 995 words of visible text.
4 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact us” and “Request Information”.
Analytics in place
Analytics detected: Google Analytics and HubSpot.
Direct contact links
Visitors can reach you directly: 5 phone links and 0 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and HubSpot (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
5Opening 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.
13 other companies contacted
Loading the homepage contacts 13 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 1strate.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
- Analytics
- Google Analytics
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on 1strate.co.za, including 16 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.