Website review, no card needed
amazone.net website review
Visit site (opens in a new tab)Reviewed 31 October 202630 issues · 87 checks
This review found 30 issues worth fixing on amazone.net, 11 of them high impact, across 87 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
85BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 114 ms |
| May 16, 2026 | 116 ms |
| May 23, 2026 | 119 ms |
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 121 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 122 ms |
| Jun 27, 2026 | 123 ms |
| Jul 4, 2026 | 123 ms |
| Jul 11, 2026 | 128 ms |
| Jul 18, 2026 | 125 ms |
| Jul 25, 2026 | 123 ms |
| Aug 1, 2026 | 124 ms |
| Aug 8, 2026 | 123 ms |
| Aug 15, 2026 | 126 ms |
| Aug 22, 2026 | 127 ms |
| Aug 29, 2026 | 130 ms |
| Sep 5, 2026 | 135 ms |
| Sep 12, 2026 | 137 ms |
| Sep 19, 2026 | 141 ms |
| Sep 26, 2026 | 142 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 148 ms |
| Oct 17, 2026 | 149 ms |
| Oct 24, 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: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
600 ms · 135 KiBAbout 135 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Reduce unused CSS
450 ms · 101 KiBAbout 101 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Use efficient cache lifetimes
350 ms · 61 KiB6 files are served with short cache lifetimes, so returning visitors download them again (61 KiB).
Render-blocking requests
400 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.
Improve image delivery
150 ms · 111 KiB5 images could be 111 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
2 third-party services on the page
2 third-party services load with your homepage (consentmanager.net and Cloudflare), adding 146 KiB and 184 ms of main-thread time.
Legacy JavaScript
150 ms · 28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 111 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 491 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 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: 7.4 s
7.4 sYour largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “DISCOVER THE VENTERRA HIGH OUTPUT HOE”.
Time to Interactive: 7.5 s
7.5 sThe page becomes fully interactive after 7.5 s. Good is under 3.8 s.
Tap response (INP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 114 ms to 149 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 31% slower for real visitors
+31%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.6 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 878 ms
878 msReal visitors wait 878 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.1 s
5.1 sVisually, the page fills in at 5.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 183 ms
183 msReal visitors wait 183 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 113 ms
113 msScripts block the page for only 113 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
4 images in older formats
4 images (178 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.
1 image below the first screen load straight away
1 image further down the page (36 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.4 g of CO₂ per visit
0.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.36 g of CO₂e: 43.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.3 MB in 57 requests
1.3 MBYour homepage downloads 1.3 MB in 57 requests on a phone: fonts 385 KiB (6), images 361 KiB (32) and scripts 329 KiB (11). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
10 images without alt text
10 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Structured data has 1 problem
Structured data found (CollectionPage, ContactPoint, Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.
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.
212 internal links, 33 external
The homepage links to 212 pages on amazone.net and 33 external pages.
6 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Welcome to AMAZONE! We are a manufacturer of agricultural and groundcare machinery and a systems provider for intellige…”.
Title: 30 characters
Your title is a healthy 30 characters: “Amazone agricultural machinery”.
Canonical URL set
The canonical URL is https://amazone.net/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://amazone.net/service-sitemap-8fa4975ebf303fcfc14e9c48de067282-sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://amazone.net/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 contact details; sameAs (social profiles) and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,239 words), so crawlers that don't run JavaScript still read it.
Other pages
12 pages share a meta description
https://amazone.net/en/experience-acquire/acquire/sales-contacts/dealer-locator, https://amazone.net/en/company/company-news, https://amazone.net/en/company/image-films, https://amazone.net/en/company/company-history, https://amazone.net/en/company/certification and https://amazone.net/en/company/sustainability and 6 others use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 158 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 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 15 pages that loaded have a <title>.
Best practices
11 small tap targets
11 of 40 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 916 words of copy
The homepage carries about 916 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Fan-Shop” and “Contact”.
9 calls to action
The homepage has 9 calls to action, for example “Contact us”, “Online Fan Shop” and “AMAZONE paint-book”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
3 other companies contacted
Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: consentmanager
A consent management tool (consentmanager) loads with the page.
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 amazone.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- CoreMedia CMS
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on amazone.net, including 14 speed issues, 3 SEO issues and 2 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.