Website review, no card needed

elbeflugzeugwerke.com logo

elbeflugzeugwerke.com website review

Visit site (opens in a new tab)Reviewed 30 October 202615 issues · 71 checks

This review found 15 issues worth fixing on elbeflugzeugwerke.com, 4 of them high impact, across 71 checks. The most urgent: page weight: 4.8 MB in 92 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
2.1 s1.8 sMay 9Oct 241.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.9 s
May 16, 20262.0 s
May 23, 20262.1 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20261.9 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20261.9 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
101 ms88 msMay 9Oct 2495 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202695 ms
May 16, 202695 ms
May 23, 202696 ms
May 30, 202698 ms
Jun 6, 202699 ms
Jun 13, 202695 ms
Jun 20, 202694 ms
Jun 27, 202693 ms
Jul 4, 202693 ms
Jul 11, 202693 ms
Jul 18, 202693 ms
Jul 25, 202690 ms
Aug 1, 202689 ms
Aug 8, 202690 ms
Aug 15, 202692 ms
Aug 22, 202694 ms
Aug 29, 202694 ms
Sep 5, 202694 ms
Sep 12, 202695 ms
Sep 19, 202694 ms
Sep 26, 202694 ms
Oct 3, 202693 ms
Oct 10, 202692 ms
Oct 17, 202695 ms
Oct 24, 202695 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 elbeflugzeugwerke.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. elbeflugzeugwerke.com at 0.5 s0.5 s
  2. elbeflugzeugwerke.com at 1.1 s1.1 s
  3. elbeflugzeugwerke.com at 1.6 s1.6 s
  4. elbeflugzeugwerke.com at 2.1 s2.1 s
  5. elbeflugzeugwerke.com at 2.7 s2.7 s
  6. elbeflugzeugwerke.com at 3.2 s3.2 s
  7. elbeflugzeugwerke.com at 3.7 s3.7 s
  8. elbeflugzeugwerke.com at 4.3 s4.3 s

Speed

1 to fix91
  • Reduce unused JavaScript

    300 ms · 105 KiB

    About 105 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Usercentrics CMP), adding 225 KiB and 122 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 64 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    27 KiB

    About 27 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    11 KiB

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

  • Use efficient cache lifetimes

    10 KiB

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

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

  • 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: 91

    91/100

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

  • Main-thread work: 1.1 s

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

  • Server response: 123 ms

    123 ms

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

Core Web Vitals

2 to fix100
  • Speed Index: 4.9 s

    4.9 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

10 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: 2.0 s

    2.0 s

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

  • Real-user INP: 101 ms

    101 ms

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 692 ms

    692 ms

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

  • 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 text “This site uses third-party website tracking technologies to…”.

  • Time to Interactive: 3.5 s

    3.5 s

    The page is fully interactive after 3.5 s.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 7 ms

    7 ms

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

Images and page weight

1 to fix70
  • Page weight: 4.8 MB in 92 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 92 requests on a phone: media 4.0 MB (2), images 342 KiB (35) and scripts 309 KiB (41). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.36 g

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

3 checks passed
  • 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

3 to fixGoogle 9395
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • ARIA role should be appropriate for the element (3 elements)

    ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 42 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 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10089
  • Title is long (113 characters)

    Your title is 113 characters, so Google will cut it off around 60: “EFW: We equip. We convert. We maintain. Certified. All your Airbus aircraft. Worldwide. |…”.

  • No structured data

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

  • 65 internal links, 9 external

    The homepage links to 65 pages on elbeflugzeugwerke.com and 9 external pages.

6 checks passed
  • Meta description: 87 characters

    Your meta description is 87 characters: “Based in Dresden. In the heart of Europe. At ten global sites. Delivering to the world.”.

  • One H1 headline

    Your main headline reads: “We equip. We convert. We maintain. Certified. All your Airbus aircraft. Worldwide.”.

  • Canonical URL set

    The canonical URL is https://www.elbeflugzeugwerke.com/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.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.elbeflugzeugwerke.com/en/sitemap.xml.

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

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

Other pages

1 to fix95
  • 15 pages without a meta description

    https://www.elbeflugzeugwerke.com/en/company, https://www.elbeflugzeugwerke.com/en/company/about-us, https://www.elbeflugzeugwerke.com/en/company/management, https://www.elbeflugzeugwerke.com/en/company/sustainability, https://www.elbeflugzeugwerke.com/en/company/approvals-certificates and https://www.elbeflugzeugwerke.com/en/company/multimedia and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages slow to respond

    https://www.elbeflugzeugwerke.com/en/company/management and https://www.elbeflugzeugwerke.com/en/company/sustainability took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • 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

2 to fixGoogle 9687
  • 3 small tap targets

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

  • 2 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 362 words of copy

    The homepage carries about 362 words of visible text.

4 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Support & Contact” and “Contact Persons”.

  • 1 short form

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

  • Social proof on the page

    Social proof on the homepage: 25 customer or partner logos, 1 trust badge and “40+ customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 2 other companies contacted

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

2 checks passed
  • Consent tool: Usercentrics

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

  • 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 elbeflugzeugwerke.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
TYPO3 CMS
Analytics
Google Tag Manager
Hosting
Managedhosting

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 15 issues on elbeflugzeugwerke.com, including 3 speed issues, 2 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