Website review, no card needed

micasaenbcn.es logo

micasaenbcn.es website review

Visit site (opens in a new tab)Reviewed 13 November 202625 issues · 53 checks

This review found 25 issues worth fixing on micasaenbcn.es, 11 of them high impact, across 53 checks. The most urgent: fails Core Web Vitals for real visitors. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor tap response (INP)75th percentile, phones
153 ms125 msAug 8Nov 7134 ms
Show as table
DateReal-visitor tap response (INP)
Aug 8, 2026141 ms
Aug 15, 2026141 ms
Aug 29, 2026141 ms
Sep 5, 2026138 ms
Sep 12, 2026140 ms
Sep 19, 2026128 ms
Sep 26, 2026132 ms
Oct 3, 2026142 ms
Oct 10, 2026142 ms
Oct 17, 2026150 ms
Oct 24, 2026143 ms
Oct 31, 2026129 ms
Nov 7, 2026134 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 micasaenbcn.es (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. micasaenbcn.es at 1.6 s1.6 s
  2. micasaenbcn.es at 3.2 s3.2 s
  3. micasaenbcn.es at 4.9 s4.9 s
  4. micasaenbcn.es at 6.5 s6.5 s
  5. micasaenbcn.es at 8.1 s8.1 s
  6. micasaenbcn.es at 9.7 s9.7 s
  7. micasaenbcn.es at 11.3 s11.3 s
  8. micasaenbcn.es at 12.9 s12.9 s

Speed

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 110 KiB and 0 ms of main-thread time.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 0.5 s

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

6 to fix50
  • 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.56

    0.56

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 818 ms

    818 ms

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

  • Speed Index: 4.8 s

    4.8 s

    Visually, the page fills in at 4.8 s (Speed Index). Good is under 3.4 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

    -7%

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

3 checks passed
  • Real-user INP: 134 ms

    134 ms

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

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix33
  • 1 image over 500 KB

    hero-bg-D4IkWn6N.png weighs 1.2 MB. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    533 KiB

    4 images are downloaded at several times the size a phone draws them, for example picaña3.jpeg at 1,320 px wide, shown at 358 px. Resized copies would save about 533 KiB.

  • Page weight: 2.6 MB in 21 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 21 requests on a phone: images 2.4 MB (11), fonts 109 KiB (3) and scripts 108 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

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

  • 2 images below the first screen load straight away

    2 images further down the page (461 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.7 g of CO₂ per visit

    0.74 g

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

Accessibility

3 to fixGoogle 9695
  • 38 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

4 to fixGoogle 10080
  • No H1 headline

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

  • Canonical points to another host

    Your canonical URL points to mi-casa-web.vercel.app, not micasaenbcn.es, so Google may credit that host instead.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 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 X (Twitter) card tag

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

5 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “El mejor restaurante brasileño en Sants, Barcelona. Disfruta de la auténtica feijoada, picanha, y comida casera brasile…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Mi Casa Bar & Restaurante | Restaurante brasileño en Barcelona”.

  • 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://mi-casa-web.vercel.app/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 940 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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://micasaenbcn.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

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Best practices

Google 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix20
  • 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 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 940 words of copy

    The homepage carries about 940 words of visible text.

Privacy and tracking

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

  • 3 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
10 Shopify Products;Dondy;Shopify;Shopify Local Pickup;Shopify Plus;Shopify POS
Hosting
Vercel

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on micasaenbcn.es, including 6 speed issues, 4 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