Website review, no card needed

slmandic.edu.br logo

slmandic.edu.br website review

Visit site (opens in a new tab)Reviewed 26 October 202629 issues · 78 checks

This review found 29 issues worth fixing on slmandic.edu.br, 8 of them high impact, across 78 checks. The most urgent: fails Core Web Vitals for real visitors. 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
4.6 s3.3 sMay 2Oct 173.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.0 s
May 9, 20264.2 s
May 16, 20264.3 s
May 23, 20264.4 s
May 30, 20264.4 s
Jun 6, 20264.3 s
Jun 13, 20264.2 s
Jun 20, 20264.2 s
Jun 27, 20264.1 s
Jul 4, 20264.1 s
Jul 11, 20263.8 s
Jul 18, 20263.6 s
Jul 25, 20263.7 s
Aug 1, 20263.6 s
Aug 8, 20263.6 s
Aug 15, 20263.5 s
Aug 22, 20263.5 s
Aug 29, 20263.6 s
Sep 5, 20263.7 s
Sep 12, 20264.0 s
Sep 19, 20264.0 s
Sep 26, 20264.0 s
Oct 3, 20264.0 s
Oct 10, 20263.9 s
Oct 17, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
614 ms172 msMay 2Oct 17346 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026226 ms
May 9, 2026223 ms
May 16, 2026224 ms
May 23, 2026229 ms
May 30, 2026229 ms
Jun 6, 2026232 ms
Jun 13, 2026234 ms
Jun 20, 2026230 ms
Jun 27, 2026230 ms
Jul 4, 2026229 ms
Jul 11, 2026228 ms
Jul 18, 2026232 ms
Jul 25, 2026238 ms
Aug 1, 2026246 ms
Aug 8, 2026289 ms
Aug 15, 2026335 ms
Aug 22, 2026374 ms
Aug 29, 2026427 ms
Sep 5, 2026458 ms
Sep 12, 2026495 ms
Sep 19, 2026542 ms
Sep 26, 2026563 ms
Oct 3, 2026511 ms
Oct 10, 2026435 ms
Oct 17, 2026346 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 slmandic.edu.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. slmandic.edu.br at 0.7 s0.7 s
  2. slmandic.edu.br at 1.3 s1.3 s
  3. slmandic.edu.br at 2.0 s2.0 s
  4. slmandic.edu.br at 2.6 s2.6 s
  5. slmandic.edu.br at 3.3 s3.3 s
  6. slmandic.edu.br at 3.9 s3.9 s
  7. slmandic.edu.br at 4.6 s4.6 s
  8. slmandic.edu.br at 5.2 s5.2 s

Speed

11 to fix68
  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Facebook and Hubspot and others), adding 1.6 MB and 1.3 s of main-thread time.

  • Google Tag Manager adds 978 ms

    978 ms

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

  • Mobile performance score: 68

    68/100

    Your mobile performance score is 68 (desktop: 68). Pages that score under 90 lose visitors before the first paint.

  • Reduce initial server response time

    918 ms

    Reduce initial server response time. Google estimates savings of 918 ms on a phone.

  • Document request latency

    900 ms

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

  • Reduce unused JavaScript

    774 KiB

    About 774 KiB of JavaScript is downloaded but never used on this page.

  • Improve image delivery

    400 ms · 40 KiB

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

  • Main-thread work: 3.3 s

    A phone's processor spends 3.3 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Use efficient cache lifetimes

    303 KiB

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

  • Render-blocking requests

    300 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

  • Server response: 1.0 s

    1.0 s

    Your server takes 1.0 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 17 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 27 KiB

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

  • Legacy JavaScript

    24 KiB

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

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

Core Web Vitals

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

  • Time to Interactive: 18.5 s

    18.5 s

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

  • Speed Index: 7.9 s

    7.9 s

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

  • Total Blocking Time: 792 ms

    792 ms

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

  • Real-user INP: 283 ms

    283 ms

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

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

    +74%

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Largest Contentful Paint: 2.9 s

    2.9 s

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

  • 8 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -6%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.0 s to 3.8 s 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 CLS: 0.00

    0.00

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

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

    2.9 MB

    Your homepage downloads 2.9 MB in 92 requests on a phone: scripts 2.1 MB (45), images 655 KiB (32) and HTML 98 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (29 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • 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.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 9296
  • Hidden but focusable

    9 elements hidden from screen readers can still receive keyboard focus.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 178 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

Google 100100
  • 120 internal links, 23 external

    The homepage links to 120 pages on slmandic.edu.br and 23 external pages.

8 checks passed
  • Meta description: 98 characters

    Your meta description is 98 characters: “Portal institucional da São Leopoldo Mandic com cursos, unidades, notícias e conteúdos editoriais.”.

  • One H1 headline

    Your main headline reads: “Vestibular Medicina Mandic 2027”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “São Leopoldo Mandic | Portal Institucional”.

  • Canonical URL set

    The canonical URL is https://slmandic.edu.br/.

  • Structured data in place

    Structured data found: CollegeOrUniversity.

  • Open Graph tags complete

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

  • 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://slmandic.edu.br/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://slmandic.edu.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 (2,510 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 4 pages slow to respond

    https://slmandic.edu.br/alumni, https://slmandic.edu.br/atendimento-a-comunidade, https://slmandic.edu.br/fale-conosco and https://slmandic.edu.br/cursos/curso/graduacao-em-odontologia took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

1 to fixGoogle 10093
  • 24 small tap targets

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

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

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.

  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 951 words of visible text.

2 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 1 email link.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel (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.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies (measured from a US location before any click).

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

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 slmandic.edu.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
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on slmandic.edu.br, including 21 speed 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