Website review, no card needed

hiperideal.com.br logo

hiperideal.com.br website review

Visit site (opens in a new tab)Reviewed 30 October 202655 issues · 91 checks

This review found 55 issues worth fixing on hiperideal.com.br, 22 of them high impact, across 91 checks. The most urgent: render-blocking 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.2 s3.8 sMay 9Oct 244.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.9 s
May 16, 20263.9 s
May 23, 20263.9 s
May 30, 20263.9 s
Jun 6, 20263.9 s
Jun 13, 20263.9 s
Jun 20, 20263.9 s
Jun 27, 20263.9 s
Jul 4, 20263.9 s
Jul 11, 20263.9 s
Jul 18, 20263.9 s
Jul 25, 20264.0 s
Aug 1, 20264.0 s
Aug 8, 20264.0 s
Aug 15, 20264.0 s
Aug 22, 20263.9 s
Aug 29, 20263.8 s
Sep 5, 20263.9 s
Sep 12, 20263.9 s
Sep 19, 20263.9 s
Sep 26, 20263.9 s
Oct 3, 20263.9 s
Oct 10, 20264.0 s
Oct 17, 20264.1 s
Oct 24, 20264.2 s
Real-visitor tap response (INP)75th percentile, phones
232 ms183 msMay 9Oct 24221 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026197 ms
May 16, 2026191 ms
May 23, 2026189 ms
May 30, 2026192 ms
Jun 6, 2026193 ms
Jun 13, 2026199 ms
Jun 20, 2026200 ms
Jun 27, 2026201 ms
Jul 4, 2026204 ms
Jul 11, 2026197 ms
Jul 18, 2026195 ms
Jul 25, 2026198 ms
Aug 1, 2026192 ms
Aug 8, 2026190 ms
Aug 15, 2026194 ms
Aug 22, 2026192 ms
Aug 29, 2026196 ms
Sep 5, 2026205 ms
Sep 12, 2026204 ms
Sep 19, 2026204 ms
Sep 26, 2026209 ms
Oct 3, 2026209 ms
Oct 10, 2026219 ms
Oct 17, 2026226 ms
Oct 24, 2026221 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 hiperideal.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hiperideal.com.br at 1.2 s1.2 s
  2. hiperideal.com.br at 2.3 s2.3 s
  3. hiperideal.com.br at 3.5 s3.5 s
  4. hiperideal.com.br at 4.7 s4.7 s
  5. hiperideal.com.br at 5.9 s5.9 s
  6. hiperideal.com.br at 7.0 s7.0 s
  7. hiperideal.com.br at 8.2 s8.2 s
  8. hiperideal.com.br at 9.4 s9.4 s

Speed

14 to fix32
  • Render-blocking requests

    3.1 s

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

  • vtexassets.com adds 1.8 s

    1.8 s

    vtexassets.com costs a phone 1.8 s of main-thread work and 2.7 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.

  • Mobile performance score: 32

    32/100

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

  • Main-thread work: 8.7 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (vtexassets.com, Google CDN and Google Tag Manager and others), adding 4.5 MB and 4.1 s of main-thread time.

  • Improve image delivery

    150 ms · 1.7 MB

    12 images could be 1.7 MB 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.

  • Reduce unused JavaScript

    150 ms · 995 KiB

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

  • Use efficient cache lifetimes

    500 ms · 460 KiB

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

  • Google CDN adds 820 ms

    820 ms

    Google CDN costs a phone 820 ms of main-thread work and 743 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.

  • Google Tag Manager adds 675 ms

    675 ms

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

  • 20 long tasks on the main thread

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

  • Facebook adds 484 ms

    484 ms

    Facebook costs a phone 484 ms of main-thread work and 310 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.

  • Legacy JavaScript

    300 ms · 49 KiB

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

  • 1,574 HTML elements

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

  • Reduce unused CSS

    33 KiB

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

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 43 ms

    43 ms

    Your server sent the HTML in 43 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 FCP: 3.5 s

    3.5 s

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

  • Time to Interactive: 21.8 s

    21.8 s

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

  • Largest Contentful Paint: 8.4 s

    8.4 s

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

  • Total Blocking Time: 2.6 s

    2.6 s

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

  • Speed Index: 9.0 s

    9.0 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Real-user LCP: 3.8 s

    3.8 s

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

  • Real-user INP: 240 ms

    240 ms

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

  • Real-user CLS: 0.23

    0.23

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • 14 images without width and height

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

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

    +15%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

