papilora.ro website review

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

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

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

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

8 third-party services load with your homepage (uploadly-cdn.com, Shopify and chatlab.com and others), adding 1.3 MB and 672 ms of main-thread time.

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

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

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

chatlab.com costs a phone 134 ms of main-thread work and 362 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.

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

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

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

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.

3 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Pictură pe numere · −10 % – O seară liniștită cu pensula în…”.

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

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

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

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

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

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

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

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

Your homepage downloads 3.9 MB in 254 requests on a phone: scripts 1.3 MB (64), images 1.3 MB (28) and other files 819 KiB (102). Under 2 MB keeps phones on slow connections fast.

ob-2026-ro-mobil.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).

4 images are downloaded at several times the size a phone draws them, for example fe2a09a18f234dde9c082853d6d7985d.thumbnail.0000000000.jpg at 1,440 px wide, shown at 190 px. Resized copies would save about 230 KiB.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

Some list items are not inside a list.

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

2 elements hidden from screen readers can still receive keyboard focus.

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

Interactive controls must not be nested: 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: 14 elements on the page fail this check, rated moderate by axe-core.

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

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

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

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

The homepage links to 161 pages on papilora.ro and 139 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

Your homepage links to https://papilora.ro/collections/tablouri-toamna, https://papilora.ro/blogs/sfaturi-pentru-alegerea-si-agatarea-tablourilor and https://papilora.ro/products/tablouri-de-ingeri-rugaciunea-de-dimineata-100-original-acrilic-pictat-ro-xogmdpa158e1, which answer with an error. Visitors hit a dead end and search engines drop them.

https://papilora.ro/pages/wishlist, https://papilora.ro/pages/idei-pentru-perete, https://papilora.ro/products/pictat-manual-pop-art-pictura-al-pacino-1-buc-al12-ro-yobppal12, https://papilora.ro/products/pictat-manual-pop-art-pictura-bob-dylan-1-parte-bd-ro-yobppbd, https://papilora.ro/products/tablou-de-perete-pictat-abstrakt-1-parte-120x40-cm-cwf1137l-145e1-ro-cwf1137l-145e1 and https://papilora.ro/products/imagine-eleganta-a-unei-femei-sleep-ro-xobmdld107e1 and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://papilora.ro/products/imaginea-din-fotografie-obd-nik-ro-xobfoto-o and https://papilora.ro/products/caricatura-personalizata-din-poza-cadou-amuzant-pe-panza-ro-xobkar001e1 have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://papilora.ro/collections/seturi-premium-de-tablouri took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://papilora.ro/.

2 errors were logged to the browser console while the page loaded, for example “ReferenceError: $ is not defined”.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 826 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 11 cookies (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 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.