unicampus.it website review

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

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

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

About 717 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

10 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

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

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

The page has 2,790 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Polyfills for old browsers add 46 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

Your largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Job Day 2026 Save the date: mercoledì 18 novembre Scopri di…”.

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

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

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

Your homepage downloads 2.9 MB in 101 requests on a phone: scripts 1.8 MB (36), images 867 KiB (24) and HTML 66 KiB (1). Under 2 MB keeps phones on slow connections fast.

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

2 dropdowns have no label.

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

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

1 element hidden from screen readers can still receive keyboard focus.

All page content should be contained by landmarks: 34 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

There are 9 <h1> headlines (“Job Day 2026”, “Roma Corre in Bici: incentivi per la mobilità sos…” and “Ammissioni in corso - a.a. 2026/2027”). One clear main headline is easier for people and search engines.

Your meta description is 288 characters; Google truncates after about 160, so the end of your pitch is cut.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 305 pages on unicampus.it and 87 external pages.

There is no https://www.unicampus.it/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.

https://www.unicampus.it/news and https://www.unicampus.it/servizi/faq-domande-frequenti have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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 404 ()”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 2,459 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

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

Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.