oneclickflare.com website review

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

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

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

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

About 145 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

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

2 third-party services load with your homepage (Plausible and ctfassets.net), adding 1.5 MB and 5 ms of main-thread time.

ctfassets.net costs a phone 0 ms of main-thread work and 1.5 MB 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.

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

1 long task block the main thread while loading, the longest for 74 ms. During a long task the page ignores taps.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

Your largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Depuis 10 ans, nous accompagnons les porteurs de projets da…”.

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

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

30 images have no width and height attributes, so the layout jumps as each one loads.

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Capture_d_e_cran_2023-09-14_a__14.21.56.png weighs 920 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.3 MB in 64 requests on a phone: images 2.2 MB (42), scripts 505 KiB (13) and stylesheets 314 KiB (2). Under 2 MB keeps phones on slow connections fast.

14 images (1.7 MB) 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.

18 images further down the page (1.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example Capture_d_e_cran_2023-09-14_a__14.21.56.png at 1,246 px wide, shown at 360 px. Resized copies would save about 229 KiB.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

10 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

The page declares lang=“zxx”, which is not a usable language code (“zxx” means “no linguistic content”), so screen readers and translation tools guess.

Your canonical URL points to oneclickflare.fr, not oneclickflare.com, so Google may credit that host instead.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 29 pages on oneclickflare.com and 1 external page.

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.oneclickflare.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.

Your homepage links to https://www.oneclickflare.com/forms.gle/3g3tmCqqZsthGAVg7, https://www.oneclickflare.com/www.linkedin.com/company/oneclickflare, https://www.oneclickflare.com/www.twitter.com/oneclickflare and https://www.oneclickflare.com/www.facebook.com/One-Click-Flare-155683474479165, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.oneclickflare.com/contact has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.oneclickflare.com/services/architecture and https://www.oneclickflare.com/services/conception-saas took over 3 s to send their HTML from our server.

We fetched 12 pages linked from your homepage and read each the way a search engine does.

6 errors were logged to the browser console while the page loaded, for example “Invalid href passed to next/router: //forms.gle/3g3tmCqqZsthGAVg7, repeated forward-slashes (//) or backslashes \ are n…”.

3 images are served at too low a resolution for sharp phone screens.

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

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

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 975 words of visible text.

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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.