Website review, no card needed

fr-chinology.com logo

fr-chinology.com website review

Visit site (opens in a new tab)Reviewed 7 November 202640 issues · 76 checks

This review found 40 issues worth fixing on fr-chinology.com, 13 of them high impact, across 76 checks. The most urgent: reduce unused JavaScript. 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 fr-chinology.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

13 to fix60
  • Reduce unused JavaScript

    2.1 s · 468 KiB

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

  • Improve image delivery

    300 ms · 913 KiB

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

  • Mobile performance score: 60

    60/100

    Your mobile performance score is 60. 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 (Google Tag Manager, replocdn.com and Facebook and others), adding 2.0 MB and 728 ms of main-thread time.

  • Render-blocking requests

    750 ms

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

  • Use efficient cache lifetimes

    500 ms · 211 KiB

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

  • Reduce unused CSS

    300 ms · 92 KiB

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

  • 6 long tasks on the main thread

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

  • replocdn.com adds 191 ms

    191 ms

    replocdn.com costs a phone 191 ms of main-thread work and 772 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.

  • Main-thread work: 2.6 s

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

  • Google Tag Manager adds 226 ms

    226 ms

    Google Tag Manager costs a phone 226 ms of main-thread work and 314 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.

  • 2,361 HTML elements

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

  • Shopify adds 43 ms

    43 ms

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

  • Legacy JavaScript

    250 ms · 52 KiB

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

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

1 checks passed
  • Server response: 40 ms

    40 ms

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

Core Web Vitals

6 to fix61
  • Largest Contentful Paint: 17.4 s

    17.4 s

    Your largest element takes 17.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Woman wearing a white face mask with four smaller images of…”.

  • Time to Interactive: 21.8 s

    21.8 s

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

  • Speed Index: 9.2 s

    9.2 s

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

  • 30 images without width and height

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

  • Total Blocking Time: 257 ms

    257 ms

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix33
  • Page weight: 5.3 MB in 232 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 232 requests on a phone: images 2.8 MB (61), scripts 1.5 MB (70) and other files 693 KiB (79). Under 2 MB keeps phones on slow connections fast.

  • 12 images far larger than shown

    1.7 MB

    12 images are downloaded at several times the size a phone draws them, for example selfie_with_product_1.jpg at 2,316 px wide, shown at 68 px. Resized copies would save about 1.7 MB.

  • 13 images below the first screen load straight away

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

  • 3 images in older formats

    3 images (1.1 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.

  • About 1.5 g of CO₂ per visit

    1.51 g

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

Accessibility

8 to fixGoogle 8189
  • 1 button without a name

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

  • 9 tap targets too small

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

  • 6 text elements with low contrast

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

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 67 images without alt text

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

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (3 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 9 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
  • Title is short (17 characters)

    Your title is only 17 characters: “Chinology™ France”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 16 H1 headlines

    There are 16 <h1> headlines (“Chinology™ France”, “Éliminez votre double menton en 3 Semaines” and “⚠️L'Offre Anniversaire 4 ans se termine aujourd'h…”). One clear main headline is easier for people and search engines.

  • Meta description is long (299 characters)

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

  • 26 internal links, 1 external

    The homepage links to 26 pages on fr-chinology.com and 1 external page.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.fr-chinology.com/.

  • 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.fr-chinology.com/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.fr-chinology.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.

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

Other pages

100
  • 6 internal pages checked

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

7 checks passed
  • Linked pages load

    4 pages of 6 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

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

Best practices

Google 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 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 1,235 words of copy

    The homepage carries about 1,235 words of visible text.

3 checks passed
  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 29 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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 (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.

  • 28 other companies contacted

    Loading the homepage contacts 28 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 fr-chinology.com, 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 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Kaching Bundles · Klaviyo Email Marketing Sms

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
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on fr-chinology.com, including 19 speed issues, 4 SEO issues 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