smithweb.com website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Intercom and Google CDN and others), adding 1.4 MB and 1.6 s of main-thread time.

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

Google Tag Manager costs a phone 740 ms of main-thread work and 533 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.

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

About 64 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.

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

Intercom costs a phone 278 ms of main-thread work and 232 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.

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

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

29 KiB could be saved by minifying CSS.

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

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

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.

3 KiB could be saved by minifying JavaScript.

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 18.4 s. Good is under 3.8 s.

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

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

Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Your homepage downloads 2.4 MB in 168 requests on a phone: scripts 1.6 MB (60), fonts 415 KiB (9) and images 224 KiB (33). Under 2 MB keeps phones on slow connections fast.

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

2 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.

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

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 on the page fails this check, rated moderate by axe-core.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

2 links have no real href, so search engines can't follow them.

The homepage links to 109 pages on smithweb.com and 17 external pages.

There is no https://smithweb.com/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.

/ and https://smithweb.com/de all use the title “Smith - Intelligent Distribution”. Search engines can't tell which page to show for a search, so each competes with the others.

https://smithweb.com/contact, https://smithweb.com/services/procurement, https://smithweb.com/services/data-center-services, https://smithweb.com/services/solar-services, https://smithweb.com/industries and https://smithweb.com/services/products and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://smithweb.com/services/franchise-lines took over 3 s to send its HTML from our server.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Content security policy”).

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.

Social proof on the homepage: 18 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 616 words of visible text.

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