Website review, no card needed

petiteladeux.com logo

petiteladeux.com website review

Visit site (opens in a new tab)Reviewed 11 November 202650 issues · 83 checks

This review found 50 issues worth fixing on petiteladeux.com, 19 of them high impact, across 83 checks. The most urgent: improve image delivery. 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.4 s1.1 sMay 23Nov 71.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.3 s
May 30, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.2 s
Jul 4, 20261.3 s
Jul 11, 20261.4 s
Jul 18, 20261.3 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Sep 12, 20261.2 s
Sep 26, 20261.2 s
Oct 24, 20261.2 s
Nov 7, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
254 ms218 msMay 23Nov 7231 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026222 ms
Jul 4, 2026228 ms
Jul 11, 2026243 ms
Jul 18, 2026250 ms
Sep 26, 2026236 ms
Nov 7, 2026231 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 petiteladeux.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix43
  • Improve image delivery

    3.2 s · 18.5 MB

    43 images could be 18.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.2 s faster on a phone.

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 43

    43/100

    Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Use efficient cache lifetimes

    600 ms · 4.7 MB

    67 files are served with short cache lifetimes, so returning visitors download them again (4.7 MB).

  • 8 third-party services on the page

    8 third-party services load with your homepage (myeeglobal.com, buyee.jp and Google Tag Manager and others), adding 22.5 MB and 576 ms of main-thread time.

  • shop-pro.jp adds 3 ms

    3 ms

    shop-pro.jp costs a phone 3 ms of main-thread work and 16.9 MB 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 JavaScript

    300 ms · 600 KiB

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

  • Adobe TypeKit adds 50 ms

    50 ms

    Adobe TypeKit costs a phone 50 ms of main-thread work and 2.8 MB 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.

  • sns-linked.com adds 76 ms

    76 ms

    sns-linked.com costs a phone 76 ms of main-thread work and 1.8 MB 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.

  • myeeglobal.com adds 139 ms

    139 ms

    myeeglobal.com costs a phone 139 ms of main-thread work and 372 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.

  • buyee.jp adds 127 ms

    127 ms

    buyee.jp costs a phone 127 ms of main-thread work and 375 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.

  • 6 long tasks on the main thread

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

  • Reduce unused CSS

    52 KiB

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

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 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 CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.4 s

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

  • Server response: 81 ms

    81 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 31.5 s

    31.5 s

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

  • Time to Interactive: 38.5 s

    38.5 s

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

  • Cumulative Layout Shift: 1

    1

    The layout shifts by 1 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 5.3 s

    5.3 s

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

  • 38 images without width and height

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • Tap response (INP) held steady for real visitors

    +4%

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

7 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: 1.0 s

    1.0 s

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

  • 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: 0.8 s

    0.8 s

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

  • Real-user TTFB: 514 ms

    514 ms

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

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

    -11%

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

  • Total Blocking Time: 128 ms

    128 ms

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

Images and page weight

4 to fix38
  • Page weight: 26.2 MB in 141 requests

    26.2 MB

    Your homepage downloads 26.2 MB in 141 requests on a phone: images 22.2 MB (73), other files 2.7 MB (30) and scripts 1.2 MB (23). Under 2 MB keeps phones on slow connections fast.

  • 8 images over 500 KB

    8 images weigh 9.1 MB together. On a phone connection a single image that size takes seconds.

  • 13 images in older formats

    13 images (9.5 MB) are 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.

  • 7 images below the first screen load straight away

    7 images further down the page (7.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 7.4 g of CO₂ per visit

    7.44 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

13 to fixGoogle 4573
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • 2 tap targets too small

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

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

  • 47 images without alt text

    47 images have no alt text, which hurts accessibility and image search.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

  • 10 links without text

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

1 checks passed
  • 22 automated accessibility rules passed

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

SEO

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 218 internal links, 15 external

    The homepage links to 218 pages on petiteladeux.com and 15 external pages.

4 checks passed
  • Meta description: 127 characters

    Your meta description is 127 characters: “�ץƥ���ɥ�����ˡ���ۥʥץ����Ȥ��п����Τ���������ޤ�������������&amp;#9825;ǥ��&amp;#9825;������ν����β�ǽ�������֤����ܼ�����ϥåԡ��ˤʤ…”.

  • Title: 39 characters

    Your title is a healthy 39 characters: “���������֤Τ�Ź��Petite la' deux�åץƥ���ɥ�”.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://petiteladeux.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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://petiteladeux.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.

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

Best practices

5 to fixGoogle 6559
  • No mobile viewport

    No viewport meta tag, so phones render the desktop layout zoomed out.

  • 75 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

Content and conversion

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

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

  • Only about 57 words

    The homepage has only about 57 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (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.

  • 3 cookies set on arrival

    3

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

  • 11 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2012.

Stack

Framework
jQuery
Analytics
Google Analytics
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on petiteladeux.com, including 17 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