upjs.sk website review

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

About 341 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

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

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

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

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

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

5 third-party services load with your homepage (Google Tag Manager, jQuery CDN and Adobe TypeKit and others), adding 456 KiB and 310 ms of main-thread time.

3 images could be 62 KiB 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.

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

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

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

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 7.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (3.3 s).

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 137 ms to 134 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 1.9 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

1 image (81 KiB) is 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 0.38 g of CO₂e: 45.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

26 elements hidden from screen readers can still receive keyboard focus.

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

1 text element doesn'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: 13 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.

24 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, 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.

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

Your title is 77 characters, so Google will cut it off around 60: “UPJŠ Košice - múdrosť minulosti – poznatky prítomnosti – vzdelanie budúcnosti”.

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

The homepage links to 222 pages on upjs.sk and 54 external pages.

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

/ and https://www.upjs.sk/uk all use the title “UPJŠ Košice - múdrosť minulosti – poznatky prítomnosti – vzdelanie bu…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.upjs.sk/informacie/verejnost-media/vztahy-s-verejnostou/univerzitne-media/universitas-safarikiana, https://www.upjs.sk/en, https://www.upjs.sk/uk, https://www.upjs.sk/univerzita/informacie-o-univerzite, https://www.upjs.sk/historia-univerzity and https://www.upjs.sk/univerzita/organizacna-struktura and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.upjs.sk/en, https://www.upjs.sk/uk and https://www.upjs.sk/zo-zivota-upjs have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.upjs.sk/uk has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

Large scripts ship without source maps.

Social proof on the homepage: 11 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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 1,242 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, 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 2 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 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.