Website review, no card needed

andrela.ro logo

andrela.ro website review

Visit site (opens in a new tab)Reviewed 18 November 202633 issues · 76 checks

This review found 33 issues worth fixing on andrela.ro, 13 of them high impact, across 76 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.6 s2.4 sMay 30Jun 272.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.5 s
Jun 6, 20262.4 s
Jun 13, 20262.6 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
402 ms396 msJun 6Jun 27397 ms
Show as table
DateReal-visitor tap response (INP)
Jun 6, 2026401 ms
Jun 13, 2026397 ms
Jun 20, 2026397 ms
Jun 27, 2026397 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 andrela.ro (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. andrela.ro at 0.4 s0.4 s
  2. andrela.ro at 0.9 s0.9 s
  3. andrela.ro at 1.3 s1.3 s
  4. andrela.ro at 1.7 s1.7 s
  5. andrela.ro at 2.2 s2.2 s
  6. andrela.ro at 2.6 s2.6 s
  7. andrela.ro at 3.0 s3.0 s
  8. andrela.ro at 3.4 s3.4 s

Speed

5 to fix69
  • Render-blocking requests

    1.9 s

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

  • Use efficient cache lifetimes

    150 ms · 934 KiB

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

  • Mobile performance score: 69

    69/100

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

  • Reduce unused JavaScript

    300 ms · 419 KiB

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

  • Google Tag Manager adds 246 ms

    246 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and adtrafficquality.google and others), adding 1,009 KiB and 348 ms of main-thread time.

  • Improve image delivery

    150 ms · 233 KiB

    6 images could be 233 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    140 ms · 75 KiB

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

  • 5 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    8 KiB

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

  • Minify CSS

    7 KiB

    7 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: 1.5 s

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

  • Server response: 169 ms

    169 ms

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

Core Web Vitals

5 to fix75
  • Time to Interactive: 11.2 s

    11.2 s

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

  • Largest Contentful Paint: 5.0 s

    5.0 s

    Your largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 7.2 s

    7.2 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • 17 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 42 ms

    42 ms

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

Images and page weight

4 to fix58
  • Page weight: 3.8 MB in 112 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 112 requests on a phone: images 2.2 MB (48), scripts 1.2 MB (29) and fonts 184 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 16 images below the first screen load straight away

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

  • 5 images in older formats

    5 images (540 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.

  • 1 image far larger than shown

    50 KiB

    1 image is downloaded at several times the size a phone draws it, for example logookAsset-7.png at 603 px wide, shown at 50 px. Resized copies would save about 50 KiB.

  • About 1.1 g of CO₂ per visit

    1.07 g

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

Accessibility

7 to fixGoogle 8090
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 80 text elements with low contrast

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

  • 2 tap targets too small

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

  • 1 image without alt text

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 14 links without text

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

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

4 to fixGoogle 8385
  • Meta description is short (23 characters)

    Your meta description is only 23 characters: “Blogger. Om creativ. PR”. 70 to 160 characters is enough to sell the click.

  • No XML sitemap

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

  • No robots.txt

    There is no robots.txt at andrela.ro/robots.txt, the first file search crawlers ask for.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 99 internal links, 36 external

    The homepage links to 99 pages on andrela.ro and 36 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Andrela.ro”.

  • Title: 36 characters

    Your title is a healthy 36 characters: “Andrela.ro - Blogger. Om creativ. PR”.

  • Canonical URL set

    The canonical URL is https://andrela.ro/.

  • Structured data in place

    Structured data found: BreadcrumbList, CollectionPage, Organization, Person and WebSite.

  • Open Graph tags complete

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

AI search readiness

100
  • No llms.txt

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

3 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

4 to fix41
  • 14 linked pages are broken

    Your homepage links to https://andrela.ro/despre-andrela, https://andrela.ro/category/smart-stuff, https://andrela.ro/category/marketing, https://andrela.ro/category/comunicare-media-pr, https://andrela.ro/category/design-grafic and https://andrela.ro/category/piatadetimisoara and 8 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 page without a title

    https://andrela.ro/portofoliu has no <title>, so Google invents the link text in results.

  • 1 page without a meta description

    https://andrela.ro/portofoliu has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://andrela.ro/portofoliu has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

2 checks passed
  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

1 to fixGoogle 10093
  • 30 small tap targets

    30 of 47 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 1,109 words of copy

    The homepage carries about 1,109 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 4 cookies set on arrival

    4

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

  • 13 other companies contacted

    Loading the homepage contacts 13 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 andrela.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 Analytics
Hosting
Space Ro SRL

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on andrela.ro, including 10 speed issues, 4 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