Website review, no card needed

bluebananabrand.de logo

bluebananabrand.de website review

Visit site (opens in a new tab)Reviewed 20 November 202631 issues · 83 checks

This review found 31 issues worth fixing on bluebananabrand.de, 14 of them high impact, across 83 checks. The most urgent: main-thread work: 28.8 s. 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.8 s1.9 sAug 29Nov 142.0 s
Show as table
DateReal-visitor load time (LCP)
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.7 s
Sep 19, 20262.6 s
Sep 26, 20262.7 s
Oct 3, 20262.5 s
Oct 10, 20262.3 s
Oct 17, 20262.2 s
Oct 31, 20262.1 s
Nov 7, 20262.1 s
Nov 14, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
333 ms272 msSep 12Nov 14279 ms
Show as table
DateReal-visitor tap response (INP)
Sep 12, 2026326 ms
Sep 19, 2026295 ms
Sep 26, 2026301 ms
Oct 17, 2026283 ms
Oct 31, 2026320 ms
Nov 7, 2026323 ms
Nov 14, 2026279 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 bluebananabrand.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bluebananabrand.de at 2.8 s2.8 s
  2. bluebananabrand.de at 5.6 s5.6 s
  3. bluebananabrand.de at 8.4 s8.4 s
  4. bluebananabrand.de at 11.2 s11.2 s
  5. bluebananabrand.de at 14.0 s14.0 s
  6. bluebananabrand.de at 16.8 s16.8 s
  7. bluebananabrand.de at 19.6 s19.6 s
  8. bluebananabrand.de at 22.4 s22.4 s

Speed

9 to fix34
  • Main-thread work: 28.8 s

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

  • Reduce unused JavaScript

    1.2 s · 553 KiB

    About 553 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.

  • 10,258 HTML elements

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

  • Mobile performance score: 34

    34/100

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

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 5.1 s. During a long task the page ignores taps.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and Klaviyo and others), adding 1.4 MB and 1.1 s of main-thread time.

  • Render-blocking requests

    900 ms

    18 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

  • Shopify adds 351 ms

    351 ms

    Shopify costs a phone 351 ms of main-thread work and 680 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.

  • Google Tag Manager adds 334 ms

    334 ms

    Google Tag Manager costs a phone 334 ms of main-thread work and 192 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.

  • Improve image delivery

    150 ms · 229 KiB

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

  • Use efficient cache lifetimes

    100 ms · 157 KiB

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

  • Reduce unused CSS

    150 ms · 59 KiB

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

  • Legacy JavaScript

    150 ms · 51 KiB

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

  • Duplicated JavaScript

    180 KiB

    180 KiB JavaScript is shipped twice across bundles.

  • Minify JavaScript

    42 KiB

    42 KiB could be saved by minifying JavaScript.

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 58 ms

    58 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 13.2 s

    13.2 s

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

  • Total Blocking Time: 10.5 s

    10.5 s

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

  • Time to Interactive: 22.7 s

    22.7 s

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

  • Speed Index: 10.0 s

    10.0 s

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

  • Real-user INP: 285 ms

    285 ms

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Tap response (INP) held steady for real visitors

    -3%

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

6 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user CLS: 0.08

    0.08

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 526 ms

    526 ms

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

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

    -19%

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

  • Cumulative Layout Shift: 0.004

    0.004

    The layout barely moves while loading (CLS 0.004, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 5.2 MB in 493 requests

    5.2 MB

    Your homepage downloads 5.2 MB in 493 requests on a phone: images 1.8 MB (73), scripts 1.4 MB (120) and other files 1.2 MB (236). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (98 KiB) is 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.

  • About 1.5 g of CO₂ per visit

    1.46 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.46 g of CO₂e: 175.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 load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 8995
  • 19 text elements with low contrast

    19 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 (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • ARIA role should be appropriate for the element (72 elements)

    ARIA role should be appropriate for the element: 72 elements on the page fail this check, rated minor by axe-core.

  • 55 links without text

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

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

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

2 checks passed
  • Every image has alt text

    All 36 images in the HTML carry an alt attribute.

  • 54 automated accessibility rules passed

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

SEO

1 to fixGoogle 9295
  • One H1 headline

    Your <h1> is empty.

  • 280 internal links, 4 external

    The homepage links to 280 pages on bluebananabrand.de and 4 external pages.

7 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Somos la nueva aventura. Solo en Blue Banana. Descubre las primeras prendas carbon negative de España. Fabricadas con p…”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Blue Banana Brand - Sudaderas, camisetas y hoodies”.

  • Canonical URL set

    The canonical URL is https://www.bluebananabrand.de/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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.bluebananabrand.com/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,579 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.bluebananabrand.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 8 pages without a meta description

    https://www.bluebananabrand.de/policies/shipping-policy, https://www.bluebananabrand.de/collections/black-friday-hombre, https://www.bluebananabrand.de/collections/black-friday-50-hombre, https://www.bluebananabrand.de/collections/black-friday-30-hombre, https://www.bluebananabrand.de/collections/black-friday-20-hombre and https://www.bluebananabrand.de/collections/black-friday-mujer and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.bluebananabrand.de/collections/all, https://www.bluebananabrand.de/products/perfume-advtrn-aw25, https://www.bluebananabrand.de/products/off-white-stripes-socks-aw26, https://www.bluebananabrand.de/products/cream-nature-tote-bag-ss25, https://www.bluebananabrand.de/products/olive-green-nature-socks-aw26 and https://www.bluebananabrand.de/products/white-amsterdam-socks-aw26 and 9 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 106 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.

  • Titles are unique

    Every page we checked has its own title.

  • 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

2 to fixGoogle 9287
  • 50 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) ReferenceError: Shopify is not defined”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • 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 1,633 words of copy

    The homepage carries about 1,633 words of visible text.

2 checks passed
  • 25 short forms

    25 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 8 trackers load before any consent

    8

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

  • 29 cookies set on arrival

    29

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

  • 53 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 bluebananabrand.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Gorgias Live Chat Helpdesk · Sc Easy Redirects · Klaviyo Email Marketing Sms · Kaching Bundles · Judge Me Reviews · Doofinder Search Discovery · Eg Auto Add To Cart · Mp Size Chart

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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 bluebananabrand.de, including 16 speed issues, 1 SEO issue 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