1001obuvki.com website review

58 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.

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

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

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

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

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

About 94 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

6 third-party services load with your homepage (Google Tag Manager, Yandex Metrica and Google Analytics and others), adding 678 KiB and 537 ms of main-thread time.

Google Tag Manager costs a phone 448 ms of main-thread work and 587 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 KiB could be saved by minifying CSS.

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

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.

Your largest element takes 15.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Дамски сникърси PESHTERA™ от естествена кожа и велур в тъмн…”.

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

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

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

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

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

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

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

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

5 images are downloaded at several times the size a phone draws them, for example 5-отстъпка-над-99-мобилна.m.jpg at 9,449 px wide, shown at 390 px. Resized copies would save about 843 KiB.

Your homepage downloads 3.8 MB in 138 requests on a phone: images 2.7 MB (104), scripts 741 KiB (8) and fonts 268 KiB (5). Under 2 MB keeps phones on slow connections fast.

7 images (1.3 MB) 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.

15 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

3 visible links have no text or label, so screen readers cannot say where they go.

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

There are 5 <h1> headlines (“Специални предложения от ДАМСКИ БОТИ”, “Специални предложения от ДАМСКИ ЕЖЕДНЕВНИ ОБУВКИ” and “Специални предложения от ДАМСКИ ЛОУФЪРИ”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 527 pages on 1001obuvki.com and 9 external pages.

Your Organization JSON-LD is missing url, logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

Your homepage links to https://www.1001obuvki.com/namerete-vashite-obuvki-peshtera, https://www.1001obuvki.com/damski-boti, https://www.1001obuvki.com/elegantni-boti, https://www.1001obuvki.com/damski-zimni-boti and https://www.1001obuvki.com/damski-botushi, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.1001obuvki.com/bg declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://www.1001obuvki.com/bg all use the title “Обувки онлайн | ПЕЩЕРА СТИЛ – PESHTERA™ Footwear”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.1001obuvki.com/bg and https://www.1001obuvki.com/damski-klarkove took over 3 s to send their HTML from our server.

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

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Yandex Metrica (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 13 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.