A site is considered slow as soon as its largest visible element takes more than 2.5 seconds to appear, a threshold published by Google. For Luxembourg SMEs, the cause almost always comes down to images, the theme, plugins or hosting. The diagnosis takes thirty minutes and needs no technical skill.
What Google really measures when it judges your site slow
Most business owners discover the subject through a score out of 100 shown in red in a testing tool. That score comes from a lab simulation and is not what Google uses. What counts are the measurements collected from real visits.
Google groups these measurements under the name Core Web Vitals. Three indicators, three public thresholds, and one rule of reading that changes everything: your page is judged at the 75th percentile of visits, in other words on the three quarters of your audience that are served worst. A page that is fast on fibre in the office can fail for a visitor on 4G.
The three thresholds published by Google
LCP (Largest Contentful Paint): the largest visible element must appear in 2.5 seconds at most. This is loading.
INP (Interaction to Next Paint): the page must respond to a click in 200 milliseconds or less. This is responsiveness.
CLS (Cumulative Layout Shift): the visual shift score must stay below 0.1. This is what stops a button dodging away under your finger.
These thresholds are documented by Google on web.dev (page updated on 31 October 2024). The Google Search Central documentation (updated on 10 December 2025) states that these indicators align with what the ranking systems seek to reward. It is not the number one SEO factor, but it is a factor your competitors can fix before you do.
What slowness costs in visitors and revenue
The cost never shows up in a dashboard: a visitor who leaves during loading is simply counted as a visit with no follow-up. That is why the subject stays invisible for years.
Case studies published by the Chrome team give documented orders of magnitude. Vodafone Italy improved its LCP by 31% and recorded 8% more sales. Agrofy Market improved its LCP by 70% and saw a 76% reduction in abandonment during loading. These figures come from the page The business impact of Core Web Vitals published by Google on web.dev (September 2021). They concern large platforms and do not transfer to a Luxembourg business website, but they indicate the possible scale.
One point deserves the attention of business owners who invest in advertising: on a Google Ads or Meta campaign, you pay for the click before the page appears. Slowness therefore mechanically raises the cost of your paid traffic.
The 7 most common causes for SMEs
On a business website or a small online shop running WordPress, the same causes come back with striking regularity.
1. Images published as they are
A photo straight from a camera often weighs several megabytes to be displayed in a block 600 pixels wide. This is the first cause of a poor LCP, and the simplest to fix: a properly prepared banner rarely exceeds 200 kilobytes in a modern format.
2. A theme and page builder that are too heavy
Visual builders generate a lot of code for little visible result. When the theme bought four years ago also brings its own libraries, the page loads files of which it uses only a few lines.
3. An accumulation of plugins
Each plugin adds its files to every page, including those where it serves no purpose. A contact form sometimes loads its library on the home page. Twenty active plugins are a warning sign.
4. Shared hosting that is running out of steam
If the server takes more than a second to respond before it even sends the page, no content optimisation will make up the delay. This is the typical case of a plan shared with hundreds of other sites.
5. Third-party scripts and the cookie banner
Analytics, advertising pixels, live chat, maps, review widgets: each one opens an external connection. The consent banner, loaded with top priority, often delays the display of the main content.
6. No cache and no compression
Without a cache, the server rebuilds the whole page on every visit. Without compression or modern image formats, it sends files two to three times heavier than necessary. These are settings, not development work.
7. Fonts and carousels that make the page jump
A font that loads late makes all the text move. A carousel with no declared dimensions pushes the content down when it appears. The CLS gets worse, and the user clicks the wrong button.
| Cause | Indicator | Effort |
|---|---|---|
| Unoptimised images | LCP | Low |
| Heavy theme and builder | LCP and INP | High |
| Accumulated plugins | LCP and INP | Medium |
| Slow hosting | LCP | Medium |
| Third-party scripts and cookies | INP and LCP | Medium |
| No cache or compression | LCP | Low |
| Fonts and carousels | CLS | Low |
Why the Luxembourg context makes the problem worse
Three local particularities weigh on the performance of SME websites in Luxembourg and the Greater Region.
Multilingual sites. A site in French, German and English generally goes through a translation plugin that adds its own processing layer to every page. Badly configured, it loads the resources of all three versions instead of just one.
An audience on the move. A significant share of traffic comes from cross-border commuters browsing on their phones, between Arlon, Thionville, Trier and the capital, on a variable mobile connection. These are exactly the visits that pull your 75th percentile down.
Sites built in layers. Many Luxembourg sites were created six or eight years ago, then modified by several successive providers, each adding their plugins without removing those of the previous one. The slowness is not an accident, it is sedimentation.
Diagnosing your site in thirty minutes
No technical skill is needed to know where you stand.
- Test three pages, not one. Home page, main service page and contact page. Problems differ from one page template to another.
- Open PageSpeed Insights and read the top block first. This is the section with real data collected from Chrome users. The coloured score further down is a simulation: it guides the fixes, it does not judge your site.
- Note the three values of LCP, INP and CLS for mobile, and compare them with the thresholds of 2.5 seconds, 200 milliseconds and 0.1.
- Look at the server response time. If it exceeds one second, the main problem is the hosting and nothing else will make up for it.
- Open the Core Web Vitals report in Google Search Console. It groups your URLs by type of problem across the whole site.
The trap of the score out of 100. A site can show 92 in simulation and fail on real data. A provider that promises a score rather than a measured improvement for your visitors is selling the wrong indicator.
What budget to plan for fixing it
The levels that follow are indicative orders of magnitude, matching ranges of effort commonly seen on the market for an SME business website on WordPress, to be adjusted according to the size and age of the site.
Level 1, the clean-up. Image compression, proper cache, removing unnecessary plugins, adding missing dimensions. One to two days of work: the best ratio of effort to result, often enough on a simple site.
Level 2, in-depth optimisation. Reworking page templates, deferred loading of third-party scripts, a decision on the consent banner, hosting migration, sometimes replacing theme components. Three to six days depending on scale.
Level 3, the redesign. When the theme and the page builder are themselves the cause, optimisation hits a ceiling and every fix becomes a workaround. At that stage, it is better to invest in a technical redesign of the site, keeping the content and the SEO.
The tipping criterion is simple: if after level 1 the three indicators are still red on mobile, the problem is structural. Our method: measure, fix, then measure again over twenty-eight days of real data. A gain that doesn’t show up in the field is not a gain.
Mistakes to avoid when you hand over the optimisation
Buying a score instead of an experience. Some services satisfy the testing tool without the visitor noticing anything. Demand a before-and-after comparison on field data.
Piling a cache plugin on top of the problem. Badly set up, it masks a heavy architecture and sometimes breaks the display. It treats the symptom, not the cause.
Forgetting monitoring. An optimised site degrades as soon as a plugin is added or a new pixel is installed. Continuous site monitoring avoids redoing the same work eighteen months later. And if the slowness comes with a drop in visibility, the subject also becomes a matter of SEO.
Frequently asked questions
At what loading time is a site considered slow?
Google sets the LCP threshold at 2.5 seconds for the largest visible element of the page, measured on real visits at the 75th percentile. Beyond 4 seconds, the page is rated poor in Google’s tools.
Does speed really influence SEO?
It is one of the page experience signals that Google documents publicly. It is not the dominant criterion, content and relevance come first, but all else being equal between two sites, page experience breaks the tie.
My site is fast on my computer, so why does the test say the opposite?
Because you are testing from a fast connection, with a page already cached in your browser. The official measurements are about visitors discovering the page, often on mobile and over a cellular network.
Do you need to change host to go faster?
Only if the server response time regularly exceeds one second. In many cases, the weight of the images and the number of plugins matter more than the hosting itself.
Is a multilingual site necessarily slower?
No, but it often is, because the translation layer is badly configured. A well-built trilingual site loads only the resources of the language displayed.
How long before I see a result in Search Console?
The Core Web Vitals report relies on a rolling window of twenty-eight days of real data. Allow about a month after the fix to see the curves fully move.
Sources
- Google, Web Vitals, web.dev, page updated on 31 October 2024: definitions and thresholds of LCP, INP and CLS, reading at the 75th percentile.
- Google Search Central, Understanding Core Web Vitals and Google search results, updated on 10 December 2025: role of Core Web Vitals in page experience.
- Google, The business impact of Core Web Vitals, web.dev, September 2021: Vodafone Italy and Agrofy Market case studies.
- Google PageSpeed Insights and Google Search Console: official measurement tools cited in the diagnostic method.









