uni-mate.hu website review

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

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

About 217 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

YouTube costs a phone 1.2 s of main-thread work and 2.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

7 third-party services load with your homepage (YouTube, Facebook and Google Tag Manager and others), adding 3.5 MB and 1.5 s of main-thread time.

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

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

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

20 KiB could be saved by minifying CSS.

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

18 long tasks block the main thread while loading, the longest for 145 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.

3 KiB JavaScript is shipped twice across bundles.

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.

For real visitors the layout shifts by 0.46 (75th percentile). Good is under 0.1.

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

Your largest element takes 31.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “MATE 2030 Cselekvő egyetemként a zöld jövő szolgálatában TO…”.

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

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

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

9 images 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 127 ms to 125 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.8 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.3 MB in 183 requests on a phone: scripts 3.4 MB (93), images 2.0 MB (28) and fonts 1.0 MB (10). Under 2 MB keeps phones on slow connections fast.

11 images (621 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.

6 images further down the page (305 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 2.07 g of CO₂e: 248.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

1 tap target is too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

There are 6 <h1> headlines (“Hírek”, “Események” and “Doktori védések, Habilitációs előadások”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: 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 97 pages on uni-mate.hu and 60 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://uni-mate.hu/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://uni-mate.hu/home, https://uni-mate.hu/k%C3%B6sz%C3%B6nt%C5%91, https://uni-mate.hu/az-egyetem-t%C3%B6rt%C3%A9nete, https://uni-mate.hu/az-egyetem-vezet%C3%A9se, https://uni-mate.hu/k%C3%B6zz%C3%A9t%C3%A9teli and https://uni-mate.hu/gazd%C3%A1lkod%C3%A1si-inform%C3%A1ci%C3%B3k and 4 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/ and https://uni-mate.hu/home all use the title “Home - Magyar Agrár- és Élettudományi Egyetem - MATE”. Search engines can't tell which page to show for a search, so each competes with the others.

https://uni-mate.hu/home, https://uni-mate.hu/k%C3%B6sz%C3%B6nt%C5%91, https://uni-mate.hu/az-egyetem-t%C3%B6rt%C3%A9nete, https://uni-mate.hu/az-egyetem-vezet%C3%A9se, https://uni-mate.hu/k%C3%B6zz%C3%A9t%C3%A9teli and https://uni-mate.hu/egyetemi-dokumentumok and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

Chrome logged issues while loading the page (“Cookie”).

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 832 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 9 cookies, 1 of them by other companies (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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.