Website review, no card needed

egu.eu logo

egu.eu website review

Visit site (opens in a new tab)Reviewed 23 October 202624 issues · 85 checks

This review found 24 issues worth fixing on egu.eu, 4 of them high impact, across 85 checks. The most urgent: fails Core Web Vitals for real visitors. 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.7 s1.5 sMay 2Oct 171.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.8 s
May 9, 20261.7 s
May 16, 20261.8 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20262.3 s
Jun 13, 20262.4 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20261.9 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.9 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.7 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
159 ms134 msMay 2Oct 17155 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026147 ms
May 9, 2026137 ms
May 16, 2026138 ms
May 23, 2026138 ms
May 30, 2026138 ms
Jun 6, 2026152 ms
Jun 13, 2026149 ms
Jun 20, 2026148 ms
Jun 27, 2026146 ms
Jul 4, 2026146 ms
Jul 11, 2026145 ms
Jul 18, 2026146 ms
Jul 25, 2026150 ms
Aug 1, 2026151 ms
Aug 8, 2026150 ms
Aug 15, 2026152 ms
Aug 22, 2026149 ms
Aug 29, 2026151 ms
Sep 5, 2026152 ms
Sep 12, 2026152 ms
Sep 19, 2026154 ms
Sep 26, 2026153 ms
Oct 3, 2026156 ms
Oct 10, 2026156 ms
Oct 17, 2026155 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 egu.eu (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

egu.eu does not allow embedding, so this is Google's rendering of the page.

Speed

4 to fix98
  • Improve image delivery

    750 ms · 276 KiB

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

  • Render-blocking requests

    700 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

  • Font display

    450 ms

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

  • Reduce unused CSS

    310 ms · 48 KiB

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

  • Reduce unused JavaScript

    34 KiB

    About 34 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    18 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (18 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.

3 checks passed
  • Mobile performance score: 98

    98/100

    Your mobile performance score is 98 (desktop: 99). That is in Google's “good” band (90 and up).

  • Main-thread work: 0.5 s

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

  • Server response: 110 ms

    110 ms

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

Core Web Vitals

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 999 ms

    999 ms

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

  • 2 images without width and height

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

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

    +10%

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

9 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 160 ms

    160 ms

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

  • Largest Contentful Paint: 2.4 s

    2.4 s

    Your largest element renders in 2.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image “grace shephard.jpg (Credit: Grace Shephard)”.

  • Time to Interactive: 2.4 s

    2.4 s

    The page is fully interactive after 2.4 s.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Speed Index: 2.3 s

    2.3 s

    Visually, the page fills in at 2.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.008

    0.008

    The layout barely moves while loading (CLS 0.008, 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

100
  • About 0.3 g of CO₂ per visit

    0.30 g

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

4 checks passed
  • Page weight: 1.1 MB in 30 requests

    1.1 MB

    Your homepage downloads 1.1 MB in 30 requests on a phone: fonts 492 KiB (5), images 376 KiB (13) and scripts 133 KiB (7). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • Images are sized for phones

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

Accessibility

1 to fixGoogle 9698
  • Links look like plain text

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

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 42 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: 42 passed and 1 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 9270
  • Title is short (26 characters)

    Your title is only 26 characters: “European Geosciences Union”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 6 H1 headlines

    There are 6 <h1> headlines (“EGU news Teachers and educators: apply now for th…”, “EGU news GeoCinema at EGU27 – submit your short f…” and “EGU news Early Career Scientists step into the ro…”). 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.

  • Meta description is long (198 characters)

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

  • No XML sitemap

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

  • 19 links with vague text

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

  • No X (Twitter) card tag

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

  • 194 internal links, 46 external

    The homepage links to 194 pages on egu.eu and 46 external pages.

2 checks passed
  • 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 /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 (1,524 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix98
  • 15 pages share a meta description

    /structure/divisions, /as, /bg, /cl, /cr and /emrp and 9 others use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

7 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 meta description

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

Best practices

1 to fixGoogle 10093
  • 14 small tap targets

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

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.

Security and trust

100
  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

9 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (egu.eu).

  • Valid certificate (58 days left)

    The certificate from Let's Encrypt · YR1 verifies for egu.eu and is valid for another 58 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • HSTS enabled

    Strict-Transport-Security is set, so browsers always use https.

  • http:// redirects to https

    http://egu.eu redirects to the secure version.

  • HTTP/2

    The server speaks HTTP/2, so browsers load many files over one connection.

  • All 60 links work

    All 60 links checked from your homepage (40 internal, 20 external) answered without errors.

  • security.txt published

    A security.txt file tells researchers how to report a problem with your site.

Domain and trust

1 checks passed
  • Certificate issuers are restricted

    CAA records allow only letsencrypt.org to issue certificates for egu.eu, so a mis-issued certificate from anyone else is refused.

Content and conversion

4 to fix40
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 822 words of visible text.

1 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact”.

Email authentication

1 to fix75
  • No DKIM key on the usual selectors

    We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

  • Email authentication score: 75/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

2 checks passed
  • DMARC policy: quarantine

    DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 mx ip4:5.75.213.112 ip6:2a01:4f8:1c17:a118::1 include:in9dyqwgl5.powerspf.com include:mailbox.org ~all”.

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

Upkeep, stack and company

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

Framework
jQuery

Company

Founded
2002
Headquarters
Munich

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on egu.eu, including 8 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