uoc.gr website review

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

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

About 2.8 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 14.7 s faster on a phone.

About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.1 s faster on a phone.

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

The HTML itself could arrive about 1.9 s sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 1.8 s on a phone.

200 KiB could be saved by minifying JavaScript.

204 KiB could be saved by minifying CSS.

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

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

Your server takes 1.9 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

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

5 images could be 135 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

FontAwesome CDN costs a phone 88 ms of main-thread work and 502 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.

4 third-party services load with your homepage (Google Tag Manager, FontAwesome CDN and Google Fonts and others), adding 813 KiB and 207 ms of main-thread time.

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

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

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.

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.

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

Your largest element takes 60.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “prosklisi_mitis_26-01-01 (1)”.

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

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

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

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

Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.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-24, real Chrome visitors' tap response (inp) went from 156 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 13.0 MB in 268 requests on a phone: scripts 3.9 MB (126), images 3.8 MB (54) and stylesheets 3.0 MB (66). Under 2 MB keeps phones on slow connections fast.

prosklisi_mitis_26-01-01-1.jpg 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).

3 images (149 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.

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

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

8 images have no alt text, which hurts accessibility and image search.

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

13 visible links have no text or label, so screen readers cannot say where they go.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 19 characters: “Πανεπιστήμιο Κρήτης”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 3 <h1> headlines (“Το Πανεπιστήμιο”, “Ημερολόγιο Εκδηλώσεων” and “Εκδηλώσεις”). One clear main headline is easier for people and search engines.

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

5 links have no real href, so search engines can't follow them.

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

The homepage links to 329 pages on uoc.gr and 92 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.uoc.gr/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.

robots.txt blocks ClaudeBot, 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.

https://www.uoc.gr/foitites, https://www.uoc.gr/faculty-staff, https://www.uoc.gr/visit-2, https://www.uoc.gr/alumni, https://www.uoc.gr/en/home and https://www.uoc.gr/arxiki/xairetismos and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.uoc.gr/faculty-staff, https://www.uoc.gr/visit-2, https://www.uoc.gr/alumni, https://www.uoc.gr/arxiki/thesmiko and https://www.uoc.gr/dioikitikes-yphresies took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'find')”.

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

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

Social proof on the homepage: 4 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.

The homepage has only about 205 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

Opening the homepage sets 4 cookies (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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.