westbasedirect.com website review

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

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

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

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

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

8 third-party services load with your homepage (Trust Pilot, Clarity and Google CDN and others), adding 2.8 MB and 649 ms of main-thread time.

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

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

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

Shopify costs a phone 91 ms of main-thread work and 1.8 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.

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

Polyfills for old browsers add 25 KiB JavaScript that modern phones do not need.

4 images could be 23 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

19 KiB JavaScript is shipped twice across bundles.

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.

2 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “RELIABLE ELECTRICAL PRODUCTS. COMPETITIVE PRICES.”.

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

Real visitors wait 319 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

Your homepage downloads 4.9 MB in 355 requests on a phone: scripts 2.0 MB (113), images 1.5 MB (55) and other files 839 KiB (152). Under 2 MB keeps phones on slow connections fast.

westbase-text-bg-pink-1720x760-9KB.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image (59 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.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Some list items are not inside a list.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 1,216 pages on westbasedirect.com and 2 external pages.

https://westbasedirect.com/blogs/news has no meta description, so Google writes the search snippet from whatever text it finds.

https://westbasedirect.com/collections/metal-screwed-switches-sockets, https://westbasedirect.com/collections/brushed-steel, https://westbasedirect.com/collections/polished-chrome, https://westbasedirect.com/collections/black-nickel, https://westbasedirect.com/collections/antique-brass and https://westbasedirect.com/collections/matt-black-1 and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://westbasedirect.com/collections/metal-screwed-switches-sockets, https://westbasedirect.com/collections/polished-chrome and https://westbasedirect.com/collections/antique-brass took over 3 s to send their HTML from our server.

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

4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Chrome logged issues while loading the page (“Mixed content”).

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,322 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 mores (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 22 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 46 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.