Approach
First comes measurement: which scripts, fonts and images does the site load, which are needed and which are just carried along?
Sometimes a clean-up is enough: removing plugins, serving images at the right size or only loading them once the user actually scrolls there, setting up caching.
If the structure of the site itself is the problem, only a rebuild without it helps: server-rendered, loading only the code the page needs when it needs it, and the Core Web Vitals are in the green.
That also helps the placement on Google and in AI search engines.
What drives the effort
- Whether a clean-up is enough or something has to be replaced
- The number and kind of pages, images and embedded services
- Forms and features that should be rebuilt
Every quote is preceded by a free conversation.
In practice
When it is not worth it
If the measurement shows two plugins and uncompressed images are the problem, it gets cleaned up, not rebuilt. A rebuild only pays off with deeper problems such as an outdated technical base, or when a redesign is wanted.
Common questions
- How much does load time really matter?
Do not underestimate how quickly clients lose interest these days. Load time is one of the most important factors in whether someone stays, which is why the big search engines weigh it in their rankings. Above all it shapes the first impression, before a single word has been read.
- Can we check the load time ourselves?
Yes, for free with Google’s PageSpeed Insights. The mobile figures are the ones that count.
- Why are all these plugins on my site?
It seems quicker to build features with specialised plugins. A prominent example is a plugin for the image slideshow at the top of the page. But these plugins are huge, because they cover thousands of use cases. For an individual case, custom code is often the better choice: the result looks the same and usually loads noticeably faster.