b5plusgroup.com website review

13 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

46 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.

About 672 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 720 ms faster on a phone.

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

7 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.6 MB and 768 ms of main-thread time.

Google CDN costs a phone 580 ms of main-thread work and 1.1 MB 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.

A phone's processor spends 2.9 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 1,507 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

About 38 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 200 ms faster on a phone.

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

3 files are served with short cache lifetimes, so returning visitors download them again (8 KiB).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 visitors wait 6.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 4.8 s (75th percentile). Good is under 1.8 s.

Your largest element takes 11.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.3 s to 5.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.

Scripts block taps and scrolling for 346 ms in total while the page loads. Good is under 200 ms.

17 images have no width and height attributes, so the layout jumps as each one loads.

The first text or image appears after 2.0 s on a phone. Good is under 1.8 s.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 130 ms to 141 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.5 MB in 141 requests on a phone: images 5.3 MB (40), scripts 1.4 MB (42) and other files 352 KiB (2). Under 2 MB keeps phones on slow connections fast.

8 images (534 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.

2 images further down the page (156 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

2 tap targets are too small or too close together to hit reliably with a finger.

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.

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

4 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h1 → h6, h3 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.

The homepage links to 95 pages on b5plusgroup.com and 11 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no /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.

/%f0%9f%8c%8d%f0%9d%97%95%f0%9d%9f%b1-%f0%9d%97%a3%f0%9d%97%b9%f0%9d%98%82%f0%9d%98%80-%f0%9d%97%95%f0%9d%97%bf%f0%9d%97%b6%f0%9d%97%bb%f0%9d%97%b4%f0%9d%98%80-%f0%9d%97%9b%f0%9d%97%bc%f0%9d%97%b9 has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /%f0%9f%8c%8d%f0%9d%97%95%f0%9d%9f%b1-%f0%9d%97%a3%f0%9d%97%b9%f0%9d%98%82%f0%9d%98%80-%f0%9d%97%95%f0%9d%97%bf%f0%9d%97%b6%f0%9d%97%bb%f0%9d%97%b4%f0%9d%98%80-%f0%9d%97%9b%f0%9d%97%bc%f0%9d%97%b9, whose canonical is /%F0%9F%8C%8D%F0%9D%97%95%F0%9D%9F%B1-%F0%9D%97%A3%F0%9D%97%B9%F0%9D%98%82%F0%9D%98%80-%F0%9D%97%95%F0%9D%97%BF%F0%9D%97%B6%F0%9D%97%BB%F0%9D%97%B4%F0%9D%98%80-%F0%9D%97%9B%F0%9D%97%BC%F0%9D%97%B9. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/mining has no <h1> headline, so visitors and search engines get no clear main topic.

/steel-about-us and /gra-commends-b5-plus-one-billion-cedis-taxes took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 image is served at too low a resolution for sharp phone screens.

1 link to other sites is dead, for example https://www.linkedin.com/in/b5plusgroup?originalSubdomain=gh (999).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

b5plusgroup.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

b5plusgroup.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Social proof on the homepage: 8 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage carries about 654 words of visible text.

b5plusgroup.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads 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.

Opening the homepage sets 2 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.