How can I improve my website’s loading time?
A slow website costs visitors, inquiries and visibility. This guide takes you through seven steps from measurement to lasting monitoring – and shows what you can do yourself and when experts make sense.

You improve your website’s loading time fastest by measuring on a mobile device first and then removing the biggest bottlenecks: shrink oversized images and deliver them in modern formats, ensure a fast server response through good hosting and caching, remove unneeded code and font weights and reduce third-party scripts. According to Google’s Core Web Vitals, an LCP of up to 2.5 seconds, an INP of up to 200 milliseconds and a CLS of up to 0.1 count as good. At Nano Concepts we handle analysis and implementation; we calculate page speed optimization individually by scope and send you a quote after the free initial consultation.
Step 1: Measure loading time and know the target values
Before you change anything, you need baseline values. Use Google PageSpeed Insights to measure at least the home page and two important subpages, each for mobile devices. The tool shows two kinds of data: field data from real visitors, where enough exists, and lab data from a simulated test. The field data is decisive, and you also find it in the Google Search Console in the Core Web Vitals report. Write down the values so you can prove progress.
The three metrics set the bar: LCP measures when the largest visible content has loaded, INP how quickly the page responds to clicks and input, and CLS how much content shifts while loading. In each case the 75th percentile of visits is assessed. A high score in the lab test is a hint but not proof; what matters more is whether real visitors on real devices experience fast pages.
- LCP (largest visible content): good up to 2.5 seconds
- INP (response to input): good up to 200 milliseconds
- CLS (layout shifts): good up to 0.1
- Measure on mobile, separately for home page, service page and contact page
Step 2: Slim down images and videos
Images are the biggest lever on many websites. Photos are often uploaded at original size even though they are displayed small. Scale images to the actual display size, compress them and deliver modern formats such as WebP or AVIF. With several sizes per image, a smartphone loads only the small version. Also specify width and height so the space is reserved and the page does not jump while loading.
Load images below the visible area with a delay, but the main image at the top immediately and with high priority – this image is often the LCP element. Videos should not load automatically. Embedded videos from platforms can be set up so that only a preview image appears and the player loads after a click. This saves data and also fits the requirements of data protection.
Step 3: Check server, hosting and caching
A website cannot appear faster than the server responds. Check the server response time in the measurement tools: if it is permanently high, the cause is often overloaded cheap hosting, outdated server software or a website that recalculates every page on every request. Switch to a current PHP version if your system uses PHP, and clarify with your host whether the plan matches your visitor volume.
Caching avoids unnecessary work: a page cache serves finished pages, browser caching lets returning visitors reuse files locally, a content delivery network brings files closer to the visitor. Also enable compression of the transfer, for example with Brotli or gzip. With WordPress it is also worth looking into the database, where revisions and leftovers accumulate that can slow down every request.
- Check server response time in the measurement tools
- Review hosting plan and PHP version
- Set up page cache and browser caching
- Enable compression of the transfer
- Consider a content delivery network for an international audience
Step 4: Slim down code – CSS, JavaScript and fonts
Every script and every stylesheet has to be loaded and processed. Remove what you do not need: unused libraries, duplicate functions, superfluous plugins. Files can be minified and combined; JavaScript that is not needed for the first display should load later or deferred. Themes and page builders that ship a lot of code for features your site never uses are a particular drag.
Fonts cost time too. Use only the font weights that actually appear, load them in the compact WOFF2 format and serve them from your own server instead of calling external services – that is usually faster and more privacy-friendly. With a suitable setting, a fallback font is shown first so text is readable immediately. For every plugin, check whether its benefit justifies the loading effort.
Step 5: Keep third-party scripts under control
Analytics, advertising pixels, chat windows, maps, social media embeds and cookie banners come from external servers and run outside your control. Each of these services costs loading time, burdens the page’s responsiveness and is also a data protection issue. List all integrated services and remove what has no clear benefit. Old tags in the tag manager are a frequent find.
What remains should be loaded as late and as conditionally as possible: scripts that require visitor consent only after the decision, maps and videos only after a click, chat widgets after the first interaction. That relieves the important first impression, and your privacy solution works cleanly. For legal questions about consent, please seek expert advice; this does not replace legal advice.
Step 6: Improve layout shifts and responsiveness
A high CLS value arises when content shifts during loading because space is missing: images without size information, banners that load late, embeds or fonts that change size on swap. Reserve space for such elements and make sure notice bars do not push the content down. This can often be fixed with a few layout adjustments and improves the impression immediately.
A poor INP value shows that the page shows nothing for too long after a click – usually because heavy scripts block the browser. Less and leaner JavaScript, splitting long tasks and doing without elaborate effects help here. Test on a simple, older smartphone and not only on your fast work device, because that is where weaknesses become visible that your visitors experience every day.
Step 7: Stay on it – measurement, budget and editorial rules
A fast website does not stay fast on its own. Every new plugin, every large image and every additional script gradually worsens the values. Set limits, such as maximum image sizes for the editorial team and a check before new services are integrated. Measure again after larger changes and updates and watch the Core Web Vitals report in the Search Console, because it shows bad trends early.
Sometimes the adjustments are not enough: if the theme, page builder or system architecture itself is the drag, a technical rebuild or relaunch is the more economical solution. Speed is one factor among many for visibility but does not replace good content; above all it improves your visitors’ experience. We analyze your website, implement the measures and set up monitoring so the values stay good in the long term.
What to look out for
Measure and set targets
Measure on mobile, pay attention to field data and record baseline values for LCP, INP and CLS.
Images and videos
Scale to display size, compress, use modern formats and reserve space.
Server and caching
Fast server response, current software, page cache, browser caching and compression.
Code and fonts
Remove unused scripts and plugins, minify files, load fonts lean and locally.
Third-party scripts
List services, remove unnecessary ones, load the rest only after consent or a click.
Layout stability
Reserve space for images, banners and embeds so nothing jumps.
Responsiveness
Reduce heavy scripts, split long tasks and test on simple devices.
Lasting monitoring
Editorial rules, measuring again after updates and watching the Search Console.
Your take-away checklist
- Measure the home page and two other important pages with PageSpeed Insights on mobile and note the values
- Check the Core Web Vitals report in Google Search Console
- Shrink images to display size, compress them and deliver them in modern formats
- Prioritize the main image in the visible area and lazy-load the other images
- Check hosting plan, PHP version, page cache and compression
- Remove unneeded plugins, scripts and font weights
- List all third-party scripts and reduce them to what is necessary
- Measure again after every larger change and document the values
How we support you

