unibg.it website review

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

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

Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.

14 images could be 683 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

google.com costs a phone 0 ms of main-thread work and 384 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.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).

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

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

20 KiB could be saved by minifying CSS.

3 third-party services load with your homepage (Cloudflare, cineca.it and google.com), adding 469 KiB and 7 ms of main-thread time.

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.

Your largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Slider home canale Sant'Agostino”.

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

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

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

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

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

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

Your homepage downloads 4.2 MB in 94 requests on a phone: images 3.6 MB (33), fonts 225 KiB (4) and scripts 186 KiB (7). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.5 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example APP_CAREER_DAY_2026_2048x1368.png at 1,600 px wide, shown at 390 px. Resized copies would save about 790 KiB.

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

APP_CAREER_DAY_2026_2048x1368.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

4 images further down the page (83 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

Some list items are not inside a list.

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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 156 pages on unibg.it and 41 external pages.

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.

There is no https://www.unibg.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.unibg.it/language-switcher declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://www.unibg.it/language-switcher all use the title “Università degli studi di Bergamo | UniBg”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.unibg.it/rubrica, https://www.unibg.it/node/15273, https://www.unibg.it/webmail, https://www.unibg.it/ateneo, https://www.unibg.it/ateneo/chi-siamo and https://www.unibg.it/ateneo/organizzazione-e-struttura and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.unibg.it/language-switcher has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.unibg.it/studiare/perche-scegliere-unibg took over 3 s to send its HTML from our server.

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

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

2 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.unibg.it/libraries/splide/dist/css/splide-core.min.css?tnvrgq' because its MIM…”.

1 image is served at too low a resolution for sharp phone screens.

Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 375 words of visible text.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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.

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