spuerkeess.lu website review

12 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.5 s.

About 220 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.

About 165 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.2 s).

The page has 3,022 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

14 images could be 345 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.

Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.

3 third-party services load with your homepage (piwik.pro, cookieinformation.com and eye-able.com), adding 358 KiB and 297 ms of main-thread time.

8 files are served with short cache lifetimes, so returning visitors download them again (51 KiB).

4 long tasks block the main thread while loading, the longest for 173 ms. During a long task the page ignores taps.

Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

4 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 14.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Nous et nos partenaires commerciaux utilisons des technolog…”.

The page becomes fully interactive after 14.4 s. Good is under 3.8 s.

The first text or image appears after 4.6 s on a phone. Good is under 1.8 s.

Visually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.

Real visitors wait 419 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 203 ms to 321 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Scripts block taps and scrolling for 242 ms in total while the page loads. Good is under 200 ms.

Your homepage downloads 2.1 MB in 69 requests on a phone: images 982 KiB (29), scripts 554 KiB (22) and fonts 350 KiB (6). Under 2 MB keeps phones on slow connections fast.

14 images (864 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

15 images further down the page (663 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images are downloaded at several times the size a phone draws them, for example csm_261023_cover-leaseplus-fall-2026__1__22111e42d7.jpeg at 1,554 px wide, shown at 358 px. Resized copies would save about 248 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 0.61 g of CO₂e: 72.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

No XML sitemap at https://www.spuerkeess.lu/fr/particuliers?sitemap=pages&type=1533906435, so Google discovers your pages only by following links.

The homepage links to 84 pages on spuerkeess.lu and 15 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.spuerkeess.lu/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.spuerkeess.lu/fr/particuliers and / all use the title “Spuerkeess: Votre banque au Luxembourg”. Search engines can't tell which page to show for a search, so each competes with the others.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://www.spuerkeess.lu/fr/particuliers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

We fetched 15 pages linked from your homepage (of 55 found) and read each the way a search engine does.

8 of 37 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “Error: <svg> attribute width: Expected length, "64c".”.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 5 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,843 words of visible text.

Opening the homepage sets 4 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.