Website review, no card needed

eurostargroup.com logo

eurostargroup.com website review

Visit site (opens in a new tab)Reviewed 28 October 202642 issues · 80 checks

This review found 42 issues worth fixing on eurostargroup.com, 15 of them high impact, across 80 checks. The most urgent: font display. 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.3 s3.4 sMay 9Jul 253.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.1 s
May 16, 20264.0 s
May 23, 20263.8 s
May 30, 20263.8 s
Jun 6, 20263.8 s
Jun 13, 20264.0 s
Jun 20, 20264.2 s
Jun 27, 20264.0 s
Jul 4, 20263.9 s
Jul 11, 20263.5 s
Jul 18, 20263.5 s
Jul 25, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
128 ms102 msJun 6Jun 27125 ms
Show as table
DateReal-visitor tap response (INP)
Jun 6, 2026105 ms
Jun 13, 2026118 ms
Jun 20, 2026119 ms
Jun 27, 2026125 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 eurostargroup.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. eurostargroup.com at 1.3 s1.3 s
  2. eurostargroup.com at 2.5 s2.5 s
  3. eurostargroup.com at 3.8 s3.8 s
  4. eurostargroup.com at 5.1 s5.1 s
  5. eurostargroup.com at 6.3 s6.3 s
  6. eurostargroup.com at 7.6 s7.6 s
  7. eurostargroup.com at 8.8 s8.8 s
  8. eurostargroup.com at 10.1 s10.1 s

Speed

9 to fix48
  • Font display

    2.6 s

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

  • Reduce unused JavaScript

    2.1 s · 416 KiB

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

  • Use efficient cache lifetimes

    1.9 s · 620 KiB

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

  • Improve image delivery

    1.6 s · 764 KiB

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

  • Render-blocking requests

    1.3 s

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

  • Mobile performance score: 48

    48/100

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

  • Reduce unused CSS

    600 ms · 103 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, ShareThis and Twitter and others), adding 830 KiB and 558 ms of main-thread time.

  • Minify JavaScript

    300 ms · 80 KiB

    80 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    150 ms · 23 KiB

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

  • 3 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 88 but mobile only 48. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

6 to fix48
  • Largest Contentful Paint: 14.7 s

    14.7 s

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

  • Speed Index: 14.0 s

    14.0 s

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

  • Time to Interactive: 16.0 s

    16.0 s

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

  • Cumulative Layout Shift: 0.265

    0.265

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

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +9%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Largest content (LCP) got 10% faster for real visitors

    -10%

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

  • Total Blocking Time: 67 ms

    67 ms

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

Images and page weight

3 to fix65
  • Page weight: 2.4 MB in 141 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 141 requests on a phone: images 1.1 MB (32), scripts 887 KiB (48) and stylesheets 175 KiB (26). Under 2 MB keeps phones on slow connections fast.

  • 14 images in older formats

    14 images (998 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.

  • 1 image far larger than shown

    16 KiB

    1 image is downloaded at several times the size a phone draws it, for example BANNER-Final-04-1400x500.jpg at 1,400 px wide, shown at 390 px. Resized copies would save about 16 KiB.

  • About 0.7 g of CO₂ per visit

    0.69 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.69 g of CO₂e: 82.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 load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

8 to fixGoogle 7890
  • 3 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

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

  • 8 tap targets too small

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

  • Hidden but focusable

    7 elements hidden from screen readers can still receive keyboard focus.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 42 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: 42 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 7569
  • No H1 headline

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

  • Title is long (71 characters)

    Your title is 71 characters, so Google will cut it off around 60: “communications, satellite, logistics, personal care, etisalat dubai uae”.

  • Meta description is long (329 characters)

    Your meta description is 329 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

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

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 2 links crawlers can't follow

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

  • 108 internal links, 6 external

    The homepage links to 108 pages on eurostargroup.com and 6 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.eurostargroup.com/en/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

100
  • No llms.txt

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

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (449 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 5 pages without a meta description

    https://www.eurostargroup.com/en/videocompression, https://www.eurostargroup.com/en/beyond-security-solutions, https://www.eurostargroup.com/en/building-materials, https://www.eurostargroup.com/en/smart-phone and https://www.eurostargroup.com/en/consumer-electronics have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://www.eurostargroup.com/en/led, https://www.eurostargroup.com/en/digital-satellite-receiving-system, https://www.eurostargroup.com/en/convergent-technologies-tendering, https://www.eurostargroup.com/en/electronic-multimedia-pay-tv, https://www.eurostargroup.com/en/integrated-security-solutions and https://www.eurostargroup.com/en/3pl and 6 others 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 24 found) and read each the way a search engine does.

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

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

Best practices

3 to fixGoogle 6985
  • 7 small tap targets

    7 of 11 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.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 2 low-resolution images

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

  • 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

4 to fix57
  • 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 social proof

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

  • 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 212 words

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

3 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Apply Online”, “Shop Now” and “Enquire Now”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

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.

  • 5 other companies contacted

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

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on eurostargroup.com, including 15 speed issues, 7 SEO issues and 4 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