Website review, no card needed
bsisteel.com website review
Visit site (opens in a new tab)Reviewed 3 November 202629 issues · 73 checks
This review found 29 issues worth fixing on bsisteel.com, 14 of them high impact, across 73 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
73C- #88,009 of 118,657 reviewed websitesbeats 22%
- #55,221 of 67,370 online storesbeats 15%
- #1,662 of 2,718 WooCommerce storesbeats 33%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 6.7 s |
| May 23, 2026 | 7.1 s |
| May 30, 2026 | 7.7 s |
| Jun 6, 2026 | 8.1 s |
| Jun 13, 2026 | 8.4 s |
| Jun 20, 2026 | 8.0 s |
| Jun 27, 2026 | 7.9 s |
| Jul 4, 2026 | 7.8 s |
| Jul 11, 2026 | 8.2 s |
| Jul 18, 2026 | 8.0 s |
| Jul 25, 2026 | 8.2 s |
| Aug 1, 2026 | 8.5 s |
| Aug 8, 2026 | 8.0 s |
| Aug 15, 2026 | 7.8 s |
| Aug 22, 2026 | 7.9 s |
| Aug 29, 2026 | 7.7 s |
| Sep 5, 2026 | 7.1 s |
| Sep 12, 2026 | 6.6 s |
| Sep 19, 2026 | 6.2 s |
| Sep 26, 2026 | 6.1 s |
| Oct 3, 2026 | 6.3 s |
| Oct 10, 2026 | 6.3 s |
| Oct 17, 2026 | 6.1 s |
| Oct 24, 2026 | 6.0 s |
| Oct 31, 2026 | 6.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 152 ms |
| May 23, 2026 | 163 ms |
| May 30, 2026 | 143 ms |
| Jun 6, 2026 | 131 ms |
| Jun 13, 2026 | 136 ms |
| Jun 20, 2026 | 131 ms |
| Jun 27, 2026 | 134 ms |
| Jul 4, 2026 | 134 ms |
| Jul 11, 2026 | 131 ms |
| Jul 18, 2026 | 133 ms |
| Jul 25, 2026 | 135 ms |
| Aug 1, 2026 | 135 ms |
| Aug 8, 2026 | 128 ms |
| Aug 15, 2026 | 126 ms |
| Aug 22, 2026 | 124 ms |
| Aug 29, 2026 | 130 ms |
| Sep 5, 2026 | 133 ms |
| Sep 12, 2026 | 143 ms |
| Sep 19, 2026 | 143 ms |
| Sep 26, 2026 | 145 ms |
| Oct 3, 2026 | 140 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 135 ms |
| Oct 24, 2026 | 122 ms |
| Oct 31, 2026 | 121 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
1.6 s
3.2 s
4.8 s
6.4 s
8.0 s
9.6 s
11.1 s
12.7 s
Speed
Render-blocking requests
4.7 s48 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.7 s.
Font display
1.4 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.4 s).
Reduce unused CSS
1.1 s · 164 KiBAbout 164 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 130 KiBAbout 130 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
2,219 HTML elements
The page has 2,219 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Clarity and Google Fonts and others), adding 260 KiB and 205 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 81 ms. During a long task the page ignores taps.
Improve image delivery
15 KiB1 image could be 15 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
11 KiB2 files are served with short cache lifetimes, so returning visitors download them again (11 KiB).
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
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
3 KiB3 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 1.0 s of it running JavaScript. That is comfortably low.
Server response: 243 ms
243 msYour server sent the HTML in 243 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: 8.2 s
8.2 sReal visitors wait 8.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 7.9 s
7.9 sReal visitors see the first content after 7.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 6.4 s
6.4 sReal visitors wait 6.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 18.6 s
18.6 sVisually, the page fills in at 18.6 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 8.2 s
8.2 sYour largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SOUTH AFRICA'S LEADING STEEL SUPPLIER & STEEL MERCHANT”. Most of its time is resource load delay (10.0 s).
Time to Interactive: 8.2 s
8.2 sThe page becomes fully interactive after 8.2 s. Good is under 3.8 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.182
0.182The layout shifts by 0.182 while loading, so content jumps under the reader's thumb. Good is under 0.1.
5 checks passed
Real-user INP: 134 ms
134 msReal visitors wait 134 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Tap response (INP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 152 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 6.7 s to 6.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 49 ms
49 msScripts block the page for only 49 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.9 MB in 131 requests
2.9 MBYour homepage downloads 2.9 MB in 131 requests on a phone: images 2.0 MB (22), scripts 508 KiB (51) and stylesheets 246 KiB (45). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (90 KiB) is 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 0.8 g of CO₂ per visit
0.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.81 g of CO₂e: 97.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
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.
Links look like plain text
2 links inside paragraphs rely on colour alone to stand out.
All page content should be contained by landmarks (15 elements)
All page content should be contained by landmarks: 15 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.
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.
Headings skip levels
Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 16 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
5 H1 headlines
There are 5 <h1> headlines (“SOUTHern AFRICA'S”, “LEADING STEEL SUPPLIER & STEEL MERCHANT” and “SOUTH AFRICA'S”). One clear main headline is easier for people and search engines.
Meta description is long (203 characters)
Your meta description is 203 characters; Google truncates after about 160, so the end of your pitch is cut.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
205 internal links, 7 external
The homepage links to 205 pages on bsisteel.com and 7 external pages.
6 checks passed
Title: 45 characters
Your title is a healthy 45 characters: “BSI Steel South Africa - Forging Partnerships”.
Canonical URL set
The canonical URL is https://www.bsisteel.com/.
Structured data in place
Structured data found: BreadcrumbList, 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://www.bsisteel.com/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 (1,036 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.bsisteel.com/llms.txt (28 KiB, 117 links), a plain-text guide to the site for AI tools.
Other pages
Your server turned our page checks away
15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.
Best practices
1 small tap target
1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “elementorFrontend.waypoint is not a function”.
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.
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 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 310 words of copy
The homepage carries about 310 words of visible text.
3 checks passed
19 calls to action
The homepage has 19 calls to action, for example “Contact Us”, “Get a Quote” and “Request a quote”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Microsoft Clarity (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
6 other companies contacted
Loading the homepage contacts 6 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 bsisteel.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- (Pty) Ltd - Xneelo (Pty) Ltd
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on bsisteel.com, including 15 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.