Zum Inhalt springen
Personal, from the Hildesheim region
Webdesign

Improve Website Loading Speed: Faster Means More Enquiries

13 min read
LadezeitCore Web VitalsPerformanceWebdesign

A potential customer taps your search result, the page builds up slowly – and after three seconds they are gone, often to a competitor. Loading speed is not a technical detail for developers; it decides whether a click turns into an enquiry. Studies show: when the load time of a mobile page rises from one to three seconds, around 53 percent (Google) of visitors leave. Just one second (Deloitte) of additional delay can noticeably lower the probability of a conversion. This article explains the three Core Web Vitals LCP, INP and CLS clearly and shows the four most effective levers: images, hosting, code and caching. No jargon, just concrete steps for local businesses in Hildesheim and the region.

The Three Core Web Vitals ExplainedLCPLargest Contentful PaintWhen does the largestcontent appear?Target: under 2.5 sINPInteraction to Next PaintHow fast does the pagereact to clicks?Target: under 200 msCLSCumulative Layout ShiftDoes the layout shiftwhile loading?Target: under 0.1Four levers: images, hosting, code and caching1Imagescompressed, WebP2Hostingfast servers3Codelean, few scripts4Cachingstore and reuse53%leave after 3 s (Google)1 scosts conversions (Deloitte)2.5 sgood LCP targetLCP | INP | CLS | loading faster means more regional enquiries

Key takeaways

  • Loading speed is a conversion factor: faster pages keep visitors and bring measurably more regional enquiries.
  • The three Core Web Vitals measure loading speed (LCP), responsiveness (INP) and visual stability (CLS) – understandable and verifiable.
  • The four biggest levers in almost every project are images, hosting, code and caching – usually in that order.
  • Uncompressed images are the most common bottleneck and can often be fixed fastest.
  • With the free Lighthouse measurement, progress becomes traceable – gut feeling turns into solid numbers.

Why Loading Speed Decides Enquiries

On the web, speed is not a comfort topic but a direct business factor. People are impatient, especially on smartphones and on the move. When a page does not appear quickly, visitors assume something is broken and return to the search. In its own analyses, Google found that with every additional second of load time the probability of a bounce rises: from one to three seconds it increases by around 32 percent (Google), and from one to five seconds by about 90 percent (Google). Other analyses show that within the first five seconds (Portent) of load time the conversion rate drops markedly with every additional second. For a local business this means very concretely: fewer calls, fewer completed contact forms, fewer jobs.

There is also the effect on visibility. Google evaluates loading speed as part of the user experience and factors it into the assessment of search results. A fast page therefore has a double advantage: it keeps visitors and at the same time sends a positive signal to the search engine. How these signals relate to overall search engine optimization is explored in our article on SEO basics for local businesses. Those who neglect the technical side give away potential in two places at once.

The effort pays off especially in local competition. In a region like Hildesheim you rarely compete with hundreds of providers but with a manageable number of businesses. Since over 60 percent (Statista) of global web traffic now comes from smartphones, the first impression is usually decided on the mobile, often slower network. A noticeably faster website can be the difference that decides the enquiry. This is exactly why we build performance into every web design project from the start – not as an afterthought patch, but as part of the foundation.

Faster means more conversions

Every saved second lowers the bounce rate and raises the chance that a visit turns into a call or enquiry. Even an improvement in load time of just 0.1 seconds (Deloitte) measurably increased retail conversions in one study. Loading speed acts directly on revenue, not just on the statistics.

Faster means better visibility

Google factors loading speed into its assessment of the user experience. A fast page therefore has better chances of good placements for local searches.

The Three Core Web Vitals Made Simple

So that speed does not remain pure gut feeling, Google has defined three measurable metrics, the Core Web Vitals. They describe the actual experience of real users and can be measured for free. The first metric is LCP, short for Largest Contentful Paint. It measures how long it takes until the largest visible element of a page appears – usually the main image or the large heading. Simplified, LCP answers the question: when does the visitor see that the page is really there? A good value is an LCP under 2.5 seconds.

The second metric is INP, short for Interaction to Next Paint. In 2024 it replaced the older responsiveness metric and measures how fast the page reacts to an input – for example a click on a button or opening a menu. INP answers the question: does the page feel smooth or does it lag? A good INP value is under 200 milliseconds, while a value above 500 milliseconds is considered poor (Google). Pages with many scripts and extensions often struggle here, because the browser is too busy to react immediately.

The third metric is CLS, short for Cumulative Layout Shift. It measures visual stability: does the layout jump while loading, because an image loads in without reserved space or a banner pushes in? Anyone who has ever tapped the wrong button because the page shifted at the last moment knows the problem. CLS answers the question: does everything stay calmly in place? A good value is under 0.1. These three values together give a realistic picture of perceived speed – and exactly this picture is the starting point for every performance optimization we carry out.

LCP – Load Time

Largest Contentful Paint measures when the largest visible content appears. Target: under 2.5 seconds. The main bottleneck is usually large, uncompressed images.

INP – Responsiveness

Interaction to Next Paint measures how fast the page reacts to clicks. Target: under 200 milliseconds. Too many scripts make the page sluggish.

CLS – Stability

Cumulative Layout Shift measures whether the layout jumps while loading. Target: under 0.1. Images and ads need fixed, reserved space.

Measure it yourself with Lighthouse

In the Chrome browser you can start a Lighthouse analysis of your page via the built-in developer tools. It delivers a free assessment of the Core Web Vitals and concrete hints on what is slowing the page down. This gives you a first, honest picture of the current state – without any investment.

Lever 1: Images – The Most Common Bottleneck

