addi.com website review

Framer CDN costs a phone 1.5 s of main-thread work and 2.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

A phone's processor spends 5.6 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 load with your homepage (Framer CDN, Google Tag Manager and TikTok and others), adding 3.6 MB and 2.7 s of main-thread time.

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

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

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

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

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

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

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

About 14 KiB of CSS is downloaded but never applied on this page.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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.

Your largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Celular mostrando una confirmación de compra con Addi”.

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

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

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

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

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

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

Your homepage downloads 3.8 MB in 166 requests on a phone: images 1.9 MB (85), scripts 1.6 MB (53) and fonts 166 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

1 image is downloaded at several times the size a phone draws it, for example CmVsMwqzTN4VrPi8MO7OdPOY4a0.png at 412 px wide, shown at 78 px. Resized copies would save about 33 KiB.

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

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

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

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

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

There are 5 <h1> headlines (“Compra lo que quieres hoy, págalo después”, “Compra loque quieres hoy, págalo después” and “Descarga la app”). One clear main headline is easier for people and search engines.

1 link has no real href, so search engines can't follow it.

The homepage links to 71 pages on addi.com and 43 external pages.

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.

There is no /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.

/, /%C3%A9tica-y-conducta and /tyc-links-addi all use the title “Paga a cuotas sin papeleos ni tarjeta de crédito con Addi”. Search engines can't tell which page to show for a search, so each competes with the others.

/%C3%A9tica-y-conducta, /tyc-links-addi, /pp, /pa, /pp-addi-tecnologia and /pa-addi-tecnologia use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /ofertas/minutoganador2026, whose canonical is /ofertas/minutoganador. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/pa-addi-tecnologia took over 3 s to send its HTML from our server.

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

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

HSTS is set, but max-age is 30 days; one year is the recommended minimum.

2 links go through two or more redirects, for example https://addi.onelink.me/FhId?af_xp=custom&addishop://screenName=FEATURE_JOURNEY_AUTHENTICATED_HOME&guestScreenName=FEATURE_JOURNEY_GUEST_HOME.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

addi.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

addi.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 900 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads 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.

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.

Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.