wihatools.com website review

Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

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

8 third-party services load with your homepage (Yotpo, 506.io and iovation and others), adding 1.4 MB and 1.5 s of main-thread time.

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

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

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

Yotpo costs a phone 509 ms of main-thread work and 566 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.

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

Klaviyo costs a phone 204 ms of main-thread work and 342 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 99 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

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

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

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

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

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

Your homepage downloads 6.8 MB in 414 requests on a phone: images 4.2 MB (185), scripts 1.5 MB (88) and other files 855 KiB (124). Under 2 MB keeps phones on slow connections fast.

11 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images are downloaded at several times the size a phone draws them, for example [email protected] at 1,400 px wide, shown at 358 px. Resized copies would save about 194 KiB.

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

1 button has no accessible name, so screen readers announce just “button”.

28 elements hidden from screen readers can still receive keyboard focus.

13 images have no alt text, which hurts accessibility and image search.

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

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

Your title is 69 characters, so Google will cut it off around 60: “Professional Hand Tools, Insulated Tools & Tool Kits | Wiha Tools USA”.

There are 2 <h1> headlines (“Wiha Tools” and “Wiha For Electricians”). One clear main headline is easier for people and search engines.

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

The homepage links to 358 pages on wihatools.com and 5 external pages.

https://www.wihatools.com/policies/shipping-policy, https://www.wihatools.com/policies/refund-policy and https://www.wihatools.com/apps/shop have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.wihatools.com/pages/contact, https://www.wihatools.com/pages/start-your-career-at-wiha, https://www.wihatools.com/pages/faq, https://www.wihatools.com/pages/pro-rewards, https://www.wihatools.com/policies/shipping-policy and https://www.wihatools.com/policies/refund-policy and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.wihatools.com/pages/pro-rewards, https://www.wihatools.com/collections/complete-tool-kits, https://www.wihatools.com/collections/tool-storage and https://www.wihatools.com/collections/slimline-system took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 132 found) 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.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-widget-assets.yotpo.com/LoyaltyFloaterWidget/AUmCZs22QcObRjZPZHoByw/css-overri…”.

Large scripts ship without source maps.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

Before a visitor clicks anything, the page loads Klaviyo (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, 4 of them by other companies (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 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.