Website review, no card needed

aflury.ch logo

aflury.ch website review

Visit site (opens in a new tab)Reviewed 23 October 202638 issues · 83 checks

This review found 38 issues worth fixing on aflury.ch, 11 of them high impact, across 83 checks. The most urgent: use efficient cache lifetimes. 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.3 s933 msMay 2Oct 171.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.1 s
May 9, 20261.0 s
May 16, 20261.1 s
May 23, 20261.0 s
May 30, 2026973 ms
Jun 6, 2026985 ms
Jun 13, 2026993 ms
Jun 20, 20261.0 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.0 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.0 s
Oct 3, 2026982 ms
Oct 10, 20261.0 s
Oct 17, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
86 ms68 msMay 2Oct 1784 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202677 ms
May 9, 202675 ms
May 16, 202676 ms
May 23, 202676 ms
May 30, 202670 ms
Jun 6, 202671 ms
Jun 13, 202671 ms
Jun 20, 202673 ms
Jun 27, 202678 ms
Jul 4, 202677 ms
Jul 11, 202678 ms
Jul 18, 202677 ms
Jul 25, 202678 ms
Aug 1, 202679 ms
Aug 8, 202679 ms
Aug 15, 202681 ms
Aug 22, 202679 ms
Aug 29, 202678 ms
Sep 5, 202678 ms
Sep 12, 202679 ms
Sep 19, 202678 ms
Sep 26, 202680 ms
Oct 3, 202679 ms
Oct 10, 202678 ms
Oct 17, 202684 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 aflury.ch (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix48
  • Use efficient cache lifetimes

    2.8 s · 2.3 MB

    38 files are served with short cache lifetimes, so returning visitors download them again (2.3 MB).

  • Render-blocking requests

    3.3 s

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

  • Reduce unused CSS

    2.3 s · 500 KiB

    About 500 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.3 s faster on a phone.

  • Mobile performance score: 48

    48/100

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

  • Reduce unused JavaScript

    310 ms · 543 KiB

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

  • Improve image delivery

    300 ms · 462 KiB

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

  • Minify CSS

    470 ms · 78 KiB

    78 KiB could be saved by minifying CSS.

  • Font display

    500 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (iubenda, Google Tag Manager and dntfctn.com and others), adding 277 KiB and 270 ms of main-thread time.

  • Minify JavaScript

    109 KiB

    109 KiB could be saved by minifying JavaScript.

  • 1 long task on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 91 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.

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 352 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
  • Cumulative Layout Shift: 0.559

    0.559

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

  • Largest Contentful Paint: 5.1 s

    5.1 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Speed Index: 5.5 s

    5.5 s

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

  • Time to Interactive: 5.1 s

    5.1 s

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

  • 8 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Largest content (LCP) held steady for real visitors

    -4%

    Over the last 25 four-week periods to 2026-10-17, 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).

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: 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 INP: 85 ms

    85 ms

    Real visitors wait 85 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: 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: 702 ms

    702 ms

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

  • 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

4 to fix58
  • Page weight: 2.6 MB in 51 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 51 requests on a phone: scripts 1.0 MB (26), images 787 KiB (10) and stylesheets 507 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 8 images in older formats

    8 images (754 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

    119 KiB

    1 image is downloaded at several times the size a phone draws it, for example csm_Slider_Bahntechnik_828503be69.jpg at 1,600 px wide, shown at 390 px. Resized copies would save about 119 KiB.

  • 4 images below the first screen load straight away

    4 images further down the page (323 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.7 g of CO₂ per visit

    0.74 g

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

Accessibility

6 to fixGoogle 8190
  • 12 text elements with low contrast

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

  • 6 images without alt text

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 7 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed
  • 35 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 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

5 to fixGoogle 8578
  • Title is short (25 characters)

    Your title is only 25 characters: “Startseite - Arthur Flury”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 3 H1 headlines

    There are 3 <h1> headlines (“Bahntechnik”, “Erdung und Blitzschutz” and “Energienetztechnik”). One clear main headline is easier for people and search engines.

  • Meta description is long (196 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

  • No X (Twitter) card tag

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

  • 65 internal links, 0 external

    The homepage links to 65 pages on aflury.ch and 0 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.aflury.ch/de/startseite/.

  • Structured data in place

    Structured data found: WebPage.

  • 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.aflury.ch/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.aflury.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.

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

Other pages

4 to fix81
  • 8 pages share 3 titles

    https://www.aflury.ch/de/produkte/bahntechnik/cat/bahntechnik-93601, https://www.aflury.ch/de/dokumentationen/bahntechnik and https://www.aflury.ch/de/aktuell/bahntechnik all use the title “Bahntechnik - Arthur Flury”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages share a meta description

    https://www.aflury.ch/de/dokumentationen/bahntechnik, https://www.aflury.ch/de/dokumentationen/erdung-und-blitzschutz, https://www.aflury.ch/de/dokumentationen/energienetztechnik, https://www.aflury.ch/de/dokumentationen/unternehmen, https://www.aflury.ch/de/vertrieb/hauptsitz-schweiz and https://www.aflury.ch/de/vertrieb/tochtergesellschaften and 6 others use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.aflury.ch/de/produkte/bahntechnik/cat/bahntechnik-93601, whose canonical is https://www.aflury.ch/de/produkte/bahntechnik. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 10 pages without an H1

    https://www.aflury.ch/de/dokumentationen/bahntechnik, https://www.aflury.ch/de/dokumentationen/erdung-und-blitzschutz, https://www.aflury.ch/de/dokumentationen/energienetztechnik, https://www.aflury.ch/de/dokumentationen/unternehmen, https://www.aflury.ch/de/vertrieb/tochtergesellschaften and https://www.aflury.ch/de/vertrieb/vertriebspartner and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.aflury.ch/de/aktuell/bahntechnik, https://www.aflury.ch/de/aktuell/absturzsicherung and https://www.aflury.ch/de/fachwissen/subventionenliste-blitzschutz 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.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    15 of 15 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 193 words

    The homepage has only about 193 words of visible text; thin pages give Google and first-time buyers little to go on.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 and LinkedIn Insight.

Privacy and tracking

  • 2 trackers load before any consent

    2

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

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies (measured from a US location before any click).

  • 7 other companies contacted

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

1 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) 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 aflury.ch, 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
Framework
jQuery
Analytics
Google Tag Manager

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 aflury.ch, including 14 speed issues, 5 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