bridgemaker.com website review

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

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

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

Polyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

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

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

2 third-party services load with your homepage (Plausible and YouTube), adding 56 KiB and 12 ms of main-thread time.

Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Ergebnis. KI-nativ. Umgesetzt.”.

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

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

1 image is downloaded at several times the size a phone draws it, for example maxresdefault.jpg at 1,280 px wide, shown at 358 px. Resized copies would save about 16 KiB.

1 image (52 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image further down the page (52 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

Structured data found (Organization and Service) but with 3 problems, for example “Service: no offers (price) block”.

The homepage links to 44 pages on bridgemaker.com and 5 external pages.

/impressum 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 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 24 customer or partner logos. 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.

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

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

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