bazaar-online.gr website review

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

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

YouTube costs a phone 1.3 s of main-thread work and 1.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 2.3 MB and 1.9 s of main-thread time.

About 1.3 MB of JavaScript is downloaded but never used on this page.

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

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

71 KiB could be saved by minifying CSS.

Google Tag Manager costs a phone 346 ms of main-thread work and 178 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.

Facebook costs a phone 281 ms of main-thread work and 223 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.

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

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

21 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 12 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.

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.

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

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

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

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

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

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

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

Real visitors wait 495 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

Your homepage downloads 4.8 MB in 165 requests on a phone: scripts 2.2 MB (29), images 1.9 MB (90) and stylesheets 341 KiB (19). Under 2 MB keeps phones on slow connections fast.

8 images further down the page (258 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images (109 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.

By the Sustainable Web Design model, a visit to your homepage emits about 1.36 g of CO₂e: 163.5 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”.

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

2 frames have no title, so screen-reader users cannot tell what they contain.

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (4 elements).

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 canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

24 links have no real href, so search engines can't follow them.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.bazaar-online.gr/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 1,948 pages on bazaar-online.gr and 0 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.

/allantika-delicatessen, /allantika-delicatessen/delicatessen, /allantika-delicatessen/delicatessen/alipasta, /allantika-delicatessen/delicatessen/ayga-rarion, /allantika-delicatessen/delicatessen/elies and /allantika-delicatessen/delicatessen/etoima-fagita and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/allantika-delicatessen, /allantika-delicatessen/delicatessen, /allantika-delicatessen/delicatessen/alipasta, /allantika-delicatessen/delicatessen/ayga-rarion, /allantika-delicatessen/delicatessen/elies and /allantika-delicatessen/delicatessen/etoima-fagita and 9 others 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.

/allantika-delicatessen/allantika/galopoula-vrasti-riti took over 3 s to send its HTML from our server.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

4 images are served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

bazaar-online.gr has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

bazaar-online.gr has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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