mbl.bg website review

49 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).

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

About 483 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.4 s faster on a phone.

Your mobile performance score is 61 (desktop: 79). Pages that score under 90 lose visitors before the first paint.

About 145 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

9 images could be 383 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

102 KiB could be saved by minifying CSS.

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

2 third-party services load with your homepage (Facebook and Cloudflare CDN), adding 103 KiB and 54 ms of main-thread time.

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

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

3 KiB could be saved by minifying JavaScript.

Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “MBL IS A FULL-SERVICE REAL ESTATE COMPANY”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.0 MB in 52 requests on a phone: images 935 KiB (23), stylesheets 539 KiB (8) and scripts 312 KiB (12). Under 2 MB keeps phones on slow connections fast.

2 images (255 KiB) 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.

3 images further down the page (276 KiB) 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 0.58 g of CO₂e: 69.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h5, h2 → h5 and 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).

Your title is only 3 characters: “MBL”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your meta description is only 3 characters: “MBL”. 70 to 160 characters is enough to sell the click.

There are 6 <h1> headlines (“MBL offers a full scope of services to property d…”, “Market Overview for Office Space in Sofia - Q1 20…” and “MBL analysis: The future is in the hybrid model o…”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://mbl.bg/sitemap.xml, so Google discovers your pages only by following links.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 59 pages on mbl.bg and 7 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 https://mbl.bg/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.

https://mbl.bg/en-us, https://mbl.bg/en-us/index, https://mbl.bg/bg-bg/index, https://mbl.bg/en-us/the-company, https://mbl.bg/en-us/services and https://mbl.bg/en-us/projects and 10 others all use the title “MBL”. Search engines can't tell which page to show for a search, so each competes with the others.

https://mbl.bg/en-us/index, https://mbl.bg/bg-bg/index, https://mbl.bg/en-us/the-company, https://mbl.bg/en-us/services, https://mbl.bg/en-us/projects and https://mbl.bg/en-us/market-research and 9 others use the same meta description. A description written for each page earns more clicks.

https://mbl.bg/en-us/contacts has no <h1> headline, so visitors and search engines get no clear main topic.

https://mbl.bg/en-us/services and https://mbl.bg/en-us/ref-project-management-and-design 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.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

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

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

Before a visitor clicks anything, the page loads 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 3 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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.