Website review, no card needed
eugin.es website review
Visit site (opens in a new tab)Reviewed 4 November 202645 issues · 94 checks
This review found 45 issues worth fixing on eugin.es, 16 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.6 s |
| May 23, 2026 | 3.7 s |
| May 30, 2026 | 3.9 s |
| Jun 6, 2026 | 4.1 s |
| Jun 13, 2026 | 4.3 s |
| Jun 20, 2026 | 4.4 s |
| Jun 27, 2026 | 4.2 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.0 s |
| Jul 18, 2026 | 3.8 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.6 s |
| Sep 12, 2026 | 3.6 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.5 s |
| Oct 31, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 114 ms |
| May 23, 2026 | 119 ms |
| May 30, 2026 | 125 ms |
| Jun 6, 2026 | 132 ms |
| Jun 13, 2026 | 140 ms |
| Jun 20, 2026 | 143 ms |
| Jun 27, 2026 | 143 ms |
| Jul 4, 2026 | 143 ms |
| Jul 11, 2026 | 142 ms |
| Jul 18, 2026 | 139 ms |
| Jul 25, 2026 | 136 ms |
| Aug 1, 2026 | 133 ms |
| Aug 8, 2026 | 129 ms |
| Aug 15, 2026 | 128 ms |
| Aug 22, 2026 | 128 ms |
| Aug 29, 2026 | 129 ms |
| Sep 5, 2026 | 129 ms |
| Sep 12, 2026 | 128 ms |
| Sep 19, 2026 | 129 ms |
| Sep 26, 2026 | 130 ms |
| Oct 3, 2026 | 132 ms |
| Oct 10, 2026 | 134 ms |
| Oct 17, 2026 | 135 ms |
| Oct 24, 2026 | 135 ms |
| Oct 31, 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
Speed
Reduce unused JavaScript
1.8 s · 711 KiBAbout 711 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Render-blocking requests
2.3 s25 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Use efficient cache lifetimes
700 ms · 1.4 MB120 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, trengo.eu and Hubspot and others), adding 1.4 MB and 956 ms of main-thread time.
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
450 ms · 230 KiBAbout 230 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 426 ms
426 msGoogle Tag Manager costs a phone 426 ms of main-thread work and 535 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.
Minify JavaScript
300 ms · 44 KiB44 KiB could be saved by minifying JavaScript.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
trengo.eu adds 255 ms
255 mstrengo.eu costs a phone 255 ms of main-thread work and 417 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.
2,531 HTML elements
The page has 2,531 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
150 ms · 130 KiB4 images could be 130 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 204 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Minify CSS
30 KiB30 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: 157 ms
157 msYour server sent the HTML in 157 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.
Real-user LCP: 4.2 s
4.2 sReal visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 2.4 s
2.4 sReal visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 10.5 s
10.5 sYour largest element takes 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (4.7 s).
Speed Index: 11.8 s
11.8 sVisually, the page fills in at 11.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 17.0 s
17.0 sThe page becomes fully interactive after 17.0 s. Good is under 3.8 s.
Real-user FCP: 3.0 s
3.0 sReal visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 420 ms
420 msScripts block taps and scrolling for 420 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 114 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.6 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 124 ms
124 msReal visitors wait 124 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.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.9 MB in 163 requests
7.9 MBYour homepage downloads 7.9 MB in 163 requests on a phone: images 5.4 MB (26), scripts 1.9 MB (85) and fonts 231 KiB (10). Under 2 MB keeps phones on slow connections fast.
About 2.2 g of CO₂ per visit
2.23 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.23 g of CO₂e: 267.2 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
1 dropdown has no label.
34 text elements with low contrast
34 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
19 images without alt text
19 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
9 form fields without a label
9 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h5), 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 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 11 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Sueñoscompartidos,familias únicas” and “Sueñoscompartidos,familias únicas”). One clear main headline is easier for people and search engines.
Structured data has 2 problems
Structured data found (ImageObject, MedicalClinic, MedicalOrganization and Organization) but with 2 problems, for example “MedicalClinic: logo is not an absolute URL ("https://www.eugin.es/wp-content/uploads/2019/09/Logo-Eugin.png")”.
5 links crawlers can't follow
5 links have no real href, so search engines can't follow them.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
132 internal links, 38 external
The homepage links to 132 pages on eugin.es and 38 external pages.
6 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Eugin es especialista en tratamientos de reproducción asistida como IAD, FIV y ovodonación con prediagnóstico online y …”.
Title: 49 characters
Your title is a healthy 49 characters: “Clínica Eugin: Reproducción asistida y fertilidad”.
Canonical URL set
The canonical URL is https://www.eugin.es/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.eugin.es/sitemap_index.xml.
AI search readiness
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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,720 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
/ and https://www.eugin.es/area-privada-2025 all use the title “Clínica Eugin: Reproducción asistida y fertilidad”. Search engines can't tell which page to show for a search, so each competes with the others.
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.eugin.es/area-privada-2025, whose canonical is https://www.eugin.es/area-privada. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
14 pages without an H1
https://www.eugin.es/area-privada-2025, https://www.eugin.es/conoce-eugin, https://www.eugin.es/conoce-eugin/nuestro-equipo, https://www.eugin.es/conoce-eugin/clinicas-de-reproduccion-asistida-centros, https://www.eugin.es/conoce-eugin/responsabilidad-social-corporativa and https://www.eugin.es/conoce-eugin/calidad and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://www.eugin.es/area-privada-2025, https://www.eugin.es/conoce-eugin/calidad, https://www.eugin.es/fecundacion-in-vitro/ovulos-propios-semen-donante and https://www.eugin.es/preservacion-fertilidad took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 40 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 a meta description
All 15 pages that loaded have a meta description.
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
9 small tap targets
9 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.eugin.es/wp-content/plugins/revslider/public/assets/css/rs6.css?ver=7.1.4' bec…”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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 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 13-field form
Your longest form asks for 13 fields (11 required). Every extra field lowers completion.
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,469 words of copy
The homepage carries about 1,469 words of visible text.
6 checks passed
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and 4 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 6 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Taboola (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
8 cookies set on arrival
8Opening the homepage sets 8 cookies (measured from a US location before any click).
26 other companies contacted
Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 eugin.es, 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 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 45 issues on eugin.es, including 21 speed issues, 4 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.