Website review, no card needed

scandia.ro logo

scandia.ro website review

Visit site (opens in a new tab)Reviewed 19 November 202626 issues · 75 checks

This review found 26 issues worth fixing on scandia.ro, 12 of them high impact, across 75 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
3.1 s1.9 sMay 30Nov 142.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.7 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20262.8 s
Aug 8, 20262.5 s
Aug 15, 20262.4 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.1 s
Oct 24, 20262.2 s
Oct 31, 20262.4 s
Nov 7, 20262.4 s
Nov 14, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
125 ms81 msMay 30Nov 14103 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026104 ms
Jun 6, 2026101 ms
Jun 13, 2026102 ms
Jun 20, 2026100 ms
Jun 27, 2026101 ms
Jul 4, 2026102 ms
Jul 11, 2026102 ms
Jul 18, 2026103 ms
Jul 25, 202694 ms
Aug 1, 202691 ms
Aug 8, 202686 ms
Aug 15, 202695 ms
Aug 22, 2026104 ms
Aug 29, 2026111 ms
Sep 5, 2026120 ms
Sep 12, 2026116 ms
Sep 19, 2026114 ms
Sep 26, 2026110 ms
Oct 3, 2026105 ms
Oct 10, 2026105 ms
Oct 17, 2026104 ms
Oct 24, 2026100 ms
Oct 31, 202696 ms
Nov 7, 202698 ms
Nov 14, 2026103 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 scandia.ro (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. scandia.ro at 1.0 s1.0 s
  2. scandia.ro at 2.1 s2.1 s
  3. scandia.ro at 3.1 s3.1 s
  4. scandia.ro at 4.2 s4.2 s
  5. scandia.ro at 5.2 s5.2 s
  6. scandia.ro at 6.2 s6.2 s
  7. scandia.ro at 7.3 s7.3 s
  8. scandia.ro at 8.3 s8.3 s

Speed

7 to fix55
  • Use efficient cache lifetimes

    9.7 s · 2.3 MB

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

  • Render-blocking requests

    10.8 s

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

  • Reduce unused CSS

    9.0 s · 1.4 MB

    About 1.4 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 9.0 s faster on a phone.

  • Reduce unused JavaScript

    1.5 s · 188 KiB

    About 188 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Mobile performance score: 55

    55/100

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

  • Minify CSS

    450 ms · 101 KiB

    101 KiB could be saved by minifying CSS.

  • Font display

    500 ms

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 369 KiB and 135 ms of main-thread time.

  • Improve image delivery

    161 KiB

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

  • Document request latency

    99 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 2 long tasks on the main thread

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

  • Minify JavaScript

    57 KiB

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

2 checks passed
  • Main-thread work: 0.8 s

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

  • Server response: 370 ms

    370 ms

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

Core Web Vitals

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

  • Real-user TTFB: 1.9 s

    1.9 s

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

  • First Contentful Paint: 11.6 s

    11.6 s

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

  • Largest Contentful Paint: 15.2 s

    15.2 s

    Your largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Scandia Food este o companie românească cu tradiție, defini…”.

  • Speed Index: 15.9 s

    15.9 s

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

  • Time to Interactive: 15.2 s

    15.2 s

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

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -2%

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

5 checks passed
  • Real-user INP: 102 ms

    102 ms

    Real visitors wait 102 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.

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

    -11%

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

  • Cumulative Layout Shift: 0.027

    0.027

    The layout barely moves while loading (CLS 0.027, 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

1 to fix85
  • Page weight: 2.8 MB in 69 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 69 requests on a phone: stylesheets 1.5 MB (21), scripts 586 KiB (25) and images 378 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

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

  • 7 images below the first screen load straight away

    7 images further down the page (262 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.80 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

Google 100100
  • 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 15 images in the HTML carry an alt attribute.

  • 49 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: 49 passed and 0 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10085
  • No H1 headline

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

  • Meta description is short (23 characters)

    Your meta description is only 23 characters: “Viață plină de savoare!”. 70 to 160 characters is enough to sell the click.

  • 31 internal links, 7 external

    The homepage links to 31 pages on scandia.ro and 7 external pages.

6 checks passed
  • Title: 38 characters

    Your title is a healthy 38 characters: “Scandia Food – Viață plină de savoare!”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: 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://scandia.ro/wp-sitemap.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: 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 (450 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 13 pages without a meta description

    https://scandia.ro/despre-noi, https://scandia.ro/istoria-scandia-food, https://scandia.ro/fabricile-scandia-food, https://scandia.ro/energie-verde, https://scandia.ro/sustenabilitate and https://scandia.ro/comunicate-de-presa and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://scandia.ro/despre-noi, https://scandia.ro/istoria-scandia-food, https://scandia.ro/fabricile-scandia-food, https://scandia.ro/energie-verde, https://scandia.ro/sustenabilitate and https://scandia.ro/comunicate-de-presa and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://scandia.ro/energie-verde, https://scandia.ro/congelate and https://scandia.ro/cariere took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 18 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 9687
  • 4 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “jQuery is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 294 words of copy

    The homepage carries about 294 words of visible text.

4 checks passed
  • Clear next step on the first screen

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

  • 2 calls to action

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

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 scandia.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
GTS Telecom SRL

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on scandia.ro, including 16 speed issues, 2 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