Website review, no card needed

aldelis.com logo

aldelis.com website review

Visit site (opens in a new tab)Reviewed 18 November 202641 issues · 77 checks

This review found 41 issues worth fixing on aldelis.com, 21 of them high impact, across 77 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
6.1 s5.0 sMay 30Nov 145.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20265.5 s
Jun 6, 20265.3 s
Jun 13, 20265.2 s
Jun 20, 20265.2 s
Jun 27, 20265.2 s
Jul 4, 20265.1 s
Jul 11, 20265.1 s
Jul 18, 20265.1 s
Jul 25, 20265.2 s
Aug 1, 20265.2 s
Aug 8, 20265.3 s
Aug 15, 20265.3 s
Aug 22, 20265.3 s
Aug 29, 20265.4 s
Sep 5, 20265.5 s
Sep 12, 20265.6 s
Sep 19, 20265.7 s
Sep 26, 20265.7 s
Oct 3, 20265.8 s
Oct 10, 20265.8 s
Oct 17, 20265.9 s
Oct 24, 20265.9 s
Oct 31, 20265.9 s
Nov 7, 20265.9 s
Nov 14, 20265.9 s
Real-visitor tap response (INP)75th percentile, phones
177 ms157 msMay 30Nov 14169 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026159 ms
Jun 6, 2026159 ms
Jun 13, 2026159 ms
Jun 20, 2026161 ms
Jun 27, 2026161 ms
Jul 4, 2026162 ms
Jul 11, 2026162 ms
Jul 18, 2026160 ms
Jul 25, 2026160 ms
Aug 1, 2026160 ms
Aug 8, 2026161 ms
Aug 15, 2026164 ms
Aug 22, 2026167 ms
Aug 29, 2026168 ms
Sep 5, 2026168 ms
Sep 12, 2026169 ms
Sep 19, 2026167 ms
Sep 26, 2026170 ms
Oct 3, 2026171 ms
Oct 10, 2026172 ms
Oct 17, 2026175 ms
Oct 24, 2026173 ms
Oct 31, 2026174 ms
Nov 7, 2026171 ms
Nov 14, 2026169 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 aldelis.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aldelis.com at 1.0 s1.0 s
  2. aldelis.com at 1.9 s1.9 s
  3. aldelis.com at 2.9 s2.9 s
  4. aldelis.com at 3.8 s3.8 s
  5. aldelis.com at 4.8 s4.8 s
  6. aldelis.com at 5.8 s5.8 s
  7. aldelis.com at 6.7 s6.7 s
  8. aldelis.com at 7.7 s7.7 s

Speed

11 to fix43
  • Use efficient cache lifetimes

    8.8 s · 3.1 MB

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

  • Reduce unused JavaScript

    4.7 s · 983 KiB

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

  • Render-blocking requests

    4.1 s

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

  • Improve image delivery

    1.8 s · 1.3 MB

    11 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 1.8 s faster on a phone.

  • Reduce unused CSS

    1.2 s · 288 KiB

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

  • Mobile performance score: 43

    43/100

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

  • Font display

    950 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 2.0 MB and 712 ms of main-thread time.

  • YouTube adds 311 ms

    311 ms

    YouTube costs a phone 311 ms of main-thread work and 1.0 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.

  • Google Tag Manager adds 259 ms

    259 ms

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

  • Main-thread work: 2.6 s

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

  • 9 long tasks on the main thread

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

  • Legacy JavaScript

    22 KiB

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

  • Minify JavaScript

    9 KiB

    9 KiB could be saved by minifying JavaScript.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • 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: 8 ms

    8 ms

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

Core Web Vitals

12 to fix0
  • 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 LCP: 5.2 s

    5.2 s

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

  • Real-user CLS: 0.35

    0.35

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

  • Real-user FCP: 3.4 s

    3.4 s

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

  • Real-user TTFB: 2.8 s

    2.8 s

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

  • Largest Contentful Paint: 27.8 s

    27.8 s

    Your largest element takes 27.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 15.6 s

    15.6 s

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

  • Time to Interactive: 28.1 s

    28.1 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Real-user INP: 204 ms

    204 ms

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

  • Cumulative Layout Shift: 0.25

    0.25

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

  • 8 images without width and height

    8 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-14, real Chrome visitors' tap response (inp) went from 159 ms to 169 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

    +10%

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

1 checks passed
  • Total Blocking Time: 188 ms

    188 ms

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

Images and page weight

1 to fix0
  • Page weight: 4.9 MB in 207 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 207 requests on a phone: scripts 2.3 MB (110), images 1.9 MB (19) and stylesheets 364 KiB (42). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.39 g

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

Accessibility

7 to fix69
  • Form elements do not have associated labels

    Form elements do not have associated labels (1 element).

  • Zoom is disabled

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

  • 6 text elements with low contrast

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

  • 5 links without text

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

  • 4 tap targets too small

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Headings skip levels

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

1 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

SEO

2 to fixGoogle 8588
  • No H1 headline

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 112 internal links, 7 external

    The homepage links to 112 pages on aldelis.com and 7 external pages.

7 checks passed
  • Meta description: 125 characters

    Your meta description is 125 characters: “Marca de alimentación dedicada a la comercialización de productos frescos y elaborados a base de pollo y pavo principal…”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Aldelís, ingredientes excelentes, alimentos deliciosos”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization 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.aldelis.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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

Other pages

4 to fix78
  • 2 pages share a title

    / and https://www.aldelis.com/en all use the title “Aldelís, ingredientes excelentes, alimentos deliciosos”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://www.aldelis.com/nosotros, https://www.aldelis.com/historia and https://www.aldelis.com/nuestros-productos/adobados have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.aldelis.com/nuestros-productos/adobados, whose canonical is https://www.aldelis.com/nuestros-productos/nuestras-gamas/adobados. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.aldelis.com/en has no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://www.aldelis.com/nosotros, https://www.aldelis.com/historia and https://www.aldelis.com/nuestros-productos/adobados took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 4 pages that loaded have a <title>.

Best practices

2 to fixGoogle 6988
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix60
  • 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 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 841 words of copy

    The homepage carries about 841 words of visible text.

3 checks passed
  • 2 short forms

    2 short forms (2 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.

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 aldelis.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
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 41 issues on aldelis.com, including 23 speed issues, 2 SEO issues and 2 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