piata9.ro website review

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

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

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

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

Your mobile performance score is 27. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Clarity, omnisnippet1.com and Shopify and others), adding 1.0 MB and 1.1 s of main-thread time.

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

Clarity costs a phone 326 ms of main-thread work and 28 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.

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

omnisnippet1.com costs a phone 257 ms of main-thread work and 119 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.

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

Polyfills for old browsers add 53 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

3 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 22.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Piersici Piața9”.

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

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

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

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

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

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

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

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

Your homepage downloads 4.2 MB in 274 requests on a phone: images 1.5 MB (24), other files 1.0 MB (113) and scripts 1.0 MB (89). Under 2 MB keeps phones on slow connections fast.

BabkaCafea_hero_mobile_RO.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

1 element hidden from screen readers can still receive keyboard focus.

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

13 images have no alt text, which hurts accessibility and image search.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

58 form fields have no label, so screen readers announce an empty box and autofill guesses.

39 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: 10 elements on the page fail this check, rated minor by axe-core.

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

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

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

Your <h1> is empty.

The homepage links to 167 pages on piata9.ro and 8 external pages.

https://piata9.ro/collections/brutarie, https://piata9.ro/collections/brutarie/panettone, https://piata9.ro/collections/brutarie/babka, https://piata9.ro/collections/sugar-free, https://piata9.ro/collections/brutarie/fursecuri and https://piata9.ro/collections/spreads and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://piata9.ro/collections/brutarie, https://piata9.ro/collections/brutarie/panettone, https://piata9.ro/collections/brutarie/babka, https://piata9.ro/collections/sugar-free, https://piata9.ro/collections/brutarie/fursecuri and https://piata9.ro/collections/spreads and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://piata9.ro/pages/cetate and https://piata9.ro/pages/cariere took over 3 s to send their HTML from our server.

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

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

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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,247 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

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

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