Website review, no card needed

naturaforce.com logo

naturaforce.com website review

Visit site (opens in a new tab)Reviewed 6 November 202639 issues · 87 checks

This review found 39 issues worth fixing on naturaforce.com, 14 of them high impact, across 87 checks. The most urgent: mobile performance score: 48. 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 naturaforce.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. naturaforce.com at 1.2 s1.2 s
  2. naturaforce.com at 2.3 s2.3 s
  3. naturaforce.com at 3.5 s3.5 s
  4. naturaforce.com at 4.6 s4.6 s
  5. naturaforce.com at 5.8 s5.8 s
  6. naturaforce.com at 7.0 s7.0 s
  7. naturaforce.com at 8.1 s8.1 s
  8. naturaforce.com at 9.3 s9.3 s

Speed

12 to fix48
  • Mobile performance score: 48

    48/100

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

  • Main-thread work: 9.5 s

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

  • 6,371 HTML elements

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

  • Reduce unused JavaScript

    1.9 MB

    About 1.9 MB of JavaScript is downloaded but never used on this page.

  • 8 third-party services on the page

    8 third-party services load with your homepage (openreviews.io, Shopify and appstle.com and others), adding 1.5 MB and 1.7 s of main-thread time.

  • Render-blocking requests

    850 ms

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

  • Use efficient cache lifetimes

    427 KiB

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

  • openreviews.io adds 393 ms

    393 ms

    openreviews.io costs a phone 393 ms of main-thread work and 183 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.

  • Shopify adds 346 ms

    346 ms

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

  • appstle.com adds 346 ms

    346 ms

    appstle.com costs a phone 346 ms of main-thread work and 338 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.

  • Klaviyo adds 260 ms

    260 ms

    Klaviyo costs a phone 260 ms of main-thread work and 323 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.

  • 20 long tasks on the main thread

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

  • Improve image delivery

    138 KiB

    3 images could be 138 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    85 KiB

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

  • Legacy JavaScript

    48 KiB

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

  • Minify JavaScript

    28 KiB

    28 KiB could be saved by minifying JavaScript.

  • Minify CSS

    16 KiB

    16 KiB could be saved by minifying CSS.

  • Duplicated JavaScript

    11 KiB

    11 KiB JavaScript is shipped twice across bundles.

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

    21 ms

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

Core Web Vitals

7 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: 20.0 s

    20.0 s

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

  • Largest Contentful Paint: 7.0 s

    7.0 s

    Your largest element takes 7.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Retrouvez énergie & vitalité, au naturel”.

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • Real-user TTFB: 842 ms

    842 ms

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

  • 96 images without width and height

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

  • Speed Index: 4.4 s

    4.4 s

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

8 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 181 ms

    181 ms

    Real visitors wait 181 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.

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Tap response (INP) got 43% faster for real visitors

    -43%

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

  • Largest content (LCP) got 52% faster for real visitors

    -52%

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Cumulative Layout Shift: 0.011

    0.011

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

Images and page weight

2 to fix81
  • Page weight: 3.4 MB in 373 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 373 requests on a phone: scripts 1.8 MB (146), images 887 KiB (53) and fonts 236 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    sportive_cf2c6054-2c17-406a-9d05-b12ad4fa7fe2.webp 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).

  • 6 images in older formats

    6 images (223 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 1.0 g of CO₂ per visit

    0.95 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8991
  • 50 text elements with low contrast

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

  • 4 tap targets too small

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

  • Scrollable region must have keyboard access (3 elements)

    Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

  • 9 images without alt text

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

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

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

  • 2 form fields without a label

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

  • ARIA role should be appropriate for the element (7 elements)

    ARIA role should be appropriate for the element: 7 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 55 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9290
  • Meta description is long (246 characters)

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

  • One H1 headline

    Your <h1> is empty.

  • 399 internal links, 4 external

    The homepage links to 399 pages on naturaforce.com and 4 external pages.

6 checks passed
  • Title: 55 characters

    Your title is a healthy 55 characters: “Natura Force : compléments alimentaires naturels et bio”.

  • Canonical URL set

    The canonical URL is https://www.naturaforce.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.naturaforce.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.naturaforce.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.

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.

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

Other pages

1 to fix75
  • 3 linked pages are broken

    Your homepage links to https://www.naturaforce.com/collections/en-promotion, https://www.naturaforce.com/pages/nous-contacter and https://www.naturaforce.com/products/chardon-marie-bio-anti-gaspi, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 15 internal pages checked

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

6 checks passed
  • Canonical URLs point to themselves

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

  • Every page has a meta description

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

Best practices

3 to fixGoogle 9285
  • 7 small tap targets

    7 of 26 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “appstleStringSetting is not defined”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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 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 1,242 words of copy

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

2 checks passed
  • 39 short forms

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

  • Social proof on the page

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

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, Klaviyo and Meta Pixel 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.

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 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.

  • 50 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on naturaforce.com, including 19 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

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