Website review, no card needed

adereso.ai logo

adereso.ai website review

Visit site (opens in a new tab)Reviewed 4 November 202621 issues · 76 checks

This review found 21 issues worth fixing on adereso.ai, 4 of them high impact, across 76 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

Real-visitor load time (LCP)75th percentile, phones
7.5 s1.4 sMay 16Oct 312.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20266.8 s
May 23, 20266.4 s
May 30, 20264.8 s
Jun 6, 20263.5 s
Jun 13, 20262.5 s
Jun 20, 20262.3 s
Jun 27, 20262.1 s
Jul 4, 20262.2 s
Jul 11, 20262.3 s
Jul 18, 20262.4 s
Jul 25, 20262.7 s
Aug 1, 20262.6 s
Aug 8, 20262.5 s
Aug 15, 20262.6 s
Aug 22, 20262.5 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.6 s
Oct 17, 20262.7 s
Oct 24, 20262.7 s
Oct 31, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
644 ms157 msMay 16Oct 31588 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026246 ms
May 23, 2026219 ms
May 30, 2026213 ms
Jun 6, 2026221 ms
Jun 13, 2026221 ms
Jun 20, 2026306 ms
Jun 27, 2026282 ms
Jul 4, 2026293 ms
Jul 11, 2026319 ms
Jul 18, 2026345 ms
Jul 25, 2026345 ms
Aug 1, 2026367 ms
Aug 8, 2026345 ms
Aug 15, 2026343 ms
Aug 22, 2026405 ms
Aug 29, 2026409 ms
Sep 5, 2026405 ms
Sep 12, 2026420 ms
Sep 19, 2026340 ms
Sep 26, 2026294 ms
Oct 3, 2026309 ms
Oct 10, 2026358 ms
Oct 17, 2026453 ms
Oct 24, 2026554 ms
Oct 31, 2026588 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 adereso.ai (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. adereso.ai at 0.6 s0.6 s
  2. adereso.ai at 1.1 s1.1 s
  3. adereso.ai at 1.7 s1.7 s
  4. adereso.ai at 2.2 s2.2 s
  5. adereso.ai at 2.8 s2.8 s
  6. adereso.ai at 3.4 s3.4 s
  7. adereso.ai at 3.9 s3.9 s
  8. adereso.ai at 4.5 s4.5 s

Speed

7 to fix73
  • Reduce unused JavaScript

    900 ms · 310 KiB

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

  • Mobile performance score: 73

    73/100

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

  • Render-blocking requests

    700 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, dreamdata.cloud and simpleicons.org and others), adding 569 KiB and 543 ms of main-thread time.

  • Google Tag Manager adds 498 ms

    498 ms

    Google Tag Manager costs a phone 498 ms of main-thread work and 530 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: 3.1 s

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

  • 2,948 HTML elements

    The page has 2,948 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 12 long tasks on the main thread

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

  • Improve image delivery

    150 ms · 24 KiB

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

  • Legacy JavaScript

    50 ms · 23 KiB

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

  • Use efficient cache lifetimes

    31 KiB

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

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

    7 ms

    Your server sent the HTML in 7 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.

  • Real-user INP: 661 ms

    661 ms

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

  • Largest Contentful Paint: 6.6 s

    6.6 s

    Your largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Usamos cookies para que el sitio funcione, mejorar tu naveg…”.

  • Time to Interactive: 9.9 s

    9.9 s

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Tap response (INP) got 146% slower for real visitors

    +146%

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

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

  • 37 images without width and height

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

  • Total Blocking Time: 213 ms

    213 ms

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

6 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Real-user TTFB: 777 ms

    777 ms

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

  • Largest content (LCP) got 57% faster for real visitors

    -57%

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

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

  • Speed Index: 2.1 s

    2.1 s

    Visually, the page fills in at 2.1 s (Speed Index), inside the 3.4 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

100
  • About 0.5 g of CO₂ per visit

    0.46 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.46 g of CO₂e: 54.7 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.6 MB in 85 requests

    1.6 MB

    Your homepage downloads 1.6 MB in 85 requests on a phone: scripts 940 KiB (19), images 427 KiB (43) and fonts 90 KiB (2). 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

Google 100100
2 checks passed
  • Every image has alt text

    All 91 images in the HTML carry an alt attribute.

  • 20 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 20 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 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 10089
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Automatiza venta y postventa con inteligencia artificial | Adereso AI”.

  • Structured data has 1 problem

    Structured data found (FAQPage, Organization, SoftwareApplication and WebSite) but with 1 problem, for example “SoftwareApplication: image is not an absolute URL ("https://adereso.ai/media/wp/2025/10/portada-website-1.webp")”.

  • 136 internal links, 17 external

    The homepage links to 136 pages on adereso.ai and 17 external pages.

6 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Automatiza ventas y atención al cliente con IA en WhatsApp, Instagram y más canales. +150 empresas como Falabella y Wal…”.

  • One H1 headline

    Your main headline reads: “Convierte conversacionesen ventas con IA”.

  • Canonical URL set

    The canonical URL is https://adereso.ai/.

  • 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://adereso.ai/sitemap.xml.

AI search readiness

100
4 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 contact details; description would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://adereso.ai/llms.txt (6 KiB, 16 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

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

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

Best practices

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 2,681 words of copy

    The homepage carries about 2,681 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Pricing”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Pricing” and “¿Cómo funciona el modelo de pricing?”.

  • Social proof on the page

    Social proof on the homepage: 71 testimonial or review blocks, 5 customer or partner logos and 3 trust badges.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 5 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
Google

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on adereso.ai, including 16 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