novistar.ro website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and omnisnippet1.com and others), adding 33.3 MB and 643 ms of main-thread time.

Shopify costs a phone 148 ms of main-thread work and 32.5 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.

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

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

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

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

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

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

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

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

The layout shifts by 0.102 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 34.7 MB in 197 requests on a phone: media 32.1 MB (2), scripts 1.2 MB (51) and other files 693 KiB (85). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (22 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

There are 2 <h1> headlines (“” and “Produse Profesionale de Curățenie și Igienă - Nov…”). One clear main headline is easier for people and search engines.

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

The homepage links to 220 pages on novistar.ro and 12 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://novistar.ro/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://novistar.ro/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

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

https://novistar.ro/customer_authentication/redirect, https://novistar.ro/collections/detergenti-profesionali and https://novistar.ro/collections/pardoseli have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 31 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

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

Opening the homepage sets 17 cookies, 1 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.