flsunfrance.com website review

9 images could be 782 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.

8 third-party services load with your homepage (Shopify, Stripe and razorpay.com and others), adding 2.2 MB and 968 ms of main-thread time.

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

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

Shopify costs a phone 608 ms of main-thread work and 1.1 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.

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

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

About 428 KiB of JavaScript is downloaded but never used on this page.

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

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

razorpay.com costs a phone 150 ms of main-thread work and 789 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.

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

20 KiB could be saved by minifying CSS.

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

Polyfills for old browsers add 23 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.

5 KiB could be saved by minifying JavaScript.

Your largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

Your homepage downloads 4.1 MB in 405 requests on a phone: other files 1.7 MB (318), images 1.1 MB (16) and scripts 1.0 MB (57). Under 2 MB keeps phones on slow connections fast.

8 images are downloaded at several times the size a phone draws them, for example lesimprimantes_SR.jpg at 1,280 px wide, shown at 360 px. Resized copies would save about 307 KiB.

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

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

3 buttons have no accessible name, so screen readers announce just “button”.

3 dropdowns have no label.

64 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

6 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 26 characters: “FLSUN FRANCE – FlsunFrance”. Between 30 and 65 characters leaves room to say what you do and for whom.

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.

The homepage links to 147 pages on flsunfrance.com and 12 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.

https://flsunfrance.com/products/flsun-v400-super-racer-imprimante-3d-delta-flsun3d declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://flsunfrance.com/products/flsun-v400-super-racer-imprimante-3d-delta-flsun3d all use the title “FLSUN FRANCE – FlsunFrance”. Search engines can't tell which page to show for a search, so each competes with the others.

https://flsunfrance.com/collections/imprimante-3d-delta, https://flsunfrance.com/collections/tous-nos-filaments, https://flsunfrance.com/collections/pla-ultra-speed, https://flsunfrance.com/collections/bobine-plastique-ams-roll, https://flsunfrance.com/collections/mega-pack-grossiste and https://flsunfrance.com/collections/pla-premium and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://flsunfrance.com/products/flsun-v400-super-racer-imprimante-3d-delta-flsun3d has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

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: 21 testimonial or review blocks. 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.

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

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