Website review, no card needed

agentnateur.com logo

agentnateur.com website review

Visit site (opens in a new tab)Reviewed 9 November 202635 issues · 85 checks

This review found 35 issues worth fixing on agentnateur.com, 11 of them high impact, across 85 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

Real-visitor load time (LCP)75th percentile, phones
2.5 s1.9 sMay 23Nov 72.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.4 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.2 s
Jun 27, 20262.3 s
Jul 4, 20262.2 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20261.9 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.0 s
Sep 26, 20262.1 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20262.2 s
Nov 7, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
123 ms106 msMay 23Nov 7114 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026115 ms
May 30, 2026114 ms
Jun 6, 2026115 ms
Jun 13, 2026114 ms
Jun 20, 2026112 ms
Jun 27, 2026112 ms
Jul 4, 2026112 ms
Jul 11, 2026111 ms
Jul 18, 2026112 ms
Jul 25, 2026108 ms
Aug 1, 2026111 ms
Aug 8, 2026113 ms
Aug 15, 2026112 ms
Aug 22, 2026113 ms
Aug 29, 2026114 ms
Sep 5, 2026113 ms
Sep 12, 2026120 ms
Sep 19, 2026119 ms
Sep 26, 2026120 ms
Oct 3, 2026121 ms
Oct 10, 2026120 ms
Oct 17, 2026119 ms
Oct 24, 2026113 ms
Oct 31, 2026112 ms
Nov 7, 2026114 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 agentnateur.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. agentnateur.com at 0.7 s0.7 s
  2. agentnateur.com at 1.5 s1.5 s
  3. agentnateur.com at 2.2 s2.2 s
  4. agentnateur.com at 2.9 s2.9 s
  5. agentnateur.com at 3.7 s3.7 s
  6. agentnateur.com at 4.4 s4.4 s
  7. agentnateur.com at 5.1 s5.1 s
  8. agentnateur.com at 5.9 s5.9 s

Speed

13 to fix47
  • Reduce unused JavaScript

    5.3 s · 1.4 MB

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

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 47

    47/100

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

  • Main-thread work: 4.7 s

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

  • Improve image delivery

    3.7 MB

    6 images could be 3.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, alia-prod.com and rebuyengine.com and others), adding 5.4 MB and 1.3 s of main-thread time.

  • alia-prod.com adds 271 ms

    271 ms

    alia-prod.com costs a phone 271 ms of main-thread work and 2.8 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.

  • Google Tag Manager adds 406 ms

    406 ms

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

    350 ms · 74 KiB

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

  • Reduce unused CSS

    380 ms · 39 KiB

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

  • rebuyengine.com adds 147 ms

    147 ms

    rebuyengine.com costs a phone 147 ms of main-thread work and 734 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 109 ms

    109 ms

    Shopify costs a phone 109 ms of main-thread work and 391 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 86 ms

    86 ms

    Klaviyo costs a phone 86 ms of main-thread work and 318 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 · 247 KiB

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

  • 14 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Minify JavaScript

    30 ms · 15 KiB

    15 KiB could be saved by minifying JavaScript.

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 27.7 s

    27.7 s

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

  • Time to Interactive: 33.7 s

    33.7 s

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

  • Speed Index: 12.5 s

    12.5 s

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Total Blocking Time: 476 ms

    476 ms

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

  • 9 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 111 ms

    111 ms

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (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.

  • Real-user TTFB: 473 ms

    473 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix14
  • Page weight: 11.7 MB in 441 requests

    11.7 MB

    Your homepage downloads 11.7 MB in 441 requests on a phone: images 6.2 MB (22), scripts 3.2 MB (133) and other files 1.4 MB (246). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 3.2 MB together. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    1.6 MB

    3 images are downloaded at several times the size a phone draws them, for example JenaHoliManeLatte_2.jpg at 3,600 px wide, shown at 200 px. Resized copies would save about 1.6 MB.

  • 2 images in older formats

    2 images (3.2 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.

  • An image on the first screen is lazy-loaded

    hero-mobile-tray-lower-3.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 3.3 g of CO₂ per visit

    3.31 g

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

Accessibility

3 to fixGoogle 10097
  • All page content should be contained by landmarks (35 elements)

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

  • Alternative text of images should not be repeated as text (3 elements)

    Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (3 elements)

    Elements marked as presentational should be consistently ignored: 3 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 28 images in the HTML carry an alt attribute.

  • 47 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: 47 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9288
  • 4 H1 headlines

    There are 4 <h1> headlines (“Featured”, “Category” and “Discover”). One clear main headline is easier for people and search engines.

  • Meta description is long (281 characters)

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 75 internal links, 5 external

    The homepage links to 75 pages on agentnateur.com and 5 external pages.

6 checks passed
  • Title: 41 characters

    Your title is a healthy 41 characters: “Agent Nateur | Always Pure, Never Diluted”.

  • Canonical URL set

    The canonical URL is https://www.agentnateur.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.agentnateur.com/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 (1,273 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 10 pages without a meta description

    https://www.agentnateur.com/collections/shop-all-1, https://www.agentnateur.com/collections/subscribe-save, https://www.agentnateur.com/blogs/agent-tips, https://www.agentnateur.com/collections/best-sellers, https://www.agentnateur.com/collections/best-sellers-1 and https://www.agentnateur.com/collections/hair-growth and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • 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

2 to fixGoogle 9687
  • 12 small tap targets

    12 of 54 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 “Unexpected token '}'”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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,210 words of copy

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Subscribe & Save” and “Shop All”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Shop”, “Subscribe & Save” and “Shop All”.

  • 11 short forms

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

  • Social proof on the page

    Social proof on the homepage: 22 testimonial or review blocks and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

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 Microsoft Clarity (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.

  • 12 cookies set on arrival

    12

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

  • 45 other companies contacted

    Loading the homepage contacts 45 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 agentnateur.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 16 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Bubblehouse For Agent Nateur · Yotpo Product Reviews · Savedby Package Protection · Triplewhale · Uppromote Affiliate · Rebuy Personalization Engine · Klaviyo Email Marketing Sms · Referralcandy · Affliate By Secomapp · Freegifts · privy.com · chimpstatic.com · rechargecdn.com · rebuyengine.com · bogos.io · cloudfront.net

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

Company

Headquarters
Los Angeles

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on agentnateur.com, including 19 speed issues, 3 SEO issues and 1 conversion gap. 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