ug.edu.pl website review

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

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

Your mobile performance score is 53 (desktop: 66). Pages that score under 90 lose visitors before the first paint.

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

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

skynettechnologies.com costs a phone 5 ms of main-thread work and 410 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 94 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

About 122 KiB of JavaScript is downloaded but never used on this page.

2 third-party services load with your homepage (skynettechnologies.com and Google Fonts), adding 664 KiB and 5 ms of main-thread time.

1 long task block the main thread while loading, the longest for 50 ms. During a long task the page ignores taps.

12 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need.

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 layout shifts by 0.498 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Your largest element takes 4.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Pożegnanie dr. Grzegorza Stunży”.

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

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

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

1270x580.jpg.webp 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).

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

2 images are downloaded at several times the size a phone draws them, for example 1270x580.jpg.webp at 1,270 px wide, shown at 390 px. Resized copies would save about 44 KiB.

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

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

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.

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings skip levels (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.

Your title is only 21 characters: “| Uniwersytet Gdański”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

No XML sitemap at https://ug.edu.pl/sitemap.xml, so Google discovers your pages only by following links.

1 link has no real href, so search engines can't follow it.

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

The homepage links to 118 pages on ug.edu.pl and 37 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://ug.edu.pl/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://ug.edu.pl/kandydaci, https://ug.edu.pl/kandydaci/studia-wspolne-w-ramach-sea-eu, https://ug.edu.pl/rekrutacja/szkoly_doktorskie, https://ug.edu.pl/kandydaci/studia-podyplomowe, https://ug.edu.pl/rekrutacja/kursy_i_szkolenia and https://ug.edu.pl/kandydaci/potwierdzanie-efektow-uczenia and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://ug.edu.pl/kandydaci/potwierdzanie-efektow-uczenia, whose canonical is https://ug.edu.pl/pracownicy/strony_jednostek/biuro-jakosci-ksztalcenia/potwierdzanie-efektow-uczenia. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://ug.edu.pl/rekrutacja/studia_i_i_ii_stopnia_oraz_jednolite_magisterskie has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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.

There is no form on the homepage, so every lead has to click through to another page first.

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

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