wrenchgroup.com website review

32 images could be 5.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

About 135 KiB of JavaScript is downloaded but never used on this page.

2 third-party services load with your homepage (Adobe Tag Manager and adobedc.net), adding 56 KiB and 70 ms of main-thread time.

1 long task block the main thread while loading, the longest for 61 ms. During a long task the page ignores taps.

1 file is served with short cache lifetimes, so returning visitors download them again (39 KiB).

About 19 KiB of CSS is downloaded but never applied on this page.

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

8 KiB could be saved by minifying JavaScript.

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.

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

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

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

Your homepage downloads 6.7 MB in 90 requests on a phone: images 6.3 MB (39), fonts 211 KiB (6) and scripts 147 KiB (20). Under 2 MB keeps phones on slow connections fast.

7 images weigh 5.0 MB together. On a phone connection a single image that size takes seconds.

10 images are downloaded at several times the size a phone draws them, for example media_1e79ff8a8b222b9f83f014324e8620fabdebd4a96.jpg at 700 px wide, shown at 166 px. Resized copies would save about 2.7 MB.

35 images further down the page (6.2 MB) 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 1.91 g of CO₂e: 228.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Your title is only 27 characters: “Wrench Group - Wrench Group”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is 270 characters; Google truncates after about 160, so the end of your pitch is cut.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 7 pages on wrenchgroup.com and 0 external pages.

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.

There is no https://www.wrenchgroup.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.

https://www.wrenchgroup.com/our-story, https://www.wrenchgroup.com/contact and https://www.wrenchgroup.com/brands have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.wrenchgroup.com/contact has 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.

We fetched 3 pages linked from your homepage and read each the way a search engine does.

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

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

1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

1 error was 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 (“Cookie”).

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

There is no form on the homepage, so every lead has to click through to another page first.

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

Opening the homepage sets 4 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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.