Website review, no card needed
mutuamadridopen.com website review
Visit site (opens in a new tab)Reviewed 25 October 202641 issues · 85 checks
This review found 41 issues worth fixing on mutuamadridopen.com, 17 of them high impact, across 85 checks. The most urgent: render-blocking requests. 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
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.3 s |
| May 9, 2026 | 2.3 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 126 ms |
| May 9, 2026 | 127 ms |
| May 16, 2026 | 127 ms |
| May 23, 2026 | 127 ms |
| May 30, 2026 | 128 ms |
| Jun 6, 2026 | 125 ms |
| Jun 13, 2026 | 123 ms |
| Jun 20, 2026 | 122 ms |
| Jun 27, 2026 | 124 ms |
| Jul 4, 2026 | 121 ms |
| Jul 11, 2026 | 124 ms |
| Jul 18, 2026 | 126 ms |
| Jul 25, 2026 | 127 ms |
| Aug 1, 2026 | 127 ms |
| Aug 8, 2026 | 126 ms |
| Aug 15, 2026 | 122 ms |
| Aug 22, 2026 | 122 ms |
| Aug 29, 2026 | 133 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 135 ms |
| Sep 19, 2026 | 133 ms |
| Sep 26, 2026 | 128 ms |
| Oct 3, 2026 | 122 ms |
| Oct 10, 2026 | 123 ms |
| Oct 17, 2026 | 123 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
0.9 s
1.7 s
2.6 s
3.5 s
4.3 s
5.2 s
6.1 s
7.0 s
Speed
Render-blocking requests
4.0 s47 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.0 s.
Improve image delivery
1.1 s · 1.3 MB12 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
3,179 HTML elements
The page has 3,179 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 62
62/100Your mobile performance score is 62 (desktop: 97). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
750 ms · 142 KiBAbout 142 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Font display
700 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 700 ms).
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 904 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2 third-party services on the page
2 third-party services load with your homepage (rolex.com and Cloudflare CDN), adding 126 KiB and 61 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 59 ms. During a long task the page ignores taps.
Reduce unused CSS
39 KiBAbout 39 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
12 KiB12 KiB could be saved by minifying JavaScript.
Phones get a much slower page than desktops
Desktop scores 97 but mobile only 62. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 27 ms
27 msYour server sent the HTML in 27 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.6 s
14.6 sYour largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “CAMPEÓN INDISCUTIBLE COMPRA YA TUS ENTRADAS PARA 2027”.
Time to Interactive: 15.1 s
15.1 sThe page becomes fully interactive after 15.1 s. Good is under 3.8 s.
Speed Index: 7.0 s
7.0 sVisually, the page fills in at 7.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 126 ms to 123 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 115 ms
115 msReal visitors wait 115 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 501 ms
501 msReal visitors wait 501 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 37% faster for real visitors
-37%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.3 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Total Blocking Time: 5 ms
5 msScripts block the page for only 5 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.3 MB in 138 requests
4.3 MBYour homepage downloads 4.3 MB in 138 requests on a phone: images 3.0 MB (27), fonts 566 KiB (10) and scripts 486 KiB (44). Under 2 MB keeps phones on slow connections fast.
8 images in older formats
8 images (667 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.
1 image far larger than shown
121 KiB1 image is downloaded at several times the size a phone draws it, for example chatbot-2024-768x768.png at 390 px wide, shown at 41 px. Resized copies would save about 121 KiB.
3 images below the first screen load straight away
3 images further down the page (363 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.23 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.23 g of CO₂e: 147.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
2 frames have no title, so screen-reader users cannot tell what they contain.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
13 images without alt text
13 images have no alt text, which hurts accessibility and image search.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
57 links without text
57 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (3 elements)
ARIA role should be appropriate for the element: 3 elements on the page fail 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
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 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
Title is short (26 characters)
Your title is only 26 characters: “Inicio - Mutua Madrid Open”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“Del 20 de abril al 3 de mayo 2026. CAJA MÁGICA” and “#MMOPEN”). One clear main headline is easier for people and search engines.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
196 internal links, 114 external
The homepage links to 196 pages on mutuamadridopen.com and 114 external pages.
6 checks passed
Meta description: 86 characters
Your meta description is 86 characters: “El Mutua Madrid Open se celebra en La Caja Mágica del 20 de abril al 3 de mayo de 2026”.
Canonical URL set
The canonical URL is https://mutuamadridopen.com/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person and TennisComplex.
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://mutuamadridopen.com/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://mutuamadridopen.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.
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 (1,106 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://mutuamadridopen.com/entrenamientos, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page without a title
https://mutuamadridopen.com/game-set-madrid has no <title>, so Google invents the link text in results.
1 page without a meta description
https://mutuamadridopen.com/game-set-madrid has no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://mutuamadridopen.com/resultados-en-directo, https://mutuamadridopen.com/resultados, https://mutuamadridopen.com/cuadro-fase-previa, https://mutuamadridopen.com/cuadro-principal, https://mutuamadridopen.com/jugadores-2026 and https://mutuamadridopen.com/palmares and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 55 found) and read each the way a search engine does.
3 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
19 of 20 tappable elements near the top are at least 24 px.
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.
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 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 172 words
The homepage has only about 172 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
2 short forms
2 short forms (3 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 mutuamadridopen.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2024.
Stack
- CMS
- WordPress
- Framework
- Vue.js
- Analytics
- Google Analytics | Google Tag Manager
Company
- Founded
- 1990
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on mutuamadridopen.com, including 11 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.