conekta.com website review

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

8 third-party services load with your homepage (Google Tag Manager, website-files.com and Google Fonts and others), adding 5.2 MB and 1.2 s of main-thread time.

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

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

website-files.com costs a phone 471 ms of main-thread work and 4.2 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 costs a phone 646 ms of main-thread work and 920 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.

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

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

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

6 images could be 154 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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.

4 KiB could be saved by minifying CSS.

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 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NUEVO Conekta Bundle, una sola integración para todo México…”.

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

Real visitors wait 2.6 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-24, real Chrome visitors' tap response (inp) went from 90 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

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

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

Your homepage downloads 5.3 MB in 114 requests on a phone: images 3.7 MB (64), scripts 1.3 MB (34) and stylesheets 106 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

11 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: 88 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

Headings skip levels (h1 → h3 and h1 → h3), 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 12 <h1> headlines (“La forma más conveniente de pagar en México”, “14 añosperfeccionando los pagos en México” and “Todas las opciones para que cada mexicano pague c…”). One clear main headline is easier for people and search engines.

The homepage links to 48 pages on conekta.com and 20 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.

/solutions/billing has no meta description, so Google writes the search snippet from whatever text it finds.

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

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

1 link to other sites is dead, for example https://identity.conekta.com/Account/Register (503).

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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.

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

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

Opening the homepage sets 4 cookies (measured from a US location before any click).

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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.