flybaby.berlin website review

Not measured in this review.

• Page weight: 3.9 MB

  3.9 MB

  Your homepage downloads 3.9 MB on a phone, 626 KiB of it images (16%). Under 2 MB keeps phones on slow connections fast.

• An image on the first screen is lazy-loaded

  1c89537868744593a1c43586af0fd85a.thumbnail.0000000000.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  Elements (3)

• 2 images in older formats

  2 images (129 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.

  Elements (2)

• 1 image below the first screen load straight away

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

  Elements (1)

• About 1.1 g of CO₂ per visit

  1.11 g

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

• Certain ARIA roles must contain particular children (1 element)

  Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  Elements (1)

• 10 tap targets too small

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

  Elements (3)

• Scrollable region must have keyboard access (2 elements)

  Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  Elements (2)

• 22 images without alt text

  22 images have no alt text, which hurts accessibility and image search.

  View sourceElements (3)

• All page content should be contained by landmarks (83 elements)

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

  Elements (3)

• Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

  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.

  Elements (1)

• ARIA role should be appropriate for the element (1 element)

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

  Elements (1)

• Headings skip levels

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

  View source

• Title is short (7 characters)

  Your title is only 7 characters: “Flybaby”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• 2 H1 headlines

  There are 2 <h1> headlines (“Flybaby” and “Big love for Mokka. Bigger adventures ahead.”). One clear main headline is easier for people and search engines.

  View source

• 174 internal links, 6 external

  The homepage links to 174 pages on flybaby.berlin and 6 external pages.

• 5 pages without a meta description

  https://flybaby.berlin/en/pages/unsere-beiden-tragen-vergleichen, https://flybaby.berlin/en/pages/uber-uns, https://flybaby.berlin/en/pages/faq, https://flybaby.berlin/en/pages/sicherheits-und-pflegehinweise and https://flybaby.berlin/en/pages/contact have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (5)

• 7 pages without an H1

  https://flybaby.berlin/en/products/flybaby-carrier, https://flybaby.berlin/en/pages/unsere-beiden-tragen-vergleichen, https://flybaby.berlin/en/pages/uber-uns, https://flybaby.berlin/en/pages/faq, https://flybaby.berlin/en/pages/how-to and https://flybaby.berlin/en/pages/sicherheits-und-pflegehinweise and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

• 4 pages slow to respond

  https://flybaby.berlin/en/products/everything-set, https://flybaby.berlin/en/products/flybaby-geschenkgutschein, https://flybaby.berlin/en/pages/uber-uns and https://flybaby.berlin/en/pages/faq took over 3 s to send their HTML from our server.

• 15 internal pages checked

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

• 24 small tap targets

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

• 1 JavaScript error while loading

  1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

• About 1,651 words of copy

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

• 6 trackers load before any consent

  6

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.

• 30 cookies set on arrival

  30

  Opening the homepage sets 30 cookies, 3 of them by other companies (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.

• 37 other companies contacted

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