1 checks passed
  • Cumulative Layout Shift: 0.053

    0.053

    The layout barely moves while loading (CLS 0.053, good is under 0.1).

Images and page weight

4 to fix35
  • Page weight: 5.1 MB in 186 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 186 requests on a phone: scripts 2.4 MB (57), images 1.9 MB (37) and other files 383 KiB (38). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    bd72d733-1832-46ab-aab4-d26ff7d857fe___41085ab776d6e2d8da156 weighs 1.5 MB. On a phone connection a single image that size takes seconds.

  • 2 images in older formats

    2 images (1.6 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 2 images far larger than shown

    339 KiB

    2 images are downloaded at several times the size a phone draws them, for example bd72d733-1832-46ab-aab4-d26ff7d857fe___41085ab776d6e2d8da156 at 1,226 px wide, shown at 374 px. Resized copies would save about 339 KiB.

  • About 1.5 g of CO₂ per visit

    1.46 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

9 to fixGoogle 7485
  • Unlabelled dropdowns

    5 dropdowns have no label.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 43 text elements with low contrast

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

  • 37 tap targets too small

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

  • 56 images without alt text

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

  • All page content should be contained by landmarks (19 elements)

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

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

  • 12 links without text

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

  • 6 form fields without a label

    6 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (5 elements).

1 checks passed
  • 39 automated accessibility rules passed

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

SEO

6 to fixGoogle 8562
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (26 characters)

    Your title is only 26 characters: “Hiperideal | Supermercados”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 1 problem

    Structured data found (ItemList and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.lojavazia.com.br/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 48 internal links, 11 external

    The homepage links to 48 pages on hiperideal.com.br and 11 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://www.hiperideal.com.br/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

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://www.hiperideal.com.br/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 (1,162 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 7 pages share a title

    /, https://www.hiperideal.com.br/fale-com-a-gente, https://www.hiperideal.com.br/institucional/nossas-lojas, https://www.hiperideal.com.br/descontos, https://www.hiperideal.com.br/clube-ideal and https://www.hiperideal.com.br/especial/encartes and 1 other all use the title “Hiperideal | Supermercados”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages without a meta description

    https://www.hiperideal.com.br/fale-com-a-gente, https://www.hiperideal.com.br/institucional/nossas-lojas, https://www.hiperideal.com.br/descontos, https://www.hiperideal.com.br/clube-ideal, https://www.hiperideal.com.br/encarte-semanal and https://www.hiperideal.com.br/especial/adegaideal and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://www.hiperideal.com.br/descontos, https://www.hiperideal.com.br/clube-ideal, https://www.hiperideal.com.br/encarte-semanal, https://www.hiperideal.com.br/especial/adegaideal, https://www.hiperideal.com.br/lancamentoideal and https://www.hiperideal.com.br/exclusivo-no-ideal and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.hiperideal.com.br/descontos and https://www.hiperideal.com.br/clube-ideal have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 5 pages slow to respond

    https://www.hiperideal.com.br/especial/adegaideal, https://www.hiperideal.com.br/lancamentoideal, https://www.hiperideal.com.br/exclusivo-no-ideal, https://www.hiperideal.com.br/especial/encartes and https://www.hiperideal.com.br/tropinhaideal took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • 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

2 to fixGoogle 9687
  • 11 small tap targets

    11 of 46 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix38
  • No call to action on the first screen

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

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 546 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and TikTok Pixel.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 18 cookies set on arrival

    18

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

  • 24 other companies contacted

    Loading the homepage contacts 24 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 hiperideal.com.br, 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
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 55 issues on hiperideal.com.br, including 26 speed issues, 6 SEO 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