Website review, no card needed
scsalud.es website review
Visit site (opens in a new tab)Reviewed 19 November 202644 issues · 82 checks
This review found 44 issues worth fixing on scsalud.es, 14 of them high impact, across 82 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
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.6 s |
| Oct 31, 2026 | 2.6 s |
| Nov 7, 2026 | 2.6 s |
| Nov 14, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 138 ms |
| Jun 6, 2026 | 139 ms |
| Jun 13, 2026 | 136 ms |
| Jun 20, 2026 | 136 ms |
| Jun 27, 2026 | 136 ms |
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 138 ms |
| Jul 18, 2026 | 138 ms |
| Jul 25, 2026 | 137 ms |
| Aug 1, 2026 | 137 ms |
| Aug 8, 2026 | 137 ms |
| Aug 15, 2026 | 138 ms |
| Aug 22, 2026 | 132 ms |
| Aug 29, 2026 | 129 ms |
| Sep 5, 2026 | 128 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 130 ms |
| Sep 26, 2026 | 135 ms |
| Oct 3, 2026 | 138 ms |
| Oct 10, 2026 | 146 ms |
| Oct 17, 2026 | 155 ms |
| Oct 24, 2026 | 156 ms |
| Oct 31, 2026 | 156 ms |
| Nov 7, 2026 | 152 ms |
| Nov 14, 2026 | 150 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.9 s · 809 KiBAbout 809 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Render-blocking requests
1.8 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Improve image delivery
600 ms · 12.0 MB15 images could be 12.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Minify JavaScript
900 ms · 269 KiB269 KiB could be saved by minifying JavaScript.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
450 ms · 98 KiBAbout 98 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.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
2,921 HTML elements
The page has 2,921 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, jQuery CDN and mPulse and others), adding 448 KiB and 270 ms of main-thread time.
Minify CSS
150 ms · 20 KiB20 KiB could be saved by minifying CSS.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 75 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
6 KiB1 file is served with short cache lifetimes, so returning visitors download them again (6 KiB).
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.
Duplicated JavaScript
2 KiB2 KiB JavaScript is shipped twice across bundles.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 473 ms of it running JavaScript. That is comfortably low.
Server response: 18 ms
18 msYour server sent the HTML in 18 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.
Time to Interactive: 43.0 s
43.0 sThe page becomes fully interactive after 43.0 s. Good is under 3.8 s.
Largest Contentful Paint: 7.6 s
7.6 sYour largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load duration (3.1 s).
Speed Index: 10.4 s
10.4 sVisually, the page fills in at 10.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Largest content (LCP) got 39% slower for real visitors
+39%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 838 ms
838 msReal visitors wait 838 ms for your server to start answering (75th percentile). Good is under 800 ms.
17 images without width and height
17 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.113
0.113The layout shifts by 0.113 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 138 ms to 150 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 148 ms
148 msReal visitors wait 148 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 29 ms
29 msScripts block the page for only 29 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 14.1 MB in 142 requests
14.1 MBYour homepage downloads 14.1 MB in 142 requests on a phone: images 12.7 MB (34), scripts 1.1 MB (73) and fonts 179 KiB (3). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 11.7 MB together. On a phone connection a single image that size takes seconds.
7 images far larger than shown
8.3 MB7 images are downloaded at several times the size a phone draws them, for example 3696b059-1812-a093-2a68-690b984a2a7b at 3,276 px wide, shown at 286 px. Resized copies would save about 8.3 MB.
17 images in older formats
17 images (12.5 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.
12 images below the first screen load straight away
12 images further down the page (6.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.0 g of CO₂ per visit
4.01 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.01 g of CO₂e: 481.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Form elements should have a visible label (1 element)
Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 54 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (15 characters)
Your title is only 15 characters: “Salud Cantabria”. 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.
Meta description is short (15 characters)
Your meta description is only 15 characters: “Salud Cantabria”. 70 to 160 characters is enough to sell the click.
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://saludcantabria.com:443/sitemap.xml, so Google discovers your pages only by following links.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
670 internal links, 63 external
The homepage links to 670 pages on scsalud.es and 63 external pages.
3 checks passed
One H1 headline
Your main headline reads: “Configuración de Cookies”.
Canonical URL set
The canonical URL is https://www.scsalud.es/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
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.scsalud.es/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 (3,720 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://www.scsalud.es/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
6 pages share 3 titles
/ and https://www.scsalud.es/home all use the title “Salud Cantabria”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
12 pages without a meta description
https://www.scsalud.es/noticias, https://www.scsalud.es/contactar_scs, https://www.scsalud.es/consultas-y-gestiones, https://www.scsalud.es/buscador-avanzado, https://www.scsalud.es/consejeria-y-scs and https://www.scsalud.es/consejeria and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.scsalud.es/contactar_consejeria and https://www.scsalud.es/web/guest/contactar_consejeria use the same meta description. A description written for each page earns more clicks.
2 pages slow to respond
https://www.scsalud.es/buscador-avanzado and https://www.scsalud.es/scs took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 200 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 15 pages that loaded have a <title>.
Best practices
8 small tap targets
8 of 26 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
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: 11 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 558 words of copy
The homepage carries about 558 words of visible text.
3 checks passed
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 4 phone links and 3 email links.
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.
8 cookies set on arrival
8Opening the homepage sets 8 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 scsalud.es, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on scsalud.es, including 20 speed issues, 6 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.