Website review, no card needed

darjeeling.fr logo

darjeeling.fr website review

Visit site (opens in a new tab)Reviewed 30 October 202631 issues · 76 checks

This review found 31 issues worth fixing on darjeeling.fr, 11 of them high impact, across 76 checks. The most urgent: page weight: 28.4 MB in 136 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
3.1 s2.9 sMay 9Oct 243.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.0 s
May 16, 20263.0 s
May 23, 20263.0 s
May 30, 20263.1 s
Jun 6, 20263.1 s
Jun 13, 20263.1 s
Jun 20, 20263.1 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.9 s
Aug 15, 20262.9 s
Aug 22, 20262.9 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20263.0 s
Sep 19, 20263.0 s
Sep 26, 20263.0 s
Oct 3, 20263.0 s
Oct 10, 20262.9 s
Oct 17, 20263.0 s
Oct 24, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
928 ms686 msMay 9Oct 24714 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026772 ms
May 16, 2026759 ms
May 23, 2026740 ms
May 30, 2026757 ms
Jun 6, 2026765 ms
Jun 13, 2026779 ms
Jun 20, 2026800 ms
Jun 27, 2026840 ms
Jul 4, 2026862 ms
Jul 11, 2026889 ms
Jul 18, 2026900 ms
Jul 25, 2026879 ms
Aug 1, 2026887 ms
Aug 8, 2026873 ms
Aug 15, 2026866 ms
Aug 22, 2026874 ms
Aug 29, 2026862 ms
Sep 5, 2026837 ms
Sep 12, 2026798 ms
Sep 19, 2026769 ms
Sep 26, 2026746 ms
Oct 3, 2026748 ms
Oct 10, 2026752 ms
Oct 17, 2026731 ms
Oct 24, 2026714 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 darjeeling.fr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix51
  • Reduce unused JavaScript

    150 ms · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Mobile performance score: 51

    51/100

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

  • Render-blocking requests

    750 ms

    11 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

  • Improve image delivery

    150 ms · 567 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (chantelle.com, Didomi and curator.io and others), adding 1.0 MB and 525 ms of main-thread time.

  • Use efficient cache lifetimes

    468 KiB

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

  • Main-thread work: 3.6 s

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

  • 11 long tasks on the main thread

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

  • Reduce unused CSS

    38 KiB

    About 38 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    22 KiB

    Polyfills for old browsers add 22 KiB JavaScript that modern phones do not need.

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 124 ms

    124 ms

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

Core Web Vitals

9 to fix33
  • 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.

  • Real-user INP: 937 ms

    937 ms

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

  • Real-user CLS: 0.62

    0.62

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

  • Largest Contentful Paint: 56.1 s

    56.1 s

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

  • Speed Index: 36.2 s

    36.2 s

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

  • Time to Interactive: 68.2 s

    68.2 s

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

  • Real-user TTFB: 813 ms

    813 ms

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

  • Total Blocking Time: 553 ms

    553 ms

    Scripts block taps and scrolling for 553 ms in total while the page loads. Good is under 200 ms.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -6%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

4 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix45
  • Page weight: 28.4 MB in 136 requests

    28.4 MB

    Your homepage downloads 28.4 MB in 136 requests on a phone: images 16.5 MB (17), media 8.7 MB (2) and scripts 2.3 MB (54). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    sans-titre-3_ah26_1920-x-900_01-1.jpg weighs 9.1 MB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (9.1 MB) is 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 8.1 g of CO₂ per visit

    8.06 g

    By the Sustainable Web Design model, a visit to your homepage emits about 8.06 g of CO₂e: 966.9 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 to fixGoogle 9296
  • 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.

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • 34 links without text

    34 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed
  • Every image has alt text

    All 31 images in the HTML carry an alt attribute.

  • 49 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: 49 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10096
  • No structured data

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

  • 139 internal links, 23 external

    The homepage links to 139 pages on darjeeling.fr and 23 external pages.

7 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Découvrez les collections de lingerie, nuit, sport, homewear et bain Darjeeling. Du bonnet A au bonnet H. E-reservation…”.

  • One H1 headline

    Your main headline reads: “Darjeeling”.

  • Title: 32 characters

    Your title is a healthy 32 characters: “Bienvenue sur le site Darjeeling”.

  • Canonical URL set

    The canonical URL is https://www.darjeeling.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.darjeeling.fr/sitemap.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.darjeeling.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 (536 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without a meta description

    https://www.darjeeling.fr/storelocator has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

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

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 5 small tap targets

    5 of 25 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-m…”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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.

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

    The homepage carries about 286 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More →”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies (measured from a US location before any click).

  • 14 other companies contacted

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

1 checks passed
  • Consent tool: Didomi

    A consent management tool (Didomi) 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 darjeeling.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
Next.js
Analytics
Google Tag Manager
Hosting
AWS

Company

Founded
1995

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on darjeeling.fr, including 17 speed issues, 1 SEO issue 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

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