qonto.com website review

JSDelivr CDN costs a phone 2.3 s of main-thread work and 96 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 6.9 s on main-thread work while loading, 3.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

7 files are served with short cache lifetimes, so returning visitors download them again (6.1 MB).

8 third-party services load with your homepage (JSDelivr CDN, Didomi and Bing Ads and others), adding 645 KiB and 2.5 s of main-thread time.

2 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

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

Didomi costs a phone 115 ms of main-thread work and 359 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 46 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

Polyfills for old browsers add 7 KiB JavaScript that modern phones do not need.

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.

4 KiB could be saved by minifying JavaScript.

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 17.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your data. Your choice. Like many websites, we use cookies.…”.

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

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

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

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

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

The layout shifts by 0.105 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Your homepage downloads 10.0 MB in 135 requests on a phone: images 7.6 MB (22), scripts 1.3 MB (68) and other files 742 KiB (37). Under 2 MB keeps phones on slow connections fast.

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

<svg> elements with an img or image role must have alternative text: 8 elements on the page fail this check, rated serious by axe-core.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Structured data found (Brand, Product, Service and ServiceChannel) but with 2 problems, for example “Service: no offers (price) block”.

No XML sitemap at https://qonto.com/sitemap.xml.gz, so Google discovers your pages only by following links.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 143 pages on qonto.com and 22 external pages.

Your Organization JSON-LD is missing url, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://qonto.com/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://qonto.com/en/get-paid is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

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

1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=6001655&tm=gtm002&Ver=2&mid=02ebdf80-9050-4d7d-b90d-ec34fca70b45&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Manage%20all%20your%20finances%20from%20your%2.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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.

The homepage carries about 896 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Microsoft Ads (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.

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

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