Website review, no card needed

emtmadrid.es logo

emtmadrid.es website review

Visit site (opens in a new tab)Reviewed 26 October 202640 issues · 57 checks

This review found 40 issues worth fixing on emtmadrid.es, 15 of them high impact, across 57 checks. The most urgent: avoid multiple page redirects. 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

Real-visitor load time (LCP)75th percentile, phones
1.1 s901 msMay 9Oct 241.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.0 s
May 16, 2026987 ms
May 23, 2026990 ms
May 30, 20261.0 s
Jun 6, 2026988 ms
Jun 13, 20261.0 s
Jun 20, 2026989 ms
Jun 27, 2026982 ms
Jul 4, 2026994 ms
Jul 11, 2026958 ms
Jul 18, 2026952 ms
Jul 25, 2026943 ms
Aug 1, 2026920 ms
Aug 8, 2026933 ms
Aug 15, 2026936 ms
Aug 22, 2026944 ms
Aug 29, 2026957 ms
Sep 5, 2026976 ms
Sep 12, 2026990 ms
Sep 19, 2026979 ms
Sep 26, 20261.0 s
Oct 3, 20261.0 s
Oct 10, 20261.0 s
Oct 17, 20261.0 s
Oct 24, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
291 ms266 msMay 9Oct 24274 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026283 ms
May 16, 2026281 ms
May 23, 2026288 ms
May 30, 2026285 ms
Jun 6, 2026279 ms
Jun 13, 2026277 ms
Jun 20, 2026277 ms
Jun 27, 2026281 ms
Jul 4, 2026284 ms
Jul 11, 2026284 ms
Jul 18, 2026284 ms
Jul 25, 2026277 ms
Aug 1, 2026277 ms
Aug 8, 2026277 ms
Aug 15, 2026276 ms
Aug 22, 2026274 ms
Aug 29, 2026272 ms
Sep 12, 2026270 ms
Sep 19, 2026269 ms
Sep 26, 2026270 ms
Oct 3, 2026273 ms
Oct 10, 2026275 ms
Oct 17, 2026278 ms
Oct 24, 2026274 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 emtmadrid.es (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. emtmadrid.es at 0.7 s0.7 s
  2. emtmadrid.es at 1.4 s1.4 s
  3. emtmadrid.es at 2.1 s2.1 s
  4. emtmadrid.es at 2.8 s2.8 s
  5. emtmadrid.es at 3.6 s3.6 s
  6. emtmadrid.es at 4.3 s4.3 s
  7. emtmadrid.es at 5.0 s5.0 s
  8. emtmadrid.es at 5.7 s5.7 s

Speed

6 to fix61
  • Avoid multiple page redirects

    1.6 s

    The page goes through 2 redirects before it starts loading, costing about 1.6 s. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    930 ms · 125 KiB

    About 125 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 930 ms faster on a phone.

  • Mobile performance score: 61

    61/100

    Your mobile performance score is 61 (desktop: 68). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    800 ms · 127 KiB

    About 127 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 800 ms faster on a phone.

  • Render-blocking requests

    450 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • Main-thread work: 2.8 s

    A phone's processor spends 2.8 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 181 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    16 KiB

    4 files are served with short cache lifetimes, so returning visitors download them again (16 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.

1 checks passed
  • Server response: 211 ms

    211 ms

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

Core Web Vitals

10 to fix33
  • 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.9 s

    4.9 s

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

  • Real-user FCP: 4.8 s

    4.8 s

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

  • Real-user TTFB: 3.6 s

    3.6 s

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

  • Largest Contentful Paint: 23.2 s

    23.2 s

    Your largest element takes 23.2 s to render on a phone. Google's threshold for “good” is 2.5 s.

  • Time to Interactive: 23.8 s

    23.8 s

    The page becomes fully interactive after 23.8 s. Good is under 3.8 s.

  • Speed Index: 11.2 s

    11.2 s

    Visually, the page fills in at 11.2 s (Speed Index). Good is under 3.4 s.

  • Real-user CLS: 0.11

    0.11

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

  • First Contentful Paint: 2.2 s

    2.2 s

    The first text or image appears after 2.2 s on a phone. Good is under 1.8 s.

  • 8 images without width and height

    8 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -2%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 283 ms to 274 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +5%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user INP: 88 ms

    88 ms

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

  • Total Blocking Time: 180 ms

    180 ms

    Scripts block the page for only 180 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix0
  • Page weight: 4.4 MB in 90 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 90 requests on a phone: images 3.7 MB (39), scripts 328 KiB (22) and stylesheets 201 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • About 1.2 g of CO₂ per visit

    1.25 g

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

Accessibility

3 to fix91
  • 6 images without alt text

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

  • 4 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • No main landmark

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

SEO

12 to fixGoogle 7350
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (15 characters)

    Your title is only 15 characters: “E.M.T de Madrid”. 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.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 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 XML sitemap

    No XML sitemap at https://emtmadrid.es/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at emtmadrid.es/robots.txt, the first file search crawlers ask for.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

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

  • No X (Twitter) card tag

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

AI search readiness

1 to fix83
  • 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://emtmadrid.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.

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Best practices

2 to fixGoogle 7739
  • No mobile viewport

    No viewport meta tag, so phones render the desktop layout zoomed out.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

Content and conversion

5 to fix30
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

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

  • 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 0 words

    The homepage has only about 0 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

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

Upkeep, stack and company

Stack

Hosting
Telefonica De Espana

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on emtmadrid.es, including 16 speed issues, 12 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

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