titan.gr website review

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

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

8 images could be 890 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

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

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

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

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

5 third-party services load with your homepage (Google Tag Manager, Cookiebot and Google CDN and others), adding 950 KiB and 273 ms of main-thread time.

15 KiB could be saved by minifying CSS.

13 KiB could be saved by minifying JavaScript.

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

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.

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.

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

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

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

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

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

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

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

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

Your homepage downloads 2.9 MB in 39 requests on a phone: images 1.6 MB (12), scripts 1,009 KiB (12) and fonts 161 KiB (6). Under 2 MB keeps phones on slow connections fast.

1 image (130 KiB) is 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.

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

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

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

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

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

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

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

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

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

Your title is only 21 characters: “Αρχική - Titan Greece”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

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

There is no robots.txt at titan.gr/robots.txt, the first file search crawlers ask for.

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

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

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

The homepage links to 135 pages on titan.gr and 12 external pages.

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.

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

https://www.titan.gr/el declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://www.titan.gr/el all use the title “Αρχική - Titan Greece”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.titan.gr/en, https://www.titan.gr/el, https://www.titan.gr/el/sxetika-me-emas/dynamiki-parousia-stin-ellada, https://www.titan.gr/el/sxetika-me-emas/stratigiki-omilou, https://www.titan.gr/el/sxetika-me-emas/purpose-values and https://www.titan.gr/el/sxetika-me-emas/etairiki-diakybernisi/dioikitiko-symboulio and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.titan.gr/en, https://www.titan.gr/el and https://www.titan.gr/el/sxetika-me-emas/dynamiki-parousia-stin-ellada have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.titan.gr/el, https://www.titan.gr/el/sxetika-me-emas, https://www.titan.gr/el/sxetika-me-emas/dynamiki-parousia-stin-ellada, https://www.titan.gr/el/sxetika-me-emas/stratigiki-omilou, https://www.titan.gr/el/sxetika-me-emas/purpose-values and https://www.titan.gr/el/sxetika-me-emas/etairiki-diakybernisi/dioikitiko-symboulio and 7 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.

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

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

6 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://analytics.google.com/g/collect?v=2&tid=G-GETGT8DHKQ&gtm=45je6au1v9125768759za20ozb812450108zd812…”.

Chrome logged issues while loading the page (“Content security policy”).

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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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