Website review, no card needed
photoweb.fr website review
Visit site (opens in a new tab)Reviewed 18 November 202636 issues · 89 checks
This review found 36 issues worth fixing on photoweb.fr, 16 of them high impact, across 89 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
79C- #52,640 of 116,442 reviewed websitesbeats 49%
- #35,121 of 66,775 online storesbeats 41%
- #140 of 709 Magento storesbeats 76%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.6 s |
| Oct 31, 2026 | 2.6 s |
| Nov 7, 2026 | 2.6 s |
| Nov 14, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 155 ms |
| Jun 6, 2026 | 153 ms |
| Jun 13, 2026 | 152 ms |
| Jun 20, 2026 | 152 ms |
| Jun 27, 2026 | 153 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 155 ms |
| Jul 18, 2026 | 156 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 155 ms |
| Aug 8, 2026 | 156 ms |
| Aug 15, 2026 | 158 ms |
| Aug 22, 2026 | 159 ms |
| Aug 29, 2026 | 159 ms |
| Sep 5, 2026 | 156 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 152 ms |
| Sep 26, 2026 | 153 ms |
| Oct 3, 2026 | 154 ms |
| Oct 10, 2026 | 156 ms |
| Oct 17, 2026 | 158 ms |
| Oct 24, 2026 | 157 ms |
| Oct 31, 2026 | 155 ms |
| Nov 7, 2026 | 154 ms |
| Nov 14, 2026 | 154 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.8 s
1.5 s
2.3 s
3.0 s
3.8 s
4.5 s
5.3 s
6.1 s
Speed
Use efficient cache lifetimes
1.7 s · 299 KiB13 files are served with short cache lifetimes, so returning visitors download them again (299 KiB).
Reduce unused JavaScript
1.1 s · 150 KiBAbout 150 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Improve image delivery
1.9 MB16 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 175 KiBAbout 175 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Render-blocking requests
650 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
2,243 HTML elements
The page has 2,243 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Kameleoon and Segment and others), adding 689 KiB and 258 ms of main-thread time.
Legacy JavaScript
150 ms · 24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Duplicated JavaScript
150 ms · 4 KiB4 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 81 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 871 ms of it running JavaScript. That is comfortably low.
Server response: 102 ms
102 msYour server sent the HTML in 102 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 26.5 s
26.5 sYour largest element takes 26.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Photoweb Homepage banner”.
Time to Interactive: 27.3 s
27.3 sThe page becomes fully interactive after 27.3 s. Good is under 3.8 s.
Speed Index: 8.9 s
8.9 sVisually, the page fills in at 8.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
21 images without width and height
21 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 155 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 142 ms
142 msReal visitors wait 142 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 398 ms
398 msReal visitors wait 398 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Total Blocking Time: 28 ms
28 msScripts block the page for only 28 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 6.0 MB in 126 requests
6.0 MBYour homepage downloads 6.0 MB in 126 requests on a phone: images 3.0 MB (45), scripts 2.1 MB (34) and fonts 555 KiB (10). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
PW-visuel-home-app-mobile_1.jpg weighs 509 KiB. On a phone connection a single image that size takes seconds.
25 images in older formats
25 images (2.9 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.
12 images below the first screen load straight away
12 images further down the page (1.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.7 g of CO₂ per visit
1.70 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.70 g of CO₂e: 203.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
Orphan list items
Some list items are not inside a list.
ARIA tab nodes must have an accessible name (1 element)
ARIA tab nodes must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (2 elements)
Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 75 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 4 problems
Structured data found (ContactPoint, ImageObject, Organization and Person) but with 4 problems, for example “Person: missing name”.
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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
181 internal links, 27 external
The homepage links to 181 pages on photoweb.fr and 27 external pages.
6 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Photoweb transforme vos photos en souvenirs inoubliables. Plus de 20 ans de passion pour vous offrir la meilleure quali…”.
One H1 headline
Your main headline reads: “Photoweb, votre site de photos à imprimer & sublimer”.
Title: 54 characters
Your title is a healthy 54 characters: “Photoweb | Transformez vos photos en souvenirs uniques”.
Canonical URL set
The canonical URL is https://www.photoweb.fr/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.photoweb.fr/media/google_sitemap_fr.xml.
AI search readiness
No llms.txt
There is no https://www.photoweb.fr/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.
3 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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (2,675 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.photoweb.fr/notifications is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://www.photoweb.fr/service-studio and https://www.photoweb.fr/notifications have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 104 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
4 broken images
4 images failed to load on a phone, for example https://www.photoweb.fr/.
12 small tap targets
12 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v4.7.0/css/font-awesome-css.min.css' from origin 'htt…”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 982 words of copy
The homepage carries about 982 words of visible text.
2 checks passed
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Segment.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Segment (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.
24 cookies set on arrival
24Opening the homepage sets 24 cookies (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: Didomi
A consent management tool (Didomi) 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 photoweb.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
- Bootstrap
- E-commerce
- Magento
- Analytics
- Segment
- Hosting
- Fastly
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on photoweb.fr, including 12 speed issues, 2 SEO issues and 2 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.