Website review, no card needed

roger-gallet.jp logo

roger-gallet.jp website review

Visit site (opens in a new tab)Reviewed 21 November 202635 issues · 85 checks

This review found 35 issues worth fixing on roger-gallet.jp, 18 of them high impact, across 85 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
1.8 s1.4 sMay 30Nov 141.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.5 s
Jun 6, 20261.4 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.6 s
Aug 29, 20261.7 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.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.5 s
Nov 7, 20261.5 s
Nov 14, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
123 ms100 msMay 30Nov 14107 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026108 ms
Jun 6, 2026109 ms
Jun 13, 2026111 ms
Jun 20, 2026111 ms
Jun 27, 2026110 ms
Jul 4, 2026109 ms
Jul 11, 2026108 ms
Jul 18, 2026107 ms
Jul 25, 2026106 ms
Aug 1, 2026103 ms
Aug 8, 2026104 ms
Aug 15, 2026104 ms
Aug 22, 2026109 ms
Aug 29, 2026115 ms
Sep 5, 2026116 ms
Sep 12, 2026116 ms
Sep 19, 2026116 ms
Sep 26, 2026116 ms
Oct 3, 2026116 ms
Oct 10, 2026118 ms
Oct 17, 2026120 ms
Oct 24, 2026118 ms
Oct 31, 2026115 ms
Nov 7, 2026112 ms
Nov 14, 2026107 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 roger-gallet.jp (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. roger-gallet.jp at 2.9 s2.9 s
  2. roger-gallet.jp at 5.7 s5.7 s
  3. roger-gallet.jp at 8.6 s8.6 s
  4. roger-gallet.jp at 11.5 s11.5 s
  5. roger-gallet.jp at 14.4 s14.4 s
  6. roger-gallet.jp at 17.2 s17.2 s
  7. roger-gallet.jp at 20.1 s20.1 s
  8. roger-gallet.jp at 23.0 s23.0 s

Speed

11 to fix56
  • Render-blocking requests

    3.0 s

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

  • Reduce unused JavaScript

    2.3 s · 420 KiB

    About 420 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

  • Use efficient cache lifetimes

    1.9 s · 319 KiB

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

  • Shopify adds 1.4 s

    1.4 s

    Shopify costs a phone 1.4 s of main-thread work and 211 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 8.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Clarity and Google CDN and others), adding 1.0 MB and 2.1 s of main-thread time.

  • Improve image delivery

    1.3 MB

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

  • Mobile performance score: 56

    56/100

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

  • Clarity adds 446 ms

    446 ms

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

  • 1,562 HTML elements

    The page has 1,562 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Stamped.io adds 47 ms

    47 ms

    Stamped.io costs a phone 47 ms of main-thread work and 324 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

    150 ms · 160 KiB

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

  • Legacy JavaScript

    150 ms · 8 KiB

    Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 3 long tasks on the main thread

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

  • 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

5 to fix100
  • Largest Contentful Paint: 20.9 s

    20.9 s

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

  • Speed Index: 22.4 s

    22.4 s

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

  • Time to Interactive: 21.2 s

    21.2 s

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

  • First Contentful Paint: 5.5 s

    5.5 s

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

  • 56 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

8 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: 128 ms

    128 ms

    Real visitors wait 128 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.2 s

    1.2 s

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

  • Real-user TTFB: 545 ms

    545 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 10 ms

    10 ms

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

Images and page weight

3 to fix43
  • Page weight: 5.1 MB in 353 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 353 requests on a phone: images 1.7 MB (50), other files 1.3 MB (231) and fonts 1.1 MB (4). Under 2 MB keeps phones on slow connections fast.

  • 7 images far larger than shown

    541 KiB

    7 images are downloaded at several times the size a phone draws them, for example RG-PouchKit26-Fig-2000x2000_1024x1024.jpg at 1,024 px wide, shown at 100 px. Resized copies would save about 541 KiB.

  • 6 images below the first screen load straight away

    6 images further down the page (319 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.4 g of CO₂ per visit

    1.45 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

7 to fixGoogle 7390
  • 23 buttons without a name

    23 buttons have no accessible name, so screen readers announce just “button”.

  • 3 text elements with low contrast

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

  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

  • Frames without titles

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

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

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

  • Zoom is disabled

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

  • 3 form fields without a label

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

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

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

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

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

SEO

1 to fixGoogle 10095
  • One H1 headline

    Your <h1> is empty.

  • 151 internal links, 13 external

    The homepage links to 151 pages on roger-gallet.jp and 13 external pages.

7 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “1862年にパリで誕生したロジェ・ガレ。長年に渡り継承した蒸留技術により抽出した希少な植物エキスをはじめ、こだわりの自然由来成分を配合したフレグランス ビューティ製品(香水・フレグランス・ボディケア)を展開。 ロジェ・ガレの香りで全身をケ…”.

  • Title: 31 characters

    Your title is a healthy 31 characters: “ロジェ・ガレ公式オンラインストア|ROGER & GALLET”.

  • Canonical URL set

    The canonical URL is https://www.roger-gallet.jp/.

  • Structured data in place

    Structured data found: BreadcrumbList.

  • 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.roger-gallet.jp/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.

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.

  • llms.txt published

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

Other pages

100
  • 15 pages with very little text

    https://www.roger-gallet.jp/collections/fleur-de-figuier, https://www.roger-gallet.jp/collections/the, https://www.roger-gallet.jp/collections/gingembre-rouge, https://www.roger-gallet.jp/collections/vanillesoleil, https://www.roger-gallet.jp/collections/fleur-d-osmanthu and https://www.roger-gallet.jp/collections/rose and 9 others have 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.

  • 15 internal pages checked

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

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

  • Every page has a meta description

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

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of null (reading 'addEventListener')”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

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 144 words

    The homepage has only about 144 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
  • 5 short forms

    5 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

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.

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 cookies, 2 of them by other companies (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.

  • 33 other companies contacted

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

Apps on your store

Your storefront loads 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Gempages Builder · Judge Me Reviews · Fbp Fast Bundle · Automatic Discounts Upsells · stamped.io

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on roger-gallet.jp, including 16 speed issues, 1 SEO issue 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