Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

baby-walz.at

baby-walz Home | baby-walz

Page Load Speed

3.6 sec in total

First Response

462 ms

Resources Loaded

2.7 sec

Page Rendered

491 ms

baby-walz.at screenshot

About Website

Click here to check amazing Baby Walz content for Austria. Otherwise, check out these important facts you probably never knew about baby-walz.at

Familienfreundliche Preise ✓ Kostenlose Rücksendung ✓ Geprüfte Qualität ➣ persönliche Beratung in über 20 baby-walz Filialen

Visit baby-walz.at

Key Findings

We analyzed Baby-walz.at page load time and found that the first response time was 462 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

baby-walz.at performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value6.7 s

37/100

10%

TBT (Total Blocking Time)

Value790 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.544

13/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

www.baby-walz.at

462 ms

javascript_93077bb238.minified.js

177 ms

stylesheet_2028b4f09b.minified.css

441 ms

javascript_4f8e6c3897.minified.js

720 ms

emos2.js

269 ms

Our browser made a total of 121 requests to load all elements on the main page. We found that 27% of them (33 requests) were addressed to the original Baby-walz.at, 36% (44 requests) were made to Cdn.baby-walz.com and 4% (5 requests) were made to T23.intelliad.de. The less responsive or slowest element that took the longest time to load (720 ms) belongs to the original domain Baby-walz.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (50%)

Content Size

2.3 MB

After Optimization

1.1 MB

In fact, the total size of Baby-walz.at main page is 2.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 905.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 143.1 kB

  • Original 171.9 kB
  • After minification 145.9 kB
  • After compression 28.8 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 26.0 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 143.1 kB or 83% of the original size.

Image Optimization

-5%

Potential reduce by 45.1 kB

  • Original 905.8 kB
  • After minification 860.7 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Baby Walz images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 628.2 kB

  • Original 815.1 kB
  • After minification 593.5 kB
  • After compression 186.9 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 628.2 kB or 77% of the original size.

CSS Optimization

-83%

Potential reduce by 310.1 kB

  • Original 374.1 kB
  • After minification 368.1 kB
  • After compression 64.0 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Baby-walz.at needs all CSS files to be minified and compressed as it can save up to 310.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (36%)

Requests Now

104

After Optimization

67

The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Baby Walz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

baby-walz.at accessibility score

62

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

baby-walz.at best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Prevents users to paste into password fields

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

baby-walz.at SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Baby-walz.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Baby-walz.at main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of Baby Walz. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: