Website review, no card needed

amoreterra.com logo

amoreterra.com website review

Visit site (opens in a new tab)Reviewed 21 October 202632 issues · 81 checks

This review found 32 issues worth fixing on amoreterra.com, 13 of them high impact, across 81 checks. The most urgent: iubenda adds 1.1 s. 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
4.3 s2.9 sMay 2Oct 173.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.1 s
May 9, 20263.2 s
May 16, 20263.2 s
May 23, 20263.4 s
May 30, 20263.7 s
Jun 6, 20263.9 s
Jun 13, 20264.2 s
Jun 20, 20264.1 s
Jun 27, 20264.1 s
Jul 4, 20264.1 s
Jul 11, 20264.0 s
Jul 18, 20264.0 s
Jul 25, 20263.9 s
Aug 1, 20263.8 s
Aug 8, 20263.9 s
Aug 15, 20263.9 s
Aug 22, 20264.0 s
Aug 29, 20264.1 s
Sep 5, 20264.0 s
Sep 12, 20264.0 s
Sep 19, 20264.0 s
Sep 26, 20263.9 s
Oct 3, 20263.9 s
Oct 10, 20263.9 s
Oct 17, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
200 ms151 msMay 2Oct 17193 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026175 ms
May 9, 2026178 ms
May 16, 2026171 ms
May 23, 2026162 ms
May 30, 2026166 ms
Jun 6, 2026157 ms
Jun 13, 2026159 ms
Jun 20, 2026164 ms
Jun 27, 2026161 ms
Jul 4, 2026174 ms
Jul 11, 2026171 ms
Jul 18, 2026160 ms
Jul 25, 2026157 ms
Aug 1, 2026159 ms
Aug 8, 2026163 ms
Aug 15, 2026172 ms
Aug 22, 2026175 ms
Aug 29, 2026173 ms
Sep 5, 2026173 ms
Sep 12, 2026173 ms
Sep 19, 2026177 ms
Sep 26, 2026183 ms
Oct 3, 2026194 ms
Oct 10, 2026194 ms
Oct 17, 2026193 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 amoreterra.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. amoreterra.com at 1.1 s1.1 s
  2. amoreterra.com at 2.3 s2.3 s
  3. amoreterra.com at 3.4 s3.4 s
  4. amoreterra.com at 4.5 s4.5 s
  5. amoreterra.com at 5.6 s5.6 s
  6. amoreterra.com at 6.8 s6.8 s
  7. amoreterra.com at 7.9 s7.9 s
  8. amoreterra.com at 9.0 s9.0 s

Speed

9 to fix43
  • iubenda adds 1.1 s

    1.1 s

    iubenda costs a phone 1.1 s of main-thread work and 154 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 43

    43/100

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

  • Main-thread work: 9.6 s

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

  • 6,340 HTML elements

    The page has 6,340 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 (iubenda, Google Tag Manager and trustmate.pro and others), adding 765 KiB and 1.6 s of main-thread time.

  • Improve image delivery

    450 ms · 299 KiB

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

  • Reduce unused JavaScript

    300 ms · 202 KiB

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

  • Google Tag Manager adds 331 ms

    331 ms

    Google Tag Manager costs a phone 331 ms of main-thread work and 351 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 · 54 KiB

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

  • Use efficient cache lifetimes

    150 ms · 119 KiB

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

  • 19 long tasks on the main thread

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

  • Render-blocking requests

    100 ms

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

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 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: 67 ms

    67 ms

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

Core Web Vitals

8 to fix67
  • 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: 11.0 s

    11.0 s

    Your largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “(offerta) 6 Pz. Eliche bio”.

  • Time to Interactive: 16.8 s

    16.8 s

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

  • Speed Index: 8.1 s

    8.1 s

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

  • Total Blocking Time: 768 ms

    768 ms

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

  • Real-user LCP: 3.9 s

    3.9 s

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

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

    +24%

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Tap response (INP) got 10% slower for real visitors

    +10%

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

5 checks passed
  • Real-user INP: 194 ms

    194 ms

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

  • Real-user CLS: 0.08

    0.08

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 578 ms

    578 ms

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

  • Cumulative Layout Shift: 0.067

    0.067

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

Images and page weight

1 to fix85
  • Page weight: 3.4 MB in 224 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 224 requests on a phone: images 1.5 MB (34), scripts 1,024 KiB (105) and other files 488 KiB (48). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    0.96 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

7 to fixGoogle 8391
  • 21 text elements with low contrast

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

  • Invalid ARIA attributes

    98 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • 6 images without alt text

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 2 tap targets too small

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

3 to fixGoogle 9284
  • Title is long (80 characters)

    Your title is 80 characters, so Google will cut it off around 60: “We have always been organic, we cultivate and create goodness. – AmoreTerra shop”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • One H1 headline

    Your <h1> is empty.

  • 259 internal links, 13 external

    The homepage links to 259 pages on amoreterra.com and 13 external pages.

5 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “We grow and transform our all Italyn raw materials. Handcrafted organic products, fast and free delivery at 49 €. Disco…”.

  • Canonical URL set

    The canonical URL is https://amoreterra.com/en.

  • 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://shop.amoreterra.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

  • llms.txt published

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://amoreterra.com/en/collections/scopri-amoreterra has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://amoreterra.com/en/collections/scopri-amoreterra has 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 107 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

Google 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    42 of 50 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix86
  • 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.

  • About 1,846 words of copy

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

6 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “CONTACT US”.

  • 44 short forms

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

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 3 email links.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo and Meta Pixel (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies (measured from a US location before any click).

  • 18 other companies contacted

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

1 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) loads with the page.

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 amoreterra.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 32 issues on amoreterra.com, including 17 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