Website review, no card needed

cafesevilla.com logo

cafesevilla.com website review

Visit site (opens in a new tab)Reviewed 18 October 202635 issues · 81 checks

This review found 35 issues worth fixing on cafesevilla.com, 13 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. 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
2.1 s1.7 sApr 25Oct 102.0 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.7 s
May 2, 20261.8 s
May 9, 20261.7 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.7 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20261.9 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20262.1 s
Oct 10, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
98 ms81 msApr 25Oct 1095 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202685 ms
May 2, 202686 ms
May 9, 202687 ms
May 16, 202687 ms
May 23, 202687 ms
May 30, 202686 ms
Jun 6, 202683 ms
Jun 13, 202683 ms
Jun 20, 202685 ms
Jun 27, 202687 ms
Jul 4, 202687 ms
Jul 11, 202687 ms
Jul 18, 202687 ms
Jul 25, 202688 ms
Aug 1, 202689 ms
Aug 8, 202695 ms
Aug 15, 202696 ms
Aug 22, 202695 ms
Aug 29, 202696 ms
Sep 5, 202692 ms
Sep 12, 202691 ms
Sep 19, 202695 ms
Sep 26, 202694 ms
Oct 3, 202696 ms
Oct 10, 202695 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 cafesevilla.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cafesevilla.com at 0.4 s0.4 s
  2. cafesevilla.com at 0.8 s0.8 s
  3. cafesevilla.com at 1.3 s1.3 s
  4. cafesevilla.com at 1.7 s1.7 s
  5. cafesevilla.com at 2.1 s2.1 s
  6. cafesevilla.com at 2.5 s2.5 s
  7. cafesevilla.com at 3.0 s3.0 s
  8. cafesevilla.com at 3.4 s3.4 s

Speed

14 to fix39
  • Use efficient cache lifetimes

    12.3 s · 2.2 MB

    15 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).

  • Reduce unused JavaScript

    11.6 s · 1.8 MB

    About 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 11.6 s faster on a phone.

  • Render-blocking requests

    2.7 s

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

  • Mobile performance score: 39

    39/100

    Your mobile performance score is 39 (desktop: 35). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 5.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (audioeye.com, getbento.com and Google CDN and others), adding 12.9 MB and 2.6 s of main-thread time.

  • getbento.com adds 607 ms

    607 ms

    getbento.com costs a phone 607 ms of main-thread work and 4.1 MB 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.

  • audioeye.com adds 842 ms

    842 ms

    audioeye.com costs a phone 842 ms of main-thread work and 310 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 CSS

    460 ms · 101 KiB

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

  • Google CDN adds 380 ms

    380 ms

    Google CDN costs a phone 380 ms of main-thread work and 739 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

    300 ms · 78 KiB

    Polyfills for old browsers add 78 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • sevenrooms.com adds 240 ms

    240 ms

    sevenrooms.com costs a phone 240 ms of main-thread work and 716 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.

  • 19 long tasks on the main thread

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

  • Google Tag Manager adds 229 ms

    229 ms

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

  • Font display

    50 ms

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

  • Improve image delivery

    7 KiB

    1 image could be 7 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.

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 33.5 s

    33.5 s

    Your largest element takes 33.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “"TAKE A TRIP TO SPAIN WITHOUT THE AIRFARE" - ROGELIO HUIDOB…”.

  • Time to Interactive: 34.4 s

    34.4 s

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

  • Speed Index: 11.1 s

    11.1 s

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

  • First Contentful Paint: 3.7 s

    3.7 s

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

  • Total Blocking Time: 847 ms

    847 ms

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

  • Real-user LCP: 3.5 s

    3.5 s

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

  • Real-user CLS: 0.12

    0.12

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

  • 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) got 12% slower for real visitors

    +12%

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

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

    +18%

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

4 checks passed
  • Real-user INP: 98 ms

    98 ms

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 350 ms

    350 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 13.7 MB in 101 requests

    13.7 MB

    Your homepage downloads 13.7 MB in 101 requests on a phone: other files 6.5 MB (18), scripts 4.2 MB (28) and images 2.4 MB (37). Under 2 MB keeps phones on slow connections fast.

  • About 3.9 g of CO₂ per visit

    3.89 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.89 g of CO₂e: 466.4 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

1 to fixGoogle 9999
  • 1 form field without a label

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

  • Elements with role="none" or role="presentation" have conflicts

    Elements with role="none" or role="presentation" have conflicts (1 element).

2 checks passed
  • Every image has alt text

    All 33 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 0 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 10091
  • Meta description is long (172 characters)

    Your meta description is 172 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 2 problems

    Structured data found (Organization, WebPage and WebSite) but with 2 problems, for example “Organization: sameAs is not an absolute URL ("https://www.cafesevilla.com/facebook/")”.

  • 64 internal links, 14 external

    The homepage links to 64 pages on cafesevilla.com and 14 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Home”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Cafe Sevilla - Restaurant & Tapas - Southern California”.

  • Canonical URL set

    The canonical URL is https://www.cafesevilla.com/.

  • 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.cafesevilla.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

2 to fix93
  • 15 pages share a meta description

    https://www.cafesevilla.com/who-we-are, https://www.cafesevilla.com/menus, https://www.cafesevilla.com/overview, https://www.cafesevilla.com/music-san-diego, https://www.cafesevilla.com/music-costa-mesa and https://www.cafesevilla.com/private-events-san-diego and 9 others use the same meta description. A description written for each page earns more clicks.

  • 6 pages without an H1

    https://www.cafesevilla.com/overview, https://www.cafesevilla.com/music-san-diego, https://www.cafesevilla.com/music-costa-mesa, https://www.cafesevilla.com/flamenco-san-diego, https://www.cafesevilla.com/costa-mesa-flamenco and https://www.cafesevilla.com/promos-costa-mesa 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 25 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 15 pages that loaded have a meta description.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

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

    The homepage carries about 594 words of visible text.

3 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Contact”, “E-Club Sign Up” and “Text-Club Sign Up”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies, 2 of them by other companies (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.

  • 23 other companies contacted

    Loading the homepage contacts 23 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 cafesevilla.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
Bootstrap
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on cafesevilla.com, including 23 speed issues, 2 SEO issues and 3 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