Website review, no card needed

aerostar.ro logo

aerostar.ro website review

Visit site (opens in a new tab)Reviewed 17 November 202639 issues · 84 checks

This review found 39 issues worth fixing on aerostar.ro, 10 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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
4.6 s2.0 sMay 30Nov 142.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.3 s
Jun 6, 20264.2 s
Jun 13, 20264.3 s
Jun 20, 20264.1 s
Jun 27, 20264.0 s
Jul 4, 20263.7 s
Jul 11, 20263.4 s
Jul 18, 20263.1 s
Jul 25, 20263.1 s
Aug 1, 20263.4 s
Aug 8, 20263.5 s
Aug 15, 20263.6 s
Aug 22, 20263.5 s
Aug 29, 20263.3 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20262.8 s
Sep 26, 20262.7 s
Oct 3, 20262.8 s
Oct 10, 20262.5 s
Oct 17, 20262.4 s
Oct 24, 20262.5 s
Oct 31, 20262.4 s
Nov 7, 20262.5 s
Nov 14, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
98 ms74 msMay 30Nov 1481 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202688 ms
Jun 6, 202695 ms
Jun 13, 202695 ms
Jun 20, 202687 ms
Jun 27, 202687 ms
Jul 4, 202685 ms
Jul 11, 202685 ms
Jul 18, 202685 ms
Jul 25, 202683 ms
Aug 1, 202680 ms
Aug 8, 202681 ms
Aug 15, 202685 ms
Aug 22, 202689 ms
Aug 29, 202688 ms
Sep 5, 202687 ms
Sep 12, 202687 ms
Sep 19, 202686 ms
Sep 26, 202686 ms
Oct 3, 202687 ms
Oct 10, 202685 ms
Oct 17, 202680 ms
Oct 24, 202681 ms
Oct 31, 202677 ms
Nov 7, 202678 ms
Nov 14, 202681 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 aerostar.ro (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aerostar.ro at 0.6 s0.6 s
  2. aerostar.ro at 1.2 s1.2 s
  3. aerostar.ro at 1.9 s1.9 s
  4. aerostar.ro at 2.5 s2.5 s
  5. aerostar.ro at 3.1 s3.1 s
  6. aerostar.ro at 3.7 s3.7 s
  7. aerostar.ro at 4.3 s4.3 s
  8. aerostar.ro at 5.0 s5.0 s

Speed

11 to fix62
  • Use efficient cache lifetimes

    6.5 s · 2.3 MB

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

  • Render-blocking requests

    3.5 s

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

  • Reduce unused CSS

    900 ms · 296 KiB

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

  • Mobile performance score: 62

    62/100

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

  • Reduce unused JavaScript

    150 ms · 574 KiB

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

  • Improve image delivery

    600 ms · 86 KiB

    1 image could be 86 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

  • 5 third-party services on the page

    5 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Google Fonts and others), adding 1.2 MB and 347 ms of main-thread time.

  • YouTube adds 339 ms

    339 ms

    YouTube costs a phone 339 ms of main-thread work and 1.0 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.

  • Font display

    400 ms

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

  • Main-thread work: 2.0 s

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

  • 1,573 HTML elements

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

  • 4 long tasks on the main thread

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

  • Minify JavaScript

    6 KiB

    6 KiB could be saved by minifying JavaScript.

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 5 ms

    5 ms

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

Core Web Vitals

10 to fix0
  • 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.

  • Largest Contentful Paint: 9.5 s

    9.5 s

    Your largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Pentru a oferi cea mai bună experiență, folosim tehnologii,…”.

  • Time to Interactive: 18.0 s

    18.0 s

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

  • Speed Index: 8.0 s

    8.0 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user CLS: 0.24

    0.24

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • 2 images without width and height

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

4 checks passed
  • Tap response (INP) got 13% faster for real visitors

    -13%

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

  • Largest content (LCP) got 43% faster for real visitors

    -43%

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

  • Total Blocking Time: 65 ms

    65 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

2 to fix75
  • Page weight: 3.5 MB in 125 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 125 requests on a phone: images 1.4 MB (24), scripts 1.2 MB (40) and fonts 545 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 15 images in older formats

    15 images (1.2 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.

  • About 1.0 g of CO₂ per visit

    0.99 g

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

2 checks passed
  • 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

5 to fixGoogle 9391
  • 5 text elements with low contrast

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

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 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 (21 elements)

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

  • Headings should not be empty (4 elements)

    Headings should not be empty: 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
  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 4 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 9278
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (16 characters)

    Your title is only 16 characters: “Acasa - Aerostar”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 3 H1 headlines

    There are 3 <h1> headlines (“AEROSTAR S.A.”, “PERFORMANȚĂ PRIN PROFESIONALISM!” and “Sisteme Pentru Aparare”). One clear main headline is easier for people and search engines.

  • 100 internal links, 12 external

    The homepage links to 100 pages on aerostar.ro and 12 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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.aerostar.ro/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

2 to fix90
  • 15 pages without a meta description

    https://www.aerostar.ro/aerostar-astazi, https://www.aerostar.ro/filip-grigore, https://www.aerostar.ro/damaschin-doru, https://www.aerostar.ro/filip-alexandru, https://www.aerostar.ro/toncea-radu and https://www.aerostar.ro/doros-claudiu and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.aerostar.ro/aerostar-astazi, https://www.aerostar.ro/filip-grigore, https://www.aerostar.ro/damaschin-doru, https://www.aerostar.ro/filip-alexandru, https://www.aerostar.ro/toncea-radu and https://www.aerostar.ro/doros-claudiu and 9 others have 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 44 found) and read each the way a search engine does.

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

  • 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

2 to fixGoogle 7391
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'closest')”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • Local business without LocalBusiness data

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

  • Thin social proof

    Social proof on the homepage: 42 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

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

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

    The homepage carries about 735 words of visible text.

5 checks passed
  • Clear next step on the first screen

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

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact”.

  • 1 short form

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

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie, 1 of them by other companies (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.

  • 9 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Hosting
Vodafone Romania S.A.

Company

Founded
1953
Headquarters
Bacău

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on aerostar.ro, including 21 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