Website review, no card needed

linticoshop.fr logo

linticoshop.fr website review

Visit site (opens in a new tab)Reviewed 6 November 202642 issues · 83 checks

This review found 42 issues worth fixing on linticoshop.fr, 15 of them high impact, across 83 checks. The most urgent: avoid multiple page redirects. 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.3 s1.8 sMay 16Jul 181.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.2 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jul 4, 20261.9 s
Jul 18, 20261.9 s

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 linticoshop.fr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. linticoshop.fr at 2.3 s2.3 s
  2. linticoshop.fr at 4.5 s4.5 s
  3. linticoshop.fr at 6.8 s6.8 s
  4. linticoshop.fr at 9.0 s9.0 s
  5. linticoshop.fr at 11.3 s11.3 s
  6. linticoshop.fr at 13.5 s13.5 s
  7. linticoshop.fr at 15.8 s15.8 s
  8. linticoshop.fr at 18.1 s18.1 s

Speed

12 to fix38
  • Avoid multiple page redirects

    49.8 s

    The page goes through 2 redirects before it starts loading, costing about 49.8 s. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    8.6 s · 1.7 MB

    About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.6 s faster on a phone.

  • Main-thread work: 12.7 s

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

  • Mobile performance score: 38

    38/100

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

  • 4,359 HTML elements

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

  • Improve image delivery

    700 ms · 4.3 MB

    37 images could be 4.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (cloudfront.net, PayPal and Shopify and others), adding 3.2 MB and 2.4 s of main-thread time.

  • cloudfront.net adds 721 ms

    721 ms

    cloudfront.net costs a phone 721 ms of main-thread work and 1.1 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.

  • PayPal adds 636 ms

    636 ms

    PayPal costs a phone 636 ms of main-thread work and 769 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.

  • Use efficient cache lifetimes

    150 ms · 562 KiB

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

  • Shopify adds 621 ms

    621 ms

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

  • Document request latency

    300 ms

    The HTML itself could arrive about 300 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    42 KiB

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

  • Reduce unused CSS

    39 KiB

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • 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: 20 ms

    20 ms

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

Core Web Vitals

6 to fix48
  • First Contentful Paint: 8.7 s

    8.7 s

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

  • Largest Contentful Paint: 45.0 s

    45.0 s

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

  • Speed Index: 22.5 s

    22.5 s

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

  • Time to Interactive: 67.4 s

    67.4 s

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

  • Total Blocking Time: 664 ms

    664 ms

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

  • 3 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

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

    0.052

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

Images and page weight

1 to fix70
  • Page weight: 18.3 MB in 709 requests

    18.3 MB

    Your homepage downloads 18.3 MB in 709 requests on a phone: images 11.8 MB (165), scripts 3.6 MB (237) and other files 1.2 MB (251). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (137 KiB) 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 5.2 g of CO₂ per visit

    5.19 g

    By the Sustainable Web Design model, a visit to your homepage emits about 5.19 g of CO₂e: 622.3 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

6 to fixGoogle 9292
  • 18 text elements with low contrast

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

  • Zoom is disabled

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

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

    All page content should be contained by landmarks: 21 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 (2 elements)

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

  • 15 links without text

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

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 496 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 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 10080
  • Title is long (83 characters)

    Your title is 83 characters, so Google will cut it off around 60: “LINTICO | L’élégance naturelle du lin, pour une vie saine et sans cont – LINTICO-FR”.

  • Meta description is long (230 characters)

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

  • No social preview image

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

  • One H1 headline

    Your <h1> is empty.

  • 130 internal links, 0 external

    The homepage links to 130 pages on linticoshop.fr and 0 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://linticoshop.fr/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://linticoshop.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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (484 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

5 to fix63
  • 1 page without a title

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

  • 1 linked page hidden from search

    https://linticoshop.fr/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://linticoshop.fr/customer_authentication/redirect, https://linticoshop.fr/collections/all and https://linticoshop.fr/collections/meilleures-ventes have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 links to non-canonical URLs

    Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://linticoshop.fr/collections/meilleures-ventes/products/haut-en-lin-100-a-col-asymetrique-avec-pli-inverse-ottilie-bot22, whose canonical is https://linticoshop.fr/products/haut-en-lin-100-a-col-asymetrique-avec-pli-inverse-ottilie-bot22. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 8 pages without an H1

    https://linticoshop.fr/customer_authentication/redirect, https://linticoshop.fr/collections/all, https://linticoshop.fr/collections/meilleures-ventes, https://linticoshop.fr/collections/meilleures-ventes/products/robe-dete-col-v-naturelle-100-lin-alexa-mdd70, https://linticoshop.fr/collections/meilleures-ventes/products/pantalon-en-lin-simple-a-braguette-boutonnee-heidi-pt13 and https://linticoshop.fr/collections/meilleures-ventes/products/chemise-en-lin-a-col-en-v-et-manches-courtes-penny-ot33 and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 pages with very little text

    https://linticoshop.fr/collections/all, https://linticoshop.fr/collections/meilleures-ventes, https://linticoshop.fr/collections/meilleures-ventes/products/blouse-sans-manches-a-col-structure-100-lin-blair-ot58, https://linticoshop.fr/collections/meilleures-ventes/products/robe-dete-col-v-naturelle-100-lin-alexa-mdd70, https://linticoshop.fr/collections/meilleures-ventes/products/pantalon-en-lin-simple-a-braguette-boutonnee-heidi-pt13 and https://linticoshop.fr/collections/meilleures-ventes/products/chemise-en-lin-a-col-en-v-et-manches-courtes-penny-ot33 and 4 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.

  • 11 pages slow to respond

    https://linticoshop.fr/customer_authentication/redirect, https://linticoshop.fr/collections/all, https://linticoshop.fr/collections/meilleures-ventes, https://linticoshop.fr/collections/meilleures-ventes/products/robe-dete-col-v-naturelle-100-lin-alexa-mdd70, https://linticoshop.fr/collections/meilleures-ventes/products/haut-ample-en-lin-100-a-epaules-tombantes-avec-ourlet-asymetrique-superpose-viola-bot20 and https://linticoshop.fr/collections/meilleures-ventes/products/pantalon-decontracte-en-lin-a-plis-sculptes-et-dos-elastique-veridiana-pt67 and 5 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

Best practices

3 to fixGoogle 5091
  • Deprecated browser APIs

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    86 of 90 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 746 words of visible text.

2 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact”.

  • 2 short forms

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

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

  • 25 other companies contacted

    Loading the homepage contacts 25 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 linticoshop.fr, 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 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Inbox · Cartsee Email Marketing Sms · Starapps Variant Image · Judge Me Reviews · Swatch King · Tms Prod V 71ff83e · Selleasy · Smart Menu

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

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on linticoshop.fr, including 18 speed issues, 4 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