fdp.ch website review

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

5 images could be 184 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.

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

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

Your mobile performance score is 69 (desktop: 81). Pages that score under 90 lose visitors before the first paint.

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

28 KiB could be saved by minifying JavaScript.

24 KiB could be saved by minifying CSS.

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

4 third-party services load with your homepage (YouTube, Unpkg and Cloudflare CDN and others), adding 57 KiB and 8 ms of main-thread time.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

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

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

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

Your homepage downloads 2.7 MB in 77 requests on a phone: fonts 1.5 MB (7), images 493 KiB (12) and scripts 452 KiB (31). Under 2 MB keeps phones on slow connections fast.

4 images (461 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.

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

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

<html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

The page declares lang=“de_CH”, which is not a usable language code, so screen readers and translation tools guess.

Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

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

Your hreflang tags are invalid, so Google may show the wrong language version.

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

The homepage links to 71 pages on fdp.ch and 129 external pages.

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.

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.

Your homepage links to /partei/werte, which answers with an error. Visitors hit a dead end and search engines drop it.

/medien, /spenden, /mitmachen, /aktuell/vorstoesse, /aktuell/vernehmlassungen and /aktuell/freisinn and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

/aktuell and /aktuell/medienmitteilungen use the same meta description. A description written for each page earns more clicks.

/spenden, /mitmachen, /aktuell, /aktuell/vorstoesse, /aktuell/freisinn and /aktuell/stellenangebote and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

/aktuell and /partei 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.

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

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

4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.fdp.ch/_assets/a80390fea21a0fc4fc64fa273c3f90b2/hh_ckeditor_custom/Resources/P…”.

1 link from your homepage to your own site is broken, for example https://www.fdp.ch/partei/werte/ (404).

Your certificate from Let's Encrypt · YE1 expires in 5 days. If it doesn't renew automatically, visitors get a security warning.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

HSTS is set, but max-age is 182 days; one year is the recommended minimum.

5 links go through two or more redirects, for example http://www.plrt.ch/.

Opening https://fdp.ch goes through 2 redirects before the homepage loads.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

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

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

fdp.ch has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 666 words of visible text.

DMARC is set to p=none, so mail pretending to be fdp.ch is still delivered. Reports are on, so moving to quarantine is the next step.

Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 mx a include:spf.protection.outlook.com include:spf.tocco.ch include:spf1.fdp.ch include:_spf.seen.io ?all”.

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.

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

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.

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