Website review, no card needed

aperitivossnack.com logo

aperitivossnack.com website review

Visit site (opens in a new tab)Reviewed 3 November 202628 issues · 76 checks

This review found 28 issues worth fixing on aperitivossnack.com, 15 of them high impact, across 76 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
3.8 s2.6 sMay 16Oct 313.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.1 s
May 23, 20263.4 s
May 30, 20263.3 s
Jun 6, 20263.5 s
Jun 13, 20263.6 s
Jun 20, 20263.4 s
Jun 27, 20263.3 s
Jul 4, 20262.9 s
Jul 11, 20262.8 s
Jul 18, 20263.1 s
Jul 25, 20263.1 s
Aug 1, 20263.2 s
Aug 8, 20263.0 s
Aug 15, 20262.9 s
Aug 22, 20262.8 s
Aug 29, 20263.0 s
Sep 5, 20263.3 s
Sep 12, 20263.4 s
Sep 19, 20263.5 s
Sep 26, 20263.3 s
Oct 3, 20263.0 s
Oct 10, 20262.7 s
Oct 17, 20262.7 s
Oct 24, 20263.0 s
Oct 31, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
115 ms81 msMay 16Oct 3190 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026111 ms
May 23, 2026110 ms
May 30, 202696 ms
Jun 6, 202698 ms
Jun 13, 202698 ms
Jun 20, 202689 ms
Jun 27, 202695 ms
Jul 4, 202685 ms
Jul 11, 202688 ms
Jul 18, 202696 ms
Jul 25, 202697 ms
Aug 29, 202697 ms
Sep 5, 202697 ms
Sep 12, 2026105 ms
Sep 26, 202699 ms
Oct 3, 2026103 ms
Oct 10, 202694 ms
Oct 17, 202692 ms
Oct 24, 202691 ms
Oct 31, 202690 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 aperitivossnack.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aperitivossnack.com at 1.4 s1.4 s
  2. aperitivossnack.com at 2.7 s2.7 s
  3. aperitivossnack.com at 4.1 s4.1 s
  4. aperitivossnack.com at 5.5 s5.5 s
  5. aperitivossnack.com at 6.8 s6.8 s
  6. aperitivossnack.com at 8.2 s8.2 s
  7. aperitivossnack.com at 9.6 s9.6 s
  8. aperitivossnack.com at 10.9 s10.9 s

Speed

7 to fix55
  • Use efficient cache lifetimes

    5.4 s · 1.7 MB

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

  • Reduce unused JavaScript

    1.6 s · 343 KiB

    About 343 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

  • Render-blocking requests

    1.4 s

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

  • Reduce unused CSS

    1.1 s · 236 KiB

    About 236 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 55

    55/100

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

  • Improve image delivery

    250 ms · 532 KiB

    4 images could be 532 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

  • Main-thread work: 2.2 s

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

  • 6 long tasks on the main thread

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

  • Legacy JavaScript

    100 ms · 33 KiB

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (openli.com), adding 98 KiB and 115 ms of main-thread time.

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

1 checks passed
  • Server response: 122 ms

    122 ms

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

Core Web Vitals

8 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.2 s

    3.2 s

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

  • Real-user TTFB: 2.7 s

    2.7 s

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

  • Speed Index: 15.4 s

    15.4 s

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

  • Largest Contentful Paint: 7.4 s

    7.4 s

    Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Aperitivos Snack”. Most of its time is resource load delay (9.6 s).

  • Time to Interactive: 7.6 s

    7.6 s

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

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

  • Total Blocking Time: 377 ms

    377 ms

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

  • Largest content (LCP) held steady for real visitors

    0%

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

5 checks passed
  • Real-user INP: 92 ms

    92 ms

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

  • Real-user CLS: 0.02

    0.02

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

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

    -18%

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

  • Cumulative Layout Shift: 0.077

    0.077

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.50 g

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

4 checks passed
  • Page weight: 1.8 MB in 43 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 43 requests on a phone: images 710 KiB (5), scripts 578 KiB (20) and fonts 242 KiB (7). That is a lean page.

  • 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

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

  • 2 tap targets too small

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

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

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 65 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 4 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
  • 2 H1 headlines

    There are 2 <h1> headlines (“Publicaciones recientes” and “Marcamos la diferencia”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 91 internal links, 10 external

    The homepage links to 91 pages on aperitivossnack.com and 10 external pages.

6 checks passed
  • Meta description: 114 characters

    Your meta description is 114 characters: “Fabricamos y distribuimos emociones que convierten tus momentos en inolvidables en todos los rincones de #Canarias”.

  • Title: 30 characters

    Your title is a healthy 30 characters: “Inicio - Aperitivos Snack S.A.”.

  • Canonical URL set

    The canonical URL is https://aperitivossnack.com/.

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

AI search readiness

100
  • No llms.txt

    There is no https://aperitivossnack.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: 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 (418 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 6 pages without a meta description

    https://aperitivossnack.com/quienes-somos, https://aperitivossnack.com/quienes-somos/mision-vision-y-valores, https://aperitivossnack.com/quienes-somos/comite-de-direccion, https://aperitivossnack.com/quienes-somos/codigo-de-conducta, https://aperitivossnack.com/contacto/delegaciones-en-canarias and https://aperitivossnack.com/contacto/atencion-al-cliente have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages slow to respond

    https://aperitivossnack.com/quienes-somos, https://aperitivossnack.com/quienes-somos/mision-vision-y-valores, https://aperitivossnack.com/quienes-somos/comite-de-direccion, https://aperitivossnack.com/quienes-somos/codigo-de-conducta, https://aperitivossnack.com/contacto/delegaciones-en-canarias and https://aperitivossnack.com/contacto/atencion-al-cliente took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    6 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 11 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'addEventListener')”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Only about 244 words

    The homepage has only about 244 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Direct contact links

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

Privacy and tracking

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 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 aperitivossnack.com, 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
E-commerce
WooCommerce

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on aperitivossnack.com, including 15 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