Website review, no card needed
paul-bakeries.com website review
Visit site (opens in a new tab)Reviewed 30 October 202639 issues · 83 checks
This review found 39 issues worth fixing on paul-bakeries.com, 17 of them high impact, across 83 checks. The most urgent: minify JavaScript. 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
74C- #87,657 of 125,664 reviewed websitesbeats 26%
- #54,810 of 70,239 online storesbeats 18%
- #323 of 730 Magento storesbeats 51%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.8 s |
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 3.1 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.2 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.3 s |
| Oct 24, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 91 ms |
| May 16, 2026 | 92 ms |
| May 23, 2026 | 90 ms |
| May 30, 2026 | 91 ms |
| Jun 6, 2026 | 89 ms |
| Jun 13, 2026 | 88 ms |
| Jun 20, 2026 | 90 ms |
| Jun 27, 2026 | 92 ms |
| Jul 4, 2026 | 94 ms |
| Jul 11, 2026 | 95 ms |
| Jul 18, 2026 | 95 ms |
| Jul 25, 2026 | 96 ms |
| Aug 1, 2026 | 96 ms |
| Aug 8, 2026 | 95 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 95 ms |
| Aug 29, 2026 | 93 ms |
| Sep 5, 2026 | 94 ms |
| Sep 12, 2026 | 94 ms |
| Sep 19, 2026 | 93 ms |
| Sep 26, 2026 | 93 ms |
| Oct 3, 2026 | 90 ms |
| Oct 10, 2026 | 89 ms |
| Oct 17, 2026 | 87 ms |
| Oct 24, 2026 | 87 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Minify JavaScript
1.4 s · 267 KiB267 KiB could be saved by minifying JavaScript.
Render-blocking requests
1.4 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Reduce unused CSS
880 ms · 169 KiBAbout 169 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 880 ms faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
700 ms · 212 KiBAbout 212 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 700 ms faster on a phone.
Use efficient cache lifetimes
350 ms · 36 KiB1 file is served with short cache lifetimes, so returning visitors download them again (36 KiB).
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Cookiebot and New Relic and others), adding 346 KiB and 200 ms of main-thread time.
Improve image delivery
100 ms · 128 KiB5 images could be 128 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.
Minify CSS
130 ms · 32 KiB32 KiB could be saved by minifying CSS.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 76 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, 1.1 s of it running JavaScript. That is comfortably low.
Server response: 96 ms
96 msYour server sent the HTML in 96 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.7 s
12.7 sYour largest element takes 12.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Les cookies nous permettent de personnaliser le contenu et …”.
Time to Interactive: 12.8 s
12.8 sThe page becomes fully interactive after 12.8 s. Good is under 3.8 s.
Speed Index: 6.5 s
6.5 sVisually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 91 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.8 s to 3.2 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: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 86 ms
86 msReal visitors wait 86 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.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 703 ms
703 msReal visitors wait 703 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 51 ms
51 msScripts block the page for only 51 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.1 MB in 320 requests
2.1 MBYour homepage downloads 2.1 MB in 320 requests on a phone: scripts 1.3 MB (259), fonts 424 KiB (17) and images 258 KiB (20). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
60 KiB1 image is downloaded at several times the size a phone draws it, for example Paul-galette_des_rois-French_tradition-kings_cake_1.jpg at 1,200 px wide, shown at 285 px. Resized copies would save about 60 KiB.
3 images below the first screen load straight away
3 images further down the page (182 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.61 g of CO₂e: 73.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
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.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 7 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.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
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.paul-bakeries.com/sitemap.xml, so Google discovers your pages only by following links.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
22 internal links, 57 external
The homepage links to 22 pages on paul-bakeries.com and 57 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Find my PAUL”.
Title: 50 characters
Your title is a healthy 50 characters: “PAUL : Family-Owned Company Established since 1889”.
Canonical URL set
The canonical URL is https://www.paul-bakeries.com/.
robots.txt in place
robots.txt is in place.
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.paul-bakeries.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 (376 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages are broken
Your homepage links to https://www.paul-bakeries.com/paul-house/our-story and https://www.paul-bakeries.com/paul-house/social-responsability, which answer with an error. Visitors hit a dead end and search engines drop them.
1 page without a title
https://www.paul-bakeries.com/pnews/news/index has no <title>, so Google invents the link text in results.
1 page points its canonical at the homepage
https://www.paul-bakeries.com/stores/store/redirect/___store/fr/___from_store/en/uenc/aHR0cHM6Ly93d3cucGF1bC1iYWtlcmllcy5jb20vP19fX3N0b3JlPWZy declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://www.paul-bakeries.com/stores/store/redirect/___store/fr/___from_store/en/uenc/aHR0cHM6Ly93d3cucGF1bC1iYWtlcmllcy5jb20vP19fX3N0b3JlPWZy all use the title “PAUL : Family-Owned Company Established since 1889”. Search engines can't tell which page to show for a search, so each competes with the others.
11 pages without a meta description
https://www.paul-bakeries.com/pnews/news/index, https://www.paul-bakeries.com/maison-paul/notre-histoire, https://www.paul-bakeries.com/maison-paul/nos-engagements, https://www.paul-bakeries.com/stores/store/redirect/___store/fr/___from_store/en/uenc/aHR0cHM6Ly93d3cucGF1bC1iYWtlcmllcy5jb20vP19fX3N0b3JlPWZy, https://www.paul-bakeries.com/pnews-details/octobre-rose-2022-63bd2580e7a35 and https://www.paul-bakeries.com/pnews-details/la-madeleine-on-aime-bien-ca-63b2d9b0f01b6 and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.paul-bakeries.com/mentions-legales and https://www.paul-bakeries.com/protection-des-donnees-personnelles-et-politique-cookies have no <h1> headline, so visitors and search engines get no clear main topic.
14 internal pages checked
We fetched 14 pages linked from your homepage and read each the way a search engine does.
1 checks passed
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
8 broken images
8 images failed to load on a phone, for example https://www.paul.fr/media/paul/category_menu_image/Viennoiserie.png.
53 small tap targets
53 of 74 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CERT_VERIFIER_CHANGED”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 331 words of copy
The homepage carries about 331 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact us”.
5 short forms
5 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
10 cookies set on arrival
10Opening the homepage sets 10 cookies (measured from a US location before any click).
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 paul-bakeries.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Magento
- Analytics
- Google Tag Manager
- Hosting
- CSC
Company
- Founded
- 1953
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on paul-bakeries.com, including 11 speed issues, 5 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.