Website review, no card needed

advancecare.pt logo

advancecare.pt website review

Visit site (opens in a new tab)Reviewed 20 November 202641 issues · 84 checks

This review found 41 issues worth fixing on advancecare.pt, 17 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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
7.4 s1.5 sMay 30Nov 142.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.5 s
Jun 6, 20263.7 s
Jun 13, 20263.7 s
Jun 20, 20263.8 s
Jun 27, 20264.0 s
Jul 4, 20264.2 s
Jul 11, 20264.5 s
Jul 18, 20264.9 s
Jul 25, 20265.5 s
Aug 1, 20265.7 s
Aug 8, 20266.5 s
Aug 15, 20266.7 s
Aug 22, 20265.7 s
Aug 29, 20265.2 s
Sep 5, 20264.6 s
Sep 12, 20264.2 s
Sep 19, 20264.7 s
Sep 26, 20264.5 s
Oct 3, 20263.8 s
Oct 10, 20263.0 s
Oct 17, 20262.5 s
Oct 24, 20262.3 s
Oct 31, 20262.2 s
Nov 7, 20262.2 s
Nov 14, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
173 ms160 msMay 30Nov 14166 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026162 ms
Jun 6, 2026161 ms
Jun 13, 2026163 ms
Jun 20, 2026163 ms
Jun 27, 2026166 ms
Jul 4, 2026167 ms
Jul 11, 2026166 ms
Jul 18, 2026164 ms
Jul 25, 2026164 ms
Aug 1, 2026165 ms
Aug 8, 2026166 ms
Aug 15, 2026168 ms
Aug 22, 2026169 ms
Aug 29, 2026169 ms
Sep 5, 2026171 ms
Sep 12, 2026168 ms
Sep 19, 2026167 ms
Sep 26, 2026168 ms
Oct 3, 2026165 ms
Oct 10, 2026166 ms
Oct 17, 2026165 ms
Oct 24, 2026164 ms
Oct 31, 2026165 ms
Nov 7, 2026165 ms
Nov 14, 2026166 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 advancecare.pt (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. advancecare.pt at 0.6 s0.6 s
  2. advancecare.pt at 1.2 s1.2 s
  3. advancecare.pt at 1.8 s1.8 s
  4. advancecare.pt at 2.4 s2.4 s
  5. advancecare.pt at 3.0 s3.0 s
  6. advancecare.pt at 3.6 s3.6 s
  7. advancecare.pt at 4.2 s4.2 s
  8. advancecare.pt at 4.8 s4.8 s

Speed

9 to fix30
  • Use efficient cache lifetimes

    1.4 s · 2.5 MB

    82 files are served with short cache lifetimes, so returning visitors download them again (2.5 MB).

  • Reduce unused JavaScript

    3.0 s · 603 KiB

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

  • Render-blocking requests

    3.0 s

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

  • Mobile performance score: 30

    30/100

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

  • Improve image delivery

    950 ms · 3.1 MB

    12 images could be 3.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and dashboard-visor.com and others), adding 1.0 MB and 770 ms of main-thread time.

  • Reduce unused CSS

    600 ms · 76 KiB

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

  • Legacy JavaScript

    450 ms · 73 KiB

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

  • Google Tag Manager adds 368 ms

    368 ms

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

  • 8 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 18 KiB

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

2 checks passed
  • Main-thread work: 1.8 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 18.9 s

    18.9 s

    Your largest element takes 18.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Para si Para empresas Institucional”.

  • Time to Interactive: 19.7 s

    19.7 s

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

  • Cumulative Layout Shift: 0.639

    0.639

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

  • Speed Index: 8.7 s

    8.7 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Real-user FCP: 2.1 s

    2.1 s

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

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

  • Total Blocking Time: 361 ms

    361 ms

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

  • Tap response (INP) held steady for real visitors

    +2%

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

4 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 150 ms

    150 ms

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

  • Real-user CLS: 0.08

    0.08

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

  • Largest content (LCP) got 38% faster for real visitors

    -38%

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

Images and page weight

5 to fix18
  • Page weight: 21.9 MB in 106 requests

    21.9 MB

    Your homepage downloads 21.9 MB in 106 requests on a phone: images 20.5 MB (58), scripts 1.2 MB (20) and stylesheets 89 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 16.2 MB together. On a phone connection a single image that size takes seconds.

  • 18 images far larger than shown

    16.2 MB

    18 images are downloaded at several times the size a phone draws them, for example fisioterapia-cardiorrespiratria.png at 8,000 px wide, shown at 250 px. Resized copies would save about 16.2 MB.

  • 29 images in older formats

    29 images (20.3 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.

  • 25 images below the first screen load straight away

    25 images further down the page (20.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.2 g of CO₂ per visit

    6.20 g

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

Accessibility

4 to fixGoogle 8894
  • 10 text elements with low contrast

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

  • <object> elements must have alternative text (1 element)

    <object> elements must have alternative text: 1 element on the page fails this check, rated serious 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.

  • 3 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 45 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 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

5 to fixGoogle 8582
  • Title is short (11 characters)

    Your title is only 11 characters: “AdvanceCare”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 25 links crawlers can't follow

    25 links have no real href, so search engines can't follow them.

  • No social preview image

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 88 internal links, 11 external

    The homepage links to 88 pages on advancecare.pt and 11 external pages.

5 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Saiba tudo o que temos para si na AdvanceCare. Conheça a oferta de seguros de saúde, a nossa rede médica e os melhores …”.

  • One H1 headline

    Your main headline reads: “Médico online AdvanceCare”.

  • Canonical URL set

    The canonical URL is https://www.advancecare.pt/para-si.

  • 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://www.advancecare.pt/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://www.advancecare.pt/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 (642 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 4 pages without a meta description

    https://www.advancecare.pt/para-empresas/medicina-no-trabalho/redion, https://www.advancecare.pt/para-si/rede-medica---external, https://www.advancecare.pt/pesquisa and https://www.advancecare.pt/para-si/myadvancecare have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages with very little text

    https://www.advancecare.pt/para-si/rede-medica---external and https://www.advancecare.pt/pesquisa 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.

  • 15 internal pages checked

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

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

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

Best practices

2 to fixGoogle 9687
  • 11 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

  • 2 low-resolution images

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • 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: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 10-field form

    Your longest form asks for 10 fields (0 required). Every extra field lowers completion.

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

    The homepage carries about 514 words of visible text.

1 checks passed
  • Analytics in place

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

Privacy and tracking

  • 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). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 13 cookies set on arrival

    13

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

  • 13 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 advancecare.pt, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2020.

Stack

Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Azure

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on advancecare.pt, including 18 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

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