Website review, no card needed
interiors.fr website review
Visit site (opens in a new tab)Reviewed 27 October 202652 issues · 88 checks
This review found 52 issues worth fixing on interiors.fr, 23 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
55F- #115,479 of 116,487 reviewed websitesbeats 1%
- #66,644 of 66,776 online storesbeats 0%
- #162 of 165 PrestaShop storesbeats 1%
Closest competitors among PrestaShop stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.1 s |
| May 16, 2026 | 3.1 s |
| May 23, 2026 | 3.2 s |
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.1 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.2 s |
| Oct 17, 2026 | 3.2 s |
| Oct 24, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 196 ms |
| May 16, 2026 | 189 ms |
| May 23, 2026 | 191 ms |
| May 30, 2026 | 199 ms |
| Jun 6, 2026 | 202 ms |
| Jun 13, 2026 | 203 ms |
| Jun 20, 2026 | 206 ms |
| Jun 27, 2026 | 196 ms |
| Jul 4, 2026 | 195 ms |
| Jul 11, 2026 | 193 ms |
| Jul 18, 2026 | 188 ms |
| Jul 25, 2026 | 193 ms |
| Aug 1, 2026 | 193 ms |
| Aug 8, 2026 | 197 ms |
| Aug 15, 2026 | 206 ms |
| Aug 22, 2026 | 209 ms |
| Aug 29, 2026 | 207 ms |
| Sep 5, 2026 | 207 ms |
| Sep 12, 2026 | 205 ms |
| Sep 19, 2026 | 203 ms |
| Sep 26, 2026 | 191 ms |
| Oct 3, 2026 | 188 ms |
| Oct 10, 2026 | 179 ms |
| Oct 17, 2026 | 177 ms |
| Oct 24, 2026 | 185 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.2 s
1.8 s
2.3 s
2.9 s
3.5 s
4.1 s
4.7 s
Speed
Use efficient cache lifetimes
6.8 s · 3.7 MB275 files are served with short cache lifetimes, so returning visitors download them again (3.7 MB).
Render-blocking requests
3.6 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.6 s.
Reduce unused JavaScript
2.9 s · 546 KiBAbout 546 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.
Improve image delivery
2.1 s · 345 KiB6 images could be 345 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.
Mobile performance score: 25
25/100Your mobile performance score is 25 (desktop: 57). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8,450 HTML elements
The page has 8,450 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
900 ms · 177 KiBAbout 177 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Font display
700 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 700 ms).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, app-spm.com and cloudflare.com and others), adding 868 KiB and 507 ms of main-thread time.
Google Tag Manager adds 383 ms
383 msGoogle Tag Manager costs a phone 383 ms of main-thread work and 509 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.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 988 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 170 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 15 KiB15 KiB could be saved by minifying JavaScript.
Legacy JavaScript
16 KiBPolyfills for old browsers add 16 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 57 but mobile only 25. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify CSS
9 KiB9 KiB could be saved by minifying CSS.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 214 ms
214 msYour server sent the HTML in 214 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Real-user LCP: 4.0 s
4.0 sReal visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.49
0.49For real visitors the layout shifts by 0.49 (75th percentile). Good is under 0.1.
Real-user FCP: 3.2 s
3.2 sReal visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.5 s
2.5 sReal visitors wait 2.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 22.7 s
22.7 sYour largest element takes 22.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “La marque INTERIOR’S s’est longtemps démarquée de part l’es…”.
Time to Interactive: 24.0 s
24.0 sThe page becomes fully interactive after 24.0 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.73
0.73The layout shifts by 0.73 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Speed Index: 8.6 s
8.6 sVisually, the page fills in at 8.6 s (Speed Index). Good is under 3.4 s.
Real-user INP: 236 ms
236 msReal visitors wait 236 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
49 images without width and height
49 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 421 ms
421 msScripts block taps and scrolling for 421 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 196 ms to 185 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.1 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 5.4 MB in 324 requests
5.4 MBYour homepage downloads 5.4 MB in 324 requests on a phone: images 2.7 MB (263), scripts 1.0 MB (17) and other files 789 KiB (24). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
161 KiB1 image is downloaded at several times the size a phone draws it, for example 4e89f6c4157a88b94ce1dc2fbe738b9e.jpg at 1,600 px wide, shown at 390 px. Resized copies would save about 161 KiB.
1 image in older formats
1 image (346 KiB) is 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.
2 images below the first screen load straight away
2 images further down the page (41 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.5 g of CO₂ per visit
1.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.54 g of CO₂e: 185.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Orphan list items
Some list items are not inside a list.
321 images without alt text
321 images have no alt text, which hurts accessibility and image search.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
58 form fields without a label
58 form fields have no label, so screen readers announce an empty box and autofill guesses.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (10 characters)
Your title is only 10 characters: “Interior's”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“” and “Interior's”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.decoration-dautrefois.com/sitemap.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
510 internal links, 12 external
The homepage links to 510 pages on interiors.fr and 12 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://www.decoration-dautrefois.com/fr/848-interior-s.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.decoration-dautrefois.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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (5,588 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://www.decoration-dautrefois.com/nouveaux-produits, which answers with an error. Visitors hit a dead end and search engines drop it.
1 linked page hidden from search
https://www.decoration-dautrefois.com/fr/panier is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
5 pages share a title
https://www.decoration-dautrefois.com/fr/848-interior-s?i=1, https://www.decoration-dautrefois.com/en/848-interior-s, https://www.decoration-dautrefois.com/de/848-interior-s, https://www.decoration-dautrefois.com/es/848-interior-s and https://www.decoration-dautrefois.com/it/848-interior-s all use the title “Interior's”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://www.decoration-dautrefois.com/fr/module/giftcard/choicegiftcard, https://www.decoration-dautrefois.com/en/848-interior-s, https://www.decoration-dautrefois.com/de/848-interior-s, https://www.decoration-dautrefois.com/es/848-interior-s, https://www.decoration-dautrefois.com/it/848-interior-s and https://www.decoration-dautrefois.com/fr/panier have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.decoration-dautrefois.com/529-meuble, whose canonical is https://www.decoration-dautrefois.com/en/529-furniture. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.decoration-dautrefois.com/fr/promotions has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.decoration-dautrefois.com/it/848-interior-s took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 136 found) and read each the way a search engine does.
1 checks passed
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://www.decoration-dautrefois.com/fr/848-interior-s.
12 small tap targets
12 of 26 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
49 distorted images
49 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALID”.
4 low-resolution images
4 images are served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
A 20-field form
Your longest form asks for 20 fields (0 required). Every extra field lowers completion.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,450 words of copy
The homepage carries about 1,450 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, 1 customer or partner logo and a star rating.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
6 cookies set on arrival
6Opening the homepage sets 6 cookies, 1 of them by other companies (measured from a US location before any click).
17 other companies contacted
Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at interiors.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- OVHcloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 52 issues on interiors.fr, including 24 speed issues, 6 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.