Website review, no card needed

educeth.ch logo

educeth.ch website review

Visit site (opens in a new tab)Reviewed 11 November 202636 issues · 76 checks

This review found 36 issues worth fixing on educeth.ch, 12 of them high impact, across 76 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
1.5 s804 msJun 6Nov 71.0 s
Show as table
DateReal-visitor load time (LCP)
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 2026946 ms
Jun 27, 2026879 ms
Jul 4, 2026946 ms
Jul 11, 20261.1 s
Aug 22, 20261.4 s
Aug 29, 20261.2 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 2026978 ms
Sep 26, 20261.0 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.2 s
Oct 31, 20261.1 s
Nov 7, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
118 ms94 msJun 20Oct 24108 ms
Show as table
DateReal-visitor tap response (INP)
Jun 20, 202699 ms
Jun 27, 202697 ms
Jul 4, 2026102 ms
Jul 11, 2026102 ms
Aug 22, 2026115 ms
Aug 29, 2026111 ms
Sep 5, 2026111 ms
Sep 12, 2026106 ms
Sep 19, 2026102 ms
Sep 26, 2026101 ms
Oct 3, 2026103 ms
Oct 10, 2026108 ms
Oct 17, 2026106 ms
Oct 24, 2026108 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 educeth.ch (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. educeth.ch at 0.4 s0.4 s
  2. educeth.ch at 0.9 s0.9 s
  3. educeth.ch at 1.3 s1.3 s
  4. educeth.ch at 1.8 s1.8 s
  5. educeth.ch at 2.2 s2.2 s
  6. educeth.ch at 2.7 s2.7 s
  7. educeth.ch at 3.1 s3.1 s
  8. educeth.ch at 3.6 s3.6 s

Speed

8 to fix54
  • Render-blocking requests

    5.4 s

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

  • Use efficient cache lifetimes

    4.1 s · 872 KiB

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

  • Reduce unused JavaScript

    2.1 s · 425 KiB

    About 425 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.

  • Improve image delivery

    1.1 s · 181 KiB

    2 images could be 181 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.

  • Mobile performance score: 54

    54/100

    Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.

  • Font display

    700 ms

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

  • Reduce unused CSS

    460 ms · 100 KiB

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

  • 4 long tasks on the main thread

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Tag Manager and Optanon), adding 444 KiB and 227 ms of main-thread time.

  • Legacy JavaScript

    14 KiB

    Polyfills for old browsers add 14 KiB JavaScript that modern phones do not need.

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

2 checks passed
  • Main-thread work: 1.0 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 10.0 s

    10.0 s

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

  • First Contentful Paint: 5.3 s

    5.3 s

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

  • Time to Interactive: 10.0 s

    10.0 s

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

  • Speed Index: 6.4 s

    6.4 s

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

  • Total Blocking Time: 236 ms

    236 ms

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

  • 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-11-07, real Chrome visitors' tap response (inp) went from 99 ms to 108 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -7%

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

6 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.0 s

    1.0 s

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 312 ms

    312 ms

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

  • Cumulative Layout Shift: 0.087

    0.087

    The layout barely moves while loading (CLS 0.087, good is under 0.1).

Images and page weight

2 to fix86
  • An image on the first screen is lazy-loaded

    image.imageformat.1286.1298459845.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image far larger than shown

    116 KiB

    1 image is downloaded at several times the size a phone draws it, for example image.imageformat.1286.1298459845.jpg at 1,829 px wide, shown at 296 px. Resized copies would save about 116 KiB.

  • 2 images in older formats

    2 images (203 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.

  • About 0.5 g of CO₂ per visit

    0.49 g

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

1 checks passed
  • Page weight: 1.7 MB in 26 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 26 requests on a phone: scripts 1.1 MB (4), images 292 KiB (6) and fonts 219 KiB (4). That is a lean page.

Accessibility

3 to fixGoogle 9997
  • All page content should be contained by landmarks (14 elements)

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

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

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

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

SEO

6 to fixGoogle 8370
  • No meta description

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

  • Title is long (76 characters)

    Your title is 76 characters, so Google will cut it off around 60: “Homepage – EducETH - ETH-Kompetenzzentrum für Lehren und Lernen | ETH Zürich”.

  • No structured data

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

  • No XML sitemap

    No XML sitemap at https://educ.ethz.ch/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at educ.ethz.ch/robots.txt, the first file search crawlers ask for.

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

  • Open Graph partly set

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

  • No X (Twitter) card tag

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

  • 16 internal links, 25 external

    The homepage links to 16 pages on educeth.ch and 25 external pages.

2 checks passed
  • One H1 headline

    Your main headline reads: “EducETH - ETH-Kompetenzzentrum für Lehren und Lernen : Übersicht und Aktuelles”.

  • Canonical URL set

    The canonical URL is https://educ.ethz.ch/.

AI search readiness

2 to fix75
  • 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.

  • Some text only appears after JavaScript runs

    54%

    The HTML your server sends has 127 of the 236 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

    There is no https://educ.ethz.ch/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.

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

3 to fix83
  • 3 linked pages hidden from search

    https://educ.ethz.ch/footer/barrierefreiheitserklaerung.html, https://educ.ethz.ch/footer/disclaimer-copyright.html and https://educ.ethz.ch/footer/datenschutz.html are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages without a meta description

    https://educ.ethz.ch/utils/kontakt.html, https://educ.ethz.ch/footer/inhaltsverzeichnis.html, https://educ.ethz.ch/footer/impressum.html and https://educ.ethz.ch/footer/disclaimer-copyright.html have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://educ.ethz.ch/footer/inhaltsverzeichnis.html has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://educ.ethz.ch/utils/kontakt.html and https://educ.ethz.ch/footer/inhaltsverzeichnis.html 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.

  • 6 internal pages checked

    We fetched 6 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 6 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.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 9 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

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.

Content and conversion

5 to fix43
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

2 checks passed
  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 1 tracker load before any consent

    1

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

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 3 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
Switch Switch

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on educeth.ch, including 14 speed issues, 6 SEO issues and 5 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