waltersandwolf.com website review

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

About 476 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

4 third-party services load with your homepage (Vimeo, Google Tag Manager and Google Fonts and others), adding 14.8 MB and 242 ms of main-thread time.

Vimeo costs a phone 126 ms of main-thread work and 14.6 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.

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

3 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DESIGN + ENGINEERING + FABRICATION + INSTALLATION BUILDING …”. Most of its time is resource load delay (3.6 s).

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

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

The layout shifts by 0.394 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 15.6 MB in 93 requests on a phone: other files 14.1 MB (26), scripts 935 KiB (26) and images 277 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 14 characters: “Walters & Wolf”. Between 30 and 65 characters leaves room to say what you do and for whom.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 6 pages on waltersandwolf.com and 4 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://waltersandwolf.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://waltersandwolf.com/who-we-are, https://waltersandwolf.com/what-we-do, https://waltersandwolf.com/how-we-do-it-2 and https://waltersandwolf.com/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

https://waltersandwolf.com/who-we-are, https://waltersandwolf.com/what-we-do, https://waltersandwolf.com/how-we-do-it-2 and https://waltersandwolf.com/contact-us have 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.

https://waltersandwolf.com/what-we-do, https://waltersandwolf.com/how-we-do-it-2 and https://waltersandwolf.com/contact-us took over 3 s to send their HTML from our server.

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

2 of 6 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

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

4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://fonts.googleapis.com/css?family=Open+Sans+Condensed:normal&display=swap&ver=4.14.2…”.

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

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.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 25 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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