Website review, no card needed
hanseyachtsag.com website review
Visit site (opens in a new tab)Reviewed 26 October 202633 issues · 74 checks
This review found 33 issues worth fixing on hanseyachtsag.com, 14 of them high impact, across 74 checks. The most urgent: improve image delivery. 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 8.9 s |
| May 16, 2026 | 8.9 s |
| May 23, 2026 | 8.9 s |
| May 30, 2026 | 9.0 s |
| Jun 6, 2026 | 9.0 s |
| Jun 13, 2026 | 8.9 s |
| Jun 20, 2026 | 8.9 s |
| Jun 27, 2026 | 8.9 s |
| Jul 4, 2026 | 8.9 s |
| Jul 11, 2026 | 8.9 s |
| Jul 18, 2026 | 9.0 s |
| Jul 25, 2026 | 8.9 s |
| Aug 1, 2026 | 8.9 s |
| Aug 8, 2026 | 8.9 s |
| Aug 15, 2026 | 8.9 s |
| Aug 22, 2026 | 8.8 s |
| Aug 29, 2026 | 8.7 s |
| Sep 5, 2026 | 8.8 s |
| Sep 12, 2026 | 8.9 s |
| Sep 19, 2026 | 8.9 s |
| Sep 26, 2026 | 9.0 s |
| Oct 3, 2026 | 9.0 s |
| Oct 10, 2026 | 8.8 s |
| Oct 17, 2026 | 8.2 s |
| Oct 24, 2026 | 7.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 140 ms |
| May 16, 2026 | 152 ms |
| May 23, 2026 | 152 ms |
| May 30, 2026 | 141 ms |
| Jun 6, 2026 | 150 ms |
| Jun 13, 2026 | 151 ms |
| Jun 20, 2026 | 152 ms |
| Jun 27, 2026 | 162 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 151 ms |
| Jul 18, 2026 | 151 ms |
| Jul 25, 2026 | 161 ms |
| Aug 1, 2026 | 141 ms |
| Aug 8, 2026 | 141 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 131 ms |
| Aug 29, 2026 | 141 ms |
| Sep 5, 2026 | 137 ms |
| Sep 12, 2026 | 136 ms |
| Sep 19, 2026 | 138 ms |
| Sep 26, 2026 | 137 ms |
| Oct 3, 2026 | 138 ms |
| Oct 10, 2026 | 153 ms |
| Oct 17, 2026 | 136 ms |
| Oct 24, 2026 | 133 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
How it loaded on a phone
2.4 s
4.8 s
7.2 s
9.6 s
12.0 s
14.3 s
16.7 s
19.1 s
Speed
Improve image delivery
6.0 s · 8.5 MB11 images could be 8.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.0 s faster on a phone.
Reduce unused JavaScript
1.5 s · 397 KiBAbout 397 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Document request latency
1.9 sThe HTML itself could arrive about 1.9 s sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
1.9 sReduce initial server response time. Google estimates savings of 1.9 s on a phone.
Server response: 2.0 s
2.0 sYour server takes 2.0 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
5 third-party services on the page
5 third-party services load with your homepage (Usercentrics CMP, JSDelivr CDN and b-cdn.net and others), adding 11.9 MB and 227 ms of main-thread time.
b-cdn.net adds 1 ms
1 msb-cdn.net costs a phone 1 ms of main-thread work and 11.5 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.
Mobile performance score: 57
57/100Your mobile performance score is 57 (desktop: 69). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
300 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 206 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 51 KiBAbout 51 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 11 KiB6 files are served with short cache lifetimes, so returning visitors download them again (11 KiB).
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.
Real-user LCP: 7.8 s
7.8 sReal visitors wait 7.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 7.3 s
7.3 sReal visitors see the first content after 7.3 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 17.7 s
17.7 sYour largest element takes 17.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 20.2 s
20.2 sVisually, the page fills in at 20.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 19.3 s
19.3 sThe page becomes fully interactive after 19.3 s. Good is under 3.8 s.
Total Blocking Time: 322 ms
322 msScripts block taps and scrolling for 322 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 140 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 133 ms
133 msReal visitors wait 133 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 TTFB: 485 ms
485 msReal visitors wait 485 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 8.9 s to 7.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 14.0 MB in 102 requests
14.0 MBYour homepage downloads 14.0 MB in 102 requests on a phone: images 12.2 MB (28), scripts 982 KiB (32) and other files 769 KiB (28). Under 2 MB keeps phones on slow connections fast.
About 4.0 g of CO₂ per visit
3.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.97 g of CO₂e: 476.8 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (4 elements).
1 checks passed
Every image has alt text
All 23 images in the HTML carry an alt attribute.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://hanseyachtsag.com/sitemap.xml, so Google discovers your pages only by following links.
37 internal links, 15 external
The homepage links to 37 pages on hanseyachtsag.com and 15 external pages.
5 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Germany's largest manufacturer of sailing yachts & motor yachts. Design ✓ Performance ✓ Seaworthiness ✓ Handling ✓ Now …”.
One H1 headline
Your main headline reads: “HanseYachts AG”.
Title: 59 characters
Your title is a healthy 59 characters: “Yachts for Sale, New Motor & Sailing Boats | HanseYachts AG”.
Canonical URL set
The canonical URL is https://hanseyachtsag.com/corporate/gb/.
robots.txt in place
robots.txt is in place.
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
42%The HTML your server sends has 333 of the 795 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
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://hanseyachtsag.com/gb and https://hanseyachtsag.com/us all use the title “Yachts for Sale, New Motor & Sailing Boats | HanseYachts AG”. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages without a meta description
https://hanseyachtsag.com/gb/company, https://hanseyachtsag.com/gb/delisting, https://hanseyachtsag.com/gb/articles-of-association, https://hanseyachtsag.com/gb/annual-meeting, https://hanseyachtsag.com/gb/ad-hoc-messages and https://hanseyachtsag.com/gb/financial-reports and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
14 links to non-canonical URLs
Your homepage links to 14 pages by a URL that isn't their canonical one, for example https://hanseyachtsag.com/us, whose canonical is https://hanseyachtsag.com/corporate/us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages with very little text
https://hanseyachtsag.com/gb/articles-of-association and https://hanseyachtsag.com/gb/ad-hoc-messages have 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 25 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 14 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Minified React error #418; visit https://react.dev/errors/418?args[]= for the full message or use the non-minified dev …”.
2 checks passed
Tap targets are thumb-sized
11 of 13 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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 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.
About 795 words of copy
The homepage carries about 795 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact us”.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks and “36 + Satisfied customers”.
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). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
8 other companies contacted
Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) 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 hanseyachtsag.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Hosting
- Vercel
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on hanseyachtsag.com, including 17 speed issues, 3 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.