Website review, no card needed

libertatea.ro logo

libertatea.ro website review

Visit site (opens in a new tab)Reviewed 24 October 202620 issues · 72 checks

This review found 20 issues worth fixing on libertatea.ro, 1 of them high impact, across 72 checks. The most urgent: largest Contentful Paint: 4.2 s. 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.9 s1.1 sMay 2Oct 171.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.2 s
May 9, 20261.2 s
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.3 s
Jun 6, 20261.4 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.7 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
210 ms159 msMay 2Oct 17202 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026165 ms
May 9, 2026169 ms
May 16, 2026173 ms
May 23, 2026175 ms
May 30, 2026179 ms
Jun 6, 2026186 ms
Jun 13, 2026190 ms
Jun 20, 2026188 ms
Jun 27, 2026184 ms
Jul 4, 2026177 ms
Jul 11, 2026170 ms
Jul 18, 2026170 ms
Jul 25, 2026172 ms
Aug 1, 2026174 ms
Aug 8, 2026177 ms
Aug 15, 2026175 ms
Aug 22, 2026169 ms
Aug 29, 2026170 ms
Sep 5, 2026175 ms
Sep 12, 2026183 ms
Sep 19, 2026197 ms
Sep 26, 2026204 ms
Oct 3, 2026204 ms
Oct 10, 2026203 ms
Oct 17, 2026202 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 libertatea.ro (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. libertatea.ro at 0.4 s0.4 s
  2. libertatea.ro at 0.8 s0.8 s
  3. libertatea.ro at 1.2 s1.2 s
  4. libertatea.ro at 1.6 s1.6 s
  5. libertatea.ro at 2.0 s2.0 s
  6. libertatea.ro at 2.4 s2.4 s
  7. libertatea.ro at 2.8 s2.8 s
  8. libertatea.ro at 3.2 s3.2 s

Speed

3 to fix80
  • Mobile performance score: 80

    80/100

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

  • 2,424 HTML elements

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

  • cookiepro.com adds 84 ms

    84 ms

    cookiepro.com costs a phone 84 ms of main-thread work and 354 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.

  • Reduce unused JavaScript

    280 ms · 128 KiB

    About 128 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 280 ms faster on a phone.

  • Use efficient cache lifetimes

    150 ms · 190 KiB

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

  • 4 long tasks on the main thread

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (cookiepro.com, Cxense and Optanon and others), adding 421 KiB and 171 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 15 KiB

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

  • Render-blocking requests

    150 ms

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

  • Improve image delivery

    88 KiB

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

  • Legacy JavaScript

    50 ms · 19 KiB

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

  • 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 1.3 s

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

  • Server response: 342 ms

    342 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 4.2 s

    4.2 s

    Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Marian Neacsu hepta 8925594”.

  • Tap response (INP) got 21% slower for real visitors

    +21%

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

  • Largest content (LCP) got 22% slower for real visitors

    +22%

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

  • Time to Interactive: 6.1 s

    6.1 s

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

  • 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.

  • Speed Index: 4.3 s

    4.3 s

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.1 s

    1.1 s

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

  • Real-user INP: 137 ms

    137 ms

    Real visitors wait 137 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.0 s

    1.0 s

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

  • Real-user TTFB: 341 ms

    341 ms

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

  • Total Blocking Time: 114 ms

    114 ms

    Scripts block the page for only 114 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.34 g

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

1 checks passed
  • Page weight: 1.2 MB in 65 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 65 requests on a phone: images 545 KiB (33), scripts 337 KiB (18) and other files 174 KiB (8). That is a lean page.

Accessibility

4 to fixGoogle 9393
  • 130 text elements with low contrast

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

  • 83 tap targets too small

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 181 images in the HTML carry an alt attribute.

  • 22 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 24 WCAG 2.2 A/AA and best-practice rules on the phone render: 22 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9289
  • Meta description is long (191 characters)

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

  • Structured data has 1 problem

    Structured data found (ImageObject, NewsMediaOrganization, Organization and PostalAddress) but with 1 problem, for example “Organization: url points at a different host (https://www.ringier.com/)”.

  • 3 links crawlers can't follow

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

  • 353 internal links, 75 external

    The homepage links to 353 pages on libertatea.ro and 75 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Știri online de ultimă oră, video, breaking news”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Știri online de ultimă oră, video, breaking news | Libertatea”.

  • Canonical URL set

    The canonical URL is https://www.libertatea.ro/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.libertatea.ro/sitemap-news.xml.

AI search readiness

100
  • No llms.txt

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

2 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: 6 of 6 facts

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

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    1 page of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 1 page that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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 1 page that loaded have a <title>.

Best practices

1 to fixGoogle 10092
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • Thin social proof

    Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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.

  • Only about 23 words

    The homepage has only about 23 words of visible text; thin pages give Google and first-time buyers little to go on.

  • 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.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Try again”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “SHOP” and “CONTACT”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

  • 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.

  • 1 other company contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 libertatea.ro, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Company

Founded
1989
Headquarters
Bucharest

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on libertatea.ro, including 9 speed issues, 3 SEO issues and 3 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