radiozu.ro website review

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

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

13 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.

74 files are served with short cache lifetimes, so returning visitors download them again (892 KiB).

8 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Other Google APIs/SDKs and others), adding 1.7 MB and 788 ms of main-thread time.

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

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

Google/Doubleclick Ads costs a phone 230 ms of main-thread work and 460 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.2 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

About 26 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.

20 KiB could be saved by minifying JavaScript.

3 KiB could be saved by minifying CSS.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.

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.

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

Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “LIVE la ZU: Carla´s Dreams - „Mai e””.

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

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

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

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

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

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

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

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

Your homepage downloads 7.8 MB in 160 requests on a phone: images 5.4 MB (44), scripts 1.8 MB (64) and fonts 360 KiB (8). Under 2 MB keeps phones on slow connections fast.

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

12 images (3.9 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.

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

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 28 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.

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Your title is only 8 characters: “Radio ZU”. 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.

Your meta description is 189 characters; Google truncates after about 160, so the end of your pitch is cut.

No XML sitemap at https://radiozu.ro/sitemap.xml, so Google discovers your pages only by following links.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 133 pages on radiozu.ro and 32 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://radiozu.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.

/ and https://radiozu.ro/live all use the title “Radio ZU”. Search engines can't tell which page to show for a search, so each competes with the others.

https://radiozu.ro/contact and https://radiozu.ro/concursuri use the same meta description. A description written for each page earns more clicks.

https://radiozu.ro/emisiuni, https://radiozu.ro/reteauazu, https://radiozu.ro/contact, https://radiozu.ro/live, https://radiozu.ro/concursuri and https://radiozu.ro/morningzu and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'addEventListener')”.

1 image is 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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 528 words of visible text.

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