Website review, no card needed

delarte.fr logo

delarte.fr website review

Visit site (opens in a new tab)Reviewed 30 October 202629 issues · 75 checks

This review found 29 issues worth fixing on delarte.fr, 6 of them high impact, across 75 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.9 s1.5 sMay 9Oct 241.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20261.8 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
316 ms194 msMay 9Oct 24211 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026298 ms
May 16, 2026299 ms
May 23, 2026300 ms
May 30, 2026302 ms
Jun 6, 2026281 ms
Jun 13, 2026236 ms
Jun 20, 2026220 ms
Jun 27, 2026211 ms
Jul 4, 2026209 ms
Jul 11, 2026212 ms
Jul 18, 2026214 ms
Jul 25, 2026214 ms
Aug 1, 2026214 ms
Aug 8, 2026213 ms
Aug 15, 2026218 ms
Aug 22, 2026219 ms
Aug 29, 2026220 ms
Sep 5, 2026220 ms
Sep 12, 2026216 ms
Sep 19, 2026213 ms
Sep 26, 2026211 ms
Oct 3, 2026208 ms
Oct 10, 2026209 ms
Oct 17, 2026210 ms
Oct 24, 2026211 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

Full-page screenshot of delarte.fr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. delarte.fr at 0.4 s0.4 s
  2. delarte.fr at 0.8 s0.8 s
  3. delarte.fr at 1.1 s1.1 s
  4. delarte.fr at 1.5 s1.5 s
  5. delarte.fr at 1.9 s1.9 s
  6. delarte.fr at 2.3 s2.3 s
  7. delarte.fr at 2.6 s2.6 s
  8. delarte.fr at 3.0 s3.0 s

Speed

5 to fix76
  • Improve image delivery

    1.1 MB

    10 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 76

    76/100

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

  • Minify JavaScript

    300 ms · 44 KiB

    44 KiB could be saved by minifying JavaScript.

  • Render-blocking requests

    300 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

  • Google Maps adds 131 ms

    131 ms

    Google Maps costs a phone 131 ms of main-thread work and 350 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.

  • Reduce unused CSS

    290 ms · 39 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Maps, New Relic and axept.io and others), adding 416 KiB and 222 ms of main-thread time.

  • Reduce unused JavaScript

    183 KiB

    About 183 KiB of JavaScript is downloaded but never used on this page.

  • Minify CSS

    150 ms · 8 KiB

    8 KiB could be saved by minifying CSS.

  • Font display

    150 ms

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

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 85 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.

  • Use efficient cache lifetimes

    3 KiB

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

2 checks passed
  • Main-thread work: 1.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 452 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

    Your server sent the HTML in 1 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix67
  • 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: 6.9 s

    6.9 s

    Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 11.0 s

    11.0 s

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

  • Real-user LCP: 2.5 s

    2.5 s

    Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 2.5 s

    2.5 s

    Real visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.

9 checks passed
  • Real-user INP: 194 ms

    194 ms

    Real visitors wait 194 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 306 ms

    306 ms

    Real visitors wait 306 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 29% faster for real visitors

    -29%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 298 ms to 211 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 12% faster for real visitors

    -12%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Speed Index: 2.2 s

    2.2 s

    Visually, the page fills in at 2.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 24 ms

    24 ms

    Scripts block the page for only 24 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix67
  • Page weight: 3.3 MB in 236 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 236 requests on a phone: images 1.8 MB (22), scripts 795 KiB (153) and other files 334 KiB (34). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.93 g

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

Accessibility

4 to fixGoogle 9682
  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 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.

  • 3 tap targets too small

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 6 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 8 WCAG 2.2 A/AA and best-practice rules on the phone render: 6 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10080
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (180 characters)

    Your meta description is 180 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 27 internal links, 2 external

    The homepage links to 27 pages on delarte.fr and 2 external pages.

5 checks passed
  • Title: 51 characters

    Your title is a healthy 51 characters: “Restaurants Del Arte - Commande & Pizzas à emporter”.

  • Canonical URL set

    The canonical URL is https://www.delarte.fr/.

  • 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.delarte.fr/media/sitemap-index.xml.

AI search readiness

1 to fix88
  • 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.delarte.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.

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 (256 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix88
  • 1 page without a meta description

    https://www.delarte.fr/jeux-concours has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.delarte.fr/boissons and https://www.delarte.fr/programme-fidelite use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://www.delarte.fr/club-famille-spaghetto, https://www.delarte.fr/programme-fidelite and https://www.delarte.fr/offre-traiteur have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.delarte.fr/jeux-concours 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.

  • 14 internal pages checked

    We fetched 14 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 14 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix30
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 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 256 words of copy

    The homepage carries about 256 words of visible text.

Privacy and tracking

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 4 other companies contacted

    Loading the homepage contacts 4 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 delarte.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Fastly

Company

Founded
1983
Headquarters
Rennes

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on delarte.fr, including 10 speed issues, 4 SEO issues and 5 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25