Website review, no card needed

starnet.md logo

starnet.md website review

Visit site (opens in a new tab)Reviewed 26 October 202627 issues · 57 checks

This review found 27 issues worth fixing on starnet.md, 8 of them high impact, across 57 checks. The most urgent: fails Core Web Vitals for real visitors. 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.1 s1.4 sMay 9Oct 241.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.8 s
May 16, 20263.7 s
May 23, 20263.7 s
May 30, 20263.5 s
Jun 6, 20263.4 s
Jun 13, 20263.2 s
Jun 20, 20263.2 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.7 s
Jul 18, 20262.8 s
Jul 25, 20262.9 s
Aug 1, 20262.5 s
Aug 8, 20262.7 s
Aug 15, 20262.6 s
Aug 22, 20262.8 s
Aug 29, 20262.4 s
Sep 5, 20262.5 s
Sep 12, 20262.6 s
Sep 19, 20262.2 s
Sep 26, 20262.0 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
274 ms143 msMay 9Oct 24242 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026158 ms
May 16, 2026161 ms
May 23, 2026166 ms
May 30, 2026173 ms
Jun 6, 2026179 ms
Jun 13, 2026182 ms
Jun 20, 2026182 ms
Jun 27, 2026179 ms
Jul 4, 2026180 ms
Jul 11, 2026179 ms
Jul 18, 2026180 ms
Jul 25, 2026180 ms
Aug 1, 2026183 ms
Aug 8, 2026192 ms
Aug 15, 2026196 ms
Aug 22, 2026202 ms
Aug 29, 2026215 ms
Sep 5, 2026235 ms
Sep 12, 2026232 ms
Sep 19, 2026253 ms
Sep 26, 2026253 ms
Oct 3, 2026247 ms
Oct 10, 2026259 ms
Oct 17, 2026245 ms
Oct 24, 2026242 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 starnet.md (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. starnet.md at 1.2 s1.2 s
  2. starnet.md at 2.3 s2.3 s
  3. starnet.md at 3.5 s3.5 s
  4. starnet.md at 4.7 s4.7 s
  5. starnet.md at 5.8 s5.8 s
  6. starnet.md at 7.0 s7.0 s
  7. starnet.md at 8.2 s8.2 s
  8. starnet.md at 9.3 s9.3 s

Speed

7 to fix74
  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 2.3 MB and 1.3 s of main-thread time.

  • Reduce unused JavaScript

    1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page.

  • Mobile performance score: 74

    74/100

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

  • Google Tag Manager adds 812 ms

    812 ms

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

  • Render-blocking requests

    700 ms

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

  • Google CDN adds 344 ms

    344 ms

    Google CDN costs a phone 344 ms of main-thread work and 734 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.

  • Main-thread work: 3.8 s

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

  • Use efficient cache lifetimes

    223 KiB

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

  • Reduce unused CSS

    205 KiB

    About 205 KiB of CSS is downloaded but never applied on this page.

  • 20 long tasks on the main thread

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

  • Improve image delivery

    83 KiB

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

  • Legacy JavaScript

    48 KiB

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

1 checks passed
  • Server response: 281 ms

    281 ms

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

Core Web Vitals

6 to fix67
  • 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.

  • Time to Interactive: 24.6 s

    24.6 s

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

  • Speed Index: 7.0 s

    7.0 s

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

  • Total Blocking Time: 762 ms

    762 ms

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

  • Real-user INP: 276 ms

    276 ms

    Real visitors wait 276 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

    +53%

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

8 checks passed
  • Real-user LCP: 1.2 s

    1.2 s

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

  • Real-user CLS: 0.07

    0.07

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 676 ms

    676 ms

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

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

    -51%

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

  • Cumulative Layout Shift: 0.061

    0.061

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 1.5 s

    1.5 s

    Your largest element renders in 1.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image “Internet + TV acasă”.

Images and page weight

1 to fix0
  • Page weight: 4.4 MB in 101 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 101 requests on a phone: scripts 3.0 MB (43), other files 520 KiB (17) and images 426 KiB (30). Under 2 MB keeps phones on slow connections fast.

  • About 1.2 g of CO₂ per visit

    1.24 g

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

Accessibility

2 to fix91
  • Form elements do not have associated labels

    Form elements do not have associated labels (2 elements).

  • 64 text elements with low contrast

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

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

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

1 checks passed
  • Every image has alt text

    All 49 images in the HTML carry an alt attribute.

SEO

5 to fixGoogle 9277
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is short (32 characters)

    Your meta description is only 32 characters: “Mai bun, Mai rapid, Mai puternic”. 70 to 160 characters is enough to sell the click.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 62 internal links, 15 external

    The homepage links to 62 pages on starnet.md and 15 external pages.

4 checks passed
  • Title: 42 characters

    Your title is a healthy 42 characters: “Mai bun, Mai rapid, Mai puternic - StarNet”.

  • Canonical URL set

    The canonical URL is https://www.starnet.md/ro.

  • 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://starnet.md/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    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.

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.

  • llms.txt published

    The site publishes https://starnet.md/llms.txt (1 KiB, 2 links), a plain-text guide to the site for AI tools.

Other pages

  • Your server turned our page checks away

    15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

Best practices

1 to fixGoogle 9693
  • 1 console error

    1 error was logged to the browser console during Google's test (“requestStorageAccess: Permission denied.”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: 2 trust badges. 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 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 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 584 words of copy

    The homepage carries about 584 words of visible text.

1 checks passed
  • 2 short forms

    2 short forms (3 fields at most) are right on the homepage.

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

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
Starnet

Company

Employees
985
Founded
2003
Headquarters
Chișinău

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on starnet.md, including 13 speed issues, 5 SEO issues and 4 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