Website review, no card needed

sparkasse-offenburg.de logo

sparkasse-offenburg.de website review

Visit site (opens in a new tab)Reviewed 22 October 202629 issues · 77 checks

This review found 29 issues worth fixing on sparkasse-offenburg.de, 14 of them high impact, across 77 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.0 s1.8 sMay 2Oct 171.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.9 s
May 9, 20261.9 s
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
114 ms106 msMay 2Oct 17107 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026110 ms
May 9, 2026108 ms
May 16, 2026108 ms
May 23, 2026108 ms
May 30, 2026109 ms
Jun 6, 2026110 ms
Jun 13, 2026110 ms
Jun 20, 2026110 ms
Jun 27, 2026110 ms
Jul 4, 2026110 ms
Jul 11, 2026112 ms
Jul 18, 2026113 ms
Jul 25, 2026113 ms
Aug 1, 2026113 ms
Aug 8, 2026113 ms
Aug 15, 2026113 ms
Aug 22, 2026113 ms
Aug 29, 2026112 ms
Sep 5, 2026112 ms
Sep 12, 2026112 ms
Sep 19, 2026111 ms
Sep 26, 2026111 ms
Oct 3, 2026110 ms
Oct 10, 2026109 ms
Oct 17, 2026107 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 sparkasse-offenburg.de (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sparkasse-offenburg.de at 0.6 s0.6 s
  2. sparkasse-offenburg.de at 1.3 s1.3 s
  3. sparkasse-offenburg.de at 1.9 s1.9 s
  4. sparkasse-offenburg.de at 2.6 s2.6 s
  5. sparkasse-offenburg.de at 3.2 s3.2 s
  6. sparkasse-offenburg.de at 3.8 s3.8 s
  7. sparkasse-offenburg.de at 4.5 s4.5 s
  8. sparkasse-offenburg.de at 5.1 s5.1 s

Speed

6 to fix41
  • Render-blocking requests

    3.4 s

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

  • Reduce unused CSS

    1.9 s · 353 KiB

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

  • Reduce unused JavaScript

    1.2 s · 221 KiB

    About 221 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Font display

    1.4 s

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

  • Mobile performance score: 41

    41/100

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

  • Use efficient cache lifetimes

    150 ms · 755 KiB

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

  • Improve image delivery

    232 KiB

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

  • 4 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 75 but mobile only 41. 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.

  • Forced reflow

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (sparkasse.de), adding 3 KiB and 0 ms of main-thread time.

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 310 ms of it running JavaScript. That is comfortably low.

  • Server response: 128 ms

    128 ms

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

Core Web Vitals

9 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.50

    0.50

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

  • Largest Contentful Paint: 6.4 s

    6.4 s

    Your largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wir, als Ihre Sparkasse, verwenden Cookies, die unbedingt e…”. Most of its time is element render delay (4.1 s).

  • First Contentful Paint: 4.6 s

    4.6 s

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

  • Cumulative Layout Shift: 0.445

    0.445

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

  • Speed Index: 8.0 s

    8.0 s

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

  • Time to Interactive: 7.5 s

    7.5 s

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • 5 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

4 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 94 ms

    94 ms

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

  • Real-user TTFB: 730 ms

    730 ms

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

  • Total Blocking Time: 21 ms

    21 ms

    Scripts block the page for only 21 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix90
  • 2 images far larger than shown

    140 KiB

    2 images are downloaded at several times the size a phone draws them, for example 1773004051371.jpg at 560 px wide, shown at 72 px. Resized copies would save about 140 KiB.

  • 5 images in older formats

    5 images (315 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 below the first screen load straight away

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

  • About 0.4 g of CO₂ per visit

    0.41 g

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

1 checks passed
  • Page weight: 1.4 MB in 28 requests

    1.4 MB

    Your homepage downloads 1.4 MB in 28 requests on a phone: images 415 KiB (14), stylesheets 366 KiB (2) and fonts 344 KiB (6). That is a lean page.

Accessibility

2 to fixGoogle 10097
  • All page content should be contained by landmarks (5 elements)

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

  • 1 form field without a label

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

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 30 automated accessibility rules passed

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

SEO

3 to fixGoogle 10083
  • No H1 headline

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

  • No structured data

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

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

  • No X (Twitter) card tag

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

  • 343 internal links, 11 external

    The homepage links to 343 pages on sparkasse-offenburg.de and 11 external pages.

5 checks passed
  • Meta description: 119 characters

    Your meta description is 119 characters: “Ihr Finanzpartner im Internet. Mit sicherem Online-Banking, vielen Angeboten und Services für Privat- und Firmenkunden.”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “Sparkasse Offenburg/Ortenau - Internet-Filiale”.

  • Canonical URL set

    The canonical URL is https://www.sparkasse-offenburg.de/de/home.html.

  • 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.sparkasse-offenburg.de/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.sparkasse-offenburg.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,326 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix78
  • 2 pages share a title

    https://www.sparkasse-offenburg.de/pl/home.html and https://www.sparkasse-offenburg.de/cs/home.html all use the title “Home”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://www.sparkasse-offenburg.de/en/home.html, https://www.sparkasse-offenburg.de/fr/home.html, https://www.sparkasse-offenburg.de/pl/home.html, https://www.sparkasse-offenburg.de/tr/home.html and https://www.sparkasse-offenburg.de/cs/home.html have no meta description, so Google writes the search snippet from whatever text it finds.

  • 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.sparkasse-offenburg.de/de/home/immobilien-weiterleitung.html, whose canonical is https://www.sparkasse-offenburg.de/de/home/privatkunden/immobilien.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 8 pages without an H1

    https://www.sparkasse-offenburg.de/fi/home.html, https://www.sparkasse-offenburg.de/de/home/barrierefreiheit/leichte-sprache.html, https://www.sparkasse-offenburg.de/de/home/barrierefreiheit/gebaerdensprache.html, https://www.sparkasse-offenburg.de/en/home.html, https://www.sparkasse-offenburg.de/fr/home.html and https://www.sparkasse-offenburg.de/pl/home.html and 2 others have 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 198 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.

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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 348 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Sparkassen-Shop” and “Demo-Banking”.

  • 3 short forms

    3 short forms (0 fields at most) are right on the homepage.

  • Direct contact links

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

Privacy and tracking

  • 11 cookies set on arrival

    11

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

  • 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 other company contacted

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on sparkasse-offenburg.de, including 15 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