Website review, no card needed

hey.inc logo

hey.inc website review

Visit site (opens in a new tab)Reviewed 30 October 202627 issues · 79 checks

This review found 27 issues worth fixing on hey.inc, 8 of them high impact, across 79 checks. The most urgent: page weight: 9.4 MB in 545 requests. 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
4.7 s3.9 sMay 9Oct 244.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.3 s
May 16, 20264.5 s
May 23, 20264.6 s
May 30, 20264.6 s
Jun 6, 20264.5 s
Jun 13, 20264.4 s
Jun 20, 20264.3 s
Jun 27, 20264.2 s
Jul 4, 20264.1 s
Jul 11, 20264.1 s
Jul 18, 20264.1 s
Jul 25, 20264.1 s
Aug 1, 20264.1 s
Aug 8, 20264.1 s
Aug 15, 20264.1 s
Aug 22, 20264.1 s
Aug 29, 20264.0 s
Sep 5, 20264.0 s
Sep 12, 20264.0 s
Sep 19, 20264.1 s
Sep 26, 20264.1 s
Oct 3, 20264.2 s
Oct 10, 20264.3 s
Oct 17, 20264.4 s
Oct 24, 20264.4 s
Real-visitor tap response (INP)75th percentile, phones
158 ms142 msMay 9Oct 24156 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026146 ms
May 16, 2026144 ms
May 23, 2026146 ms
May 30, 2026145 ms
Jun 6, 2026147 ms
Jun 13, 2026147 ms
Jun 20, 2026146 ms
Jun 27, 2026149 ms
Jul 4, 2026150 ms
Jul 11, 2026151 ms
Jul 18, 2026152 ms
Jul 25, 2026152 ms
Aug 1, 2026148 ms
Aug 8, 2026147 ms
Aug 15, 2026146 ms
Aug 22, 2026146 ms
Aug 29, 2026149 ms
Sep 5, 2026150 ms
Sep 12, 2026149 ms
Sep 19, 2026150 ms
Sep 26, 2026150 ms
Oct 3, 2026152 ms
Oct 10, 2026154 ms
Oct 17, 2026154 ms
Oct 24, 2026156 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 hey.inc (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hey.inc at 0.4 s0.4 s
  2. hey.inc at 0.8 s0.8 s
  3. hey.inc at 1.1 s1.1 s
  4. hey.inc at 1.5 s1.5 s
  5. hey.inc at 1.9 s1.9 s
  6. hey.inc at 2.3 s2.3 s
  7. hey.inc at 2.6 s2.6 s
  8. hey.inc at 3.0 s3.0 s

Speed

6 to fix68
  • Mobile performance score: 68

    68/100

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

  • Reduce unused JavaScript

    300 ms · 555 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, TikTok and Facebook and others), adding 835 KiB and 558 ms of main-thread time.

  • Render-blocking requests

    450 ms

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

  • Google Tag Manager adds 392 ms

    392 ms

    Google Tag Manager costs a phone 392 ms of main-thread work and 516 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.3 s

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

  • Reduce unused CSS

    150 ms · 45 KiB

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

  • Use efficient cache lifetimes

    156 KiB

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

  • 10 long tasks on the main thread

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

  • Legacy JavaScript

    42 KiB

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

  • Duplicated JavaScript

    11 KiB

    11 KiB JavaScript is shipped twice across bundles.

  • Improve image delivery

    10 KiB

    1 image could be 10 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

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

    79 ms

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

Core Web Vitals

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

  • Cumulative Layout Shift: 1.011

    1.011

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

  • Time to Interactive: 11.1 s

    11.1 s

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

  • Real-user TTFB: 885 ms

    885 ms

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

  • Total Blocking Time: 300 ms

    300 ms

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

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

7 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 165 ms

    165 ms

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

  • 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 FCP: 1.6 s

    1.6 s

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

  • Speed Index: 3.1 s

    3.1 s

    Visually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • Largest Contentful Paint: 1.7 s

    1.7 s

    Your largest element renders in 1.7 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image.

  • First Contentful Paint: 1.1 s

    1.1 s

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

Images and page weight

2 to fix64
  • Page weight: 9.4 MB in 545 requests

    9.4 MB

    Your homepage downloads 9.4 MB in 545 requests on a phone: images 8.0 MB (487), scripts 1.1 MB (21) and fonts 171 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    LogoHeyBanco.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 2.7 g of CO₂ per visit

    2.66 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 8794
  • 7 images without alt text

    7 images have no alt text, which hurts accessibility and image search.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 links without text

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

  • Headings skip levels

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

1 checks passed
  • 35 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 92100
  • 156 internal links, 9 external

    The homepage links to 156 pages on hey.inc and 9 external pages.

8 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “Controla tu dinero desde tu smartphone. Abre tu cuenta bancaria en minutos con la App Hey Banco. Sin filas ni trámites …”.

  • One H1 headline

    Your main headline reads: “Maneja tu dinero desde tu Banco Digital”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “La aplicación más poderosa para tus finanzas | Hey Banco”.

  • Canonical URL set

    The canonical URL is https://banco.hey.inc/.

  • Structured data in place

    Structured data found: BreadcrumbList and WebPage.

  • 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://banco.hey.inc/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://banco.hey.inc/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.

  • Text is in the HTML

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

Other pages

3 to fix81
  • 1 page points its canonical at the homepage

    https://banco.hey.inc/universo-hey.html declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 4 pages share 2 titles

    / and https://banco.hey.inc/universo-hey.html all use the title “La aplicación más poderosa para tus finanzas | Hey Banco”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://banco.hey.inc/universo-hey/ahorra-e-invierte.html and https://banco.hey.inc/universo-hey/ahorra-e-invierte/ahorro-hey.html use the same meta description. A description written for each page earns more clicks.

  • 9 pages slow to respond

    https://banco.hey.inc/universo-hey.html, https://banco.hey.inc/universo-hey/para-ti-o-tu-negocio.html, https://banco.hey.inc/universo-hey/para-ti-o-tu-negocio/tarjetas-de-credito-hey.html, https://banco.hey.inc/universo-hey/para-ti-o-tu-negocio/creditos-hey.html, https://banco.hey.inc/universo-hey/para-ti-o-tu-negocio/nomina-en-hey.html and https://banco.hey.inc/universo-hey/para-ti-o-tu-negocio/seguros-hey.html and 3 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

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

Best practices

2 to fixGoogle 9687
  • 10 small tap targets

    10 of 21 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 “Failed to load resource: the server responded with a status of 403 (Forbidden)”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 direct contact details

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

  • No form on the homepage

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

  • 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 591 words of copy

    The homepage carries about 591 words of visible text.

2 checks passed
  • Clear next step on the first screen

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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.

  • 12 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
Google Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on hey.inc, including 11 speed issues and 3 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