Website review, no card needed

sobuy.gr logo

sobuy.gr website review

Visit site (opens in a new tab)Reviewed 9 November 202632 issues · 76 checks

This review found 32 issues worth fixing on sobuy.gr, 10 of them high impact, across 76 checks. The most urgent: hcaptcha.com adds 1.1 s. 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

Real-visitor load time (LCP)75th percentile, phones
2.2 s1.4 sMay 23Nov 71.7 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.1 s
May 30, 20261.9 s
Jun 6, 20261.8 s
Jul 25, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Oct 10, 20261.7 s
Oct 17, 20261.6 s
Oct 24, 20261.5 s
Oct 31, 20261.6 s
Nov 7, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
219 ms117 msMay 23Nov 7160 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026195 ms
May 30, 2026207 ms
Jul 18, 2026129 ms
Jul 25, 2026154 ms
Aug 29, 2026181 ms
Sep 5, 2026172 ms
Sep 12, 2026156 ms
Oct 3, 2026155 ms
Oct 10, 2026155 ms
Oct 17, 2026144 ms
Oct 24, 2026131 ms
Oct 31, 2026151 ms
Nov 7, 2026160 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

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

How it loaded on a phone

  1. sobuy.gr at 0.4 s0.4 s
  2. sobuy.gr at 0.8 s0.8 s
  3. sobuy.gr at 1.1 s1.1 s
  4. sobuy.gr at 1.5 s1.5 s
  5. sobuy.gr at 1.9 s1.9 s
  6. sobuy.gr at 2.3 s2.3 s
  7. sobuy.gr at 2.6 s2.6 s
  8. sobuy.gr at 3.0 s3.0 s

Speed

10 to fix50
  • hcaptcha.com adds 1.1 s

    1.1 s

    hcaptcha.com costs a phone 1.1 s of main-thread work and 1.2 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.

  • Main-thread work: 5.8 s

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

  • 3,326 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (hcaptcha.com, Shopify and Clarity and others), adding 2.8 MB and 1.7 s of main-thread time.

  • Mobile performance score: 50

    50/100

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

  • Reduce unused JavaScript

    150 ms · 572 KiB

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

  • Render-blocking requests

    500 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.

  • Shopify adds 360 ms

    360 ms

    Shopify costs a phone 360 ms of main-thread work and 1.2 MB 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.

  • Use efficient cache lifetimes

    367 KiB

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

  • 15 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 40 KiB

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

  • Legacy JavaScript

    59 KiB

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

  • Improve image delivery

    12 KiB

    1 image could be 12 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 25.8 s

    25.8 s

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

  • Largest Contentful Paint: 6.5 s

    6.5 s

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

  • Total Blocking Time: 978 ms

    978 ms

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

  • Speed Index: 6.0 s

    6.0 s

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

10 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user INP: 160 ms

    160 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 374 ms

    374 ms

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

  • Tap response (INP) got 23% faster for real visitors

    -23%

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

  • Largest content (LCP) got 17% faster for real visitors

    -17%

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.011

    0.011

    The layout barely moves while loading (CLS 0.011, good is under 0.1).

Images and page weight

1 to fix33
  • Page weight: 4.6 MB in 422 requests

    4.6 MB

    Your homepage downloads 4.6 MB in 422 requests on a phone: scripts 2.1 MB (183), other files 1.1 MB (182) and images 657 KiB (33). Under 2 MB keeps phones on slow connections fast.

  • About 1.3 g of CO₂ per visit

    1.29 g

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

Accessibility

5 to fixGoogle 8894
  • All page content should be contained by landmarks (3 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (1 element)

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

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

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

SEO

2 to fixGoogle 9289
  • Title is long (82 characters)

    Your title is 82 characters, so Google will cut it off around 60: “SoBuy | Καροτσάκια κουζίνας | Ντουλάπια μπάνιου | Πίνακες μπαρ | Γραφεία– SoBuy-IT”.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://sobuy.it)”.

  • 289 internal links, 9 external

    The homepage links to 289 pages on sobuy.gr and 9 external pages.

6 checks passed
  • Meta description: 124 characters

    Your meta description is 124 characters: “SoBuy Η Commercial Ltd προσφέρει καινοτόμες και σύγχρονες λύσεις επίπλων. Η εξειδίκευση καθιστά την καλύτερη δυνατή από…”.

  • One H1 headline

    Your main headline reads: “SoBuy-IT”.

  • Canonical URL set

    The canonical URL is https://sobuy.gr/.

  • 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://sobuy.gr/sitemap.xml.

AI search readiness

100
3 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • llms.txt published

    The site publishes https://sobuy.gr/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix63
  • 1 page without a title

    https://sobuy.gr/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://sobuy.gr/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 11 pages without a meta description

    https://sobuy.gr/customer_authentication/redirect, https://sobuy.gr/collections/%CE%B5%CE%AF%CF%83%CE%BF%CE%B4%CE%BF%CF%82, https://sobuy.gr/collections/%CE%B2%CE%AC%CF%83%CE%B7-%CE%B3%CE%B9%CE%B1-%CF%80%CE%B1%CE%BB%CF%84%CF%8C, https://sobuy.gr/collections/%CE%BA%CE%BF%CE%BD%CF%83%CF%8C%CE%BB%CE%B1, https://sobuy.gr/collections/%CE%BB%CE%BF%CF%8D%CF%84%CF%81%CE%BF and https://sobuy.gr/collections/%CF%88%CE%B7%CE%BB%CE%AE-%CE%BD%CF%84%CE%BF%CF%85%CE%BB%CE%AC%CF%80%CE%B1 and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 links to non-canonical URLs

    Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://sobuy.gr/collections/%CE%BD%CE%B5%CE%B5%CF%83-%CE%B1%CF%86%CE%B9%CE%BE%CE%B5%CE%B9%CF%83-1, whose canonical is https://sobuy.gr/collections/%ce%bd%ce%b5%ce%b5%cf%83-%ce%b1%cf%86%ce%b9%ce%be%ce%b5%ce%b9%cf%83-1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://sobuy.gr/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://sobuy.gr/collections/%CE%BB%CE%BF%CF%8D%CF%84%CF%81%CE%BF took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 503 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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.

  • Thin social proof

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

  • Only about 24 words

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

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

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “[email protected]”.

  • 28 short forms

    28 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Microsoft Clarity (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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies, 8 of them by other companies (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.

  • 12 other companies contacted

    Loading the homepage contacts 12 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 sobuy.gr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Blockify Fraud Filter · Inbox · Microsoft Clarity · Region Restrictions · Accessibly App · Forms · Selleasy · trustedshops.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on sobuy.gr, including 14 speed issues, 2 SEO issues and 3 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