Website review, no card needed

vivienda2.com logo

vivienda2.com website review

Visit site (opens in a new tab)Reviewed 21 October 202629 issues · 71 checks

This review found 29 issues worth fixing on vivienda2.com, 9 of them high impact, across 71 checks. The most urgent: render-blocking requests. 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
3.9 s3.0 sMay 2Oct 173.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.3 s
May 9, 20263.2 s
May 16, 20263.2 s
May 23, 20263.1 s
May 30, 20263.1 s
Jun 6, 20263.1 s
Jun 13, 20263.1 s
Jun 20, 20263.1 s
Jun 27, 20263.2 s
Jul 4, 20263.5 s
Jul 11, 20263.6 s
Jul 18, 20263.8 s
Jul 25, 20263.8 s
Aug 1, 20263.6 s
Aug 8, 20263.8 s
Aug 15, 20263.8 s
Aug 22, 20263.8 s
Aug 29, 20263.7 s
Sep 5, 20263.7 s
Sep 12, 20263.7 s
Sep 19, 20263.7 s
Sep 26, 20263.8 s
Oct 3, 20263.8 s
Oct 10, 20263.8 s
Oct 17, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
196 ms138 msMay 2Oct 17189 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026159 ms
May 9, 2026161 ms
May 16, 2026162 ms
May 23, 2026164 ms
May 30, 2026162 ms
Jun 6, 2026162 ms
Jun 13, 2026160 ms
Jun 20, 2026165 ms
Jun 27, 2026166 ms
Jul 4, 2026164 ms
Jul 11, 2026163 ms
Jul 18, 2026145 ms
Jul 25, 2026146 ms
Aug 1, 2026146 ms
Aug 8, 2026146 ms
Aug 15, 2026160 ms
Aug 22, 2026169 ms
Aug 29, 2026171 ms
Sep 5, 2026168 ms
Sep 12, 2026175 ms
Sep 19, 2026177 ms
Sep 26, 2026181 ms
Oct 3, 2026187 ms
Oct 10, 2026187 ms
Oct 17, 2026189 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 vivienda2.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. vivienda2.com at 1.0 s1.0 s
  2. vivienda2.com at 2.0 s2.0 s
  3. vivienda2.com at 3.1 s3.1 s
  4. vivienda2.com at 4.1 s4.1 s
  5. vivienda2.com at 5.1 s5.1 s
  6. vivienda2.com at 6.1 s6.1 s
  7. vivienda2.com at 7.2 s7.2 s
  8. vivienda2.com at 8.2 s8.2 s

Speed

4 to fix79
  • Render-blocking requests

    1.8 s

    13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

  • Use efficient cache lifetimes

    750 ms · 705 KiB

    36 files are served with short cache lifetimes, so returning visitors download them again (705 KiB).

  • Mobile performance score: 79

    79/100

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

  • Reduce unused JavaScript

    390 ms · 116 KiB

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

  • Reduce unused CSS

    150 ms · 18 KiB

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Maps), adding 212 KiB and 91 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 71 ms. During a long task the page ignores taps.

  • Improve image delivery

    23 KiB

    4 images could be 23 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

2 checks passed
  • Main-thread work: 0.4 s

    A phone's processor spends 0.4 s on main-thread work while loading, 150 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

9 to fix67
  • 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 TTFB: 2.5 s

    2.5 s

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

  • 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 LCP: 3.1 s

    3.1 s

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

  • Real-user FCP: 3.0 s

    3.0 s

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

  • Largest Contentful Paint: 3.5 s

    3.5 s

    Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Con el fin de ofrecer servicios del nivel más alto en nuest…”. Most of its time is element render delay (7.3 s).

  • 24 images without width and height

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

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

  • Time to Interactive: 4.5 s

    4.5 s

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

  • Tap response (INP) got 18% slower for real visitors

    +18%

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

  • Largest content (LCP) got 15% slower for real visitors

    +15%

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

4 checks passed
  • Real-user INP: 182 ms

    182 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.021

    0.021

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

  • Total Blocking Time: 11 ms

    11 ms

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

Images and page weight

2 to fix83
  • 1 image far larger than shown

    336 KiB

    1 image is downloaded at several times the size a phone draws it, for example 70246500x500-01.png at 2,438 px wide, shown at 360 px. Resized copies would save about 336 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (418 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • 2 images in older formats

    2 images (455 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.

  • About 0.3 g of CO₂ per visit

    0.27 g

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

1 checks passed
  • Page weight: 982 KiB in 58 requests

    982 KiB

    Your homepage downloads 982 KiB in 58 requests on a phone: images 672 KiB (39), scripts 269 KiB (10) and stylesheets 30 KiB (6). That is a lean page.

Accessibility

5 to fixGoogle 8090
  • 39 tap targets too small

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

  • 2 text elements with low contrast

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

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

    All page content should be contained by landmarks: 10 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.

  • 7 form fields without a label

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

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 37 images in the HTML carry an alt attribute.

  • 29 automated accessibility rules passed

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

SEO

2 to fixGoogle 10092
  • 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 X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 67 internal links, 7 external

    The homepage links to 67 pages on vivienda2.com and 7 external pages.

6 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “vivienda2: venta pisos en Madrid, nuestra inmobiliaria tiene pisos, oficinas, chalets y apartamentos para la compra y v…”.

  • One H1 headline

    Your main headline reads: “Viviendas en venta en Madrid”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “Venta de pisos en Madrid | Inmobiliaria Vivienda2”.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.vivienda2.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.vivienda2.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 (473 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

1 to fixGoogle 9693
  • 6 small tap targets

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

  • 5 low-resolution images

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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 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.

  • 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 515 words of copy

    The homepage carries about 515 words of visible text.

1 checks passed
  • 4 short forms

    4 short forms (4 fields at most) are right on the homepage.

Privacy and tracking

  • 2 cookies set on arrival

    2

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

  • 1 other company contacted

    Loading the homepage contacts 1 host 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 vivienda2.com, 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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on vivienda2.com, including 13 speed issues, 2 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