Website review, no card needed
agrilution.com website review
Visit site (opens in a new tab)Reviewed 6 November 202639 issues · 84 checks
This review found 39 issues worth fixing on agrilution.com, 6 of them high impact, across 84 checks. The most urgent: render-blocking requests. 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
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 116 ms |
| May 23, 2026 | 122 ms |
| May 30, 2026 | 126 ms |
| Jun 6, 2026 | 119 ms |
| Jun 13, 2026 | 107 ms |
| Jun 20, 2026 | 105 ms |
| Jun 27, 2026 | 106 ms |
| Jul 4, 2026 | 111 ms |
| Jul 11, 2026 | 113 ms |
| Jul 18, 2026 | 110 ms |
| Jul 25, 2026 | 110 ms |
| Aug 1, 2026 | 104 ms |
| Aug 8, 2026 | 113 ms |
| Aug 15, 2026 | 111 ms |
| Aug 22, 2026 | 112 ms |
| Aug 29, 2026 | 117 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 110 ms |
| Sep 19, 2026 | 111 ms |
| Sep 26, 2026 | 105 ms |
| Oct 3, 2026 | 107 ms |
| Oct 10, 2026 | 105 ms |
| Oct 17, 2026 | 109 ms |
| Oct 24, 2026 | 178 ms |
| Oct 31, 2026 | 253 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
Render-blocking requests
1.6 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 68
68/100Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
600 ms · 241 KiB15 files are served with short cache lifetimes, so returning visitors download them again (241 KiB).
Avoid multiple page redirects
772 msThe page goes through 1 redirect before it starts loading, costing about 772 ms. Link and advertise the final URL directly.
Reduce unused JavaScript
640 ms · 121 KiBAbout 121 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 640 ms faster on a phone.
Font display
550 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 550 ms).
Reduce unused CSS
310 ms · 61 KiBAbout 61 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.
1 third-party service on the page
1 third-party service load with your homepage (Google Tag Manager), adding 131 KiB and 113 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 92 ms. During a long task the page ignores taps.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
Improve image delivery
7 KiB1 image could be 7 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
2 checks passed
Main-thread work: 0.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 169 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.2 s
5.2 sYour largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Miele & Cie. KG uses cookies (including third-party cookies…”.
Tap response (INP) got 81% slower for real visitors
+81%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 116 ms to 253 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.178
0.178The layout shifts by 0.178 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 5.4 s
5.4 sThe page becomes fully interactive after 5.4 s. Good is under 3.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
9 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: 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: 97 ms
97 msReal visitors wait 97 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.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 690 ms
690 msReal visitors wait 690 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 3.1 s
3.1 sVisually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 21 ms
21 msScripts block the page for only 21 ms while loading. Good is under 200 ms.
Images and page weight
1 image in older formats
1 image (49 KiB) is 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 0.2 g of CO₂ per visit
0.18 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.18 g of CO₂e: 21.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 659 KiB in 23 requests
659 KiBYour homepage downloads 659 KiB in 23 requests on a phone: scripts 349 KiB (7), fonts 135 KiB (2) and stylesheets 110 KiB (3). That is a lean page.
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
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
The skip-link target should exist and be focusable (2 elements)
The skip-link target should exist and be focusable: 2 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 4 images in the HTML carry an alt attribute.
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (2 characters)
Your meta description is only 2 characters: “()”. 70 to 160 characters is enough to sell the click.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.miele.com/sitemap-index.xml, so Google discovers your pages only by following links.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
23 internal links, 4 external
The homepage links to 23 pages on agrilution.com and 4 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Agrilution has ceased operations”.
Title: 32 characters
Your title is a healthy 32 characters: “Agrilution has ceased operations”.
Canonical URL set
The canonical URL is https://www.miele.com/en/com/agrilution-7269.htm.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
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.
Some text only appears after JavaScript runs
54%The HTML your server sends has 122 of the 227 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://www.miele.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.
1 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.
Other pages
2 pages share a title
https://www.miele.com/en/com/index.htm and https://www.miele.com/en/project-business/index.htm all use the title “Home”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://www.miele.com/en/com/index.htm, https://www.miele.com/de/com/index.htm, https://www.miele.com/en/com/products-2066.htm, https://www.miele.com/en/com/index-h.htm, https://www.miele.com/en/project-business/index.htm and https://www.miele.com/en/com/index-l.htm have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages share a meta description
https://www.miele.com/en/com/about-us-2065.htm, https://www.miele.com/en/com/shops-2067.htm, https://www.miele.com/en/com/miele-service-2069.htm, https://www.miele.com/en/com/contact-us-2073.htm, https://www.miele.com/en/com/newsletter-5071.htm and https://www.miele.com/en/com/data-protection-2074.htm use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.miele.com/en/project-business/index.htm, whose canonical is https://www.miele.com/en/project-business. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://www.miele.com/en/com/products-2066.htm, https://www.miele.com/en/c/sustainability-3359.htm and https://www.miele.com/en/com/newsletter-5071.htm have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.miele.com/en/com/newsletter-5071.htm has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
1 page slow to respond
https://www.miele.com/en/p took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 20 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
19 small tap targets
19 of 26 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 “curElement.getAttribute is not a function”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 227 words
The homepage has only about 227 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact us”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
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.
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 agrilution.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on agrilution.com, including 13 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.