Website review, no card needed

cfrcalatori.ro logo

cfrcalatori.ro website review

Visit site (opens in a new tab)Reviewed 3 November 202619 issues · 74 checks

This review found 19 issues worth fixing on cfrcalatori.ro, 3 of them high impact, across 74 checks. The most urgent: render-blocking requests. 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
2.7 s2.2 sMay 16Oct 312.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.4 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.6 s
Aug 1, 20262.7 s
Aug 8, 20262.7 s
Aug 15, 20262.6 s
Aug 22, 20262.6 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.5 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.3 s
Oct 31, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
218 ms147 msMay 16Oct 31172 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026155 ms
May 23, 2026161 ms
May 30, 2026166 ms
Jun 6, 2026169 ms
Jun 13, 2026170 ms
Jun 20, 2026169 ms
Jun 27, 2026170 ms
Jul 4, 2026171 ms
Jul 11, 2026173 ms
Jul 18, 2026177 ms
Jul 25, 2026186 ms
Aug 1, 2026201 ms
Aug 8, 2026207 ms
Aug 15, 2026210 ms
Aug 22, 2026209 ms
Aug 29, 2026207 ms
Sep 5, 2026205 ms
Sep 12, 2026204 ms
Sep 19, 2026203 ms
Sep 26, 2026198 ms
Oct 3, 2026190 ms
Oct 10, 2026181 ms
Oct 17, 2026174 ms
Oct 24, 2026172 ms
Oct 31, 2026172 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 cfrcalatori.ro (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cfrcalatori.ro at 0.5 s0.5 s
  2. cfrcalatori.ro at 1.0 s1.0 s
  3. cfrcalatori.ro at 1.5 s1.5 s
  4. cfrcalatori.ro at 2.0 s2.0 s
  5. cfrcalatori.ro at 2.5 s2.5 s
  6. cfrcalatori.ro at 2.9 s2.9 s
  7. cfrcalatori.ro at 3.4 s3.4 s
  8. cfrcalatori.ro at 3.9 s3.9 s

Speed

4 to fix87
  • Render-blocking requests

    1.2 s

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

  • Use efficient cache lifetimes

    750 ms · 852 KiB

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

  • Mobile performance score: 87

    87/100

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

  • 1,733 HTML elements

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

  • Reduce unused CSS

    150 ms · 45 KiB

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

  • Improve image delivery

    52 KiB

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

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

2 checks passed
  • Main-thread work: 0.5 s

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

  • Server response: 146 ms

    146 ms

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

Core Web Vitals

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Speed Index: 5.6 s

    5.6 s

    Visually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 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.

  • Largest Contentful Paint: 3.0 s

    3.0 s

    Your largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Cumpără bilete de tren online Alege destinația și continuă …”. Most of its time is resource load delay (1.6 s).

  • Tap response (INP) held steady for real visitors

    +9%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

7 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 182 ms

    182 ms

    Real visitors wait 182 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 TTFB: 755 ms

    755 ms

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

  • Time to Interactive: 3.0 s

    3.0 s

    The page is fully interactive after 3.0 s.

  • Cumulative Layout Shift: 0.001

    0.001

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100
  • 2 images in older formats

    2 images (126 KiB) 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.

  • About 0.3 g of CO₂ per visit

    0.31 g

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

3 checks passed
  • Page weight: 1.1 MB in 59 requests

    1.1 MB

    Your homepage downloads 1.1 MB in 59 requests on a phone: images 741 KiB (17), scripts 135 KiB (25) and fonts 113 KiB (3). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

1 to fixGoogle 10099
  • All page content should be contained by landmarks (3 elements)

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

3 to fixGoogle 10086
  • Title is long (80 characters)

    Your title is 80 characters, so Google will cut it off around 60: “CFR Călători pagina oficială. Mersul trenurilor. Bilete online. Oferte. Servicii”.

  • Meta description is long (291 characters)

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 181 internal links, 14 external

    The homepage links to 181 pages on cfrcalatori.ro and 14 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Cumpără bilete de tren online”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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.cfrcalatori.ro/sitemap_index.xml.

AI search readiness

100
4 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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.cfrcalatori.ro/llms.txt (3 KiB, 21 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 7 pages without a meta description

    https://www.cfrcalatori.ro/comunicate, https://www.cfrcalatori.ro/legislatia-de-organizare-si-functionare, https://www.cfrcalatori.ro/componenta-aga, https://www.cfrcalatori.ro/en, https://www.cfrcalatori.ro/bucuresti-nord-aeroport-henri-coanda and https://www.cfrcalatori.ro/tarif-unic-pe-sectia-oravita-anina and 1 other 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 146 found) and read each the way a search engine does.

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

  • 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 15 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    39 of 43 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • A 17-field form

    Your longest form asks for 17 fields (2 required). Every extra field lowers completion.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 808 words of copy

    The homepage carries about 808 words of visible text.

3 checks passed
  • Clear next step on the first screen

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

  • 4 calls to action

    The homepage has 4 calls to action, for example “Formulare Contact”, “Date de contact” and “Contact”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

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 cfrcalatori.ro, 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 Tag Manager
Hosting
SC Informatica Feroviara SA

Company

Founded
1998
Headquarters
Bucharest

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

Go beyond the website

What your $25 Growth Playbook adds

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