Website review, no card needed
unimc.it website review
Visit site (opens in a new tab)Reviewed 26 October 202637 issues · 84 checks
This review found 37 issues worth fixing on unimc.it, 19 of them high impact, across 84 checks. The most urgent: render-blocking requests. 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.6 s |
| May 16, 2026 | 4.2 s |
| May 23, 2026 | 3.7 s |
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 176 ms |
| May 16, 2026 | 177 ms |
| May 23, 2026 | 177 ms |
| May 30, 2026 | 178 ms |
| Jun 6, 2026 | 178 ms |
| Jun 13, 2026 | 179 ms |
| Jun 20, 2026 | 178 ms |
| Jun 27, 2026 | 175 ms |
| Jul 4, 2026 | 172 ms |
| Jul 11, 2026 | 170 ms |
| Jul 18, 2026 | 170 ms |
| Jul 25, 2026 | 169 ms |
| Aug 1, 2026 | 168 ms |
| Aug 8, 2026 | 165 ms |
| Aug 15, 2026 | 162 ms |
| Aug 22, 2026 | 161 ms |
| Aug 29, 2026 | 162 ms |
| Sep 5, 2026 | 164 ms |
| Sep 12, 2026 | 166 ms |
| Sep 19, 2026 | 167 ms |
| Sep 26, 2026 | 168 ms |
| Oct 3, 2026 | 168 ms |
| Oct 10, 2026 | 166 ms |
| Oct 17, 2026 | 163 ms |
| Oct 24, 2026 | 162 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
How it loaded on a phone
1.8 s
3.5 s
5.3 s
7.1 s
8.8 s
10.6 s
12.4 s
14.1 s
Speed
Render-blocking requests
5.3 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.3 s.
Use efficient cache lifetimes
2.3 s · 487 KiB27 files are served with short cache lifetimes, so returning visitors download them again (487 KiB).
Reduce unused CSS
1.6 s · 321 KiBAbout 321 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Reduce unused JavaScript
1.5 s · 364 KiBAbout 364 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Minify JavaScript
1.6 s · 283 KiB283 KiB could be saved by minifying JavaScript.
Mobile performance score: 37
37/100Your mobile performance score is 37 (desktop: 61). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
200 ms · 1.7 MB12 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Font display
850 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 850 ms).
Legacy JavaScript
250 ms · 24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 218 ms. During a long task the page ignores taps.
Minify CSS
130 ms · 74 KiB74 KiB could be saved by minifying CSS.
1 third-party service on the page
1 third-party service load with your homepage (italia.it), adding 66 KiB and 17 ms of main-thread time.
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.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 370 ms of it running JavaScript. That is comfortably low.
Server response: 136 ms
136 msYour server sent the HTML in 136 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.3 s
13.3 sYour largest element takes 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Questo sito utilizza cookie tecnici necessari al corretto f…”. Most of its time is element render delay (6.4 s).
Speed Index: 12.1 s
12.1 sVisually, the page fills in at 12.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.9 s
5.9 sThe first text or image appears after 5.9 s on a phone. Good is under 1.8 s.
Time to Interactive: 13.6 s
13.6 sThe page becomes fully interactive after 13.6 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.32
0.32The layout shifts by 0.32 while loading, so content jumps under the reader's thumb. Good is under 0.1.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 176 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 164 ms
164 msReal visitors wait 164 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 678 ms
678 msReal visitors wait 678 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 42% faster for real visitors
-42%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.6 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 188 ms
188 msScripts block the page for only 188 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.8 MB in 68 requests
4.8 MBYour homepage downloads 4.8 MB in 68 requests on a phone: images 3.6 MB (45), scripts 797 KiB (8) and stylesheets 341 KiB (8). Under 2 MB keeps phones on slow connections fast.
13 images in older formats
13 images (620 KiB) 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.
11 images below the first screen load straight away
11 images further down the page (515 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.37 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.37 g of CO₂e: 164.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
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.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
Hidden but focusable
4 elements hidden from screen readers can still receive keyboard focus.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 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.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 38 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. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
9 H1 headlines
There are 9 <h1> headlines (“Scopri i corsi di laurea 2026/2027”, “Nuova laureaSCIENZE MOTORIE E SPORTIVE PER L'INCL…” and “Nuova laurea magistraleARCHIVI DIGITALI”). One clear main headline is easier for people and search engines.
Meta description is long (190 characters)
Your meta description is 190 characters; Google truncates after about 160, so the end of your pitch is cut.
No XML sitemap
No XML sitemap at https://www.unimc.it/sitemap.xml, so Google discovers your pages only by following links.
236 internal links, 45 external
The homepage links to 236 pages on unimc.it and 45 external pages.
4 checks passed
Title: 55 characters
Your title is a healthy 55 characters: “Università di Macerata: La tua idea di mondo INIZIA QUI”.
Canonical URL set
The canonical URL is https://www.unimc.it/it.
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.
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.
Opted out of AI training for 1 crawler
robots.txt blocks CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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 (1,345 words), so crawlers that don't run JavaScript still read it.
Other pages
12 linked pages are broken
Your homepage links to https://www.unimc.it/en/erua, https://www.unimc.it/@@multilingual-selector/6d422a628cd54111af82b7cc499ffbf6/it, https://www.unimc.it/@@multilingual-selector/6d422a628cd54111af82b7cc499ffbf6/en, https://www.unimc.it/it/ateneo/tradizione-innovazione, https://www.unimc.it/it/ateneo/tradizione-innovazione/tradizione-e-innovazione and https://www.unimc.it/it/ateneo/tradizione-innovazione/inaugurazioni-anni-accademici and 6 others, which answer with an error. Visitors hit a dead end and search engines drop them.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.unimc.it/it/ateneo/rettore/rettore, whose canonical is https://www.unimc.it/it/ateneo/rettore. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 197 found) and read each the way a search engine does.
5 checks passed
Every page has a meta description
All 3 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 3 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 503 (Service Unavailable)”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
36 of 38 tappable elements near the top are at least 24 px.
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: 12 testimonial or review blocks. 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 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 706 words of copy
The homepage carries about 706 words of visible text.
2 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 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.
1 other company contacted
Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 unimc.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Consortium GARR
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on unimc.it, including 14 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.