yettel.bg website review

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

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

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

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

1 image could be 202 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

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

4 third-party services load with your homepage (Google Tag Manager, Cookiebot and JSDelivr CDN and others), adding 442 KiB and 282 ms of main-thread time.

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

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

Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

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

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

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

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

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

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

17 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-24, real Chrome visitors' tap response (inp) went from 195 ms to 228 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 4.6 MB in 84 requests on a phone: images 3.7 MB (63), scripts 552 KiB (8) and stylesheets 169 KiB (6). Under 2 MB keeps phones on slow connections fast.

top-offers-banner-xiaomi-online-exclusive-bundles.png weighs 777 KiB. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example top-offers-banner-xiaomi-online-exclusive-bundles.png at 1,218 px wide, shown at 276 px. Resized copies would save about 851 KiB.

9 images (2.9 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.

iphone-duo-home-banner-mobile.png 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).

1 image further down the page (162 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 1.31 g of CO₂e: 156.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image (also missing: og:title, og:description), 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 196 pages on yettel.bg and 16 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/bg and / all use the title “Yettel - мобилни планове, интернет, телевизия и устройства”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/bg/ustroystva/partnyori/yettel-and-apple, /bg/partniori/yettel-i-samsung and /bg/partniori/yettel-i-xiaomi have no meta description, so Google writes the search snippet from whatever text it finds.

/bg/eshop/offers, /bg/eshop/orders and /bg/eshop/consent-list use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is /bg. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/, /bg/eshop/offers, /bg/eshop/orders, /bg/eshop/consent-list, /bg/eshop/plan-gallery and /bg/eshop/device-gallery and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

/bg/ustroystva/smartfon-vselena/multi-sim has 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.

/, /bg/ekskluzivni-oferti-v-online-magazina, /bg/eshop/landing/razprodazhba-razopakovani-ustroystva, /bg/ustroystva/partnyori/yettel-and-apple, /bg/partniori/yettel-i-samsung and /bg/partniori/yettel-i-xiaomi and 4 others took over 3 s to send their HTML from our server.

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

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 104 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

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

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 3 cookies (measured from a US location before any click).

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