Website review, no card needed

casapablo.es logo

casapablo.es website review

Visit site (opens in a new tab)Reviewed 7 November 202636 issues · 84 checks

This review found 36 issues worth fixing on casapablo.es, 12 of them high impact, across 84 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.0 s2.5 sMay 16Oct 312.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.9 s
May 23, 20262.8 s
May 30, 20262.7 s
Jun 6, 20262.8 s
Jun 13, 20262.7 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.7 s
Jul 18, 20262.7 s
Jul 25, 20262.7 s
Aug 1, 20262.6 s
Aug 8, 20262.6 s
Aug 15, 20262.6 s
Aug 22, 20262.6 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.6 s
Oct 10, 20262.7 s
Oct 17, 20262.7 s
Oct 24, 20262.6 s
Oct 31, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
115 ms90 msMay 16Oct 3199 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202697 ms
May 23, 202693 ms
May 30, 202694 ms
Jun 6, 202696 ms
Jun 13, 2026102 ms
Jun 20, 2026104 ms
Jun 27, 2026109 ms
Jul 4, 2026107 ms
Jul 11, 2026105 ms
Jul 18, 2026105 ms
Jul 25, 2026105 ms
Aug 1, 2026108 ms
Aug 8, 2026112 ms
Aug 15, 2026110 ms
Aug 22, 2026106 ms
Aug 29, 2026108 ms
Sep 5, 2026102 ms
Sep 12, 2026103 ms
Sep 19, 2026101 ms
Sep 26, 202698 ms
Oct 3, 202697 ms
Oct 10, 2026101 ms
Oct 17, 2026104 ms
Oct 24, 202699 ms
Oct 31, 202699 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 casapablo.es (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. casapablo.es at 0.6 s0.6 s
  2. casapablo.es at 1.3 s1.3 s
  3. casapablo.es at 1.9 s1.9 s
  4. casapablo.es at 2.5 s2.5 s
  5. casapablo.es at 3.2 s3.2 s
  6. casapablo.es at 3.8 s3.8 s
  7. casapablo.es at 4.4 s4.4 s
  8. casapablo.es at 5.1 s5.1 s

Speed

6 to fix60
  • Render-blocking requests

    2.5 s

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

  • Improve image delivery

    600 ms · 1.3 MB

    8 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 600 ms faster on a phone.

  • Mobile performance score: 60

    60/100

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

  • Use efficient cache lifetimes

    300 ms · 313 KiB

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

  • Font display

    350 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).

  • Google Tag Manager adds 146 ms

    146 ms

    Google Tag Manager costs a phone 146 ms of main-thread work and 321 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.

  • Reduce unused JavaScript

    150 ms · 195 KiB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, cdn-cookieyes.com and popupsmart.com and others), adding 575 KiB and 200 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 69 KiB

    About 69 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.

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    15 KiB

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

  • 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: 1.4 s

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

  • 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 CLS: 0.41

    0.41

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

  • Largest Contentful Paint: 6.5 s

    6.5 s

    Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Proveedor de vino para HORECA Tu mejor elección como distri…”.

  • Speed Index: 6.9 s

    6.9 s

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

  • Time to Interactive: 7.5 s

    7.5 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.176

    0.176

    The layout shifts by 0.176 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

3 checks passed
  • Real-user INP: 96 ms

    96 ms

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Total Blocking Time: 38 ms

    38 ms

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

Images and page weight

4 to fix53
  • 1 image over 500 KB

    10128.jpg weighs 963 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.4 MB in 95 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 95 requests on a phone: images 2.2 MB (24), scripts 596 KiB (24) and fonts 509 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (1.1 MB) 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.

  • 5 images below the first screen load straight away

    5 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    0.97 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

6 to fixGoogle 7991
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 3 images without alt text

    3 images have 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.

  • Zoom is disabled

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

  • 2 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • No main landmark

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

  • Headings skip levels

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

1 checks passed
  • 40 automated accessibility rules passed

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

SEO

2 to fixGoogle 9290
  • Title is short (19 characters)

    Your title is only 19 characters: “CASA PABLO Marbella”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 43 internal links, 8 external

    The homepage links to 43 pages on casapablo.es and 8 external pages.

6 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “Especialistas en vinos y licores desde 1966. Especialistas en hostelería. Visita nuestra tienda en Marbella o compra vi…”.

  • One H1 headline

    Your main headline reads: “CASAPABLO”.

  • Canonical URL set

    The canonical URL is https://casapablo.es/.

  • Structured data in place

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

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://casapablo.es/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://casapablo.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.

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

  • Text is in the HTML

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

Other pages

3 to fix86
  • 3 linked pages hidden from search

    https://casapablo.es/politica-privacidad, https://casapablo.es/aviso-legal and https://casapablo.es/politica-de-cookies are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://casapablo.es/politica-privacidad, https://casapablo.es/aviso-legal and https://casapablo.es/politica-de-cookies have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://casapablo.es/catas-de-vino-y-eventos-en-marbella and https://casapablo.es/catering use the same meta description. A description written for each page earns more clicks.

  • 5 pages slow to respond

    https://casapablo.es/vino-y-bodega-para-restauracion-y-horeca, https://casapablo.es/catas-de-vino-y-eventos-en-marbella, https://casapablo.es/catering, https://casapablo.es/sobre-nosotros and https://casapablo.es/tienda-de-vino-en-marbella took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage and read each the way a search engine does.

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

  • 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 10 pages that loaded have a <title>.

Best practices

1 to fixGoogle 8197
  • 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.”).

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    9 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • About 419 words of copy

    The homepage carries about 419 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Analytics and Hotjar.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Hotjar (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies (measured from a US location before any click).

  • 9 other companies contacted

    Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Hotjar
Hosting
Soluciones web on line s.l.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on casapablo.es, including 16 speed issues, 2 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
casapablo.es website review: scores and fixes | Programmable