Website review, no card needed

bmfsfj.de logo

bmfsfj.de website review

Visit site (opens in a new tab)Reviewed 26 October 202631 issues · 74 checks

This review found 31 issues worth fixing on bmfsfj.de, 11 of them high impact, across 74 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.4 s796 msMay 9Oct 24867 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.0 s
May 16, 20261.0 s
May 23, 20261.0 s
May 30, 20261.1 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 2026930 ms
Oct 10, 2026919 ms
Oct 17, 2026881 ms
Oct 24, 2026867 ms
Real-visitor tap response (INP)75th percentile, phones
88 ms80 msMay 9Oct 2484 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202683 ms
May 16, 202681 ms
May 23, 202682 ms
May 30, 202683 ms
Jun 6, 202684 ms
Jun 13, 202685 ms
Jun 20, 202686 ms
Jun 27, 202686 ms
Jul 4, 202686 ms
Jul 11, 202687 ms
Jul 18, 202686 ms
Jul 25, 202685 ms
Aug 1, 202685 ms
Aug 8, 202685 ms
Aug 15, 202686 ms
Aug 22, 202686 ms
Aug 29, 202687 ms
Sep 5, 202687 ms
Sep 12, 202686 ms
Sep 19, 202686 ms
Sep 26, 202686 ms
Oct 3, 202683 ms
Oct 10, 202684 ms
Oct 17, 202684 ms
Oct 24, 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 bmfsfj.de (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bmfsfj.de at 1.1 s1.1 s
  2. bmfsfj.de at 2.2 s2.2 s
  3. bmfsfj.de at 3.2 s3.2 s
  4. bmfsfj.de at 4.3 s4.3 s
  5. bmfsfj.de at 5.4 s5.4 s
  6. bmfsfj.de at 6.5 s6.5 s
  7. bmfsfj.de at 7.5 s7.5 s
  8. bmfsfj.de at 8.6 s8.6 s

Speed

10 to fix37
  • Use efficient cache lifetimes

    1.0 s · 2.6 MB

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

  • Font display

    1.1 s

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

  • Mobile performance score: 37

    37/100

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

  • Reduce unused JavaScript

    916 KiB

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

  • 4 long tasks on the main thread

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

  • Render-blocking requests

    550 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 550 ms.

  • Reduce unused CSS

    450 ms · 91 KiB

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

  • Improve image delivery

    481 KiB

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

  • Main-thread work: 3.7 s

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

  • 1,832 HTML elements

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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.

1 checks passed
  • Server response: 119 ms

    119 ms

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

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user CLS: 0.90

    0.90

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

  • Cumulative Layout Shift: 0.879

    0.879

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

  • Time to Interactive: 17.2 s

    17.2 s

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

  • Speed Index: 10.8 s

    10.8 s

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

  • Total Blocking Time: 876 ms

    876 ms

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

  • Largest Contentful Paint: 3.4 s

    3.4 s

    Your largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Jugendlicher mit Mobiltelefon”. Most of its time is resource load duration (1.8 s).

  • 11 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

6 checks passed
  • Real-user LCP: 1.2 s

    1.2 s

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

  • Real-user INP: 129 ms

    129 ms

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 490 ms

    490 ms

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

  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

Images and page weight

2 to fix78
  • Page weight: 2.9 MB in 68 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 68 requests on a phone: scripts 1.6 MB (2), images 875 KiB (59) and fonts 270 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 13 images below the first screen load straight away

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

  • About 0.8 g of CO₂ per visit

    0.81 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

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

    Elements with visible text labels do not have matching accessible names. (5 elements).

2 checks passed
  • Every image has alt text

    All 60 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

3 to fixGoogle 10085
  • Title is short (20 characters)

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

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 174 internal links, 57 external

    The homepage links to 174 pages on bmfsfj.de and 57 external pages.

5 checks passed
  • Meta description: 122 characters

    Your meta description is 122 characters: “Hier finden Sie aktuelle Informationen des Bundesministeriums für Bildung, Familie, Senioren, Frauen und Jugend (BMBFSF…”.

  • One H1 headline

    Your main headline reads: “BMBFSFJ”.

  • 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.bmbfsfj.bund.de/service-sitemap-b391d6efd2092a2aac9fba5db84be971-sitemap_index.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.bmbfsfj.bund.de/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 (1,332 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 2 pages share a title

    / and https://www.bmbfsfj.bund.de/bmbfsfj all use the title “Startseite - BMBFSFJ”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages without a meta description

    https://www.bmbfsfj.bund.de/bmbfsfj/meta/en, https://www.bmbfsfj.bund.de/bmbfsfj/aktuelles/presse, https://www.bmbfsfj.bund.de/bmbfsfj/meta/datenschutz, https://www.bmbfsfj.bund.de/bmbfsfj/meta/gebaerdensprache, https://www.bmbfsfj.bund.de/bmbfsfj/meta/leichte-sprache and https://www.bmbfsfj.bund.de/bmbfsfj/themen and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.bmbfsfj.bund.de/bmbfsfj/informationen-zur-verarbeitung-personenbezogener-daten-99428 and https://www.bmbfsfj.bund.de/bmbfsfj use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

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

  • 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

1 to fixGoogle 9697
  • 11 distorted images

    11 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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.

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

    The homepage carries about 765 words of visible text.

3 checks passed
  • 1 short form

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

  • Analytics in place

    Analytics detected: Matomo.

  • Direct contact links

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

Privacy and tracking

  • No consent tool detected

    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.

1 checks passed
  • 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 bmfsfj.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Matomo
Hosting
Init

Company

Employees
844
Founded
1953
Headquarters
Berlin

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on bmfsfj.de, including 18 speed issues, 3 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