In short and in plain language
Many customers look for a trade firm on their phone, often with a weak signal. If your site loads too slowly, you can lose the request.
There are mostly a few causes. Photos come straight from a phone and are too big. Maps or chat boxes load from other servers. Templates carry too many parts.
Test it yourself on your phone on mobile data, not Wi-Fi. What is still blank after a short time, a customer does not see.
Each new photo can make the site slower. So load time belongs in the regular care of your site.
We build lean sites at a fixed price.
Most enquiries to a trade business do not begin at a desk. They begin on the sofa in the evening when the heating stops working, in the van outside a site in the morning, or during a break when somebody opens three businesses one after another. Two things are true of all these moments: it is a phone, and the signal is rarely good. If your site then needs five, six or eight seconds before anything appears, it is not the quality of your work that decides the enquiry but the patience of somebody in a hurry. This article explains what load time actually costs a trade business, which three causes are almost always behind it — uncompressed photos straight from a phone, embedded third-party content and overloaded templates — and how to establish within a few minutes, without technical knowledge, whether your own site has a problem.
Key takeaways
- Enquiries in the trades arrive mainly on a phone and often over mobile data: at a bus stop, in a cellar next to a dripping pipe, in bed in the evening. The state of your site under a weak signal is therefore the normal case, not the exception.
- These causes above all determine the load time on trade websites: photos uploaded straight from a phone, content pulled from third-party servers such as maps or chat windows, and templates carrying building blocks for many industries (project experience).
- A single site photo from a current phone is often four to eight megabytes. For display on a handset a fraction of that is usually enough, without any viewer noticing a difference.
- The self-test needs no expertise: your own phone, mobile data instead of Wi-Fi, clear the browser history, open the home page and count silently to five. Whatever is still grey or empty after five seconds is invisible to a prospect as well.
- Load time is not a one-off task. It grows with every new project photo, every embed added later and every extension somebody switches on between two appointments — which is why it belongs in the ongoing upkeep of the site.
Where the enquiry actually begins
People looking for a trade business rarely do so calmly. Water damage in the cellar, a storm that has loosened the tiles, a consumer unit that has tripped: these are situations where somebody holds a phone in one hand and searches for the stopcock with the other. Even planned work — a new kitchen, a bathroom, solar panels on the roof — is researched in the evening, once the day is over and the house has gone quiet. In neither case is anybody sitting at a large screen on a fibre connection. It is a phone, it is one hand, and the signal wavers between two bars and none.
This starting point is not a guess but the condition under which your site is judged. 85 percent (Bitkom 2025) of trade businesses report that customers clearly expect constant availability. Availability today does not only mean that somebody answers the phone. It also means that the number, the service area and the contact form are visible immediately — at the moment somebody is searching, not eight seconds later. A site that contains all of this but hides it behind a long loading phase is, for the person searching, effectively unreachable.
Then there is the route by which visitors reach you at all. 88 percent (Bitkom 2025) of businesses are listed in online directories. Tapping a business name there jumps out of an application that has already loaded onto a foreign site — and that site starts with no run-up, with no cached files, under exactly whatever network conditions currently apply. The first impression of your website therefore almost never happens under good conditions. Anyone planning the structure of a site should take that case as the benchmark rather than the view from the office computer, where everything has long been cached. How such a site is built is set out in our overview of our services.
The worst connection is the normal case, not the exception. Building for the office computer means building for the only visitor who is already a customer.
What a slow site costs a trade business
Losses caused by load time are invisible, and that is precisely what makes them dangerous. A prospect who backs out of a white screen after four seconds and opens the next result leaves no trace in your inbox, no missed call, no complaint. Inside the business it looks like an ordinary day with few enquiries. Load time is therefore almost never suspected when people discuss why there are too few enquiries, or the wrong ones. What gets debated instead is wording, colours and search terms — while the drop-off happened long before, before any text could be read at all.
The second cost is comparison. In Germany 1,038,126 (ZDH 2025) businesses are entered in the trade registers and in the register of trade-like occupations, and 94 percent (Bitkom 2025) of trade businesses run their own website. In every trade and every district, several businesses therefore sit side by side in the results. Whoever is slowest in that row does not lose to a better offer but to a faster-loading page. The customer notices nothing of this comparison and simply taps the next entry.
The third point is reputation. 74 percent (Bitkom 2025) of businesses find that customers have become more critical. Anyone looking for a business for a four-figure job also checks whether that business appears to have its affairs in order. A site that stutters, jumps and shows grey boxes for a long time sends a signal that has nothing to do with craftsmanship — and lands all the same. Load time is therefore not a technical footnote but part of how the business presents itself, much like a clean van and a tidy materials trailer.
The drop-off comes before the text
Cause one: photos straight from the phone
By far the most common cause lies not in technology but in a well-meant habit. The owner photographs the finished bathroom, the freshly tiled gable, the installed consumer unit — and uploads the shot exactly as it comes off the phone. On current devices such an image often measures several thousand pixels along its edge and weighs several megabytes (project experience). On a phone screen it is displayed across perhaps four hundred pixels. Everything else is transferred, paid for in load time and data allowance — and then discarded.
It becomes critical when several such images sit on one page. A reference gallery with twelve untouched shots easily reaches several dozen megabytes. On office Wi-Fi this barely registers, because the images arrive in fractions of a second and are read from the cache on the second visit anyway. On mobile data on a country road between two villages, the same gallery is a wait nobody sits through. The business sees its site load quickly, the customer sees it load slowly — and both are looking at the same site.
The remedy is unspectacular and costs nothing in picture quality. A photo prepared for display on a website and a phone usually weighs a few hundred kilobytes rather than several megabytes, with no visible difference on screen. On top of that comes delivery in several sizes, so that a phone loads the small version and a large monitor the large one. Anyone regularly adding their own shots will find the right order of taking, choosing and preparing them in our services overview.
The trap of resizing on screen
| State of the image | Typical file size | Effect on mobile data |
|---|---|---|
| Uploaded straight from the phone | 4 to 8 MB per shot | One gallery blocks the page for many seconds |
| Scaled to display size, not compressed | 1 to 2 MB per shot | Noticeably better, still too much across twelve images |
| Scaled to display size and compressed | 150 to 400 KB per shot | Gallery appears while scrolling without slowing the page start |
| Additionally delivered in several sizes | 40 to 150 KB on a phone | The phone loads only the version it actually displays |
Cause two: content from third-party servers
The second cause is harder to spot because in the page editor it looks like a single line. An embedded map, a video above the directions, a font package from an external server, a chat window in the bottom corner, a display of reviews, plus the scripts for consent and statistics: each of these embeds is a separate call to somebody else's computer. Your phone has to look up its address, establish a secure connection, wait for the server to answer and often fetch further files that this server only names in a second step.
On a fast connection these processes run side by side and barely register. On mobile data it is the wait for that first answer that makes the difference: every additional counterpart means another connection setup, and that costs time even when only a few kilobytes are transferred in the end. Particularly unpleasant are embeds that halt the build-up of the page until they are finished. The whole page then stands still because an external service happens to be slow — and your visitor sees an empty area even though your own content has long been ready.
For a trade business the benefit of these embeds is often smaller than their price. Directions can be handled as an address with a link that opens the phone's own map application — where they belong better anyway than in a small embedded window. Fonts can sit on your own server and then start without an external counterpart. Reviews can be quoted as text on the page, provided they are genuine and verifiable. As a side effect this defuses the consent questions, because whatever is never loaded never has to be permitted. Legally each case has to be examined on its own merits; technically the rule is simple: what is absent cannot slow you down.
- Embedded map: replaceable by an address, written directions and a link that opens the phone's map application.
- Fonts from an external server: replaceable by the same fonts on your own server, which removes one counterpart entirely.
- Video above the directions: replaceable by a preview image that only loads the video after a tap.
- Chat window: worth it only if somebody in the business actually answers — otherwise it costs load time for a function nobody staffs.
- Counting and statistics scripts: one lean tool is enough, several running in parallel add no further insight.
- Review display as an embed: replaceable by quoted voices on the page, provided they are genuine and cleared for use.
Cause three: the overloaded template
The third cause lies in the foundation. A ready-made template is meant to suit as many buyers as possible and therefore brings along everything anybody might need: image galleries in four flavours, price tables, appointment calendars, scroll animations, several icon fonts, sliders for customer voices. A trade business uses perhaps a fifth of that. The rest is delivered anyway, because the template does not know which building blocks appear on which page. The visitor therefore downloads the possibilities of the kit, not just the content of your business.
Then there is the accumulation of extensions. Every function switched on later — an extra form, a calendar, an image gallery, a consent tool — brings its own files, often another font package and sometimes its own version of a code library that has already been loaded twice. After two years of upkeep by changing hands, such a site is technically a materials store in which every offcut is still lying around. Anyone wondering whether clearing up is worth it or whether a rebuild is the more honest route will find that weighing-up in our services overview.
Blocks nobody uses
Templates ship functions for twenty industries. Whatever never appears on your pages is still transferred and processed.
Duplicated libraries
Two extensions bring the same basic function in different versions. The phone loads both and keeps both in memory.
Font packages without need
Several font weights and complete icon fonts are often loaded although the page uses three icons and two weights.
The self-test: five minutes, no expertise
For a first reliable impression you need no measuring tool and no service provider. You need your own phone, mobile data instead of Wi-Fi and the willingness to look at your own site the way a stranger sees it. What matters is that the cache is empty: your phone knows your site, it already holds the images, fonts and scripts and shows them in fractions of a second. That is exactly what distorts the result. A prospect arrives without those supplies.
Run the test somewhere the signal is not ideal — in the cellar, in the workshop, in the van between two villages. That is not unfair, it is the everyday reality of your visitors. Then repeat it with the two or three pages that matter for enquiries: the home page, the most important service page and the contact page. Whatever is slow there costs work directly; whatever is slow on the page about the history of the business is annoying but secondary.
Switch off Wi-Fi
Turn Wi-Fi off in the phone settings so that the page really loads over the mobile network. Without this step you are measuring your office connection, not the reality of your visitors.
Clear history and cache
Delete the browser history including website data, or open a private window. The page then starts without supplies, exactly as it does for somebody opening it for the first time.
Count to five
Open the home page and count silently to five. Note what is visible after that time: text and phone number, or a grey area with jumping boxes.
Watch for the jump
Pay attention to whether the content still shifts after appearing because images or notices claim space belatedly. Anyone tapping the phone number at that moment ends up somewhere else.
Compare with two other businesses
From the same spot, open the sites of two businesses in the same trade. The comparison says more than any number of seconds, because it assumes the same network conditions.
Write down the result
Record in two sentences what you saw, with the date and place. That note is the basis for any conversation about the next steps.
Turn Wi-Fi off in the phone settings so that the page really loads over the mobile network. Without this step you are measuring your office connection, not the reality of your visitors.
Delete the browser history including website data, or open a private window. The page then starts without supplies, exactly as it does for somebody opening it for the first time.
Open the home page and count silently to five. Note what is visible after that time: text and phone number, or a grey area with jumping boxes.
Pay attention to whether the content still shifts after appearing because images or notices claim space belatedly. Anyone tapping the phone number at that moment ends up somewhere else.
From the same spot, open the sites of two businesses in the same trade. The comparison says more than any number of seconds, because it assumes the same network conditions.
Record in two sentences what you saw, with the date and place. That note is the basis for any conversation about the next steps.
The test that is even more honest
Which figures matter and which only look good
Anyone having a site measured ends up with numbers and often a colourful score from zero to one hundred. That overall score is the least informative part of the report, because it condenses many individual values into one figure and depends heavily on the conditions of the measurement. For a trade business, three things matter more than any score: when does the first visible content appear? When is the largest element in the visible area in place? And does the layout stay calm while the rest loads?
As orientation for the largest visible element, a value below 2.5 seconds has become established; for a calm layout, the rule is that nothing should shift after the first appearance. These are technical thresholds, not promises: a site can reach them in an office run and miss them in a signal hole. It therefore makes sense to follow not a single measured value but the direction — measure before the change, measure again after it, under the same conditions, in the same place, with the same device.
Just as revealing as the seconds is the size of the page. How many megabytes are transferred for a single visit to the home page, and how many individual requests does the phone make in the process? Both values can be read in any desktop browser's developer view and need no external service. A home page that reaches several megabytes and well over a hundred individual requests has a problem no score can talk away. And both numbers are pleasantly concrete for a business, because they change immediately with every photo removed and every embed dropped.
What a business can change without an agency
A considerable part of the load time can be cleared without technical knowledge, because it consists of content rather than programming. The single biggest lever is usually the stock of images: bringing every photo down to the width the page actually needs before uploading, and compressing it, often removes most of the transferred data volume without changing how anything looks. The tools built into the operating system or a simple image program are enough; no service provider is needed for that.
The second lever is clearing up. Go through the list of active extensions and ask one question about each: what happens if this is no longer there? For a chat window nobody has staffed for eighteen months, for a slider with three images and for a second statistics tool, the answer is usually: nothing. What remains afterwards is the honest size of your site. If you are unsure about switching things off, have the step accompanied — that is what ongoing support from 49 euros per month is for, cancellable monthly, with no minimum term. Details are in our services overview.
- Bring every photo down to the width the page actually needs before uploading and compress it.
- Cut galleries down to the shots that actually show something — twelve mediocre images are weaker than four good ones.
- Replace the embedded map with an address, written directions and a link to the map application.
- Load videos only after a tap rather than when the page opens.
- Switch off extensions whose absence nobody in the business would notice.
- Keep the phone number and the route to an enquiry high enough on the home page that both appear without scrolling.
- Repeat the mobile self-test after every change and note the result with the date.
When repair is enough and when a rebuild is more honest
Repair pays off when the foundation is sound and the weight comes from content. If your site stands in under two seconds without the images and the load time consists essentially of one heavy gallery, the matter is settled with an afternoon of work. A handful of superfluous embeds can also be removed one by one without anybody rebuilding the site. As long as the structure is right and only the luggage is too heavy, a rebuild would be the more expensive route to the same result.
It is different when the template itself is the brake, when a dozen extensions interlock and nobody can say any more which one is responsible for what. Every improvement is then a repair to a construction that was never meant for this business, and the next update may well restore the old state. In such cases a rebuild on a lean foundation is not the luxury route but the cheaper one, above all because it eases the upkeep of the years to come.
Orders of magnitude without surprises
A sober calculation helps with the decision. How many enquiries a month does your business need for the site to carry itself, and what is a single job worth in your trade? For a boiler replacement, an electrical distribution board or a roof build-up, the value of one job won often exceeds the cost of a new website. That calculation is no promise of success — it merely puts the orders of magnitude in the right relation and prevents saving in the wrong place.
Load time stays an ongoing task
A site that is fast today will not stay fast on its own for two years. Every new project photo, every embed added later, every extension somebody switched on between two appointments adds another layer. The process is gradual, and because the business usually sees its own site from the cache, it is the last to notice. Load time therefore belongs in the same rhythm as checking your equipment: a fixed date, not an occasion.
A sensible cadence is quarterly, together with a look at content and details: are the opening hours current, is the service area right, are new services represented? The five-minute self-test fits into that same slot. Anyone having the site maintained gets this check included; anyone maintaining it themselves should put the date in the calendar, because without a date it does not happen.
In the end this is not about seconds but about whether a person with a problem and little patience reaches you or the next business. The work on site decides whether they come back. The load time decides whether they call at all. Both belong to the same business, and only one of them can be improved in an afternoon. How structure, content and technology of a trade website work together is shown in our services overview.
Related Articles
Video on a trade website: short, silent, useful
How long a video on a trade website may run, why it starts silently, and what a still image, captions and load time have to do with it in daily practice.
Websites for joineries: the picture sells
How a joinery gallery shows bespoke work rather than catalogue goods: material and finish in the caption, price ranges for fitted furniture, measure as sale.
Why trade businesses lose calls before the phone rings
A number that cannot be tapped, a slow page, hidden opening hours: where a trade enquiry breaks off before anyone dials, and what a business can do here.