Website review, no card needed
orchid.eu website review
Visit site (opens in a new tab)Reviewed 22 October 202628 issues · 73 checks
This review found 28 issues worth fixing on orchid.eu, 9 of them high impact, across 73 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
73CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
2.5 s30 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Mobile performance score: 73
73/100Your mobile performance score is 73 (desktop: 76). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
540 ms · 94 KiBAbout 94 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 540 ms faster on a phone.
Improve image delivery
450 ms · 41 KiB1 image could be 41 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.
2 third-party services on the page
2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 178 KiB and 179 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 45 KiB74 files are served with short cache lifetimes, so returning visitors download them again (45 KiB).
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 119 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.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 661 ms of it running JavaScript. That is comfortably low.
Server response: 140 ms
140 msYour server sent the HTML in 140 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 10.7 s
10.7 sVisually, the page fills in at 10.7 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.7 s
4.7 sYour largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your natural choice”. Most of its time is element render delay (7.5 s).
Time to Interactive: 4.8 s
4.8 sThe page becomes fully interactive after 4.8 s. Good is under 3.8 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 114 ms
114 msScripts block the page for only 114 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
Page weight: 10.1 MB in 77 requests
10.1 MBYour homepage downloads 10.1 MB in 77 requests on a phone: media 9.4 MB (1), scripts 348 KiB (27) and images 209 KiB (17). Under 2 MB keeps phones on slow connections fast.
About 2.8 g of CO₂ per visit
2.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.85 g of CO₂e: 341.9 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
12 tap targets too small
12 tap targets are too small or too close together to hit reliably with a finger.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3 and h1 → h3), 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. (3 elements).
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Page is set to noindex
The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is short (28 characters)
Your title is only 28 characters: “Orchid – Your natural choice”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
8 H1 headlines
There are 8 <h1> headlines (“Your natural choice”, “Orchid Team @ Wind Energy Hamburg 2026” and “🌬️ Europe is having its best wind year yet – and…”). One clear main headline is easier for people and search engines.
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://orchid.eu/sitemap.xml, so Google discovers your pages only by following links.
9 links with vague text
9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
93 internal links, 8 external
The homepage links to 93 pages on orchid.eu and 8 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://orchid.eu/.
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.
No llms.txt
There is no https://orchid.eu/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.
2 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 (724 words), so crawlers that don't run JavaScript still read it.
Other pages
15 linked pages hidden from search
https://orchid.eu/wind, https://orchid.eu/pv, https://orchid.eu/civil-works, https://orchid.eu/about-us, https://orchid.eu/sustainability and https://orchid.eu/career and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
15 pages without a meta description
https://orchid.eu/wind, https://orchid.eu/pv, https://orchid.eu/civil-works, https://orchid.eu/about-us, https://orchid.eu/sustainability and https://orchid.eu/career and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
12 pages slow to respond
https://orchid.eu/pv, https://orchid.eu/civil-works, https://orchid.eu/about-us, https://orchid.eu/sustainability, https://orchid.eu/career and https://orchid.eu/orchid-team-wind-energy-hamburg-2026 and 6 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 21 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.
Every page has an H1
Each page we checked has a main headline.
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
20 of 21 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.
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 277 words of copy
The homepage carries about 277 words of visible text.
3 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Contact us”.
Analytics in place
Analytics detected: Google Analytics.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and 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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
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.
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 orchid.eu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on orchid.eu, including 7 speed issues, 9 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.