Website review, no card needed

hello-papaye.com logo

hello-papaye.com website review

Visit site (opens in a new tab)Reviewed 10 November 20269 issues · 63 checks

This review found 9 issues worth fixing on hello-papaye.com, 3 of them high impact, across 63 checks. The most urgent: 21 text elements with low contrast. 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

Full-page screenshot of hello-papaye.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

100
  • Render-blocking requests

    200 ms

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

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

3 checks passed
  • Mobile performance score: 100

    100/100

    Your mobile performance score is 100. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.1 s

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

  • Server response: 109 ms

    109 ms

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

Core Web Vitals

100
  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

6 checks passed
  • Speed Index: 2.1 s

    2.1 s

    Visually, the page fills in at 2.1 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: 1.0 s

    1.0 s

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

  • Largest Contentful Paint: 1.0 s

    1.0 s

    Your largest element renders in 1.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Votre solution en mode SaaS est géniale ?​ Faites-la connaî…”.

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 1.0 s

    1.0 s

    The page is fully interactive after 1.0 s.

Images and page weight

100
  • About 0.03 g of CO₂ per visit

    0.03 g

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

4 checks passed
  • Page weight: 101 KiB in 7 requests

    101 KiB

    Your homepage downloads 101 KiB in 7 requests on a phone: images 63 KiB (4), HTML 26 KiB (1) and stylesheets 12 KiB (1). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 to fixGoogle 9395
  • 21 text elements with low contrast

    21 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • ARIA role should be appropriate for the element (3 elements)

    ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 16 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 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9297
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 34 internal links, 0 external

    The homepage links to 34 pages on hello-papaye.com and 0 external pages.

7 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Le SEO pour les SaaS ? Oui, vous avez bien lu ! Je vous propose des services SEO sur mesure adaptés aux besoins des édi…”.

  • One H1 headline

    Your main headline reads: “Des prestations SEO pour les SaaS, adaptées à vos besoins”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “Hello Papaye : le SEO pour les SaaS”.

  • Canonical URL set

    The canonical URL is https://hello-papaye.com/.

  • Structured data in place

    Structured data found: ImageObject, Organization, Place, WebPage and WebSite.

  • 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://hello-papaye.com/sitemap_index.xml.

AI search readiness

1 to fix65
  • robots.txt blocks 1 AI answer engine crawler

    1 of 6

    Your robots.txt shuts out ChatGPT (ChatGPT-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • No llms.txt

    There is no https://hello-papaye.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.

  • Opted out of AI training for 2 crawlers

    robots.txt blocks GPTBot and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

2 checks passed
  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (785 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 13 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

Google 96100
  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    6 of 6 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix75
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 752 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Prenons contact 📅”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact” and “Prenons contact 📅”.

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

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

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 hello-papaye.com, 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
Framework
jQuery
Analytics
Google Tag Manager | Matomo
Hosting
O2switch O2switch Sas

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 9 issues on hello-papaye.com, including 1 SEO issue 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

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