Website review, no card needed

gtp.gr logo

gtp.gr website review

Visit site (opens in a new tab)Reviewed 22 October 202644 issues · 84 checks

This review found 44 issues worth fixing on gtp.gr, 14 of them high impact, across 84 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
4.5 s1.4 sMay 2Oct 171.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.7 s
May 9, 20262.8 s
May 16, 20262.6 s
May 23, 20262.6 s
May 30, 20262.3 s
Jun 6, 20262.5 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.9 s
Jul 4, 20263.0 s
Jul 11, 20263.0 s
Jul 18, 20263.1 s
Jul 25, 20263.8 s
Aug 1, 20264.2 s
Aug 8, 20264.2 s
Aug 15, 20263.9 s
Aug 22, 20263.3 s
Aug 29, 20262.9 s
Sep 5, 20262.8 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.5 s
Oct 3, 20262.2 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
209 ms87 msMay 2Oct 17134 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026150 ms
May 9, 2026131 ms
May 16, 2026114 ms
May 23, 2026114 ms
May 30, 2026101 ms
Jun 6, 2026106 ms
Jun 13, 2026113 ms
Jun 20, 2026114 ms
Jun 27, 2026130 ms
Jul 4, 2026151 ms
Jul 11, 2026162 ms
Jul 18, 2026169 ms
Jul 25, 2026180 ms
Aug 1, 2026181 ms
Aug 8, 2026189 ms
Aug 15, 2026195 ms
Aug 22, 2026194 ms
Aug 29, 2026189 ms
Sep 5, 2026180 ms
Sep 12, 2026164 ms
Sep 19, 2026145 ms
Sep 26, 2026133 ms
Oct 3, 2026126 ms
Oct 10, 2026133 ms
Oct 17, 2026134 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 gtp.gr (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gtp.gr at 0.5 s0.5 s
  2. gtp.gr at 1.0 s1.0 s
  3. gtp.gr at 1.5 s1.5 s
  4. gtp.gr at 2.0 s2.0 s
  5. gtp.gr at 2.5 s2.5 s
  6. gtp.gr at 3.0 s3.0 s
  7. gtp.gr at 3.5 s3.5 s
  8. gtp.gr at 4.0 s4.0 s

Speed

9 to fix33
  • Render-blocking requests

    3.7 s

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

  • Reduce unused JavaScript

    1.6 s · 804 KiB

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

  • Mobile performance score: 33

    33/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google/Doubleclick Ads, Google Tag Manager and Other Google APIs/SDKs and others), adding 3.2 MB and 1.3 s of main-thread time.

  • Google/Doubleclick Ads adds 911 ms

    911 ms

    Google/Doubleclick Ads costs a phone 911 ms of main-thread work and 2.1 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.

  • Improve image delivery

    150 ms · 901 KiB

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

  • Use efficient cache lifetimes

    100 ms · 715 KiB

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

  • Main-thread work: 3.1 s

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

  • JSDelivr CDN adds 64 ms

    64 ms

    JSDelivr CDN costs a phone 64 ms of main-thread work and 307 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.

  • Reduce unused CSS

    250 ms · 53 KiB

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

  • 15 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Document request latency

    28 KiB

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

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 158 ms

    158 ms

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

Core Web Vitals

10 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 CLS: 0.28

    0.28

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

  • Time to Interactive: 21.2 s

    21.2 s

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

  • Largest Contentful Paint: 8.2 s

    8.2 s

    Your largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “ΕΣΠΑ”.

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • Cumulative Layout Shift: 0.269

    0.269

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

  • Real-user TTFB: 912 ms

    912 ms

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

  • Total Blocking Time: 483 ms

    483 ms

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

  • 10 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -5%

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

4 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 133 ms

    133 ms

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

  • Real-user FCP: 1.4 s

    1.4 s

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

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

    -34%

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

Images and page weight

3 to fix53
  • Page weight: 4.1 MB in 159 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 159 requests on a phone: images 1.9 MB (38), scripts 1.8 MB (45) and fonts 250 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 13 images in older formats

    13 images (828 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.

  • 7 images below the first screen load straight away

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

  • About 1.2 g of CO₂ per visit

    1.17 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9194
  • 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.

  • Links look like plain text

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

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

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 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 9280
  • No structured data

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

  • 4 H1 headlines

    There are 4 <h1> headlines (“Discover Greece”, “Latest Travel & Tourism News from news.gtp.gr:” and “Related services”). 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://gtp.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.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 44 internal links, 37 external

    The homepage links to 44 pages on gtp.gr and 37 external pages.

4 checks passed
  • Meta description: 86 characters

    Your meta description is 86 characters: “The ultimate source of information for tourism professionals and travellers to Greece.”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “Tourism guide of Greece - Greek Travel Pages”.

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

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://gtp.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 (460 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix74
  • 3 linked pages hidden from search

    https://gtp.gr/ChangeLanguage.asp, https://gtp.gr/subscribe.asp and https://gtp.gr/LocInfo.asp are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 5 pages share 2 titles

    https://gtp.gr/ChangeLanguage.asp, https://gtp.gr/subscribe.asp and https://gtp.gr/LocInfo.asp all use the title “Greek Travel Pages”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://gtp.gr/ChangeLanguage.asp, https://gtp.gr/subscribe.asp, https://gtp.gr/greekports.asp, https://gtp.gr/ShipCompanies.asp, https://gtp.gr/Ships.asp and https://gtp.gr/LocInfo.asp have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://gtp.gr/AccomodationForm.asp and https://gtp.gr/accomodationform.asp use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://gtp.gr/ChangeLanguage.asp, https://gtp.gr/subscribe.asp and https://gtp.gr/LocInfo.asp have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 4 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 301 words of copy

    The homepage carries about 301 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Subscribe now!” and “Contact”.

  • 5 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 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.

  • 19 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on gtp.gr, including 19 speed issues, 6 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