Website review, no card needed

aerofoils.de logo

aerofoils.de website review

Visit site (opens in a new tab)Reviewed 17 November 202638 issues · 88 checks

This review found 38 issues worth fixing on aerofoils.de, 17 of them high impact, across 88 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
2.4 s1.4 sJul 4Nov 142.3 s
Show as table
DateReal-visitor load time (LCP)
Jul 4, 20262.1 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.6 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.6 s
Oct 3, 20261.7 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Oct 31, 20262.0 s
Nov 7, 20262.2 s
Nov 14, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
205 ms137 msJul 4Nov 14197 ms
Show as table
DateReal-visitor tap response (INP)
Jul 4, 2026145 ms
Jul 11, 2026149 ms
Jul 18, 2026156 ms
Jul 25, 2026156 ms
Aug 1, 2026159 ms
Aug 8, 2026165 ms
Aug 15, 2026186 ms
Aug 22, 2026192 ms
Aug 29, 2026195 ms
Sep 5, 2026197 ms
Sep 12, 2026187 ms
Sep 19, 2026183 ms
Sep 26, 2026178 ms
Oct 3, 2026161 ms
Oct 10, 2026156 ms
Oct 17, 2026154 ms
Oct 24, 2026162 ms
Oct 31, 2026191 ms
Nov 7, 2026192 ms
Nov 14, 2026197 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 aerofoils.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix49
  • Render-blocking requests

    2.1 s

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

  • Use efficient cache lifetimes

    1.6 s · 393 KiB

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

  • searchatlas.com adds 2.0 s

    2.0 s

    searchatlas.com costs a phone 2.0 s of main-thread work and 44 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 49

    49/100

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

  • Main-thread work: 6.8 s

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

  • 4,453 HTML elements

    The page has 4,453 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (searchatlas.com, ccm19.de and JSDelivr CDN and others), adding 929 KiB and 2.9 s of main-thread time.

  • Improve image delivery

    344 KiB

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

  • ccm19.de adds 301 ms

    301 ms

    ccm19.de costs a phone 301 ms of main-thread work and 250 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.

  • JSDelivr CDN adds 296 ms

    296 ms

    JSDelivr CDN costs a phone 296 ms of main-thread work and 249 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.

  • Reduce unused JavaScript

    229 KiB

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

  • 20 long tasks on the main thread

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

  • Minify JavaScript

    16 KiB

    16 KiB could be saved by minifying JavaScript.

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Duplicated JavaScript

    4 KiB

    4 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 69 ms

    69 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 15.1 s

    15.1 s

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

  • Largest Contentful Paint: 6.5 s

    6.5 s

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

  • Speed Index: 7.1 s

    7.1 s

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

  • Total Blocking Time: 718 ms

    718 ms

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

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

    +32%

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Largest content (LCP) got 13% slower for real visitors

    +13%

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

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

    2.3 s

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

  • Real-user INP: 196 ms

    196 ms

    Real visitors wait 196 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.8 s

    1.8 s

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

  • Real-user TTFB: 729 ms

    729 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix81
  • Page weight: 3.0 MB in 198 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 198 requests on a phone: scripts 1.0 MB (47), images 977 KiB (27) and other files 759 KiB (93). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    3_Com_CC_1_Hero_b4c256b6-c801-44b8-88ac-04d876678193.webp 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).

  • 5 images in older formats

    5 images (285 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.9 g of CO₂ per visit

    0.85 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

8 to fixGoogle 8487
  • Elements must only use permitted ARIA attributes (5 elements)

    Elements must only use permitted ARIA attributes: 5 elements on the page fail this check, rated serious by axe-core.

  • 4 tap targets too small

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

  • 2 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 23 images without alt text

    23 images have no alt text, which hurts accessibility and image search.

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

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

  • 40 links without text

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

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

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

2 to fixGoogle 8593
  • 2 H1 headlines

    There are 2 <h1> headlines (“The World’s Most Advanced eFoils. Now in the USA.” and “The World’s Most Advanced eFoils. Now in the USA.”). One clear main headline is easier for people and search engines.

  • 20 links with vague text

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

  • 240 internal links, 51 external

    The homepage links to 240 pages on aerofoils.de and 51 external pages.

7 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Aerofoils eFoils: quiet, performant and with aircraft-inspired safety tech. Made in Germany. Discover the lineup & book…”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Aerofoils | High-Performance eFoils Made in Germany”.

  • Canonical URL set

    The canonical URL is https://aerofoils.com/en-us.

  • Structured data in place

    Structured data found: FAQPage.

  • 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://aerofoils.com/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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://aerofoils.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix68
  • 1 page without a title

    https://aerofoils.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://aerofoils.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 8 pages without a meta description

    https://aerofoils.com/customer_authentication/redirect, https://aerofoils.com/en-us/collections/all, https://aerofoils.com/en-us/products/adventure-efoil-set, https://aerofoils.com/en-us/products/performance-efoil-set, https://aerofoils.com/en-us/products/hyperfly-efoil-set and https://aerofoils.com/en-us/products/performance-board and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://aerofoils.com/customer_authentication/redirect has 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 60 found) and read each the way a search engine does.

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

Best practices

2 to fixGoogle 9687
  • 9 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “[mux-player 3.14.1] playsInline is set to true by default and is not currently supported as a setter.”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 999 words of visible text.

5 checks passed
  • 60 calls to action

    The homepage has 60 calls to action, for example “Shop”, “Buy Now Buy Now” and “Learn More”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 78 testimonial or review blocks, 11 customer or partner logos and 8 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Microsoft Clarity and HubSpot.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 13 email links.

Privacy and tracking

  • 5 trackers load before any consent

    5

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

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies, 6 of them by other companies (measured from a US location before any click).

  • 34 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 aerofoils.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Microsoft Clarity · hubapi.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on aerofoils.de, including 16 speed issues, 2 SEO issues and 3 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