produit.co website review

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

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

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

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

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

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

7 third-party services load with your homepage (Google Tag Manager, shortpixel.ai and Google Analytics and others), adding 1.6 MB and 251 ms of main-thread time.

Google Tag Manager costs a phone 164 ms of main-thread work and 298 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.

shortpixel.ai costs a phone 33 ms of main-thread work and 1.2 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.

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

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

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

8 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 12.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Bringing brands to life Digitally.”. Most of its time is element render delay (5.0 s).

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

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

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

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

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.

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

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

3 tap targets are too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 9 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.

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

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

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

There are 2 <h1> headlines (“Home” and “Bringing brands to life Digitally.”). One clear main headline is easier for people and search engines.

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

The homepage links to 100 pages on produit.co and 10 external pages.

There is no https://www.produit.co/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 3 pages by a URL that isn't their canonical one, for example https://www.produit.co/wordpress-development, whose canonical is https://www.produit.co/affordable-wordpress-development-agency. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.produit.co/wordpress-development, https://www.produit.co/magento-development and https://www.produit.co/shopify-ecommerce-development took over 3 s to send their HTML from our server.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Your longest form asks for 13 fields (6 required). Every extra field lowers completion.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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