Website review, no card needed

esperiagroup.gr logo

esperiagroup.gr website review

Visit site (opens in a new tab)Reviewed 23 October 202644 issues · 91 checks

This review found 44 issues worth fixing on esperiagroup.gr, 11 of them high impact, across 91 checks. The most urgent: reduce unused JavaScript. 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.8 s2.4 sMay 2Oct 172.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.5 s
May 9, 20262.5 s
May 16, 20262.5 s
May 23, 20262.5 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.5 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.7 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
130 ms101 msMay 2Oct 17127 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026111 ms
May 9, 2026110 ms
May 16, 2026109 ms
May 23, 2026106 ms
May 30, 2026104 ms
Jun 6, 2026104 ms
Jun 13, 2026104 ms
Jun 20, 2026104 ms
Jun 27, 2026107 ms
Jul 4, 2026108 ms
Jul 11, 2026110 ms
Jul 18, 2026113 ms
Jul 25, 2026115 ms
Aug 1, 2026119 ms
Aug 8, 2026121 ms
Aug 15, 2026120 ms
Aug 22, 2026121 ms
Aug 29, 2026121 ms
Sep 5, 2026122 ms
Sep 12, 2026125 ms
Sep 19, 2026126 ms
Sep 26, 2026126 ms
Oct 3, 2026127 ms
Oct 10, 2026127 ms
Oct 17, 2026127 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 esperiagroup.gr (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix63
  • Reduce unused JavaScript

    2.7 s · 849 KiB

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

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 63

    63/100

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

  • Improve image delivery

    898 KiB

    23 images could be 898 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    750 ms · 146 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google CDN and dailypoint.com and others), adding 1.7 MB and 710 ms of main-thread time.

  • YouTube adds 548 ms

    548 ms

    YouTube costs a phone 548 ms of main-thread work and 964 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.

  • Font display

    400 ms

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

  • Main-thread work: 2.2 s

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

  • Google CDN adds 127 ms

    127 ms

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

  • Adobe TypeKit adds 0 ms

    0 ms

    Adobe TypeKit costs a phone 0 ms of main-thread work and 336 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.

  • 7 long tasks on the main thread

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

  • Use efficient cache lifetimes

    50 ms · 23 KiB

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

  • Legacy JavaScript

    50 ms · 10 KiB

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

  • 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

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

9 to fix100
  • 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.

  • Largest Contentful Paint: 11.5 s

    11.5 s

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

  • Time to Interactive: 17.7 s

    17.7 s

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • Speed Index: 5.5 s

    5.5 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 22 images without width and height

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

  • Total Blocking Time: 225 ms

    225 ms

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

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

    +15%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

4 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 128 ms

    128 ms

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

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (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).

Images and page weight

4 to fix58
  • Page weight: 3.9 MB in 86 requests

    3.9 MB

    Your homepage downloads 3.9 MB in 86 requests on a phone: images 1.8 MB (33), scripts 1.4 MB (21) and fonts 524 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 17 images in older formats

    17 images (1.2 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.

  • 8 images below the first screen load straight away

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

  • 1 image far larger than shown

    27 KiB

    1 image is downloaded at several times the size a phone draws it, for example box-1-bannerhotellogo566x566.png at 566 px wide, shown at 150 px. Resized copies would save about 27 KiB.

  • About 1.1 g of CO₂ per visit

    1.12 g

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

Accessibility

8 to fixGoogle 8789
  • 14 text elements with low contrast

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

  • Form elements should have a visible label (4 elements)

    Form elements should have a visible label: 4 elements on the page fail this check, rated serious by axe-core.

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 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 (100 elements)

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

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

  • 1 form field without a label

    1 form field has 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.

  • No main landmark

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

2 checks passed
  • Every image has alt text

    All 240 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

4 to fixGoogle 9285
  • 12 H1 headlines

    There are 12 <h1> headlines (“Ammades All Suites Beach Hotel & Spa - Adults Only”, “Bellevue On The Beach Suites” and “Esperos Village Blue & Spa Resort - Adults Only”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No XML sitemap

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

  • 2 links crawlers can't follow

    2 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 set, so this is minor.

  • 83 internal links, 49 external

    The homepage links to 83 pages on esperiagroup.gr and 49 external pages.

5 checks passed
  • Meta description: 144 characters

    Your meta description is 144 characters: “Discover Esperia Group's collection of luxury hotels and resorts in Rhodes, Greece. Experience unparalleled hospitality…”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Esperia Group Hotels & Resorts | Luxury Stays in Rhodes, Greece”.

  • Canonical URL set

    The canonical URL is https://www.esperiagroup.gr/en/.

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

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.esperiagroup.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 (5,091 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix70
  • 1 linked page is broken

    Your homepage links to https://www.esperiagroup.gr/engine, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 5 links to non-canonical URLs

    Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.esperiagroup.gr/en/hotels/bellevue-suites, whose canonical is https://www.esperiagroup.gr/en/hotels/bellevue-on-the-beach-suites. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 7 pages slow to respond

    https://www.esperiagroup.gr/el, https://www.esperiagroup.gr/en/contact-us, https://www.esperiagroup.gr/en/hotels/esperos-mare-resort, https://www.esperiagroup.gr/en/hotels/esperides, https://www.esperiagroup.gr/en/hotels/epsilon-hotel-apartments and https://www.esperiagroup.gr/en/hotels/the-apartments-by-esperia and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

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

Best practices

2 to fixGoogle 7382
  • 2 broken images

    2 images failed to load on a phone, for example https://www.esperiagroup.gr/.

  • 5 third-party cookies

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

  • Browser-reported issues

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

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Thin social proof

    Social proof on the homepage: 3 trust badges. 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.

  • About 508 words of copy

    The homepage carries about 508 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “Contact Us”, “Book Now” and “Esperides Car Rental Learn more”.

  • 2 short forms

    2 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 13 cookies set on arrival

    13

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

  • 23 other companies contacted

    Loading the homepage contacts 23 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 esperiagroup.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
Created by Lighthouse, powered by VENDD e-commerce platform
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 44 issues on esperiagroup.gr, including 20 speed issues, 4 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