Website review, no card needed

minisforumpc.fr logo

minisforumpc.fr website review

Visit site (opens in a new tab)Reviewed 20 November 202641 issues · 79 checks

This review found 41 issues worth fixing on minisforumpc.fr, 16 of them high impact, across 79 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
3.7 s930 msMay 30Nov 141.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.2 s
Jun 6, 20261.6 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.8 s
Jul 11, 20261.7 s
Jul 18, 20262.0 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.0 s
Aug 15, 20261.6 s
Aug 22, 20261.4 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.8 s
Oct 3, 20262.6 s
Oct 10, 20263.3 s
Oct 17, 20263.4 s
Oct 24, 20263.2 s
Oct 31, 20262.4 s
Nov 7, 20261.7 s
Nov 14, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
233 ms187 msMay 30Nov 14195 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026193 ms
Jun 6, 2026211 ms
Jun 13, 2026217 ms
Jun 20, 2026220 ms
Jun 27, 2026219 ms
Jul 4, 2026218 ms
Jul 11, 2026219 ms
Jul 18, 2026221 ms
Jul 25, 2026226 ms
Aug 1, 2026228 ms
Aug 8, 2026225 ms
Aug 15, 2026225 ms
Aug 22, 2026222 ms
Aug 29, 2026223 ms
Sep 5, 2026221 ms
Sep 12, 2026215 ms
Sep 19, 2026207 ms
Sep 26, 2026201 ms
Oct 3, 2026210 ms
Oct 10, 2026220 ms
Oct 17, 2026221 ms
Oct 24, 2026220 ms
Oct 31, 2026204 ms
Nov 7, 2026192 ms
Nov 14, 2026195 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 minisforumpc.fr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. minisforumpc.fr at 1.1 s1.1 s
  2. minisforumpc.fr at 2.3 s2.3 s
  3. minisforumpc.fr at 3.4 s3.4 s
  4. minisforumpc.fr at 4.6 s4.6 s
  5. minisforumpc.fr at 5.7 s5.7 s
  6. minisforumpc.fr at 6.9 s6.9 s
  7. minisforumpc.fr at 8.0 s8.0 s
  8. minisforumpc.fr at 9.2 s9.2 s

Speed

13 to fix45
  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 45

    45/100

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

  • Main-thread work: 8.3 s

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

  • 5,488 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, loloyal.com and gsitrix.com and others), adding 2.2 MB and 1.4 s of main-thread time.

  • Improve image delivery

    650 ms · 439 KiB

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

  • Reduce unused JavaScript

    150 ms · 650 KiB

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

  • Shopify adds 326 ms

    326 ms

    Shopify costs a phone 326 ms of main-thread work and 862 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

    300 ms · 78 KiB

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

  • 20 long tasks on the main thread

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

  • loloyal.com adds 282 ms

    282 ms

    loloyal.com costs a phone 282 ms of main-thread work and 395 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.

  • gsitrix.com adds 279 ms

    279 ms

    gsitrix.com costs a phone 279 ms of main-thread work and 177 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.

  • xcottons.com adds 218 ms

    218 ms

    xcottons.com costs a phone 218 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.

  • Use efficient cache lifetimes

    188 KiB

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

  • Legacy JavaScript

    171 KiB

    Polyfills for old browsers add 171 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.

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

    13 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Time to Interactive: 22.7 s

    22.7 s

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

  • Largest Contentful Paint: 8.0 s

    8.0 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Speed Index: 7.6 s

    7.6 s

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 8 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -4%

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

  • Largest content (LCP) got 19% slower for real visitors

    +19%

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

5 checks passed
  • 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: 177 ms

    177 ms

    Real visitors wait 177 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.016

    0.016

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

Images and page weight

1 to fix33
  • Page weight: 5.3 MB in 436 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 436 requests on a phone: scripts 2.0 MB (188), images 1.9 MB (81) and other files 877 KiB (134). Under 2 MB keeps phones on slow connections fast.

  • About 1.5 g of CO₂ per visit

    1.50 g

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

Accessibility

7 to fixGoogle 8280
  • Delayed refresh under 20 hours must not be used (1 element)

    Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

  • 48 images without alt text

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

  • 1 button without a name

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

  • Zoom is disabled

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 20 automated accessibility rules passed

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

SEO

4 to fixGoogle 8580
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Meta description is short (43 characters)

    Your meta description is only 43 characters: “Mini PCs, Mini Workstations & Tablette PCs.”. 70 to 160 characters is enough to sell the click.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, Organization and Service) but with 1 problem, for example “Service: no offers (price) block”.

  • 11 links crawlers can't follow

    11 links have no real href, so search engines can't follow them.

  • 384 internal links, 5 external

    The homepage links to 384 pages on minisforumpc.fr and 5 external pages.

5 checks passed
  • Title: 33 characters

    Your title is a healthy 33 characters: “Minisforum France – Minisforum FR”.

  • Canonical URL set

    The canonical URL is https://minisforumpc.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://minisforumpc.fr/sitemap.xml.

AI search readiness

1 to fix77
  • Parts of the site are closed to 2 AI crawlers

    Your robots.txt lets Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

2 checks passed
  • Organization data: 6 of 6 facts

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

  • llms.txt published

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

Other pages

2 to fix90
  • 14 pages without a meta description

    https://minisforumpc.fr/collections/serie-workstation, https://minisforumpc.fr/collections/frontpage, https://minisforumpc.fr/collections/serie-nas, https://minisforumpc.fr/collections/carte-mere-1, https://minisforumpc.fr/collections/accessories and https://minisforumpc.fr/pages/compare-1 and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages without an H1

    https://minisforumpc.fr/collections/serie-workstation, https://minisforumpc.fr/collections/frontpage, https://minisforumpc.fr/collections/carte-mere-1, https://minisforumpc.fr/collections/accessories, https://minisforumpc.fr/pages/compare-1 and https://minisforumpc.fr/collections/bureau-et-maison and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 84 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.

  • Canonical URLs point to themselves

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

  • Titles are unique

    Every page we checked has its own title.

  • 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

2 to fixGoogle 7789
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 10 words

    The homepage has only about 10 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.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Login / Sign Up”.

  • 48 short forms

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

  • Analytics in place

    Analytics detected: Hotjar.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 6 email links.

Privacy and tracking

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

  • 1 other company contacted

    Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 minisforumpc.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
10 Shopify Products;Shopify;Shopify Plus
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on minisforumpc.fr, including 21 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