Website review, no card needed

camus.fr logo

camus.fr website review

Visit site (opens in a new tab)Reviewed 27 October 202634 issues · 83 checks

This review found 34 issues worth fixing on camus.fr, 9 of them high impact, across 83 checks. The most urgent: render-blocking requests. 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
2.6 s1.9 sMay 9Oct 241.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.5 s
May 16, 20262.5 s
May 23, 20262.4 s
May 30, 20262.3 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.2 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
167 ms126 msMay 9Oct 24138 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026141 ms
May 16, 2026140 ms
May 23, 2026140 ms
May 30, 2026146 ms
Jun 6, 2026154 ms
Jun 13, 2026161 ms
Jun 20, 2026162 ms
Jun 27, 2026162 ms
Jul 4, 2026159 ms
Jul 11, 2026157 ms
Jul 18, 2026154 ms
Jul 25, 2026154 ms
Aug 1, 2026152 ms
Aug 8, 2026147 ms
Aug 15, 2026145 ms
Aug 22, 2026140 ms
Aug 29, 2026138 ms
Sep 5, 2026136 ms
Sep 12, 2026135 ms
Sep 19, 2026131 ms
Sep 26, 2026136 ms
Oct 3, 2026136 ms
Oct 10, 2026141 ms
Oct 17, 2026144 ms
Oct 24, 2026138 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 camus.fr (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix57
  • Render-blocking requests

    3.4 s

    9 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.4 s.

  • Use efficient cache lifetimes

    1.0 s · 210 KiB

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

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57 (desktop: 88). Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Clarity, Shopify and smile.io and others), adding 1.1 MB and 803 ms of main-thread time.

  • Reduce unused JavaScript

    590 ms · 181 KiB

    About 181 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 590 ms faster on a phone.

  • Improve image delivery

    650 ms · 113 KiB

    4 images could be 113 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

  • Reduce unused CSS

    450 ms · 20 KiB

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

  • Main-thread work: 3.8 s

    A phone's processor spends 3.8 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Clarity adds 373 ms

    373 ms

    Clarity costs a phone 373 ms of main-thread work and 33 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.

  • Shopify adds 194 ms

    194 ms

    Shopify costs a phone 194 ms of main-thread work and 569 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.

  • smile.io adds 97 ms

    97 ms

    smile.io costs a phone 97 ms of main-thread work and 352 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.

  • 3 long tasks on the main thread

    3 long tasks block the main thread while loading, the longest for 69 ms. During a long task the page ignores taps.

  • Font display

    50 ms

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

  • Phones get a much slower page than desktops

    Desktop scores 88 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 17.2 s

    17.2 s

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

  • First Contentful Paint: 6.8 s

    6.8 s

    The first text or image appears after 6.8 s on a phone. Good is under 1.8 s.

  • Time to Interactive: 17.2 s

    17.2 s

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

  • Speed Index: 8.2 s

    8.2 s

    Visually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.

  • Tap response (INP) held steady for real visitors

    0%

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

9 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 s

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

  • Real-user INP: 137 ms

    137 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 723 ms

    723 ms

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

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

    -20%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 22 ms

    22 ms

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

Images and page weight

1 to fix85
  • Page weight: 3.3 MB in 349 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 349 requests on a phone: scripts 1.0 MB (146), other files 962 KiB (159) and fonts 642 KiB (10). 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: 112.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • 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

2 to fixGoogle 9798
  • 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.

  • Links look like plain text

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Camus Cognac - Made to Measure Luxury Cognac - Independent Since 1863”.

  • Meta description is long (293 characters)

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

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 39 internal links, 7 external

    The homepage links to 39 pages on camus.fr and 7 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “CAMUS COGNAC”.

  • Canonical URL set

    The canonical URL is https://camus.fr/en-us.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://camus.fr/sitemap.xml.

AI search readiness

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

  • llms.txt published

    The site publishes https://camus.fr/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

7 to fix55
  • 1 page without a title

    https://camus.fr/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 2 linked pages hidden from search

    https://camus.fr/customer_authentication/redirect and https://camus.fr/en-us/blogs/news/tagged/camus-twist are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 3 pages share a title

    https://camus.fr/blogs/news, https://camus.fr/en-us/blogs/news/tagged/camus-twist and https://camus.fr/en-us/blogs/news all use the title “Our Latest Adventures - CAMUS COGNAC”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://camus.fr/en-us/collections/usa, https://camus.fr/en-us/pages/history, https://camus.fr/en-us/pages/uniqueness, https://camus.fr/en-us/pages/savoir-faire, https://camus.fr/customer_authentication/redirect and https://camus.fr/en-us/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://camus.fr/blogs/news, https://camus.fr/en-us/blogs/news/tagged/camus-twist and https://camus.fr/en-us/blogs/news use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://camus.fr/blogs/news, whose canonical is https://camus.fr/en-us/blogs/news. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 8 pages without an H1

    https://camus.fr/en-us/collections/usa, https://camus.fr/en-us/pages/history, https://camus.fr/en-us/pages/uniqueness, https://camus.fr/en-us/pages/savoir-faire, https://camus.fr/en-us/pages/nos-engagements and https://camus.fr/customer_authentication/redirect and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 20 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • 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.

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

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

    The homepage carries about 303 words of visible text.

4 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “SHOP” and “Subscribe”.

  • 8 short forms

    8 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 17 cookies set on arrival

    17

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

  • 43 other companies contacted

    Loading the homepage contacts 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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 camus.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
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Company

Founded
1863
Headquarters
Cognac

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on camus.fr, including 15 speed issues, 3 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

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