unibuc.ro website review

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

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

17 images could be 5.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.

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

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

Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (Google CDN, WordPress and mailerlite.com and others), adding 2.8 MB and 1.1 s of main-thread time.

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

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

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

Reduce initial server response time. Google estimates savings of 841 ms on a phone.

Google CDN costs a phone 553 ms of main-thread work and 1.8 MB 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.

WordPress costs a phone 262 ms of main-thread work and 314 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.

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

34 KiB could be saved by minifying JavaScript.

11 KiB could be saved by minifying CSS.

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

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

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

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

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

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

Your largest element takes 55.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Universitatea din București folosește module cookie strict …”.

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

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

The layout shifts by 0.826 while loading, so content jumps under the reader's thumb. Good is under 0.1.

2 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 146 ms to 135 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 16.3 MB in 283 requests on a phone: images 7.0 MB (51), scripts 5.6 MB (113) and other files 1.2 MB (16). Under 2 MB keeps phones on slow connections fast.

2 images weigh 3.9 MB together. On a phone connection a single image that size takes seconds.

10 images are downloaded at several times the size a phone draws them, for example poza-stire-SS.webp at 1,650 px wide, shown at 360 px. Resized copies would save about 2.9 MB.

12 images further down the page (5.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

2 elements use ARIA attributes their role does not allow, which confuses screen readers.

1 button has no accessible name, so screen readers announce just “button”.

Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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.

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

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

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 210 pages on unibuc.ro and 38 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://unibuc.ro/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://unibuc.ro/studii/facultati, https://unibuc.ro/ub-news, https://unibuc.ro/despre-ub/ub-astazi/profesori-ub, https://unibuc.ro/despre-ub/civis, https://unibuc.ro/presa and https://unibuc.ro/contact and 9 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://unibuc.ro/cariere, whose canonical is https://unibuc.ro/despre-ub/cariere. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://unibuc.ro/ub-news has no <h1> headline, so visitors and search engines get no clear main topic.

https://unibuc.ro/studii/facultati, https://unibuc.ro/despre-ub/ub-astazi/profesori-ub and https://unibuc.ro/despre-ub/civis took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Unexpected token '<'”.

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

Large scripts ship without source maps.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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