Website review, no card needed
atryshealth.com website review
Visit site (opens in a new tab)Reviewed 19 November 202646 issues · 87 checks
This review found 46 issues worth fixing on atryshealth.com, 19 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 4.4 s |
| Jun 6, 2026 | 4.4 s |
| Jun 13, 2026 | 4.2 s |
| Jun 20, 2026 | 4.1 s |
| Jun 27, 2026 | 4.3 s |
| Jul 4, 2026 | 4.4 s |
| Jul 11, 2026 | 4.4 s |
| Jul 18, 2026 | 4.5 s |
| Jul 25, 2026 | 4.3 s |
| Aug 1, 2026 | 4.3 s |
| Aug 8, 2026 | 4.5 s |
| Aug 15, 2026 | 4.6 s |
| Aug 22, 2026 | 4.8 s |
| Aug 29, 2026 | 4.7 s |
| Sep 5, 2026 | 4.5 s |
| Sep 12, 2026 | 4.5 s |
| Sep 19, 2026 | 4.5 s |
| Sep 26, 2026 | 4.5 s |
| Oct 3, 2026 | 4.5 s |
| Oct 10, 2026 | 4.4 s |
| Oct 17, 2026 | 4.4 s |
| Oct 24, 2026 | 4.6 s |
| Oct 31, 2026 | 4.7 s |
| Nov 7, 2026 | 4.8 s |
| Nov 14, 2026 | 5.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 117 ms |
| Jun 13, 2026 | 120 ms |
| Jun 20, 2026 | 119 ms |
| Jun 27, 2026 | 114 ms |
| Jul 4, 2026 | 111 ms |
| Jul 11, 2026 | 111 ms |
| Jul 18, 2026 | 118 ms |
| Jul 25, 2026 | 119 ms |
| Aug 1, 2026 | 129 ms |
| Aug 8, 2026 | 120 ms |
| Aug 15, 2026 | 116 ms |
| Aug 22, 2026 | 111 ms |
| Aug 29, 2026 | 106 ms |
| Sep 5, 2026 | 107 ms |
| Sep 12, 2026 | 105 ms |
| Sep 19, 2026 | 105 ms |
| Sep 26, 2026 | 97 ms |
| Oct 3, 2026 | 91 ms |
| Oct 10, 2026 | 96 ms |
| Oct 17, 2026 | 96 ms |
| Oct 24, 2026 | 97 ms |
| Oct 31, 2026 | 102 ms |
| Nov 7, 2026 | 98 ms |
| Nov 14, 2026 | 104 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
1.4 s
2.7 s
4.1 s
5.5 s
6.9 s
8.2 s
9.6 s
11.0 s
Speed
Use efficient cache lifetimes
3.8 s · 3.4 MB39 files are served with short cache lifetimes, so returning visitors download them again (3.4 MB).
Reduce unused JavaScript
3.8 s · 1.9 MBAbout 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.
Render-blocking requests
3.6 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.6 s.
Reduce unused CSS
2.1 s · 410 KiBAbout 410 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Main-thread work: 5.7 s
A phone's processor spends 5.7 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
250 ms · 624 KiB8 images could be 624 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.
Minify JavaScript
658 KiB658 KiB could be saved by minifying JavaScript.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and Cloudflare CDN and others), adding 1.3 MB and 521 ms of main-thread time.
YouTube adds 387 ms
387 msYouTube costs a phone 387 ms of main-thread work and 1,012 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 CSS
150 ms · 7 KiB7 KiB could be saved by minifying CSS.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 137 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.
1 checks passed
Server response: 130 ms
130 msYour server sent the HTML in 130 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: 6.8 s
6.8 sReal visitors wait 6.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.9 s
4.9 sReal visitors see the first content after 4.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.0 s
3.0 sReal visitors wait 3.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 16.3 s
16.3 sYour largest element takes 16.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Previous Medicina de precisión para las personas. Más cuida…”.
Speed Index: 17.0 s
17.0 sVisually, the page fills in at 17.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 36.9 s
36.9 sThe page becomes fully interactive after 36.9 s. Good is under 3.8 s.
First Contentful Paint: 5.5 s
5.5 sThe first text or image appears after 5.5 s on a phone. Good is under 1.8 s.
Real-user CLS: 0.15
0.15For real visitors the layout shifts by 0.15 (75th percentile). Good is under 0.1.
18 images without width and height
18 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.123
0.123The layout shifts by 0.123 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.4 s to 5.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 91 ms
91 msReal visitors wait 91 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 120 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 124 ms
124 msScripts block the page for only 124 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 29.2 MB in 68 requests
29.2 MBYour homepage downloads 29.2 MB in 68 requests on a phone: media 18.1 MB (1), images 7.7 MB (25) and scripts 2.9 MB (19). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 6.1 MB together. On a phone connection a single image that size takes seconds.
6 images in older formats
6 images (1.1 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.
2 images far larger than shown
181 KiB2 images are downloaded at several times the size a phone draws them, for example junta-extraordinaria-2026-1920-x-1080-px.png at 1,920 px wide, shown at 350 px. Resized copies would save about 181 KiB.
3 images below the first screen load straight away
3 images further down the page (273 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 8.3 g of CO₂ per visit
8.28 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.28 g of CO₂e: 993.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
17 images without alt text
17 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (15 elements)
All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 failed. 2 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: “Home - Atrys Health”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (229 characters)
Your meta description is 229 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
One H1 headline
Your <h1> is empty.
73 internal links, 19 external
The homepage links to 73 pages on atryshealth.com and 19 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.atryshealth.com/es/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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.atryshealth.com/es/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.atryshealth.com/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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (421 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.atryshealth.com/es and https://www.atryshealth.com/en all use the title “Home - Atrys Health”. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages share a meta description
https://www.atryshealth.com/en, https://www.atryshealth.com/es/atrys, https://www.atryshealth.com/es/areas-de-negocio, https://www.atryshealth.com/es/id, https://www.atryshealth.com/es/informacion-para-los-inversores and https://www.atryshealth.com/es/compliance and 8 others use the same meta description. A description written for each page earns more clicks.
1 page with very little text
https://www.atryshealth.com/es/dejanos-tu-cv has 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 pages slow to respond
https://www.atryshealth.com/en, https://www.atryshealth.com/es/atrys, https://www.atryshealth.com/es/areas-de-negocio, https://www.atryshealth.com/es/id, https://www.atryshealth.com/es/informacion-para-los-inversores and https://www.atryshealth.com/es/compliance and 9 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 35 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
33 small tap targets
33 of 49 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
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.
Thin social proof
Social proof on the homepage: 3 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 389 words of copy
The homepage carries about 389 words of visible text.
2 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, 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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
13 other companies contacted
Loading the homepage contacts 13 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 atryshealth.com, 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
- Headquarters
- Madrid
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on atryshealth.com, including 21 speed issues, 4 SEO issues and 4 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.