wieseusa.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, iconnode.com and Hotjar and others), adding 736 KiB and 1.1 s of main-thread time.

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

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

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).

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

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.

Your largest element takes 87.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “MATERIAL HANDLING SOLUTIONS A FULL RANGE OF POWERFUL AND VE…”.

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

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

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

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

15 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-24, real Chrome visitors' tap response (inp) went from 138 ms to 143 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 17.3 MB in 83 requests on a phone: images 16.2 MB (26), scripts 660 KiB (22) and fonts 343 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

4 images are downloaded at several times the size a phone draws them, for example Secondary_HeroBanner_ForkliftServiceAtWiese_120522.png at 1,403 px wide, shown at 366 px. Resized copies would save about 275 KiB.

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

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

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

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.

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

There are 3 <h1> headlines (“Wiese USA”, “Material Handling Solutions” and “Why Wiese?”). One clear main headline is easier for people and search engines.

The homepage links to 129 pages on wieseusa.com and 3 external pages.

There is no https://wieseusa.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://wieseusa.com/contact-wiese, https://wieseusa.com/locations, https://wieseusa.com/new-equipment, https://wieseusa.com/used-equipment, https://wieseusa.com/equipment-rental and https://wieseusa.com/equipment-rental/forklifts-for-rent and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://wieseusa.com/new-equipment took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=25038159&tm=gtm002&Ver=2&mid=51a2664b-34e2-4e03-829e-079d57e37741&bo=1&sid=e745b2e0d3fe11f1b6a33d350f14c0d4&vid=e745d870d3fe11f18bbaf5163944d768&vids=1&msclkid=N&pi=91.

3 of 14 tappable elements near the top of the page are 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: the server responded with a status of 403 ()”.

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

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Microsoft Ads and 1 more (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

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

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