Page Speed Optimization
Faster load times and better Core Web Vitals – targeted optimization of images, code, plugins and server.
Learn more
Technical SEO Audit
A review of your website's crawling, indexing, structure and load time – with a prioritized action plan and implementation.
Learn more
Web Development
Websites with real functionality: calculators, forms, customer portals and integrations – cleanly programmed and fast.
Learn more
WordPress Maintenance
Core, theme and plugin updates, backups, security and monitoring for your WordPress website – tested and logged.
Learn moreFrequently asked questions
First measure with PageSpeed Insights on a mobile device and then remove the biggest bottlenecks: shrink images, check hosting and caching, remove unneeded code and plugins and reduce third-party scripts. Then measure again. For bigger problems we support you with page speed optimization.
There is no single number of seconds for the whole page. Google evaluates three metrics: an LCP of up to 2.5 seconds, an INP of up to 200 milliseconds and a CLS of up to 0.1 count as good, each for at least three out of four visits. The yardstick is therefore the experience of real visitors.
Common causes are oversized images, slow hosting, missing caching, many plugins or heavy themes and numerous third-party scripts. Which of these is decisive in your case is shown by a measurement with an evaluation of the individual items.
Use Google PageSpeed Insights for a single page and Google Search Console for an overview of all pages. Pay attention to field data from real visitors and measure on mobile. Lab values help with troubleshooting but do not replace field data.
Yes, a lot can be done yourself: optimize images, set up a cache, remove unneeded plugins and update the PHP version. If you hit limits, for instance with a heavy theme or page builder, help from experts or a technical rebuild is worthwhile.
Core Web Vitals are one factor among many and do not replace relevant content. A fast page does, however, improve user experience, reduces the chance that visitors leave and thereby supports your goals beyond rankings.
More guides & comparisons

How much does a website cost per month – and per year?
The monthly cost of a website is made up of the domain, hosting, email mailboxes, possible licenses for themes, plugins, or tools, and maintenance and updates; an SSL…
Learn more
How much does SEO cost – and is it still worth it?
What SEO costs depends on the starting condition of the website, the competition for the desired search terms, the number of pages and locations, and whether technical…
Learn more
How long does it take for Google to find a website and for SEO to work?
It usually takes a few days to a few weeks for Google to find and index a new website – Google itself puts crawling at anywhere from a few days to a few weeks.
Learn more
WordPress or a website builder like Wix and Jimdo – which is the better fit?
A website builder like Wix or Jimdo is the right choice if you want to run a small website with only a few pages yourself, quickly and without technical effort – the…
Learn more
WordPress or TYPO3 – which CMS is right for your company?
WordPress is the right choice for most business websites, blogs and stores, up to mid-sized companies (Mittelstand): quick to set up, easy to use and backed by the…
Learn more
Wix or WordPress – which system is the better foundation for your company website?
Wix is the right choice if you want to build and maintain a manageable company website yourself, quickly, and do not want to take responsibility for technology, hosting…
Learn moreNeeds analysis: Improve loading time
Answer a few short questions – we usually get back to you within 24 hours with an initial assessment.
Request a project