Website review, no card needed
pizzacosy.fr website review
Visit site (opens in a new tab)Reviewed 26 October 202636 issues · 80 checks
This review found 36 issues worth fixing on pizzacosy.fr, 10 of them high impact, across 80 checks. The most urgent: improve image delivery. 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 189 ms |
| May 16, 2026 | 187 ms |
| May 23, 2026 | 188 ms |
| May 30, 2026 | 191 ms |
| Jun 6, 2026 | 190 ms |
| Jun 13, 2026 | 192 ms |
| Jun 20, 2026 | 196 ms |
| Jun 27, 2026 | 200 ms |
| Jul 4, 2026 | 202 ms |
| Jul 11, 2026 | 203 ms |
| Jul 18, 2026 | 200 ms |
| Jul 25, 2026 | 195 ms |
| Aug 1, 2026 | 196 ms |
| Aug 8, 2026 | 200 ms |
| Aug 15, 2026 | 204 ms |
| Aug 22, 2026 | 208 ms |
| Aug 29, 2026 | 209 ms |
| Sep 5, 2026 | 209 ms |
| Sep 12, 2026 | 211 ms |
| Sep 19, 2026 | 213 ms |
| Sep 26, 2026 | 216 ms |
| Oct 3, 2026 | 213 ms |
| Oct 10, 2026 | 214 ms |
| Oct 17, 2026 | 216 ms |
| Oct 24, 2026 | 213 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.7 s
1.4 s
2.1 s
2.8 s
3.5 s
4.2 s
4.9 s
5.6 s
Speed
Improve image delivery
1.3 s · 740 KiB3 images could be 740 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.
Use efficient cache lifetimes
550 ms · 780 KiB12 files are served with short cache lifetimes, so returning visitors download them again (780 KiB).
Mobile performance score: 69
69/100Your mobile performance score is 69 (desktop: 74). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
800 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
5 third-party services on the page
5 third-party services load with your homepage (myli.io, Google Maps and join-stories.com and others), adding 1.0 MB and 522 ms of main-thread time.
Reduce unused CSS
300 ms · 137 KiBAbout 137 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Reduce unused JavaScript
392 KiBAbout 392 KiB of JavaScript is downloaded but never used on this page.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 306 ms. During a long task the page ignores taps.
myli.io adds 225 ms
225 msmyli.io costs a phone 225 ms of main-thread work and 402 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.
Google Maps adds 198 ms
198 msGoogle Maps costs a phone 198 ms of main-thread work and 409 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.
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.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 457 ms of it running JavaScript. That is comfortably low.
Server response: 12 ms
12 msYour server sent the HTML in 12 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.
Largest Contentful Paint: 11.5 s
11.5 sYour largest element takes 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “www.pizzacosy.fr @pizzacosy”.
Time to Interactive: 11.8 s
11.8 sThe page becomes fully interactive after 11.8 s. Good is under 3.8 s.
Real-user INP: 207 ms
207 msReal visitors wait 207 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 245 ms
245 msScripts block taps and scrolling for 245 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 189 ms to 213 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 627 ms
627 msReal visitors wait 627 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.3 s
3.3 sVisually, the page fills in at 3.3 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
1 image over 500 KB
tel-mockup-site-2-768x665.png weighs 518 KiB. On a phone connection a single image that size takes seconds.
Page weight: 3.3 MB in 45 requests
3.3 MBYour homepage downloads 3.3 MB in 45 requests on a phone: images 1.9 MB (10), scripts 851 KiB (11) and fonts 388 KiB (10). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (879 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.
About 0.9 g of CO₂ per visit
0.94 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.94 g of CO₂e: 112.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 29 images in the HTML carry an alt attribute.
45 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: 45 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “PizzaCosy - Pizzas de qualité en livraison, à emporter ou sur place”.
No XML sitemap
No XML sitemap at https://www.pizzacosy.fr/sitemap.xml, so Google discovers your pages only by following links.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
27 internal links, 6 external
The homepage links to 27 pages on pizzacosy.fr and 6 external pages.
5 checks passed
Meta description: 125 characters
Your meta description is 125 characters: “Pizzerias sur place, en livraison, à emporter, ouvert 7J/7. Pizzas de qualité aux ingrédients de saison. Commandez en l…”.
Canonical URL set
The canonical URL is https://www.pizzacosy.fr/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (230 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share a title
https://www.pizzacosy.fr/cgv, https://www.pizzacosy.fr/cgu-pizzacosy, https://www.pizzacosy.fr/cgu-programme-fidelite and https://www.pizzacosy.fr/politique-de-traitement-des-donnees all use the title “Politique de confidentialité des pizzerias de Pizza Cosy”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages share a meta description
https://www.pizzacosy.fr/cgv, https://www.pizzacosy.fr/cgu-pizzacosy, https://www.pizzacosy.fr/cgu-programme-fidelite and https://www.pizzacosy.fr/politique-de-traitement-des-donnees use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://www.pizzacosy.fr/le-concept has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.pizzacosy.fr/allergenes has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
1 page slow to respond
https://www.pizzacosy.fr/actualites took over 3 s to send its HTML from our server.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 13 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 13 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
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/v5.0.13/css/all.css' from origin 'https://www.pizzaco…”.
2 checks passed
Tap targets are thumb-sized
14 of 14 tappable elements near the top are at least 24 px.
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Only about 166 words
The homepage has only about 166 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
1 short form
A short form (2 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
No consent tool detected
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.
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 pizzacosy.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Analytics
- Google Tag Manager
- Hosting
- Nfrance
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 pizzacosy.fr, including 15 speed issues, 4 SEO issues and 4 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.