Website review, no card needed
maxmilhas.com.br website review
Visit site (opens in a new tab)Reviewed 6 November 202625 issues · 65 checks
This review found 25 issues worth fixing on maxmilhas.com.br, 8 of them high impact, across 65 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 5.8 s |
| May 23, 2026 | 5.6 s |
| May 30, 2026 | 5.5 s |
| Jun 6, 2026 | 5.5 s |
| Jun 13, 2026 | 5.2 s |
| Jun 20, 2026 | 4.6 s |
| Jun 27, 2026 | 4.2 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.4 s |
| Jul 18, 2026 | 5.1 s |
| Jul 25, 2026 | 5.3 s |
| Aug 1, 2026 | 5.3 s |
| Aug 8, 2026 | 5.2 s |
| Aug 15, 2026 | 4.9 s |
| Aug 22, 2026 | 4.8 s |
| Aug 29, 2026 | 4.7 s |
| Sep 5, 2026 | 4.6 s |
| Sep 12, 2026 | 4.7 s |
| Sep 19, 2026 | 4.7 s |
| Sep 26, 2026 | 4.6 s |
| Oct 3, 2026 | 4.7 s |
| Oct 10, 2026 | 4.9 s |
| Oct 17, 2026 | 5.1 s |
| Oct 24, 2026 | 5.6 s |
| Oct 31, 2026 | 5.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 389 ms |
| May 23, 2026 | 379 ms |
| May 30, 2026 | 373 ms |
| Jun 6, 2026 | 375 ms |
| Jun 13, 2026 | 373 ms |
| Jun 20, 2026 | 376 ms |
| Jun 27, 2026 | 382 ms |
| Jul 4, 2026 | 382 ms |
| Jul 11, 2026 | 387 ms |
| Jul 18, 2026 | 400 ms |
| Jul 25, 2026 | 417 ms |
| Aug 1, 2026 | 478 ms |
| Aug 8, 2026 | 600 ms |
| Aug 15, 2026 | 762 ms |
| Aug 22, 2026 | 910 ms |
| Aug 29, 2026 | 959 ms |
| Sep 5, 2026 | 932 ms |
| Sep 12, 2026 | 850 ms |
| Sep 19, 2026 | 777 ms |
| Sep 26, 2026 | 732 ms |
| Oct 3, 2026 | 706 ms |
| Oct 10, 2026 | 714 ms |
| Oct 17, 2026 | 713 ms |
| Oct 24, 2026 | 715 ms |
| Oct 31, 2026 | 722 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
750 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
3 third-party services on the page
3 third-party services load with your homepage (Blindado, icomoon.io and convisoappsec.com), adding 5 KiB and 6 ms of main-thread time.
Use efficient cache lifetimes
2 KiB1 file is served with short cache lifetimes, so returning visitors download them again (2 KiB).
3 checks passed
Mobile performance score: 100
100/100Your mobile performance score is 100. That is in Google's “good” band (90 and up).
Main-thread work: 0.2 s
A phone's processor spends 0.2 s on main-thread work while loading, 25 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 INP: 897 ms
897 msReal visitors wait 897 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.16
0.16For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.
Tap response (INP) got 87% slower for real visitors
+87%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 389 ms to 722 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-31, real Chrome visitors' largest content (lcp) went from 5.8 s to 5.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 546 ms
546 msReal visitors wait 546 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 0.9 s
0.9 sYour largest element renders in 0.9 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Não encontramos a página que você procura”.
Speed Index: 1.0 s
1.0 sVisually, the page fills in at 1.0 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Time to Interactive: 0.9 s
0.9 sThe page is fully interactive after 0.9 s.
Images and page weight
1 image far larger than shown
81 KiB1 image is downloaded at several times the size a phone draws it, for example 672a71b0b6236sticker_maxradar_comecesuaviagem_v3.webp at 918 px wide, shown at 90 px. Resized copies would save about 81 KiB.
About 0.06 g of CO₂ per visit
0.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.06 g of CO₂e: 6.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 205 KiB in 20 requests
205 KiBYour homepage downloads 205 KiB in 20 requests on a phone: scripts 188 KiB (16), HTML 14 KiB (1) and stylesheets 3 KiB (2). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails 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.
56 form fields without a label
56 form fields have no label, so screen readers announce an empty box and autofill guesses.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
2 checks passed
Every image has alt text
All 3 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Error status code
The page answers with an error status, so search engines may drop it.
No XML sitemap
No XML sitemap at https://www.maxmilhas.com.br/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at maxmilhas.com.br/robots.txt, the first file search crawlers ask for.
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 favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
6 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “A Maxmilhas oferece as melhores opções de passagens aéreas, reservas de hotéis e venda de milhas em um só lugar. Econom…”.
One H1 headline
Your main headline reads: “Viva sua viagem ao máximo”.
Title: 54 characters
Your title is a healthy 54 characters: “Passagens Aéreas, Hotéis e Venda de Milhas | Maxmilhas”.
Canonical URL set
The canonical URL is https://www.maxmilhas.com.br/.
Structured data in place
Structured data found: Airline.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
AI search readiness
Most text only appears after JavaScript runs
5%A phone browser shows 364 words, but the HTML your server sends has only 19. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
No llms.txt
There is no https://www.maxmilhas.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.
1 checks passed
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=151021707&tm=gtm002&Ver=2&mid=11054813-f8e0-4c04-90a6-a3180b2b11f1&bo=1&sid=41501eb0da3211f1844fa779e688fc74&vid=41502fb0da3211f1a61d6589176c43bc&vids=1&msclkid=N>m_.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 500 ()”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
2 checks passed
Tap targets are thumb-sized
19 of 21 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 364 words of copy
The homepage carries about 364 words of visible text.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 3 mores (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
18Opening 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.
29 other companies contacted
Loading the homepage contacts 29 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 maxmilhas.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
- Next.js
- Hosting
- CloudFront
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 maxmilhas.com.br, including 5 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.