Website review, no card needed
cespu.pt website review
Visit site (opens in a new tab)Reviewed 29 October 202645 issues · 80 checks
This review found 45 issues worth fixing on cespu.pt, 14 of them high impact, across 80 checks. The most urgent: font display. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 882 ms |
| May 16, 2026 | 890 ms |
| May 23, 2026 | 877 ms |
| May 30, 2026 | 889 ms |
| Jun 6, 2026 | 885 ms |
| Jun 13, 2026 | 893 ms |
| Jun 20, 2026 | 907 ms |
| Jun 27, 2026 | 922 ms |
| Jul 4, 2026 | 957 ms |
| Jul 11, 2026 | 967 ms |
| Jul 18, 2026 | 952 ms |
| Jul 25, 2026 | 917 ms |
| Aug 1, 2026 | 893 ms |
| Aug 8, 2026 | 883 ms |
| Aug 15, 2026 | 890 ms |
| Aug 22, 2026 | 880 ms |
| Aug 29, 2026 | 867 ms |
| Sep 5, 2026 | 868 ms |
| Sep 12, 2026 | 898 ms |
| Sep 19, 2026 | 964 ms |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 85 ms |
| May 16, 2026 | 86 ms |
| May 23, 2026 | 84 ms |
| May 30, 2026 | 87 ms |
| Jun 6, 2026 | 87 ms |
| Jun 13, 2026 | 88 ms |
| Jun 20, 2026 | 88 ms |
| Jun 27, 2026 | 87 ms |
| Jul 4, 2026 | 88 ms |
| Jul 11, 2026 | 87 ms |
| Jul 18, 2026 | 86 ms |
| Jul 25, 2026 | 85 ms |
| Aug 1, 2026 | 85 ms |
| Aug 8, 2026 | 85 ms |
| Aug 15, 2026 | 84 ms |
| Aug 22, 2026 | 84 ms |
| Aug 29, 2026 | 83 ms |
| Sep 5, 2026 | 83 ms |
| Sep 12, 2026 | 85 ms |
| Sep 19, 2026 | 86 ms |
| Sep 26, 2026 | 87 ms |
| Oct 3, 2026 | 87 ms |
| Oct 10, 2026 | 88 ms |
| Oct 17, 2026 | 88 ms |
| Oct 24, 2026 | 89 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
Speed
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Improve image delivery
1.7 MB24 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Reduce unused CSS
150 ms · 30 KiBAbout 30 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.
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: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 83 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Cumulative Layout Shift: 0.795
0.795The layout shifts by 0.795 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user CLS: 0.16
0.16For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.
Largest content (LCP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
42 images without width and height
42 images have no width and height attributes, so the layout jumps as each one loads.
Speed Index: 4.8 s
4.8 sVisually, the page fills in at 4.8 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 3.2 s
3.2 sYour largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Lic. Enfermagem Veterinária”. Most of its time is resource load delay (1.5 s).
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 85 ms to 89 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 113 ms
113 msReal visitors wait 113 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Time to Interactive: 3.2 s
3.2 sThe page is fully interactive after 3.2 s.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 5.5 MB in 104 requests
5.5 MBYour homepage downloads 5.5 MB in 104 requests on a phone: images 5.2 MB (90), fonts 174 KiB (5) and scripts 60 KiB (5). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
PT2030_UE_Cor.png weighs 681 KiB. On a phone connection a single image that size takes seconds.
4 images far larger than shown
1.1 MB4 images are downloaded at several times the size a phone draws them, for example PT2030_UE_Cor.png at 5,253 px wide, shown at 330 px. Resized copies would save about 1.1 MB.
40 images in older formats
40 images (4.5 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.
5 images below the first screen load straight away
5 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.56 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.56 g of CO₂e: 187.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Orphan list items
Some list items are not inside a list.
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
16 images without alt text
16 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (21 elements)
All page content should be contained by landmarks: 21 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
1 checks passed
22 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 32 WCAG 2.2 A/AA and best-practice rules on the phone render: 22 passed and 10 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
104 links crawlers can't follow
104 links have no real href, so search engines can't follow them.
Title is short (6 characters)
Your title is only 6 characters: “Início”. 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.
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 (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
186 internal links, 41 external
The homepage links to 186 pages on cespu.pt and 41 external pages.
3 checks passed
Meta description: 93 characters
Your meta description is 93 characters: “Cooperativa de Ensino Superior Politécnico e Universitário, CRL - A Ensinar Saúde desde 1982.”.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at http://www.cespu.pt/sitemappt.
AI search readiness
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.cespu.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 (710 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages share 3 titles
https://www.cespu.pt/ensino/ensino-universitario/informacoes-e-contactos and https://www.cespu.pt/ensino/ensino-politecnico/informacoes-e-contactos all use the title “Informações e contactos”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://www.cespu.pt/ensino/candidaturas, https://www.cespu.pt/ensino/ensino-universitario/cursos-universidade-cespu, https://www.cespu.pt/ensino/ensino-universitario/informacoes-e-contactos, https://www.cespu.pt/ensino/apoios-finaceiros/bolsas-de-estudo, https://www.cespu.pt/ensino/ensino-universitario/departamentos and https://www.cespu.pt/ensino/erasmus-plus and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.cespu.pt/visitavirtual has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.cespu.pt/visitavirtual 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 70 found) and read each the way a search engine does.
4 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.
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
16 small tap targets
16 of 51 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 “Mixed Content: The page at 'https://www.cespu.pt/' was loaded over HTTPS, but requested an insecure font 'http://www.ce…”.
4 low-resolution images
4 images are served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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: 27 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 363 words of copy
The homepage carries about 363 words of visible text.
Privacy and tracking
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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 cespu.pt, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Eunet
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on cespu.pt, including 12 speed issues, 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.