Website review, no card needed

gilmar.es logo

gilmar.es website review

Visit site (opens in a new tab)Reviewed 3 November 202639 issues · 88 checks

This review found 39 issues worth fixing on gilmar.es, 14 of them high impact, across 88 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 s2.2 sMay 16Oct 312.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.7 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.7 s
Jul 4, 20262.9 s
Jul 11, 20263.1 s
Jul 18, 20263.4 s
Jul 25, 20263.6 s
Aug 1, 20263.5 s
Aug 8, 20263.5 s
Aug 15, 20263.5 s
Aug 22, 20263.6 s
Aug 29, 20263.7 s
Sep 5, 20263.5 s
Sep 12, 20263.3 s
Sep 19, 20262.9 s
Sep 26, 20262.6 s
Oct 3, 20262.6 s
Oct 10, 20262.6 s
Oct 17, 20262.6 s
Oct 24, 20262.6 s
Oct 31, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
233 ms192 msMay 16Oct 31214 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026206 ms
May 23, 2026206 ms
May 30, 2026207 ms
Jun 6, 2026210 ms
Jun 13, 2026210 ms
Jun 20, 2026210 ms
Jun 27, 2026214 ms
Jul 4, 2026217 ms
Jul 11, 2026221 ms
Jul 18, 2026227 ms
Jul 25, 2026226 ms
Aug 1, 2026228 ms
Aug 8, 2026228 ms
Aug 15, 2026225 ms
Aug 22, 2026224 ms
Aug 29, 2026219 ms
Sep 5, 2026217 ms
Sep 12, 2026218 ms
Sep 19, 2026217 ms
Sep 26, 2026212 ms
Oct 3, 2026205 ms
Oct 10, 2026201 ms
Oct 17, 2026197 ms
Oct 24, 2026202 ms
Oct 31, 2026214 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 gilmar.es (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gilmar.es at 1.2 s1.2 s
  2. gilmar.es at 2.3 s2.3 s
  3. gilmar.es at 3.5 s3.5 s
  4. gilmar.es at 4.6 s4.6 s
  5. gilmar.es at 5.8 s5.8 s
  6. gilmar.es at 6.9 s6.9 s
  7. gilmar.es at 8.1 s8.1 s
  8. gilmar.es at 9.2 s9.2 s

Speed

10 to fix63
  • Render-blocking requests

    3.5 s

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

  • Main-thread work: 4.6 s

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

  • Reduce unused JavaScript

    450 ms · 575 KiB

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

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    590 ms · 226 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Hubspot, callpage.io and Google Tag Manager and others), adding 1.1 MB and 691 ms of main-thread time.

  • 16 long tasks on the main thread

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

  • Use efficient cache lifetimes

    305 KiB

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

  • 1,969 HTML elements

    The page has 1,969 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • callpage.io adds 128 ms

    128 ms

    callpage.io costs a phone 128 ms of main-thread work and 364 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Legacy JavaScript

    58 KiB

    Polyfills for old browsers add 58 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    6 KiB

    6 KiB could be saved by minifying JavaScript.

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

  • Improve image delivery

    5 KiB

    1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

1 checks passed
  • Server response: 104 ms

    104 ms

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

Core Web Vitals

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

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

  • Time to Interactive: 17.8 s

    17.8 s

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

  • Total Blocking Time: 792 ms

    792 ms

    Scripts block taps and scrolling for 792 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Speed Index: 6.2 s

    6.2 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Largest Contentful Paint: 3.2 s

    3.2 s

    Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “De toda la vida,”. Most of its time is element render delay (1.6 s).

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

3 checks passed
  • Real-user INP: 187 ms

    187 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.6 MB in 157 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 157 requests on a phone: scripts 1.6 MB (52), images 412 KiB (39) and stylesheets 278 KiB (25). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.73 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

9 to fixGoogle 8490
  • 34 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • 39 links without text

    39 visible links have no text or label, so screen readers cannot say where they go.

  • ARIA role should be appropriate for the element (28 elements)

    ARIA role should be appropriate for the element: 28 elements on the page fail this check, rated minor by axe-core.

  • 12 form fields without a label

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

  • ARIA input fields do not have accessible names

    ARIA input fields do not have accessible names (1 element).

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

Google 92100
  • 174 internal links, 29 external

    The homepage links to 174 pages on gilmar.es and 29 external pages.

8 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “GILMAR: Pisos, locales y las mejores oportunidades en real estate. Especialistas en residencial, obra nueva, fincas rús…”.

  • One H1 headline

    Your main headline reads: “De toda la vida, servicio garantía un lujo.”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “GILMAR | Expertos en la compraventa y alquiler de inmuebles”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • 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://www.gilmar.es/sitemap_index.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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

1 to fix93
  • 1 linked page hidden from search

    https://www.gilmar.es/category/sector-inmobiliario is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages slow to respond

    https://www.gilmar.es/blog and https://www.gilmar.es/category/sector-inmobiliario took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 2 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 2 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9285
  • 11 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to execute 'getComputedStyle' on 'Window': parameter 1 is not of type 'Element'.”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 2,718 words of copy

    The homepage carries about 2,718 words of visible text.

4 checks passed
  • 6 short forms

    6 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, HubSpot and Meta Pixel (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.

  • 16 cookies set on arrival

    16

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

  • 34 other companies contacted

    Loading the homepage contacts 34 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 gilmar.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 39 issues on gilmar.es, including 20 speed 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