Website review, no card needed

ujep.cz logo

ujep.cz website review

Visit site (opens in a new tab)Reviewed 1 November 202634 issues · 81 checks

This review found 34 issues worth fixing on ujep.cz, 10 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.2 s1.0 sMay 9Oct 241.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.2 s
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.0 s
Jul 11, 20261.0 s
Jul 18, 20261.0 s
Jul 25, 20261.0 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.2 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
115 ms95 msMay 9Oct 24112 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026104 ms
May 16, 2026107 ms
May 23, 2026111 ms
May 30, 2026111 ms
Jun 6, 2026112 ms
Jun 13, 2026109 ms
Jun 20, 2026103 ms
Jun 27, 2026102 ms
Jul 4, 2026100 ms
Jul 11, 2026100 ms
Jul 18, 2026102 ms
Jul 25, 2026101 ms
Aug 1, 2026102 ms
Aug 8, 2026101 ms
Aug 15, 2026100 ms
Aug 22, 2026102 ms
Aug 29, 202697 ms
Sep 5, 202698 ms
Sep 12, 202698 ms
Sep 19, 202697 ms
Sep 26, 2026103 ms
Oct 3, 2026106 ms
Oct 10, 2026110 ms
Oct 17, 2026113 ms
Oct 24, 2026112 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of ujep.cz (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ujep.cz at 0.4 s0.4 s
  2. ujep.cz at 0.8 s0.8 s
  3. ujep.cz at 1.2 s1.2 s
  4. ujep.cz at 1.7 s1.7 s
  5. ujep.cz at 2.1 s2.1 s
  6. ujep.cz at 2.5 s2.5 s
  7. ujep.cz at 2.9 s2.9 s
  8. ujep.cz at 3.3 s3.3 s

Speed

8 to fix61
  • Use efficient cache lifetimes

    2.4 s · 2.5 MB

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

  • Render-blocking requests

    1.8 s

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

  • Reduce unused JavaScript

    1.2 s · 176 KiB

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

  • Mobile performance score: 61

    61/100

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

  • Font display

    750 ms

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

  • Google Tag Manager adds 368 ms

    368 ms

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

  • 6 long tasks on the main thread

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

  • Improve image delivery

    260 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Hotjar and Adobe TypeKit and others), adding 643 KiB and 492 ms of main-thread time.

  • Reduce unused CSS

    180 ms · 37 KiB

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

  • Minify CSS

    30 ms · 10 KiB

    10 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    8 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.4 s

    A phone's processor spends 1.4 s on main-thread work while loading, 586 ms of it running JavaScript. That is comfortably low.

  • Server response: 107 ms

    107 ms

    Your server sent the HTML in 107 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix100
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 12.3 s

    12.3 s

    Your largest element takes 12.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “To provide the best experiences, we use technologies like c…”.

  • Time to Interactive: 13.9 s

    13.9 s

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

  • Speed Index: 7.1 s

    7.1 s

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

  • Real-user TTFB: 851 ms

    851 ms

    Real visitors wait 851 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Total Blocking Time: 238 ms

    238 ms

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

5 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 100 ms

    100 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.4 s

    1.4 s

    Real visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

4 to fix53
  • 1 image over 500 KB

    Návrh-bez-názvu.png weighs 866 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.1 MB in 72 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 72 requests on a phone: images 2.2 MB (25), scripts 474 KiB (17) and fonts 344 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 10 images in older formats

    10 images (2.1 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.

  • 3 images below the first screen load straight away

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

  • About 0.9 g of CO₂ per visit

    0.89 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9594
  • 2 text elements with low contrast

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

  • All page content should be contained by landmarks (5 elements)

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9285
  • Title is long (99 characters)

    Your title is 99 characters, so Google will cut it off around 60: “UJEP | Univerzita J. E. Purkyně - Univerzita Jana Evangelisty Purkyně v Ústí nad Labem me…”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 93 internal links, 32 external

    The homepage links to 93 pages on ujep.cz and 32 external pages.

5 checks passed
  • Meta description: 95 characters

    Your meta description is 95 characters: “UJEP – Tvoříme příležitosti tam, kde nechybí nadšení. 10 000 studentů na 1 000 000 příležitostí”.

  • Canonical URL set

    The canonical URL is https://www.ujep.cz/cs/.

  • Structured data in place

    Structured data found: CollectionPage, Organization and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.ujep.cz/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (817 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 2 pages share a title

    https://www.ujep.cz/en and https://www.ujep.cz/cs all use the title “UJEP | Univerzita J. E. Purkyně - Univerzita Jana Evangelisty Purkyně…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages without a meta description

    https://www.ujep.cz/en/contact-information, https://www.ujep.cz/en/cat/contacts/rectorate, https://www.ujep.cz/en/scientific-board, https://www.ujep.cz/en/senate, https://www.ujep.cz/en/international-evaluation-panel and https://www.ujep.cz/en/faculties and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9293
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to set referrer policy: The value '' is not one of 'no-referrer', 'no-referrer-when-downgrade', 'origin', 'origi…”.

  • 1 low-resolution image

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

2 checks passed
  • Tap targets are thumb-sized

    25 of 27 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No call to action on the first screen

    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 direct contact details

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

  • No risk reducer

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

  • About 300 words of copy

    The homepage carries about 300 words of visible text.

4 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact information”, “How to apply” and “Contact”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 8 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 9 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at ujep.cz, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
CESNET z.s.p.o.

Company

Founded
1991
Headquarters
Ústí nad Labem

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on ujep.cz, including 16 speed issues, 3 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25