Website review, no card needed

usf.edu.br logo

usf.edu.br website review

Visit site (opens in a new tab)Reviewed 19 November 202646 issues · 91 checks

This review found 46 issues worth fixing on usf.edu.br, 21 of them high impact, across 91 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.4 s1.9 sJul 11Nov 142.2 s
Show as table
DateReal-visitor load time (LCP)
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.1 s
Oct 31, 20262.1 s
Nov 7, 20262.1 s
Nov 14, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
279 ms116 msJul 11Nov 14159 ms
Show as table
DateReal-visitor tap response (INP)
Jul 11, 2026260 ms
Jul 18, 2026260 ms
Jul 25, 2026260 ms
Aug 1, 2026260 ms
Aug 22, 2026161 ms
Aug 29, 2026154 ms
Sep 5, 2026150 ms
Sep 12, 2026150 ms
Sep 19, 2026146 ms
Sep 26, 2026144 ms
Oct 3, 2026143 ms
Oct 10, 2026138 ms
Oct 17, 2026135 ms
Oct 24, 2026139 ms
Oct 31, 2026142 ms
Nov 7, 2026153 ms
Nov 14, 2026159 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 usf.edu.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. usf.edu.br at 0.9 s0.9 s
  2. usf.edu.br at 1.7 s1.7 s
  3. usf.edu.br at 2.6 s2.6 s
  4. usf.edu.br at 3.5 s3.5 s
  5. usf.edu.br at 4.3 s4.3 s
  6. usf.edu.br at 5.2 s5.2 s
  7. usf.edu.br at 6.0 s6.0 s
  8. usf.edu.br at 6.9 s6.9 s

Speed

12 to fix28
  • Use efficient cache lifetimes

    2.9 s · 3.2 MB

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

  • Reduce unused JavaScript

    2.4 s · 809 KiB

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

  • Improve image delivery

    1.2 s · 501 KiB

    7 images could be 501 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 28

    28/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, TikTok and Facebook and others), adding 1.8 MB and 1.7 s of main-thread time.

  • Google Tag Manager adds 911 ms

    911 ms

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

  • Reduce unused CSS

    450 ms · 51 KiB

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

  • Main-thread work: 3.2 s

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

  • TikTok adds 251 ms

    251 ms

    TikTok costs a phone 251 ms of main-thread work and 171 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 267 ms. During a long task the page ignores taps.

  • handtalk.me adds 119 ms

    119 ms

    handtalk.me costs a phone 119 ms of main-thread work and 412 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.

  • Duplicated JavaScript

    42 KiB

    42 KiB JavaScript is shipped twice across bundles.

  • Legacy JavaScript

    29 KiB

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

  • Minify JavaScript

    6 KiB

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 129 ms

    129 ms

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

Core Web Vitals

8 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: 14.5 s

    14.5 s

    Your largest element takes 14.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Black Weeks Pós”.

  • Time to Interactive: 22.1 s

    22.1 s

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

  • Speed Index: 11.5 s

    11.5 s

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

  • Cumulative Layout Shift: 0.427

    0.427

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

  • Total Blocking Time: 705 ms

    705 ms

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

  • Real-user TTFB: 816 ms

    816 ms

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

  • 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

    +9%

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

6 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user INP: 169 ms

    169 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Tap response (INP) got 40% faster for real visitors

    -40%

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

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

Images and page weight

3 to fix45
  • Page weight: 4.8 MB in 115 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 115 requests on a phone: images 2.7 MB (37), scripts 1.9 MB (39) and stylesheets 87 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    1110856349182624.png weighs 1.6 MB. On a phone connection a single image that size takes seconds.

  • 5 images in older formats

    5 images (2.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.

  • 1 image below the first screen load straight away

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

  • About 1.4 g of CO₂ per visit

    1.37 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.37 g of CO₂e: 164.4 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

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

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Links must have discernible text (1 element)

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

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 40 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 7 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 9278
  • 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 social preview image

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

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

  • 134 internal links, 13 external

    The homepage links to 134 pages on usf.edu.br and 13 external pages.

4 checks passed
  • Meta description: 115 characters

    Your meta description is 115 characters: “Universidade São Francisco - Complexo educacional que oferece mais de 40 cursos de graduação e 20 de Pós-Graduação.”.

  • Title: 32 characters

    Your title is a healthy 32 characters: “USF - Universidade São Francisco”.

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

Other pages

3 to fix86
  • 14 pages share a title

    /, https://usf.edu.br/publicacoes/apresentacao.vm, https://usf.edu.br/publicacoes/alunosformados.vm, https://usf.edu.br/publicacoes/anais.vm, https://usf.edu.br/publicacoes/cartilhas.vm and https://usf.edu.br/publicacoes/dissertacoes.vm and 8 others all use the title “USF - Universidade São Francisco”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages share a meta description

    https://usf.edu.br/publicacoes/apresentacao.vm, https://usf.edu.br/publicacoes/alunosformados.vm, https://usf.edu.br/publicacoes/anais.vm, https://usf.edu.br/publicacoes/cartilhas.vm, https://usf.edu.br/publicacoes/dissertacoes.vm and https://usf.edu.br/publicacoes/normas.vm and 7 others use the same meta description. A description written for each page earns more clicks.

  • 13 pages without an H1

    https://usf.edu.br/publicacoes/apresentacao.vm, https://usf.edu.br/publicacoes/alunosformados.vm, https://usf.edu.br/publicacoes/anais.vm, https://usf.edu.br/publicacoes/cartilhas.vm, https://usf.edu.br/publicacoes/dissertacoes.vm and https://usf.edu.br/publicacoes/normas.vm and 7 others have 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 71 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8891
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Unexpected token ':'”.

  • 1 distorted image

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

  • 2 low-resolution images

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

2 checks passed
  • Tap targets are thumb-sized

    26 of 29 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • 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 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 538 words of copy

    The homepage carries about 538 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Hotjar.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 4 cookies set on arrival

    4

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

  • 11 other companies contacted

    Loading the homepage contacts 11 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 usf.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
jQuery
Analytics
Google Tag Manager | Hotjar
Hosting
As265479 Associacao Franciscana De Ensino Senhor Bom Jesus

Company

Headquarters
Braganca Paulista

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on usf.edu.br, including 20 speed issues, 5 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