Website review, no card needed

mutua.es logo

mutua.es website review

Visit site (opens in a new tab)Reviewed 24 October 202637 issues · 76 checks

This review found 37 issues worth fixing on mutua.es, 16 of them high impact, across 76 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
4.5 s4.1 sMay 2Oct 174.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.2 s
May 9, 20264.2 s
May 16, 20264.3 s
May 23, 20264.4 s
May 30, 20264.4 s
Jun 6, 20264.4 s
Jun 13, 20264.3 s
Jun 20, 20264.2 s
Jun 27, 20264.2 s
Jul 4, 20264.2 s
Jul 11, 20264.3 s
Jul 18, 20264.3 s
Jul 25, 20264.4 s
Aug 1, 20264.4 s
Aug 8, 20264.4 s
Aug 15, 20264.3 s
Aug 22, 20264.2 s
Aug 29, 20264.1 s
Sep 5, 20264.1 s
Sep 12, 20264.1 s
Sep 19, 20264.2 s
Sep 26, 20264.2 s
Oct 3, 20264.3 s
Oct 10, 20264.3 s
Oct 17, 20264.3 s
Real-visitor tap response (INP)75th percentile, phones
264 ms236 msMay 2Oct 17261 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026243 ms
May 9, 2026241 ms
May 16, 2026242 ms
May 23, 2026245 ms
May 30, 2026248 ms
Jun 6, 2026248 ms
Jun 13, 2026245 ms
Jun 20, 2026244 ms
Jun 27, 2026240 ms
Jul 4, 2026241 ms
Jul 11, 2026240 ms
Jul 18, 2026239 ms
Jul 25, 2026241 ms
Aug 1, 2026242 ms
Aug 8, 2026243 ms
Aug 15, 2026245 ms
Aug 22, 2026244 ms
Aug 29, 2026242 ms
Sep 5, 2026243 ms
Sep 12, 2026244 ms
Sep 19, 2026246 ms
Sep 26, 2026251 ms
Oct 3, 2026255 ms
Oct 10, 2026258 ms
Oct 17, 2026261 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

Full-page screenshot of mutua.es (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mutua.es at 0.4 s0.4 s
  2. mutua.es at 0.8 s0.8 s
  3. mutua.es at 1.1 s1.1 s
  4. mutua.es at 1.5 s1.5 s
  5. mutua.es at 1.9 s1.9 s
  6. mutua.es at 2.3 s2.3 s
  7. mutua.es at 2.6 s2.6 s
  8. mutua.es at 3.0 s3.0 s

Speed

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 618 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

    Your server sent the HTML in 1 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix0
  • 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 CLS: 0.32

    0.32

    For real visitors the layout shifts by 0.32 (75th percentile). Good is under 0.1.

  • Real-user LCP: 3.4 s

    3.4 s

    Real visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 256 ms

    256 ms

    Real visitors wait 256 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) held steady for real visitors

    +7%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 243 ms to 261 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-17, real Chrome visitors' largest content (lcp) went from 4.2 s to 4.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 671 ms

    671 ms

    Real visitors wait 671 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

100
  • 3 images in older formats

    3 images (161 KiB) 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.

  • 3 images below the first screen load straight away

    3 images further down the page (150 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.08 g of CO₂ per visit

    0.08 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.08 g of CO₂e: 9.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Page weight: 276 KiB in 7 requests

    276 KiB

    Your homepage downloads 276 KiB in 7 requests on a phone: scripts 260 KiB (2), HTML 11 KiB (2) and images 4 KiB (2). That is a lean page.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

17 to fixGoogle 4581
  • Certain ARIA roles must be contained by particular parents (4 elements)

    Certain ARIA roles must be contained by particular parents: 4 elements on the page fail this check, rated critical by axe-core.

  • 21 text elements with low contrast

    21 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Elements must only use permitted ARIA attributes (4 elements)

    Elements must only use permitted ARIA attributes: 4 elements on the page fail this check, rated serious by axe-core.

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • 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.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • 13 images without alt text

    13 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (62 elements)

    All page content should be contained by landmarks: 62 elements on the page fail this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Alternative text of images should not be repeated as text (19 elements)

    Alternative text of images should not be repeated as text: 19 elements on the page fail this check, rated minor by axe-core.

  • 5 form fields without a label

    5 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • 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 (h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 63 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 15 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 3664
  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Error status code

    The page answers with an error status, so search engines may drop it.

  • Title is long (73 characters)

    Your title is 73 characters, so Google will cut it off around 60: “Mutua Madrileña | Compañía de seguros de coche, moto, hogar, vida y salud”.

  • 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 X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 192 internal links, 31 external

    The homepage links to 192 pages on mutua.es and 31 external pages.

6 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Calcula el precio y contrata tu seguro de coche, moto, vida, hogar o salud ¡Vente a la Mutua Madrileña Automovilista y …”.

  • One H1 headline

    Your main headline reads: “Mutua Madrileña, Compañía Aseguradora nº 1”.

  • Canonical URL set

    The canonical URL is https://www.mutua.es/.

  • Structured data in place

    Structured data found: Organization.

  • 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.mutua.es/sitemap-indice.xml.

AI search readiness

100
4 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, sameAs (social profiles) and contact details; logo and description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (6,060 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.mutua.es/llms.txt (20 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix62
  • 13 pages without a title

    https://www.mutua.es/seguros-coche/calcular, https://www.mutua.es/seguros-coche/todo-riesgo, https://www.mutua.es/seguros-coche/terceros, https://www.mutua.es/seguros-coche/coche-clasico, https://www.mutua.es/seguros-coche/vehiculo-electrico and https://www.mutua.es/seguros-coche/servicios-coberturas and 7 others have no <title>, so Google invents the link text in results.

  • 13 linked pages hidden from search

    https://www.mutua.es/seguros-coche/calcular, https://www.mutua.es/seguros-coche/todo-riesgo, https://www.mutua.es/seguros-coche/terceros, https://www.mutua.es/seguros-coche/coche-clasico, https://www.mutua.es/seguros-coche/vehiculo-electrico and https://www.mutua.es/seguros-coche/servicios-coberturas and 7 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 13 pages without a meta description

    https://www.mutua.es/seguros-coche/calcular, https://www.mutua.es/seguros-coche/todo-riesgo, https://www.mutua.es/seguros-coche/terceros, https://www.mutua.es/seguros-coche/coche-clasico, https://www.mutua.es/seguros-coche/vehiculo-electrico and https://www.mutua.es/seguros-coche/servicios-coberturas and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.mutua.es/seguros-coche/calcular and https://www.mutua.es/seguros-moto/calcular have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.mutua.es/seguros-moto/todo-riesgo took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 114 found) and read each the way a search engine does.

2 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.

Best practices

3 to fixGoogle 8871
  • 2 broken images

    2 images failed to load on a phone, for example https://www.mutua.es/.

  • 7 small tap targets

    7 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • A 11-field form

    Your longest form asks for 11 fields (1 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 833 words of copy

    The homepage carries about 833 words of visible text.

2 checks passed
  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, 1 customer or partner logo and 2 trust badges.

  • Direct contact links

    Visitors can reach you directly: 6 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before 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.

  • 29 cookies set on arrival

    29

    Opening the homepage sets 29 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.

  • 7 other companies contacted

    Loading the homepage contacts 7 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 mutua.es, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery

Company

Founded
1930
Headquarters
La Unión y el Fénix building, Madrid

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on mutua.es, including 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25