Website review, no card needed
inkpost.fr website review
Visit site (opens in a new tab)Reviewed 11 November 202633 issues · 79 checks
This review found 33 issues worth fixing on inkpost.fr, 9 of them high impact, across 79 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76C- #61,257 of 99,948 reviewed websitesbeats 34%
- #38,180 of 54,914 online storesbeats 26%
- #36,126 of 49,854 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 155 ms |
| May 30, 2026 | 157 ms |
| Jun 6, 2026 | 160 ms |
| Jun 13, 2026 | 161 ms |
| Jun 20, 2026 | 156 ms |
| Jun 27, 2026 | 157 ms |
| Jul 4, 2026 | 161 ms |
| Jul 11, 2026 | 159 ms |
| Jul 18, 2026 | 151 ms |
| Jul 25, 2026 | 149 ms |
| Aug 1, 2026 | 144 ms |
| Aug 8, 2026 | 147 ms |
| Aug 15, 2026 | 152 ms |
| Aug 22, 2026 | 144 ms |
| Aug 29, 2026 | 142 ms |
| Sep 5, 2026 | 140 ms |
| Sep 12, 2026 | 138 ms |
| Sep 19, 2026 | 143 ms |
| Sep 26, 2026 | 145 ms |
| Oct 3, 2026 | 146 ms |
| Oct 10, 2026 | 146 ms |
| Oct 17, 2026 | 147 ms |
| Oct 24, 2026 | 149 ms |
| Oct 31, 2026 | 148 ms |
| Nov 7, 2026 | 149 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
Speed
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 327 KiBAbout 327 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Trust Pilot and others), adding 649 KiB and 553 ms of main-thread time.
Google Tag Manager adds 428 ms
428 msGoogle Tag Manager costs a phone 428 ms of main-thread work and 316 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.
Render-blocking requests
450 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 293 ms. During a long task the page ignores taps.
2,543 HTML elements
The page has 2,543 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 830 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
50 ms · 108 KiB10 images could be 108 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.
Use efficient cache lifetimes
33 KiB11 files are served with short cache lifetimes, so returning visitors download them again (33 KiB).
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
Reduce unused CSS
16 KiBAbout 16 KiB of CSS is downloaded but never applied on this page.
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: 42 ms
42 msYour server sent the HTML in 42 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 8.1 s
8.1 sYour largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 10.4 s
10.4 sThe page becomes fully interactive after 10.4 s. Good is under 3.8 s.
Real-user CLS: 0.15
0.15For real visitors the layout shifts by 0.15 (75th percentile). Good is under 0.1.
47 images without width and height
47 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.21
0.21The layout shifts by 0.21 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 302 ms
302 msScripts block taps and scrolling for 302 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 155 ms to 149 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 133 ms
133 msReal visitors wait 133 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 607 ms
607 msReal visitors wait 607 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.3 s
3.3 sVisually, the page fills in at 3.3 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 2.6 MB in 209 requests
2.6 MBYour homepage downloads 2.6 MB in 209 requests on a phone: images 857 KiB (48), scripts 828 KiB (61) and other files 821 KiB (82). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
icybackground.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 0.7 g of CO₂ per visit
0.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.74 g of CO₂e: 89.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Unlabelled dropdowns
3 dropdowns have no label.
41 text elements with low contrast
41 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
41 images without alt text
41 images have no alt text, which hurts accessibility and image search.
16 links without text
16 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 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (237 characters)
Your meta description is 237 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.
238 internal links, 1 external
The homepage links to 238 pages on inkpost.fr and 1 external page.
6 checks passed
One H1 headline
Your main headline reads: “🖨️ Trouvez vos cartouches d’encre”.
Title: 52 characters
Your title is a healthy 52 characters: “IMPRIM - Cartouches d'encre Premium au meilleur prix”.
Canonical URL set
The canonical URL is https://imprim.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://imprim.fr/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
3 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 (1,368 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://imprim.fr/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 pages without a meta description
https://imprim.fr/pages/cartouches-dencre-brother, https://imprim.fr/pages/cartouches-dencre-canon, https://imprim.fr/pages/cartouches-dencre-epson and https://imprim.fr/pages/cartouches-dencre-hp 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://imprim.fr/collections/cartouches-dencre-populaires-epson/products/cartouches-dencre-premium-compatibles-epson-603xl-multipack-t03a6, whose canonical is https://imprim.fr/products/cartouches-dencre-premium-compatibles-epson-603xl-multipack-t03a6. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages slow to respond
https://imprim.fr/collections/cartouches-dencre-populaires-epson/products/cartouches-dencre-premium-grande-capacite-compatibles-epson-502xl-t02w6-multipack, https://imprim.fr/collections/cartouches-dencre-populaires-epson/products/cartouches-dencre-premium-grande-capacite-compatible-epson-t1295-multipack and https://imprim.fr/collections/cartouches-dencre-populaires-epson/products/cartouches-dencre-premium-grande-capacite-compatible-epson-t26xl-t2636-multipack-encre-photo-noire-incluse took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 159 found) and read each the way a search engine does.
5 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.
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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
83 of 84 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: a star rating. 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 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 870 words of copy
The homepage carries about 870 words of visible text.
2 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Klaviyo (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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
15 other companies contacted
Loading the homepage contacts 15 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 inkpost.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 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · Elevar Conversion Tracking · Klaviyo Email Marketing Sms · trustpilot.com
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
- Bootstrap
- 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 33 issues on inkpost.fr, including 15 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.