Website review, no card needed

unimedrecife.com.br logo

unimedrecife.com.br website review

Visit site (opens in a new tab)Reviewed 30 October 202652 issues · 89 checks

This review found 52 issues worth fixing on unimedrecife.com.br, 22 of them high impact, across 89 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
2.5 s1.7 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.4 s
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.0 s
Sep 19, 20261.9 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.9 s
Oct 17, 20262.1 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
317 ms230 msMay 9Oct 24269 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026304 ms
May 16, 2026305 ms
May 23, 2026294 ms
May 30, 2026290 ms
Jun 6, 2026284 ms
Jun 13, 2026292 ms
Jun 20, 2026304 ms
Jun 27, 2026307 ms
Jul 4, 2026300 ms
Jul 11, 2026284 ms
Jul 18, 2026279 ms
Jul 25, 2026272 ms
Aug 1, 2026260 ms
Aug 8, 2026258 ms
Aug 15, 2026262 ms
Aug 22, 2026257 ms
Aug 29, 2026267 ms
Sep 5, 2026262 ms
Sep 12, 2026254 ms
Sep 19, 2026252 ms
Sep 26, 2026240 ms
Oct 3, 2026240 ms
Oct 10, 2026249 ms
Oct 17, 2026256 ms
Oct 24, 2026269 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 unimedrecife.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. unimedrecife.com.br at 0.9 s0.9 s
  2. unimedrecife.com.br at 1.9 s1.9 s
  3. unimedrecife.com.br at 2.8 s2.8 s
  4. unimedrecife.com.br at 3.7 s3.7 s
  5. unimedrecife.com.br at 4.6 s4.6 s
  6. unimedrecife.com.br at 5.6 s5.6 s
  7. unimedrecife.com.br at 6.5 s6.5 s
  8. unimedrecife.com.br at 7.4 s7.4 s

Speed

7 to fix30
  • Use efficient cache lifetimes

    4.5 s · 5.5 MB

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

  • Render-blocking requests

    6.8 s

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

  • Reduce unused JavaScript

    1.9 s · 339 KiB

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

  • Font display

    1.0 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.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

    850 ms · 954 KiB

    6 images could be 954 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.

  • Google Tag Manager adds 208 ms

    208 ms

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, goadopt.io and jQuery CDN and others), adding 809 KiB and 325 ms of main-thread time.

  • Reduce unused CSS

    160 ms · 65 KiB

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

  • 5 long tasks on the main thread

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

  • Minify JavaScript

    160 ms · 12 KiB

    12 KiB could be saved by minifying JavaScript.

  • Minify CSS

    160 ms · 9 KiB

    9 KiB could be saved by minifying CSS.

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

2 checks passed
  • Main-thread work: 1.4 s

    A phone's processor spends 1.4 s on main-thread work while loading, 612 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

13 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 CLS: 0.39

    0.39

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

  • Largest Contentful Paint: 10.1 s

    10.1 s

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

  • First Contentful Paint: 5.4 s

    5.4 s

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

  • Speed Index: 9.6 s

    9.6 s

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

  • Cumulative Layout Shift: 0.489

    0.489

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

  • Time to Interactive: 10.4 s

    10.4 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user INP: 336 ms

    336 ms

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 21 images without width and height

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

  • Total Blocking Time: 287 ms

    287 ms

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

1 checks passed
  • Tap response (INP) got 14% faster for real visitors

    -14%

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

Images and page weight

3 to fix53
  • Page weight: 6.1 MB in 105 requests

    6.1 MB

    Your homepage downloads 6.1 MB in 105 requests on a phone: images 4.9 MB (50), scripts 927 KiB (22) and fonts 191 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 30 images in older formats

    30 images (4.7 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.

  • 4 images below the first screen load straight away

    4 images further down the page (880 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.7 g of CO₂ per visit

    1.73 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

8 to fixGoogle 7988
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • 21 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

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

  • 48 links without text

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

  • 3 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 46 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

7 to fixGoogle 8263
  • 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.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No XML sitemap

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

  • No robots.txt

    There is no robots.txt at unimedrecife.com.br/robots.txt, the first file search crawlers ask for.

  • 3 links crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 19 internal links, 14 external

    The homepage links to 19 pages on unimedrecife.com.br and 14 external pages.

2 checks passed
  • Title: 44 characters

    Your title is a healthy 44 characters: “Unimed Recife - Atender você esse e o plano.”.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

3 to fix83
  • 3 pages share a title

    /, https://www.unimedrecife.com.br/transp_igualdade_salarial and https://www.unimedrecife.com.br/controller/ControllerAgendamentoForm.php all use the title “Unimed Recife - Atender você esse e o plano.”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages without a meta description

    https://www.unimedrecife.com.br/transp_igualdade_salarial, https://www.unimedrecife.com.br/privacidade/politica, https://www.unimedrecife.com.br/integridade, https://www.unimedrecife.com.br/odontounimed, https://www.unimedrecife.com.br/espaco-empresa and https://www.unimedrecife.com.br/portal_prestador and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://www.unimedrecife.com.br/transp_igualdade_salarial, https://www.unimedrecife.com.br/odontounimed, https://www.unimedrecife.com.br/portal_prestador, https://www.unimedrecife.com.br/vendas_adesao/allcare, https://www.unimedrecife.com.br/vendas_empresariais/pme2 and https://www.unimedrecife.com.br/vendas_empresariais/grandes_empresas and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.unimedrecife.com.br/odontounimed has 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.

  • 3 pages slow to respond

    https://www.unimedrecife.com.br/odontounimed, https://www.unimedrecife.com.br/espaco-empresa and https://www.unimedrecife.com.br/portal_prestador took over 3 s to send their HTML from our server.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 12 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 11 pages that loaded have a <title>.

Best practices

5 to fixGoogle 5881
  • 49 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 3 JavaScript errors while loading

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

  • Pasting is blocked

    A form field blocks pasting, which frustrates password managers and people on phones.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. 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 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 464 words of copy

    The homepage carries about 464 words of visible text.

2 checks passed
  • 19 short forms

    19 short forms (0 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 6 cookies set on arrival

    6

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

  • 10 other companies contacted

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

Hosting
Smart Telecomunicacoes E Servicos Ltda.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on unimedrecife.com.br, including 20 speed issues, 7 SEO issues and 4 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