Website review, no card needed

abs.com.gr logo

abs.com.gr website review

Visit site (opens in a new tab)Reviewed 17 November 202638 issues · 79 checks

This review found 38 issues worth fixing on abs.com.gr, 13 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of abs.com.gr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. abs.com.gr at 1.0 s1.0 s
  2. abs.com.gr at 1.9 s1.9 s
  3. abs.com.gr at 2.9 s2.9 s
  4. abs.com.gr at 3.9 s3.9 s
  5. abs.com.gr at 4.8 s4.8 s
  6. abs.com.gr at 5.8 s5.8 s
  7. abs.com.gr at 6.8 s6.8 s
  8. abs.com.gr at 7.8 s7.8 s

Speed

7 to fix61
  • Use efficient cache lifetimes

    2.5 s · 706 KiB

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

  • Render-blocking requests

    2.5 s

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

  • Reduce unused JavaScript

    1.2 s · 223 KiB

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

  • Reduce unused CSS

    900 ms · 180 KiB

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

  • Improve image delivery

    600 ms · 421 KiB

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

  • Mobile performance score: 61

    61/100

    Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.

  • Google Fonts adds 1 ms

    1 ms

    Google Fonts costs a phone 1 ms of main-thread work and 302 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.

  • Minify JavaScript

    150 ms · 45 KiB

    45 KiB could be saved by minifying JavaScript.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 480 KiB and 95 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Minify CSS

    8 KiB

    8 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    6 KiB

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

  • Chained critical requests

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

2 checks passed
  • Main-thread work: 1.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 573 ms of it running JavaScript. That is comfortably low.

  • Server response: 97 ms

    97 ms

    Your server sent the HTML in 97 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix63
  • Largest Contentful Paint: 9.8 s

    9.8 s

    Your largest element takes 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (6.6 s).

  • Speed Index: 12.8 s

    12.8 s

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

  • Time to Interactive: 9.9 s

    9.9 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Cumulative Layout Shift: 0.102

    0.102

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

  • 2 images without width and height

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

  • Not enough real-visitor data yet

    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.

1 checks passed
  • Total Blocking Time: 7 ms

    7 ms

    Scripts block the page for only 7 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix58
  • Page weight: 2.5 MB in 107 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 107 requests on a phone: images 1.3 MB (28), scripts 594 KiB (36) and fonts 431 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 8 images in older formats

    8 images (593 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.

  • 8 images below the first screen load straight away

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

  • 1 image far larger than shown

    82 KiB

    1 image is downloaded at several times the size a phone draws it, for example sunagermos_bg2_.jpg at 1,600 px wide, shown at 350 px. Resized copies would save about 82 KiB.

  • About 0.7 g of CO₂ per visit

    0.72 g

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

Accessibility

10 to fixGoogle 7585
  • 6 text elements with low contrast

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

  • 6 tap targets too small

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

  • ARIA commands must have an accessible name (5 elements)

    ARIA commands must have an accessible name: 5 elements on the page fail this check, rated serious by axe-core.

  • Elements must only use permitted ARIA attributes (2 elements)

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • All page content should be contained by landmarks (13 elements)

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 12 links without text

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

  • ARIA role should be appropriate for the element (2 elements)

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

  • Elements marked as presentational should be consistently ignored (2 elements)

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 18 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 11 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9293
  • 3 H1 headlines

    There are 3 <h1> headlines (“”, “” and “Συναγερμός Σπιτιών και Εταιρειών και Υπηρεσίες Ασ…”). One clear main headline is easier for people and search engines.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 90 internal links, 4 external

    The homepage links to 90 pages on abs.com.gr and 4 external pages.

7 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Οι συναγερμοί σπιτιών είναι η εξειδίκευση της ABS security στην Αττική, όπου προσφέρει αξιόπιστους συναγερμούς σπιτιών …”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Συναγερμοί σπιτιών - ABS SECURITY - Αθήνα - Αττική”.

  • Canonical URL set

    The canonical URL is https://www.abs.com.gr/.

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and WebPage.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.abs.com.gr/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

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

  • No llms.txt

    There is no https://www.abs.com.gr/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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (221 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 13 pages without a meta description

    https://www.abs.com.gr/synagermos_spition, https://www.abs.com.gr/prosfora-synagermos-spitiou-timi-270, https://www.abs.com.gr/asyrmatos_sunagermos_160_euro, https://www.abs.com.gr/sunagermos-asurmatos-prosfora-spitiou, https://www.abs.com.gr/prosfora-asurmatos-sunagermos-spitiou-2016 and https://www.abs.com.gr/prosfores-times-sungermou-spitiwn and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://www.abs.com.gr/about, https://www.abs.com.gr/access-control-360, https://www.abs.com.gr/access-control-me-smartphone and https://www.abs.com.gr/access-control-airbnb-700-ip have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages with very little text

    https://www.abs.com.gr/about, https://www.abs.com.gr/24%cf%89%cf%81%ce%bf-%ce%ba%ce%ad%ce%bd%cf%84%cf%81%ce%bf-%ce%bb%ce%ae%cf%88%ce%b7%cf%82-%cf%83%ce%b7%ce%bc%ce%ac%cf%84%cf%89%ce%bd, https://www.abs.com.gr/elegxos-prosvasis-portas-kleidoma, https://www.abs.com.gr/access-control-360, https://www.abs.com.gr/access-control-me-smartphone and https://www.abs.com.gr/access-control-airbnb-700-ip and 1 other 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.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Popover is not defined”.

2 checks passed
  • Tap targets are thumb-sized

    21 of 25 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • No call to action on the first screen

    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 calls to action

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

  • Thin social proof

    Social proof on the homepage: 10 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 209 words

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

  • No form on the homepage

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

  • No risk reducer

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

2 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

  • 2 cookies set on arrival

    2

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

  • No consent tool detected

    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.

  • 5 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at abs.com.gr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2023.

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics
Hosting
Krystal Hosting Ltd

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on abs.com.gr, including 13 speed issues, 2 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25