Website review, no card needed
hygeia.gr website review
Visit site (opens in a new tab)Reviewed 2 November 202644 issues · 89 checks
This review found 44 issues worth fixing on hygeia.gr, 14 of them high impact, across 89 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 109 ms |
| May 23, 2026 | 108 ms |
| May 30, 2026 | 108 ms |
| Jun 6, 2026 | 108 ms |
| Jun 13, 2026 | 108 ms |
| Jun 20, 2026 | 108 ms |
| Jun 27, 2026 | 108 ms |
| Jul 4, 2026 | 107 ms |
| Jul 11, 2026 | 107 ms |
| Jul 18, 2026 | 107 ms |
| Jul 25, 2026 | 106 ms |
| Aug 1, 2026 | 107 ms |
| Aug 8, 2026 | 107 ms |
| Aug 15, 2026 | 106 ms |
| Aug 22, 2026 | 107 ms |
| Aug 29, 2026 | 107 ms |
| Sep 5, 2026 | 107 ms |
| Sep 12, 2026 | 108 ms |
| Sep 19, 2026 | 107 ms |
| Sep 26, 2026 | 107 ms |
| Oct 3, 2026 | 106 ms |
| Oct 10, 2026 | 106 ms |
| Oct 17, 2026 | 106 ms |
| Oct 24, 2026 | 105 ms |
| Oct 31, 2026 | 105 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
3.3 s46 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
250 ms · 946 KiB31 images could be 946 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Facebook and WordPress Site Stats and others), adding 354 KiB and 652 ms of main-thread time.
Google Tag Manager adds 528 ms
528 msGoogle Tag Manager costs a phone 528 ms of main-thread work and 191 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.
Reduce unused JavaScript
300 ms · 103 KiBAbout 103 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 398 ms. During a long task the page ignores taps.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,103 HTML elements
The page has 2,103 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 37 KiBAbout 37 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.
Use efficient cache lifetimes
136 KiB3 files are served with short cache lifetimes, so returning visitors download them again (136 KiB).
Legacy JavaScript
35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need.
Minify CSS
9 KiB9 KiB could be saved by minifying CSS.
Minify JavaScript
7 KiB7 KiB could be saved by minifying JavaScript.
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: 234 ms
234 msYour server sent the HTML in 234 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: 16.4 s
16.4 sYour largest element takes 16.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 17.0 s
17.0 sThe page becomes fully interactive after 17.0 s. Good is under 3.8 s.
Speed Index: 8.1 s
8.1 sVisually, the page fills in at 8.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 855 ms
855 msScripts block taps and scrolling for 855 ms in total while the page loads. Good is under 200 ms.
Real-user TTFB: 883 ms
883 msReal visitors wait 883 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
15 images without width and height
15 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 109 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 111 ms
111 msReal visitors wait 111 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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.026
0.026The layout barely moves while loading (CLS 0.026, good is under 0.1).
Images and page weight
Page weight: 4.4 MB in 149 requests
4.4 MBYour homepage downloads 4.4 MB in 149 requests on a phone: images 3.1 MB (85), fonts 674 KiB (4) and scripts 512 KiB (33). Under 2 MB keeps phones on slow connections fast.
24 images in older formats
24 images (2.2 MB) 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 far larger than shown
93 KiB1 image is downloaded at several times the size a phone draws it, for example Best-Workplaces-Greece.png at 4,807 px wide, shown at 111 px. Resized copies would save about 93 KiB.
5 images below the first screen load straight away
5 images further down the page (214 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.3 g of CO₂ per visit
1.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.26 g of CO₂e: 150.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (29 elements)
All page content should be contained by landmarks: 29 elements on the page fail this check, rated moderate by axe-core.
12 form fields without a label
12 form fields have no label, so screen readers announce an empty box and autofill guesses.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (2 elements)
Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 96 images in the HTML carry an alt attribute.
42 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: 42 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
18 H1 headlines
There are 18 <h1> headlines (“PET / CT”, “Πακέτα Παιδιατρικού Ελέγχου” and “Αξονική - Μαγνητική Τομογραφία”). One clear main headline is easier for people and search engines.
25 links crawlers can't follow
25 links have no real href, so search engines can't follow them.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
425 internal links, 39 external
The homepage links to 425 pages on hygeia.gr and 39 external pages.
6 checks passed
Meta description: 137 characters
Your meta description is 137 characters: “Στα 50 χρόνια λειτουργίας του, το ΥΓΕΙΑ συνεχίζει να πρωτοπορεί, θέτοντας όλο και πιο ψηλά τον πήχη της ιδιωτικής περίθ…”.
Title: 44 characters
Your title is a healthy 44 characters: “Η επίσημη ιστοσελίδα του νοσοκομείου "ΥΓΕΙΑ"”.
Canonical URL set
The canonical URL is https://www.hygeia.gr/.
Structured data in place
Structured data found: BreadcrumbList, WebPage 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://www.hygeia.gr/sitemap.xml.
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://www.hygeia.gr/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
13 pages without a meta description
https://www.hygeia.gr/orama-kai-apostoli, https://www.hygeia.gr/hygeia/istoriki-anadromi, https://www.hygeia.gr/hygeia/50-chronia-ygeia, https://www.hygeia.gr/organotiki-domi, https://www.hygeia.gr/hygeia/deltia-typou and https://www.hygeia.gr/hygeia/etaitiki-koinoniki-eythyni and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.hygeia.gr/virtual and https://www.hygeia.gr/virtual-maieutiki use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://www.hygeia.gr/virtual and https://www.hygeia.gr/virtual-maieutiki have no <h1> headline, so visitors and search engines get no clear main topic.
10 pages with very little text
https://www.hygeia.gr/virtual, https://www.hygeia.gr/virtual-maieutiki, https://www.hygeia.gr/orama-kai-apostoli, https://www.hygeia.gr/hygeia/50-chronia-ygeia, https://www.hygeia.gr/organotiki-domi and https://www.hygeia.gr/hygeia/etaitiki-koinoniki-eythyni and 4 others 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 140 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.
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
33 small tap targets
33 of 86 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
A 11-field form
Your longest form asks for 11 fields (5 required). Every extra field lowers completion.
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 94 words
The homepage has only about 94 words of visible text; thin pages give Google and first-time buyers little to go on.
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
Social proof on the page
Social proof on the homepage: 6 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 (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.
10 other companies contacted
Loading the homepage contacts 10 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 hygeia.gr, 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
- Hosting
- Hetzner
Company
- Founded
- 1970
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on hygeia.gr, including 18 speed issues, 3 SEO issues and 5 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.