ab.gr website review

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

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

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

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

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

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

Adobe Tag Manager costs a phone 377 ms of main-thread work and 186 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.

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

1 third-party service load with your homepage (Adobe Tag Manager), adding 186 KiB and 377 ms of main-thread time.

Polyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

Desktop scores 70 but mobile only 40. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

2 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 270 ms to 326 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.5 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.1 MB in 102 requests on a phone: scripts 1.8 MB (41), images 979 KiB (52) and HTML 263 KiB (1). Under 2 MB keeps phones on slow connections fast.

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

Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.

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

Elements must only use permitted ARIA attributes: 53 elements on the page fail this check, rated serious by axe-core.

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

Elements marked as presentational should be consistently ignored: 14 elements on the page fail this check, rated minor by axe-core.

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

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

Structured data found (Organization, SoftwareApplication and WebSite) but with 7 problems, for example “Organization: url is not an absolute URL ("https://urldefense.com/v3/__https://www.ab.gr/__;!!GF_29…”.

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 83 pages on ab.gr and 13 external pages.

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.

Your homepage links to /start-sso, which answers with an error. Visitors hit a dead end and search engines drop it.

/customerhub/quick-shop/orders is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/customerhub/quick-shop/orders, /productsServices, /recipes, /loyalty and /storelocator have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 10 pages by a URL that isn't their canonical one, for example /promotions/leaflet, whose canonical is /el/promotions/leaflet. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/promotions/leaflet, /productsServices, /recipes and /loyalty 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.

/customerhub/quick-shop/orders, /promotions/leaflet, /recipes and /el/eshop/Fresko-Kreas-and-Psaria/c/002 took over 3 s to send their HTML from our server.

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

3 errors were logged to the browser console while the page loaded, for example “u: [@formatjs/intl Error FORMAT_ERROR] Error formatting message: "ecom.timeslot.expired.popup.description", using id as…”.

Large scripts ship without source maps.

1 link from your homepage to your own site is broken, for example https://www.ab.gr/start-sso?redirect_uri=%2F&registration_uri=%2Freg%2Faddress&lastViewedPage=%2F&claims=%7B%22userinfo%22%3A%7B%22ssoCiamJourneyId%22%3A%22ab-gr-SSO-sub-journey-1.0.0%22%7D%7D (400).

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

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

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 153 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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.

Opening the homepage sets 9 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 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.