Website review, no card needed

cosmodata.gr logo

cosmodata.gr website review

Visit site (opens in a new tab)Reviewed 23 October 202656 issues · 97 checks

This review found 56 issues worth fixing on cosmodata.gr, 23 of them high impact, across 97 checks. The most urgent: improve image delivery. 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
5.6 s3.6 sMay 2Oct 173.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.5 s
May 9, 20264.5 s
May 16, 20264.5 s
May 23, 20264.6 s
May 30, 20264.7 s
Jun 6, 20265.0 s
Jun 13, 20265.3 s
Jun 20, 20265.3 s
Jun 27, 20265.1 s
Jul 4, 20264.8 s
Jul 11, 20264.9 s
Jul 18, 20265.0 s
Jul 25, 20264.9 s
Aug 1, 20264.7 s
Aug 8, 20264.3 s
Aug 15, 20264.4 s
Aug 22, 20264.7 s
Aug 29, 20265.3 s
Sep 5, 20265.4 s
Sep 12, 20265.0 s
Sep 19, 20264.3 s
Sep 26, 20264.0 s
Oct 3, 20264.1 s
Oct 10, 20264.0 s
Oct 17, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
173 ms140 msMay 2Oct 17162 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026144 ms
May 9, 2026145 ms
May 16, 2026147 ms
May 23, 2026150 ms
May 30, 2026155 ms
Jun 6, 2026160 ms
Jun 13, 2026162 ms
Jun 20, 2026163 ms
Jun 27, 2026164 ms
Jul 4, 2026164 ms
Jul 11, 2026164 ms
Jul 18, 2026164 ms
Jul 25, 2026163 ms
Aug 1, 2026164 ms
Aug 8, 2026165 ms
Aug 15, 2026167 ms
Aug 22, 2026168 ms
Aug 29, 2026169 ms
Sep 5, 2026169 ms
Sep 12, 2026169 ms
Sep 19, 2026169 ms
Sep 26, 2026167 ms
Oct 3, 2026165 ms
Oct 10, 2026163 ms
Oct 17, 2026162 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 cosmodata.gr (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cosmodata.gr at 1.7 s1.7 s
  2. cosmodata.gr at 3.4 s3.4 s
  3. cosmodata.gr at 5.1 s5.1 s
  4. cosmodata.gr at 6.7 s6.7 s
  5. cosmodata.gr at 8.4 s8.4 s
  6. cosmodata.gr at 10.1 s10.1 s
  7. cosmodata.gr at 11.8 s11.8 s
  8. cosmodata.gr at 13.5 s13.5 s

Speed

14 to fix39
  • Improve image delivery

    4.7 s · 5.5 MB

    50 images could be 5.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.7 s faster on a phone.

  • Use efficient cache lifetimes

    3.6 s · 5.7 MB

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

  • Reduce unused JavaScript

    4.5 s · 937 KiB

    About 937 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.5 s faster on a phone.

  • Mobile performance score: 39

    39/100

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

  • 7,933 HTML elements

    The page has 7,933 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 (Google Tag Manager, octocom.ai and Google CDN and others), adding 1.9 MB and 806 ms of main-thread time.

  • Render-blocking requests

    900 ms

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

  • Document request latency

    800 ms

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

  • Reduce initial server response time

    781 ms

    Reduce initial server response time. Google estimates savings of 781 ms on a phone.

  • Google Tag Manager adds 336 ms

    336 ms

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

  • Main-thread work: 2.4 s

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

  • octocom.ai adds 173 ms

    173 ms

    octocom.ai costs a phone 173 ms of main-thread work and 652 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.

  • Google CDN adds 79 ms

    79 ms

    Google CDN costs a phone 79 ms of main-thread work and 348 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.

  • Server response: 881 ms

    881 ms

    Your server takes 881 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 25 KiB

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

  • Font display

    100 ms

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

  • Reduce unused CSS

    49 KiB

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

  • Minify JavaScript

    36 KiB

    36 KiB could be saved by minifying JavaScript.

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

    5 KiB

    5 KiB could be saved by minifying CSS.

Core Web Vitals

11 to fix33
  • Fails Core Web Vitals for real visitors

    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-user LCP: 7.0 s

    7.0 s

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

  • Real-user FCP: 6.1 s

    6.1 s

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

  • Real-user TTFB: 5.7 s

    5.7 s

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

  • Largest Contentful Paint: 50.5 s

    50.5 s

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

  • Speed Index: 17.8 s

    17.8 s

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

  • Time to Interactive: 53.3 s

    53.3 s

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

  • Cumulative Layout Shift: 0.343

    0.343

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

  • Real-user INP: 206 ms

    206 ms

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

  • 83 images without width and height

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

  • Total Blocking Time: 341 ms

    341 ms

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

  • Tap response (INP) got 12% slower for real visitors

    +12%

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

3 checks passed
  • Real-user CLS: 0.03

    0.03

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

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

    -12%

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

  • First Contentful Paint: 1.7 s

    1.7 s

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

Images and page weight

5 to fix18
  • Page weight: 16.1 MB in 292 requests

    16.1 MB

    Your homepage downloads 16.1 MB in 292 requests on a phone: images 13.6 MB (155), scripts 2.2 MB (73) and HTML 109 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 13 images far larger than shown

    4.8 MB

    13 images are downloaded at several times the size a phone draws them, for example 7473219_temp_1790081054_big1.jpg at 1,600 px wide, shown at 140 px. Resized copies would save about 4.8 MB.

  • 6 images over 500 KB

    6 images weigh 3.7 MB together. On a phone connection a single image that size takes seconds.

  • 38 images in older formats

    38 images (10.9 MB) 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.

  • 14 images below the first screen load straight away

    14 images further down the page (4.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.6 g of CO₂ per visit

    4.56 g

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

Accessibility

9 to fixGoogle 8186
  • 80 text elements with low contrast

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

  • 263 images without alt text

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

  • 13 tap targets too small

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

    All page content should be contained by landmarks: 299 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.

  • 71 form fields without a label

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

  • 69 links without text

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

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

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

6 to fixGoogle 8573
  • No H1 headline

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

  • No structured data

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

  • Meta description is short (49 characters)

    Your meta description is only 49 characters: “Cosmodata: Computers – Peripherals – IT Solutions”. 70 to 160 characters is enough to sell the click.

  • No social preview image

    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

    No XML sitemap at http://www.cosmodata.gr/sitemap.xml, so Google discovers your pages only by following links.

  • 19 links crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 1,305 internal links, 52 external

    The homepage links to 1,305 pages on cosmodata.gr and 52 external pages.

3 checks passed
  • Title: 61 characters

    Your title is a healthy 61 characters: “Cosmodata: Computers – Peripherals – IT Solutions | COSMODATA”.

  • Canonical URL set

    The canonical URL is https://www.cosmodata.gr/.

  • robots.txt in place

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

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.cosmodata.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 (3,470 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.cosmodata.gr/view/47/katastimata, whose canonical is https://www.cosmodata.gr/view/47/katastimata-new. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://www.cosmodata.gr/view/47/katastimata and https://www.cosmodata.gr/category/3028/ektypotes_analosima have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://www.cosmodata.gr/view/47/katastimata and https://www.cosmodata.gr/category/3028/ektypotes_analosima took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    5 pages of 15 loaded without an error (the rest turned automated requests away).

  • Every page has a meta description

    All 2 pages that loaded have a meta description.

  • 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 2 pages that loaded have a <title>.

Best practices

5 to fixGoogle 6969
  • 1 broken image

    1 image failed to load on a phone, for example https://www.cosmodata.gr/files/epektaseis/.jpg.

  • 93 distorted images

    93 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 7 small tap targets

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

  • 3 third-party cookies

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Unexpected token '!'”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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: 9 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • About 808 words of copy

    The homepage carries about 808 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Click n' Call 2111038000”.

  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies, 1 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.

  • 29 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 56 issues on cosmodata.gr, including 25 speed issues, 6 SEO issues and 2 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