Website review, no card needed
haygain.nl website review
Visit site (opens in a new tab)Reviewed 10 November 202642 issues · 86 checks
This review found 42 issues worth fixing on haygain.nl, 14 of them high impact, across 86 checks. The most urgent: page weight: 5.9 MB in 470 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
84B- #19,850 of 109,350 reviewed websitesbeats 77%
- #12,897 of 61,859 online storesbeats 73%
- #12,521 of 56,401 Shopify storesbeats 71%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
| Nov 7, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 13, 2026 | 134 ms |
| Jun 20, 2026 | 136 ms |
| Jun 27, 2026 | 130 ms |
| Jul 4, 2026 | 131 ms |
| Aug 1, 2026 | 161 ms |
| Aug 8, 2026 | 187 ms |
| Aug 15, 2026 | 190 ms |
| Aug 22, 2026 | 177 ms |
| Aug 29, 2026 | 173 ms |
| Sep 5, 2026 | 168 ms |
| Sep 12, 2026 | 167 ms |
| Sep 19, 2026 | 169 ms |
| Sep 26, 2026 | 162 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 139 ms |
| Oct 17, 2026 | 147 ms |
| Oct 24, 2026 | 140 ms |
| Oct 31, 2026 | 141 ms |
| Nov 7, 2026 | 145 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
Main-thread work: 4.2 s
A phone's processor spends 4.2 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,480 HTML elements
The page has 3,480 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
1.8 MB24 images could be 1.8 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 (Klaviyo, Shopify and Google Tag Manager and others), adding 4.5 MB and 731 ms of main-thread time.
Mobile performance score: 89
89/100Your mobile performance score is 89. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
656 KiBAbout 656 KiB of JavaScript is downloaded but never used on this page.
Shopify adds 173 ms
173 msShopify costs a phone 173 ms of main-thread work and 2.7 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.
Klaviyo adds 241 ms
241 msKlaviyo costs a phone 241 ms of main-thread work and 1,020 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.
Render-blocking requests
300 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Google Tag Manager adds 161 ms
161 msGoogle Tag Manager costs a phone 161 ms of main-thread work and 320 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.
Google CDN adds 90 ms
90 msGoogle CDN costs a phone 90 ms of main-thread work and 298 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 132 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
97 KiB12 files are served with short cache lifetimes, so returning visitors download them again (97 KiB).
Legacy JavaScript
59 KiBPolyfills for old browsers add 59 KiB JavaScript that modern phones do not need.
Reduce unused CSS
36 KiBAbout 36 KiB of CSS is downloaded but never applied on this page.
Minify CSS
9 KiB9 KiB could be saved by minifying CSS.
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: 69 ms
69 msYour server sent the HTML in 69 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 20.3 s
20.3 sThe page becomes fully interactive after 20.3 s. Good is under 3.8 s.
Speed Index: 7.8 s
7.8 sVisually, the page fills in at 7.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 218 ms
218 msScripts block taps and scrolling for 218 ms in total while the page loads. Good is under 200 ms.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 134 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 397 ms
397 msReal visitors wait 397 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 37% faster for real visitors
-37%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.6 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.01
0.01The layout barely moves while loading (CLS 0.01, good is under 0.1).
Largest Contentful Paint: 1.2 s
1.2 sYour largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “WISSENSCHAFTLICH FUNDIERTE LÖSUNGEN FÜR GESUNDE PFERDE”.
Images and page weight
Page weight: 5.9 MB in 470 requests
5.9 MBYour homepage downloads 5.9 MB in 470 requests on a phone: images 2.3 MB (41), scripts 2.2 MB (203) and other files 943 KiB (164). Under 2 MB keeps phones on slow connections fast.
11 images far larger than shown
1.5 MB11 images are downloaded at several times the size a phone draws them, for example Untitleddesign_d68e7cd6-d158-4daf-8ef9-184ed70e928f.png at 2,667 px wide, shown at 344 px. Resized copies would save about 1.5 MB.
15 images below the first screen load straight away
15 images further down the page (1.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (204 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.7 g of CO₂ per visit
1.68 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.68 g of CO₂e: 201.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
Summary elements must have discernible text (1 element)
Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
15 links without text
15 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (19 characters)
Your title is only 19 characters: “Haygain Deutschland”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“” and “WISSENSCHAFTLICH FUNDIERTE LÖSUNGEN FÜR GESUNDE P…”). One clear main headline is easier for people and search engines.
Meta description is long (202 characters)
Your meta description is 202 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
102 internal links, 6 external
The homepage links to 102 pages on haygain.nl and 6 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://haygain.de/.
Structured data in place
Structured data found: Organization and WebSite.
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://haygain.de/sitemap.xml.
AI search readiness
Some text only appears after JavaScript runs
45%The HTML your server sends has 814 of the 1,820 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
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.
llms.txt published
The site publishes https://haygain.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://haygain.de/pages/haygain-comfortstall-v2 and https://haygain.de/pages/comfortstall all use the title “Über ComfortStall | Orthopädischer Stallboden für Pferde – Haygain De…”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://haygain.de/pages/heubedampfer, https://haygain.de/collections/haygain-parts, https://haygain.de/pages/heu-einweichen-oder-bedampfen, https://haygain.de/pages/faqs and https://haygain.de/pages/forager have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://haygain.de/pages/haygain-comfortstall-v2 and https://haygain.de/pages/comfortstall 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://haygain.de/pages/haygain-comfortstall-v2, whose canonical is https://haygain.de/pages/comfortstall. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
12 pages without an H1
https://haygain.de/pages/heubedampfer, https://haygain.de/pages/quiz, https://haygain.de/pages/optimieren-sie-das-wohlbefinden-ihres-pferdes, https://haygain.de/pages/studien-heubedampfung, https://haygain.de/pages/heu-einweichen-oder-bedampfen and https://haygain.de/pages/selbstgebaute-heubedampfer-warum-eigentlich-nicht and 6 others have 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 42 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
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”.
2 checks passed
Tap targets are thumb-sized
47 of 51 tappable elements near the top are at least 24 px.
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 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 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,820 words of copy
The homepage carries about 1,820 words of visible text.
3 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Klaviyo (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.
5 cookies set on arrival
5Opening the homepage sets 5 cookies, 1 of them by other companies (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.
29 other companies contacted
Loading the homepage contacts 29 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 haygain.nl, 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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Geolocation Flow · Eg Auto Add To Cart · Google Youtube · Klaviyo Email Marketing Sms · Gdpr Cookie Consent · Xapps Geo · Ez Terms And Conditions Checkbox · Revenuehunt · amazonaws.com · call-back.co
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
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on haygain.nl, including 15 speed issues, 5 SEO issues and 3 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.