Website review, no card needed

tuc.gr logo

tuc.gr website review

Visit site (opens in a new tab)Reviewed 26 October 202646 issues · 83 checks

This review found 46 issues worth fixing on tuc.gr, 15 of them high impact, across 83 checks. The most urgent: render-blocking requests. 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.5 s2.1 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.3 s
May 16, 20262.3 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
115 ms104 msMay 9Oct 24106 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026107 ms
May 16, 2026108 ms
May 23, 2026109 ms
May 30, 2026111 ms
Jun 6, 2026112 ms
Jun 13, 2026113 ms
Jun 20, 2026111 ms
Jun 27, 2026110 ms
Jul 4, 2026109 ms
Jul 11, 2026108 ms
Jul 18, 2026109 ms
Jul 25, 2026110 ms
Aug 1, 2026112 ms
Aug 8, 2026114 ms
Aug 15, 2026113 ms
Aug 22, 2026112 ms
Aug 29, 2026106 ms
Sep 5, 2026105 ms
Sep 12, 2026106 ms
Sep 19, 2026107 ms
Sep 26, 2026107 ms
Oct 3, 2026107 ms
Oct 10, 2026106 ms
Oct 17, 2026105 ms
Oct 24, 2026106 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 tuc.gr (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tuc.gr at 1.0 s1.0 s
  2. tuc.gr at 2.0 s2.0 s
  3. tuc.gr at 3.0 s3.0 s
  4. tuc.gr at 4.0 s4.0 s
  5. tuc.gr at 5.0 s5.0 s
  6. tuc.gr at 6.0 s6.0 s
  7. tuc.gr at 7.0 s7.0 s
  8. tuc.gr at 8.0 s8.0 s

Speed

5 to fix65
  • Render-blocking requests

    1.5 s

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

  • Improve image delivery

    950 ms · 678 KiB

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

  • Mobile performance score: 65

    65/100

    Your mobile performance score is 65 (desktop: 81). Pages that score under 90 lose visitors before the first paint.

  • Font display

    800 ms

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

  • Reduce unused CSS

    300 ms · 19 KiB

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

  • Reduce unused JavaScript

    150 ms · 23 KiB

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

  • Minify JavaScript

    150 ms · 8 KiB

    8 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    22 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (22 KiB).

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

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

  • Server response: 9 ms

    9 ms

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

Core Web Vitals

9 to fix67
  • 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 TTFB: 2.6 s

    2.6 s

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

  • Largest Contentful Paint: 9.0 s

    9.0 s

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

  • Speed Index: 9.5 s

    9.5 s

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

  • Time to Interactive: 9.0 s

    9.0 s

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

  • Real-user LCP: 3.6 s

    3.6 s

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

  • Real-user FCP: 2.9 s

    2.9 s

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

  • 19 images without width and height

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

4 checks passed
  • Real-user INP: 88 ms

    88 ms

    Real visitors wait 88 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.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

4 to fix58
  • Page weight: 2.8 MB in 95 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 95 requests on a phone: images 2.3 MB (55), fonts 230 KiB (2) and scripts 217 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 8 images in older formats

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

  • 4 images far larger than shown

    198 KiB

    4 images are downloaded at several times the size a phone draws them, for example SiG-logo.jpg at 800 px wide, shown at 110 px. Resized copies would save about 198 KiB.

  • 5 images below the first screen load straight away

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

  • About 0.8 g of CO₂ per visit

    0.80 g

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

Accessibility

12 to fixGoogle 6581
  • 10 buttons without a name

    10 buttons have no accessible name, so screen readers announce just “button”.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • 49 text elements with low contrast

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

  • 10 tap targets too small

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

  • Links look like plain text

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

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

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails 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.

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 2 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 70 images in the HTML carry an alt attribute.

  • 32 automated accessibility rules passed

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

SEO

6 to fixGoogle 8268
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (25 characters)

    Your title is only 25 characters: “Αρχή - Πολυτεχνείο Κρήτης”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 5 H1 headlines

    There are 5 <h1> headlines (“Αρχή”, “Γρήγοροι Σύνδεσμοι” and “Σχολές”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No XML sitemap

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 91 internal links, 30 external

    The homepage links to 91 pages on tuc.gr and 30 external pages.

2 checks passed
  • Structured data in place

    Structured data found: CollegeOrUniversity and WebSite.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix83
  • 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.tuc.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.

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

Other pages

3 to fix63
  • 3 linked pages are broken

    Your homepage links to https://www.tuc.gr/3323.html, https://www.tuc.gr/el/index.php and https://www.tuc.gr/classifieds.html, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages share a title

    https://www.tuc.gr/el/archi and / all use the title “Αρχή - Πολυτεχνείο Κρήτης”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages without a meta description

    /, https://www.tuc.gr/el/to-polytechneio/epikoinonia, https://www.tuc.gr/el/to-polytechneio, https://www.tuc.gr/el/scholes, https://www.tuc.gr/el/spoydes and https://www.tuc.gr/el/ereyna and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages with very little text

    /, https://www.tuc.gr/el/to-polytechneio/epikoinonia, https://www.tuc.gr/el/to-polytechneio, https://www.tuc.gr/el/scholes, https://www.tuc.gr/el/spoydes and https://www.tuc.gr/el/ereyna and 4 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.

  • 3 pages slow to respond

    /, https://www.tuc.gr/el/to-polytechneio/epikoinonia and https://www.tuc.gr/telephones.html took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Canonical URLs point to themselves

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

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 37 small tap targets

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

  • 7 low-resolution images

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 80 words

    The homepage has only about 80 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.

2 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Matomo.

Privacy and tracking

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

CMS
TYPO3 CMS
Framework
jQuery
Analytics
Matomo
Hosting
TUC

Company

Founded
1984

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on tuc.gr, including 14 speed issues, 6 SEO issues and 5 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