In most projects, images are the single biggest factor behind a slow page. A single photo straight from the camera can be several megabytes – that is more than a whole well-built page should weigh. If such an image is embedded unedited, the browser has to load it fully before the page appears finished. This worsens the LCP value in particular. The good news: hardly any lever can be pulled as quickly and with as much effect as image optimization.

The first step is the right size. An image displayed 800 pixels wide on the page does not need to be delivered 4000 pixels wide. Simply adapting it to the actual display size often saves the bulk of the data volume. The second step is compression into a modern format such as WebP, which is significantly smaller than older formats at the same quality. The third step is delayed loading, so-called lazy loading: images further down the page are loaded only when the visitor scrolls there. This way the visible area appears immediately.

  • Scale images to the actual display size instead of delivering camera resolution
  • Use modern formats such as WebP – smaller at the same visible quality
  • Define width and height in the code so no layout shift (CLS) occurs
  • Enable lazy loading for images below the visible area
  • Question decorative graphics: do you really need that large background image?
  • Embed logos and symbols as SVG – freely scalable and very small

Beware of missing image dimensions

If images are embedded without a defined width and height, the browser does not know how much space to reserve while loading. The image then loads in and pushes the text away – a classic layout shift that worsens the CLS value and irritates visitors. Fixed dimensions in the code solve the problem reliably.

Levers 2 and 3: Hosting and Lean Code

The second big lever is hosting, that is, the server your website sits on. Very cheap mass-market plans share a server with hundreds of other sites. Under heavy demand the server then responds slowly, and even the first reaction to the page request is delayed. This so-called server response time is the foundation on which everything else builds – if it is poor, even the best image optimization helps only so much. Studies show that improving the server response time is among the factors with the greatest influence on the LCP value (Google). A server in Germany with short paths to your regional visitors and sufficient capacity is therefore a worthwhile investment. How we reliably bring hosting and maintenance together is shown on our page on website maintenance.

The third lever is the code of the website itself. Many sites load more than they need: extensions that are barely used, several fonts, external scripts for effects no one misses. The browser has to download and process each of these elements, which burdens the INP value in particular. Lean code means embedding only what the page truly needs and consistently removing unnecessary functions. During a website relaunch this is the ideal moment to shed old ballast and rebuild on a clean foundation.

An often overlooked point is external embeds. Maps, fonts, videos or buttons loaded from third-party servers cost time and are not under your control. Often a lot can be gained here with small measures: embed fonts locally instead of loading them remotely, start videos only on click, load maps only on demand. This fine work adds up and makes the difference between a mediocre and a genuinely fast page. Which measures bring the most for your business is something we are happy to clarify in a personal conversation.

AreaSlows the page downSpeeds the page up
ImagesCamera originals, several megabytesScaled, compressed, WebP, lazy loading
HostingOvercrowded cheap server, long response timeCapable server in Germany
CodeMany unused extensions and scriptsLean, only the essentials embedded
FontsSeveral fonts, loaded externallyFew fonts, embedded locally
External contentMaps and videos load immediatelyLoad only on click or on demand

Lever 4: Caching – Build Once, Serve Often

The fourth lever is caching, that is, intermediate storage. The idea behind it is simple: instead of rebuilding a page on every request, the finished result is stored and delivered directly on the next visit. This saves the server work and the visitor waiting time. There are several levels of caching. On the server, a page cache ensures that frequently requested pages are not recalculated every time. In the visitor's browser, images, fonts and code are cached, so that on the second visit much does not have to be loaded again.

Another effective level is a content delivery network, or CDN for short. Here copies of your content are distributed across servers in different locations, so that each visitor receives the data from a server near them. For a purely regional business in Hildesheim the effect is smaller than for a nationwide provider, but with many images it can still be noticeable. It is important to configure caching correctly: if caching is too aggressive, visitors see outdated content; if there is no caching at all, you give away speed.

Caching helps returning visitors most

The biggest advantage of browser caching shows on the second visit: returning visitors do not have to reload images, fonts and code and see the page almost instantly. For local businesses with regular customers who frequently check opening hours or services, this is a pleasant effect that costs little effort.

How to Proceed in a Structured Way

You do not have to tackle everything at once. A clear order that starts with the biggest lever makes sense. Step one is measurement: start a Lighthouse analysis and note the current values for LCP, INP and CLS. This gives you an honest starting point and lets you later prove that something has improved. Without measurement, every optimization stays gut feeling. Step two is images, because in most cases they bring the largest and fastest gain.

Step three is the look at hosting and code: does the server respond promptly, or is a switch sensible? Does the page load extensions no one uses? Step four is caching, which secures the improvements achieved and rewards returning visitors. After each step, a renewed measurement is worthwhile to see the effect. This step-by-step approach prevents you from spreading yourself too thin and makes progress visible. A fast website is not an end in itself but pays directly into more enquiries through your website.

Staying realistic also means: not every page has to be perfect in every discipline. A content-rich page with many images will never be as light as a simple business-card page. The goal is not the theoretical best score but a page that feels fast and smooth for real visitors and supports your business goals. Those who know the four levers and use them in the right order achieve exactly that – without miracle cures and without untenable promises. A fast page pays off especially when you additionally use Google Ads for local businesses wisely or run an online shop for local retailers, because every second of delay costs real money there. How a fast website fits into a coherent overall concept is shown on our page on web design from Hildesheim.

This article is based on data from: Google Search Central and Think with Google (Core Web Vitals, bounce probability and mobile load time), Deloitte (the Milliseconds Make Millions study on the impact of load time on conversions), Portent (conversion rate by load time), Statista (share of mobile web usage) and our own projects with regional businesses. The values mentioned can vary depending on industry, page structure and device; figures marked (project experience) are based on our own projects and do not represent guaranteed results.