Website review, no card needed

alice.com.br logo

alice.com.br website review

Visit site (opens in a new tab)Reviewed 17 November 202640 issues · 83 checks

This review found 40 issues worth fixing on alice.com.br, 19 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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
3.9 s1.8 sMay 30Nov 143.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.8 s
Aug 15, 20263.0 s
Aug 22, 20263.1 s
Aug 29, 20263.1 s
Sep 5, 20263.0 s
Sep 12, 20263.1 s
Sep 19, 20263.2 s
Sep 26, 20263.2 s
Oct 3, 20263.2 s
Oct 10, 20263.5 s
Oct 17, 20263.5 s
Oct 24, 20263.6 s
Oct 31, 20263.7 s
Nov 7, 20263.4 s
Nov 14, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
421 ms198 msMay 30Nov 14306 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026227 ms
Jun 6, 2026225 ms
Jun 13, 2026224 ms
Jun 20, 2026224 ms
Jun 27, 2026232 ms
Jul 4, 2026236 ms
Jul 11, 2026239 ms
Jul 18, 2026235 ms
Jul 25, 2026226 ms
Aug 1, 2026228 ms
Aug 8, 2026278 ms
Aug 15, 2026348 ms
Aug 22, 2026376 ms
Aug 29, 2026387 ms
Sep 5, 2026388 ms
Sep 12, 2026376 ms
Sep 19, 2026387 ms
Sep 26, 2026395 ms
Oct 3, 2026395 ms
Oct 10, 2026386 ms
Oct 17, 2026358 ms
Oct 24, 2026343 ms
Oct 31, 2026312 ms
Nov 7, 2026289 ms
Nov 14, 2026306 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 alice.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alice.com.br at 0.4 s0.4 s
  2. alice.com.br at 0.9 s0.9 s
  3. alice.com.br at 1.3 s1.3 s
  4. alice.com.br at 1.7 s1.7 s
  5. alice.com.br at 2.2 s2.2 s
  6. alice.com.br at 2.6 s2.6 s
  7. alice.com.br at 3.0 s3.0 s
  8. alice.com.br at 3.5 s3.5 s

Speed

11 to fix39
  • Reduce unused JavaScript

    3.5 s · 762 KiB

    About 762 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.

  • Use efficient cache lifetimes

    1.4 s · 451 KiB

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

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 39

    39/100

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

  • Main-thread work: 5.6 s

    A phone's processor spends 5.6 s on main-thread work while loading, 3.3 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 (website-files.com, Google Tag Manager and Cookie-Script.com and others), adding 2.3 MB and 2.1 s of main-thread time.

  • Reduce unused CSS

    910 ms · 142 KiB

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

  • website-files.com adds 726 ms

    726 ms

    website-files.com costs a phone 726 ms of main-thread work and 1,022 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 671 ms

    671 ms

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

  • 16 long tasks on the main thread

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

  • Cookie-Script.com adds 347 ms

    347 ms

    Cookie-Script.com costs a phone 347 ms of main-thread work and 31 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.

  • Document request latency

    107 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Improve image delivery

    86 KiB

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

  • Legacy JavaScript

    29 KiB

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

  • Minify JavaScript

    8 KiB

    8 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: 12 ms

    12 ms

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

Core Web Vitals

13 to fix33
  • 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.7 s

    3.7 s

    Real visitors see the first content after 3.7 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.

  • Largest Contentful Paint: 19.7 s

    19.7 s

    Your largest element takes 19.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mulher com cabelo longo e liso, veste blazer e olha para o …”.

  • Time to Interactive: 22.6 s

    22.6 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Speed Index: 8.8 s

    8.8 s

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

  • Total Blocking Time: 788 ms

    788 ms

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

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

    460 ms

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

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

    +32%

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

  • Largest content (LCP) got 57% slower for real visitors

    +57%

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

  • 3 images without width and height

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

2 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.006

    0.006

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

Images and page weight

1 to fix85
  • Page weight: 2.9 MB in 152 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 152 requests on a phone: scripts 2.1 MB (70), images 283 KiB (20) and HTML 161 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.82 g

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

3 checks passed
  • 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.

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 8890
  • 6 text elements with low contrast

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

  • Elements must only use permitted ARIA attributes (4 elements)

    Elements must only use permitted ARIA attributes: 4 elements on the page fail this check, rated serious by axe-core.

  • 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 (54 elements)

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 38 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 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10093
  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: url is not an absolute URL ("/")”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 65 internal links, 14 external

    The homepage links to 65 pages on alice.com.br and 14 external pages.

6 checks passed
  • Meta description: 91 characters

    Your meta description is 91 characters: “A Alice sabe de saúde, por isso oferece o melhor plano de saúde para empresas. Simule agora”.

  • One H1 headline

    Your main headline reads: “O plano de saúde empresarial que une excelência médica, tecnologia e cuidado integral.”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “Alice - Plano de Saúde Empresarial”.

  • Canonical URL set

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

  • 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://alice.com.br/sitemap.xml.

AI search readiness

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://alice.com.br/llms.txt (25 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 2 pages without a meta description

    https://alice.com.br/alice-manifesto and https://alice.com.br/tech have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://alice.com.br/simulador has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • 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

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56384192&tm=gtm002&Ver=2&mid=6e38718f-4c88-4b2f-a174-d866a60ea90d&bo=1&sid=09ef1250e26611f1ab4a17b44c333123&vid=09ef4ef0e26611f1a7e309e8690b4e31&vids=1&msclkid=N&pi=91.

  • 15 small tap targets

    15 of 34 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 404 ()”.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 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 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 848 words of copy

    The homepage carries about 848 words of visible text.

2 checks passed
  • Social proof on the page

    Social proof on the homepage: 71 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager, HubSpot and Umami.

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies, 7 of them by other companies (measured from a US location before any click).

  • 42 other companies contacted

    Loading the homepage contacts 42 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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

CMS
Webflow
Framework
jQuery
Analytics
Google Tag Manager
Hosting
CloudFront

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on alice.com.br, including 24 speed issues, 2 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