freenet.de website review

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

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

About 2.0 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 10.9 s faster on a phone.

About 2.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.2 s faster on a phone.

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

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

138 KiB could be saved by minifying JavaScript.

8 third-party services load with your homepage (md.de, privacy-mgmt.com and fraud0.com and others), adding 3.9 MB and 121 ms of main-thread time.

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

Amazon Web Services costs a phone 0 ms of main-thread work and 3.2 MB 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.

md.de costs a phone 47 ms of main-thread work and 375 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.

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

Polyfills for old browsers add 63 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

2 KiB could be saved by minifying CSS.

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

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

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

Your largest element takes 41.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Nur für kurze Zeit Samsung Galaxy S26 FE Jetzt mit Galaxy T…”.

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

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

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

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

Real visitors wait 251 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

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

Your homepage downloads 11.2 MB in 189 requests on a phone: scripts 4.6 MB (28), other files 3.4 MB (76) and stylesheets 2.0 MB (15). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example ElektroG_.png at 4,096 px wide, shown at 100 px. Resized copies would save about 81 KiB.

1 image further down the page (81 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

7 buttons have no accessible name, so screen readers announce just “button”.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

64 elements have a tabindex above 0, which scrambles the keyboard order.

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

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

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

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 135 pages on freenet.de and 18 external pages.

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 /%7B%7Bshc.shopData.homepage%7D%7D, which answers with an error. Visitors hit a dead end and search engines drop it.

/suche has no <title>, so Google invents the link text in results.

/onlineservice/registrierung and /suche have no meta description, so Google writes the search snippet from whatever text it finds.

/onlineservice/registrierung and /services/vertrag/vertragsverlaengerung have no <h1> headline, so visitors and search engines get no clear main topic.

/handytarife/ohne-handy/telekom took over 3 s to send its HTML from our server.

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

14 of 65 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 “ERROR TypeError: Cannot read properties of null (reading 'componentsCollection')”.

Large scripts ship without source maps.

1 link from your homepage to your own site is broken, for example https://www.freenet.de/%7B%7Bshc.shopData.homepage%7D%7D (404).

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.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

2 links go through two or more redirects, for example https://www.freenet.de/bk-angebote/.

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.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

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

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

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 629 words of visible text.

Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 redirect=_spf.freenet.de”.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 10 cookies (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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.