DEPerformance check

Performance

A website is a product people use. If it loads slowly, the customer leaves. Google knows that and rates speed as a ranking factor. That is why high performance is not an extra with us but the standard every page is signed off against.

Sports car from behind on a country road in the evening sun

Why speed counts

Three reasons that mean money.

  1. 01

    The customer does not wait

    Whoever searches for "19 inch wheels Golf 8" on a phone in the workshop or in a car park gives a site a few seconds. If it does not load, the next one gets a turn. Every second of load time costs visitors, and every lost visitor is a lost enquiry.

  2. 02

    Google measures along

    Google rates pages with the Core Web Vitals: how fast the largest element becomes visible (LCP), how fast the page reacts to input (INP), how stable the layout is (CLS). Pages that miss those values rank lower, with the same content.

  3. 03

    Trust is built in the first second

    A page that is there instantly feels like a workshop where everything is in its place. A page that stutters and reloads feels like the opposite. For companies that advertise precision, speed is part of credibility.

Core Web Vitals

The three values Google measures.

Core Web Vitals are the measurements Google uses to rate the user experience of a page. They are measured on real visitors and feed into rankings. The thresholds are public; the values of our sites sit well below them.

  • LCP

    Largest Contentful Paint

    Google:
    good up to 2.5 s
    Our sites:
    < 1.0 s

    How long it takes until the largest visible element (usually the main image or the headline) is there.

  • INP

    Interaction to Next Paint

    Google:
    good up to 200 ms
    Our sites:
    < 100 ms

    How fast the page reacts to a click or tap. Without heavy JavaScript that is instant.

  • CLS

    Cumulative Layout Shift

    Google:
    good up to 0.1
    Our sites:
    0

    Whether content jumps while loading. Images with fixed dimensions and self-hosted fonts prevent that.

Thresholds: Google, web.dev/vitals. Our values are the acceptance criteria per page, measured at handover on mobile with PageSpeed Insights. Third-party embeds such as video, chat or tracking cost points; we discuss that beforehand.

BMW M5 in motion
Under one second

How we achieve that

Nothing that keeps you waiting.

Most slow sites are slow because too much happens on every request: database, PHP, twenty plugins, three trackers, fonts from Google, images at original size. We take all of that away.

Precision work on a workpiece
  • Built beforehand

    Every page is generated in full at build time and delivered as a file. On request nothing happens anymore except delivery.

  • No framework in the browser

    No JavaScript library that has to load and start first. JavaScript only where it does something (menu, form), a few kilobytes.

  • Images per device

    Every image in AVIF and WebP, in several sizes. The phone gets the small one, the large monitor the large one. Never more than needed.

  • Fonts and everything else with us

    No request to third-party servers. No Google Fonts, no trackers, no embedded maps without a click. Which also means no cookie banner.

  • Edge hosting

    The site sits on servers around the world and is delivered from the nearest one, in milliseconds.

  • Sign-off by measurement

    Lighthouse 100 in all four categories and Core Web Vitals in the green are part of the handover, not a promise: measured at handover with PageSpeed Insights, on mobile, without third-party scripts added later.

Before and after

What changes for your customers.

In a relaunch we measure the old site with the same tools as the new one. The differences are typical for the move from a standard page builder to a high-performance site.

MerkmalTypical siteHigh-performance site
Lighthouse performance (mobile)40 to 70100
Largest Contentful Paint3 to 8 sunder 1 s
Data transferred per page3 to 10 MBunder 500 KB
JavaScript in the browser500 KB to 2 MBa few KB
Requests to third-party servers10 to 400
Cookie bannerrequirednot required

Values for the typical site: ranges from our own Lighthouse measurements of company and shop sites (2026, mobile) and the HTTP Archive Web Almanac 2024 (median JavaScript 558 KB per page). We measure your site concretely in the performance check.

Performance check

Know where you stand today.

Enter the address of your website. We measure load time, Core Web Vitals, data volume and third-party requests, check readability for Google and AI systems, and tell you what it would take.

Start the performance check

Next step

Ready formore performance?

Send us the address of your website or tell us what you have in mind. You get an honest assessment and a clear quote.

Direct

Start the performance check

Your details are used only to handle your enquiry. More in the privacy policy.