wefix.net website review

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Optanon and others), adding 1,017 KiB and 1.0 s of main-thread time.

Google Tag Manager costs a phone 703 ms of main-thread work and 536 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 2,122 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

8 images are downloaded at several times the size a phone draws them, for example smartphone.png at 1,042 px wide, shown at 182 px. Resized copies would save about 1.0 MB.

Your homepage downloads 3.9 MB in 100 requests on a phone: images 2.2 MB (27), scripts 1.2 MB (16) and other files 313 KiB (50). Under 2 MB keeps phones on slow connections fast.

mobile.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

4 images (814 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.

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

1 button has no accessible name, so screen readers announce just “button”.

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

Elements with visible text labels do not have matching accessible names. (10 elements).

Your title is 76 characters, so Google will cut it off around 60: “Page d'accueil - Bienvenue chez WeFix ! Experts en réparation et protection.”.

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

There are 2 <h1> headlines (“Page d'accueil - Bienvenue chez WeFix ! Experts e…” and “Quel appareil voulez-vous réparer ?”). One clear main headline is easier for people and search engines.

Your meta description is 170 characters; Google truncates after about 160, so the end of your pitch is cut.

No XML sitemap at https://wefix.net/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at wefix.net/robots.txt, the first file search crawlers ask for.

2 links have no real href, so search engines can't follow them.

The homepage links to 52 pages on wefix.net 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.

There is no /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.

/accessoires-smartphone/protection/protection-ecran, /reparation/smartphone/apple/iphone-13, /reparation/smartphone/apple/iphone-14, /bouyguestelecom, /darty-max and /blog/nos-smartphones-reconditionnes have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5808553&tm=gtm002&Ver=2&mid=b8678c43-772c-454c-91d0-d163b4db06c2&bo=1&sid=cbe06c40d5db11f192972bb047b0ad8d&vid=cbe08c80d5db11f189b9dbbf2821756e&vids=1&msclkid=N&pi=918.

5 of 19 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 “Failed to load resource: the server responded with a status of 404 ()”.

Large scripts ship without source maps.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

wefix.net has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

wefix.net's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

DMARC is set to p=none, so mail pretending to be wefix.net is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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