Website review, no card needed

mahalo.com.br logo

mahalo.com.br website review

Visit site (opens in a new tab)Reviewed 26 October 202625 issues · 59 checks

This review found 25 issues worth fixing on mahalo.com.br, 8 of them high impact, across 59 checks. The most urgent: page weight: 31.9 MB in 36 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
3.2 s2.5 sMay 9Oct 243.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.6 s
May 16, 20263.0 s
May 23, 20262.9 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20263.0 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20263.1 s
Jul 18, 20263.1 s
Jul 25, 20263.1 s
Aug 1, 20263.1 s
Aug 8, 20263.0 s
Aug 15, 20262.9 s
Aug 22, 20262.9 s
Aug 29, 20262.8 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20262.8 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20262.9 s
Oct 17, 20263.0 s
Oct 24, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
218 ms131 msMay 9Oct 24150 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026159 ms
May 16, 2026168 ms
May 23, 2026157 ms
May 30, 2026152 ms
Jun 6, 2026163 ms
Jun 13, 2026171 ms
Jun 20, 2026178 ms
Jun 27, 2026182 ms
Jul 4, 2026193 ms
Jul 11, 2026188 ms
Jul 18, 2026166 ms
Jul 25, 2026166 ms
Aug 1, 2026147 ms
Aug 8, 2026141 ms
Aug 15, 2026153 ms
Aug 22, 2026200 ms
Aug 29, 2026197 ms
Sep 5, 2026208 ms
Sep 12, 2026181 ms
Sep 19, 2026157 ms
Sep 26, 2026142 ms
Oct 3, 2026142 ms
Oct 10, 2026149 ms
Oct 17, 2026143 ms
Oct 24, 2026150 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 mahalo.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mahalo.com.br at 0.6 s0.6 s
  2. mahalo.com.br at 1.3 s1.3 s
  3. mahalo.com.br at 1.9 s1.9 s
  4. mahalo.com.br at 2.5 s2.5 s
  5. mahalo.com.br at 3.2 s3.2 s
  6. mahalo.com.br at 3.8 s3.8 s
  7. mahalo.com.br at 4.4 s4.4 s
  8. mahalo.com.br at 5.0 s5.0 s

Speed

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, RD Station and cloudfront.net and others), adding 228 KiB and 223 ms of main-thread time.

2 checks passed
  • Main-thread work: 1.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 399 ms of it running JavaScript. That is comfortably low.

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

6 to fix67
  • 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 LCP: 3.3 s

    3.3 s

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Real-user TTFB: 1.8 s

    1.8 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 4 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

5 checks passed
  • Real-user INP: 188 ms

    188 ms

    Real visitors wait 188 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.

  • Tap response (INP) got 10% faster for real visitors

    -10%

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

  • Speed Index: 3.4 s

    3.4 s

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

  • Cumulative Layout Shift: 0.02

    0.02

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

Images and page weight

4 to fix25
  • Page weight: 31.9 MB in 36 requests

    31.9 MB

    Your homepage downloads 31.9 MB in 36 requests on a phone: images 31.5 MB (14), scripts 349 KiB (13) and fonts 27 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    lp-hero-wide.jpg weighs 1.4 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    1.3 MB

    1 image is downloaded at several times the size a phone draws it, for example lp-hero-wide.jpg at 4,516 px wide, shown at 400 px. Resized copies would save about 1.3 MB.

  • 1 image in older formats

    1 image (1.4 MB) is 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.

  • About 9.0 g of CO₂ per visit

    9.04 g

    By the Sustainable Web Design model, a visit to your homepage emits about 9.04 g of CO₂e: 1084.5 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

4 to fixGoogle 8993
  • 2 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

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

SEO

4 to fixGoogle 10084
  • Title is short (21 characters)

    Your title is only 21 characters: “Mahalo | Landing Page”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 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://mahalo.com.br/sitemap.xml, so Google discovers your pages only by following links.

  • Only 1 internal link

    The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.

  • No X (Twitter) card tag

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

5 checks passed
  • Meta description: 88 characters

    Your meta description is 88 characters: “Mahalo significa gratidão: conheça nossa história, valores e lojas em Salvador e região.”.

  • One H1 headline

    Your main headline reads: “Surf como filosofia, gratidão como norte.”.

  • Canonical URL set

    The canonical URL is https://mahalo.com.br/.

  • Structured data in place

    Structured data found: Store and WebSite.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://mahalo.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 (431 words), so crawlers that don't run JavaScript still read it.

Best practices

Google 100100
2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

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

  • 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 opening hours

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

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

    The homepage carries about 431 words of visible text.

2 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    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.

  • 2 cookies set on arrival

    2

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 mahalo.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

Framework
Nuxt
Analytics
Google Tag Manager
Hosting
Cidnoc

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on mahalo.com.br, including 6 speed issues, 4 SEO issues and 5 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