Menu:

Webpage Performance Test Result

Settings: Desktopv129CableFrankfurt, Germany
More
- Test runs: 1
- Connectivity: 5000/1000 Kbps, 28ms Latency
- Custom Metrics
Share

Lighthouse Report

Lighthouse is an open-source, automated tool for improving the quality of web pages. You can run it against any web page, public or requiring authentication. Overall scoring color key: (0-49 50-89 90-100).

For scripted tests, Lighthouse report will only be available on the final step.

Did you know? Lighthouse runs in Chrome and provides a great complementary analysis alongside the many browsers, devices, and locations WebPageTest offers. To see how this site performs in more environments: Start a new test

Performance 92

Lighthouse Metrics

Values are estimated and may vary.

The performance score is calculated directly from these metrics. See calculator.

First Contentful Paint	Speed Index	Largest Contentful Paint	Time to Interactive	Total Blocking Time	Cumulative Layout Shift
1.1s	2.2s	1.1s	1.1s	0ms	0.034

Aiming to improve? check out our Opportunities & Experiments for suggestions and run No-Code Experiments to see how changes impact this site!

Filmstrip

Show audits relevant to metrics: ALL FCP LCP TBT CLS

View Tree Map

Opportunities (9)

Serve images in next-gen formats

Estimated savings 0.43 s

Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.

URL	Resource Size (bytes)	Potential Savings (bytes)
https://www.kalorienbedarf.de/content/12-home/kb_naehrstoffe.jpg	364283	312598
https://www.kalorienbedarf.de/thumbs/logo-236x92.png	14064	10088

Properly size images

Estimated savings 0.43 s

Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.

URL	Resource Size (bytes)	Potential Savings (bytes)
https://www.kalorienbedarf.de/content/12-home/kb_naehrstoffe.jpg	364283	316534

Eliminate render-blocking resources

View Experiment!

Estimated savings 0.4 s

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.

URL	Transfer Size (bytes)	Potential Savings (ms)
https://www.kalorienbedarf.de/assets/css/bootstrap.min.css	141088	1998
https://code.jquery.com/jquery-3.3.1.min.js	30624	1445
https://www.gstatic.com/charts/loader.js	18563	1291
https://gdpr-tcfv2.sp-prod.net/wrapperMessagingWithoutDetection.js	52929	1669

Efficiently encode images

Estimated savings 0.31 s

Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.

URL	Resource Size (bytes)	Potential Savings (bytes)
https://www.kalorienbedarf.de/content/12-home/kb_naehrstoffe.jpg	364283	245919

Reduce unused JavaScript

Estimated savings 0.15 s

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

URL	Transfer Size (bytes)	Potential Savings (bytes)
https://cdn.privacy-mgmt.com/Notice.c17e7.js	78221	50028
https://www.googletagmanager.com/gtag/js?id=G-WPRXLZTDXY&l=dataLayer&cx=c&gtm=45He4b70v9117919079za200	106761	40591
https://www.googletagmanager.com/gtm.js?id=GTM-PC7QN9P	77808	38457
https://www.kalorienbedarf.de/assets/js/bootstrap.min.js	50731	37313
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js	54202	31752
https://gdpr-tcfv2.sp-prod.net/wrapperMessagingWithoutDetection.js	52524	31220

Enable text compression

Estimated savings 0.09 s

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.

URL	Transfer Size (bytes)	Potential Savings (bytes)
https://www.kalorienbedarf.de/assets/css/bootstrap.min.css	140930	119831
https://www.kalorienbedarf.de/assets/js/bootstrap.min.js	50731	36693
https://www.kalorienbedarf.de/assets/css/ivbnm.css	3672	2744

Reduce unused CSS

Estimated savings 0.09 s

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

URL	Transfer Size (bytes)	Potential Savings (bytes)
https://www.kalorienbedarf.de/assets/css/bootstrap.min.css	141088	127954

Initial server response time was short

Root document took 100 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

URL	Time Spent (ms)
https://www.kalorienbedarf.de/	96

Avoid serving legacy JavaScript to modern browsers

Potential savings of 39 KiB

Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript

URL

Potential Savings (bytes)

https://cdn.privacy-mgmt.com/index.html?hasCsp=true&message_id=888194&consentUUID=null&consent_origin=https%3A%2F%2Fcdn.privacy-mgmt.com%2Fconsent%2Ftcfv2&preload_message=true&version=v1

12176

Location	Signal
URL: https://cdn.privacy-mgmt.com/index.html?hasCsp=true&message_id=888194&consentUUID=null&consent_origin=https%3A%2F%2Fcdn.privacy-mgmt.com%2Fconsent%2Ftcfv2&preload_message=true&version=v1 Line: 14 Column: 15	Array.prototype.find
URL: https://cdn.privacy-mgmt.com/index.html?hasCsp=true&message_id=888194&consentUUID=null&consent_origin=https%3A%2F%2Fcdn.privacy-mgmt.com%2Fconsent%2Ftcfv2&preload_message=true&version=v1 Line: 99 Column: 8	Array.prototype.findIndex

https://cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js

12017

Location	Signal
URL: https://cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js Line: 0 Column: 79154	Object.keys
URL: https://cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js Line: 0 Column: 83322	Array.prototype.filter
URL: https://cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js Line: 0 Column: 91590	Array.from
URL: https://cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js Line: 0 Column: 91996	Array.prototype.map
URL: https://cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js Line: 0 Column: 92189	Object.getOwnPropertyDescriptors
URL: https://cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js Line: 0 Column: 92818	Object.entries
URL: https://cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js Line: 0 Column: 108199	Object.values
URL: https://cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js Line: 0 Column: 115398	@babel/plugin-transform-classes

https://gdpr-tcfv2.sp-prod.net/wrapperMessagingWithoutDetection.js

10126

Location	Signal
URL: https://gdpr-tcfv2.sp-prod.net/wrapperMessagingWithoutDetection.js Line: 0 Column: 11064	Object.getPrototypeOf
URL: https://gdpr-tcfv2.sp-prod.net/wrapperMessagingWithoutDetection.js Line: 0 Column: 16648	Number.isInteger
URL: https://gdpr-tcfv2.sp-prod.net/wrapperMessagingWithoutDetection.js Line: 0 Column: 18487	Array.prototype.map
URL: https://gdpr-tcfv2.sp-prod.net/wrapperMessagingWithoutDetection.js Line: 0 Column: 18649	Object.keys
URL: https://gdpr-tcfv2.sp-prod.net/wrapperMessagingWithoutDetection.js Line: 0 Column: 35015	String.prototype.repeat
URL: https://gdpr-tcfv2.sp-prod.net/wrapperMessagingWithoutDetection.js Line: 0 Column: 35098	Array.from
URL: https://gdpr-tcfv2.sp-prod.net/wrapperMessagingWithoutDetection.js Line: 0 Column: 35338	Array.prototype.filter
URL: https://gdpr-tcfv2.sp-prod.net/wrapperMessagingWithoutDetection.js Line: 0 Column: 56433	Array.prototype.find
URL: https://gdpr-tcfv2.sp-prod.net/wrapperMessagingWithoutDetection.js Line: 0 Column: 62038	@babel/plugin-transform-classes
URL: https://gdpr-tcfv2.sp-prod.net/wrapperMessagingWithoutDetection.js Line: 0 Column: 118957	@babel/plugin-transform-regenerator

https://cdn.privacy-mgmt.com/unified/4.25.3/gdpr-tcf.0b327789b5d246674c71.bundle.js

5637

Location	Signal
URL: https://cdn.privacy-mgmt.com/unified/4.25.3/gdpr-tcf.0b327789b5d246674c71.bundle.js Line: 0 Column: 3816	@babel/plugin-transform-classes
URL: https://cdn.privacy-mgmt.com/unified/4.25.3/gdpr-tcf.0b327789b5d246674c71.bundle.js Line: 0 Column: 149420	Object.getPrototypeOf
URL: https://cdn.privacy-mgmt.com/unified/4.25.3/gdpr-tcf.0b327789b5d246674c71.bundle.js Line: 0 Column: 149766	Reflect.construct
URL: https://cdn.privacy-mgmt.com/unified/4.25.3/gdpr-tcf.0b327789b5d246674c71.bundle.js Line: 0 Column: 150478	Reflect.get
URL: https://cdn.privacy-mgmt.com/unified/4.25.3/gdpr-tcf.0b327789b5d246674c71.bundle.js Line: 0 Column: 155214	Number.isInteger
URL: https://cdn.privacy-mgmt.com/unified/4.25.3/gdpr-tcf.0b327789b5d246674c71.bundle.js Line: 0 Column: 159883	String.prototype.repeat

Diagnostics (12)

Page prevented back/forward cache restoration

2 failure reasons

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reason

Failure type

Pages whose main resource has cache-control:no-store cannot enter back/forward cache.

Not actionable

Frame Url
https://www.kalorienbedarf.de/

JsNetworkRequestReceivedCacheControlNoStoreResource

Not actionable

Frame Url
https://www.kalorienbedarf.de/

Avoid chaining critical requests

6 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
1. https://www.kalorienbedarf.de/ 13kb
  
  https://www.kalorienbedarf.de/assets/css/bootstrap.min.css 138kb
  https://www.kalorienbedarf.de/assets/css/ivbnm.css 4kb
  https://www.kalorienbedarf.de/assets/plugins/rechner/css/rechner.css 0kb
  https://code.jquery.com/jquery-3.3.1.min.js 30kb
  https://www.gstatic.com/charts/loader.js 18kb
  https://gdpr-tcfv2.sp-prod.net/wrapperMessagingWithoutDetection.js 52kb
Largest Contentful Paint element

1,070 ms

This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element

Avoids enormous network payloads

Total size was 1,096 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size (bytes)
https://www.kalorienbedarf.de/content/12-home/kb_naehrstoffe.jpg	364564
https://www.kalorienbedarf.de/assets/css/bootstrap.min.css	141088
https://www.googletagmanager.com/gtag/js?id=G-WPRXLZTDXY&l=dataLayer&cx=c&gtm=45He4b70v9117919079za200	107026
https://cdn.privacy-mgmt.com/Notice.c17e7.js	78603
https://www.googletagmanager.com/gtm.js?id=GTM-PC7QN9P	78416
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js	54229
https://gdpr-tcfv2.sp-prod.net/wrapperMessagingWithoutDetection.js	52929
https://www.kalorienbedarf.de/assets/js/bootstrap.min.js	50871
https://cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js	40914
https://code.jquery.com/jquery-3.3.1.min.js	30624

Avoid long main-thread tasks

1 long task found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

URL	Start Time	Duration
https://www.kalorienbedarf.de/	877	119

Minimize third-party usage

Third-party code blocked the main thread for 0 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.

Third-Party

Transfer Size (bytes)

Main-Thread Blocking Time

Google Tag Manager

185442

URL	Transfer Size	Blocking Time
https://www.googletagmanager.com/gtag/js?id=G-WPRXLZTDXY&l=dataLayer&cx=c&gtm=45He4b70v9117919079za200	107026	0
https://www.googletagmanager.com/gtm.js?id=GTM-PC7QN9P	78416	0

privacy-mgmt.com

167010

URL	Transfer Size	Blocking Time
https://cdn.privacy-mgmt.com/Notice.c17e7.js	78603	0
https://cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js	40914	0
https://cdn.privacy-mgmt.com/unified/4.25.3/gdpr-tcf.0b327789b5d246674c71.bundle.js	24040	0
https://cdn.privacy-mgmt.com/wrapper/v2/messages?hasCsp=true&env=prod&body=%7B%22accountId%22%3A1061%2C%22campaignEnv%22%3A%22prod%22%2C%22campaigns%22%3A%7B%22gdpr%22%3A%7B%22consentStatus%22%3A%7B%7D%2C%22targetingParams%22%3A%7B%7D%7D%7D%2C%22clientMMSOrigin%22%3A%22https%3A%2F%2Fcdn.privacy-mgmt.com%22%2C%22hasCSP%22%3Atrue%2C%22includeData%22%3A%7B%22localState%22%3A%7B%22type%22%3A%22string%22%7D%2C%22actions%22%3A%7B%22type%22%3A%22RecordString%22%7D%2C%22cookies%22%3A%7B%22type%22%3A%22RecordString%22%7D%7D%2C%22propertyHref%22%3A%22https%3A%2F%2Fwww.kalorienbedarf.de%2F%22%7D&localState=null&metadata=%7B%22gdpr%22%3A%7B%22applies%22%3Atrue%7D%7D&nonKeyedLocalState=null&ch=4593188634593188638d40&scriptVersion=4.25.3&scriptType=unified	7065	0
https://cdn.privacy-mgmt.com/Notice.f8044.css	6262	0
https://cdn.privacy-mgmt.com/polyfills.355e5.js	2352	0
https://cdn.privacy-mgmt.com/index.html?hasCsp=true&message_id=888194&consentUUID=null&consent_origin=https%3A%2F%2Fcdn.privacy-mgmt.com%2Fconsent%2Ftcfv2&preload_message=true&version=v1	2245	0
https://cdn.privacy-mgmt.com/consent/tcfv2/vendor-list/categories?siteId=14453&consentLanguage=de	1542	0
https://cdn.privacy-mgmt.com/consent/tcfv2/vendor-list/categories?siteId=14453	1344	0
https://cdn.privacy-mgmt.com/wrapper/v2/meta-data?hasCsp=true&accountId=1061&env=prod&metadata=%7B%22gdpr%22%3A%7B%7D%7D&propertyId=14453&scriptVersion=4.25.3&scriptType=unified	757	0
https://cdn.privacy-mgmt.com/wrapper/v2/pv-data?hasCsp=true&env=prod&ch=4593188634593188638d40&scriptVersion=4.25.3&scriptType=unified	737	0
https://cdn.privacy-mgmt.com/mms/v2/get_site_data?hasCsp=true&href=https%3A%2F%2Fwww.kalorienbedarf.de%2F&account_id=1061	612	0
https://cdn.privacy-mgmt.com/wrapper/metrics/v1/custom-metrics?hasCsp=true&scriptVersion=4.25.3&scriptVersion=4.25.3&scriptType=tcfv2	537	0

Google/Doubleclick Ads

55223

URL	Transfer Size	Blocking Time
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js	54229	0
https://stats.g.doubleclick.net/g/collect?v=2&tid=G-WPRXLZTDXY&cid=548955045.1731117217&gtm=45je4b70v883264746z89117919079za200zb9117919079&aip=1&dma=0&gcd=13l3l3l3l1l1&npa=0&frm=0&tag_exp=101823848~101925629	515	0
https://td.doubleclick.net/td/ga/rul?tid=G-WPRXLZTDXY&gacid=548955045.1731117217&gtm=45je4b70v883264746z89117919079za200zb9117919079&dma=0&gcd=13l3l3l3l1l1&npa=0&pscdl=noapi&aip=1&fledge=1&frm=0&tag_exp=101823848~101925629&z=1553344338	479	0

sp-prod.net

52929

URL	Transfer Size	Blocking Time
https://gdpr-tcfv2.sp-prod.net/wrapperMessagingWithoutDetection.js	52929	0

jQuery CDN

30624

URL	Transfer Size	Blocking Time
https://code.jquery.com/jquery-3.3.1.min.js	30624	0

symplr.de

19762

URL	Transfer Size	Blocking Time
https://cdns.symplr.de/kalorienbedarf.de/kalorienbedarf.js	19762	0

Google CDN

18563

URL	Transfer Size	Blocking Time
https://www.gstatic.com/charts/loader.js	18563	0

Google Analytics

506

URL	Transfer Size	Blocking Time
https://analytics.google.com/g/collect?v=2&tid=G-WPRXLZTDXY&gtm=45je4b70v883264746z89117919079za200zb9117919079&_p=1731117216173&_gaz=1&gcd=13l3l3l3l1l1&npa=0&dma=0&tcfd=10000&tag_exp=101823848~101925629&cid=548955045.1731117217&ul=en-us&sr=800x600&uaa=x86&uab=64&uafvl=Google%2520Chrome%3B129.0.6668.100%7CNot%253DA%253FBrand%3B8.0.0.0%7CChromium%3B129.0.6668.100&uamb=0&uam=&uap=macOS&uapv=10.15.7&uaw=0&are=1&pae=1&frm=0&pscdl=noapi&_s=1&sid=1731117216&sct=1&seg=0&dl=https%3A%2F%2Fwww.kalorienbedarf.de%2F&dt=Kalorienbedarf%20-%20so%20viel%20Energie%20ben%C3%B6tigt%20der%20K%C3%B6rper&en=page_view&_fv=1&_nsi=1&_ss=1&tfd=1711	506	0

JavaScript execution time

0.2 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

URL	Total CPU Time	Script Evaluation	Script Parse
https://www.kalorienbedarf.de/	172	23	1
Unattributable	158	2	0
https://cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js	111	53	2
https://cdn.privacy-mgmt.com/Notice.c17e7.js	103	85	4

Minimizes main-thread work

0.7 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Category	Time Spent
Script Evaluation	296
Other	174
Style & Layout	165
Script Parsing & Compilation	29
Parse HTML & CSS	22
Garbage Collection	18
Rendering	11

Avoids an excessive DOM size

437 elements

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.

Statistic	Element	Value
Total DOM Elements
Maximum DOM Depth	span#maternity > div.form-check-inline > label.form-check-label > input#schwanger
Maximum Child Elements	div.bg-white > div.row > div.col-lg-9 > div.text-area

Avoid large layout shifts

5 elements found

These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Element	Layout shift impact
body > div.container > div.bg-white	0
body > div.message-container > div#notice	0
body > div.container	0
div.col-lg-9 > div.text-area > div.row > div.col-xs-12	0
div.col-lg-9 > div.text-area > div.row > div.col-xs-12	0

Image elements do not have explicit width and height

View Experiment!

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

URL
https://www.kalorienbedarf.de/content/12-home/kb_naehrstoffe.jpg
https://www.kalorienbedarf.de/thumbs/logo-236x92.png

Serve static assets with an efficient cache policy

13 resources found

A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.

URL	Cache TTL	Transfer Size (bytes)
https://www.kalorienbedarf.de/content/12-home/kb_naehrstoffe.jpg	0	364564
https://www.kalorienbedarf.de/assets/css/bootstrap.min.css	0	141088
https://www.kalorienbedarf.de/assets/js/bootstrap.min.js	0	50871
https://www.kalorienbedarf.de/thumbs/logo-236x92.png	0	14145
https://www.kalorienbedarf.de/assets/css/ivbnm.css	0	3743
https://www.kalorienbedarf.de/content/kb-list.svg	0	1759
https://www.kalorienbedarf.de/assets/js/ivbnm.js	0	59
https://cdn.privacy-mgmt.com/Notice.c17e7.js	3600000	78603
https://gdpr-tcfv2.sp-prod.net/wrapperMessagingWithoutDetection.js	3600000	52929
https://cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js	3600000	40914
https://www.gstatic.com/charts/loader.js	3600000	18563
https://cdn.privacy-mgmt.com/Notice.f8044.css	3600000	6262
https://cdn.privacy-mgmt.com/polyfills.355e5.js	3600000	2352

Passed Audits (18)

Avoid multiple page redirects

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Preconnect to required origins

Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.
Preload key requests

Consider using <link rel=preload> to prioritize fetching resources that are currently requested later in page load. Learn how to preload key requests.
All text remains visible during webfont loads

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
Minify JavaScript

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Minify CSS

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Preload Largest Contentful Paint image

If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.
Use video formats for animated content

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formats
Largest Contentful Paint image was not lazily loaded

Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.
Lazy load third-party resources with facades

Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.
Remove duplicate modules in JavaScript bundles

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Has a <meta name="viewport"> tag with width or initial-scale

A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Avoid non-composited animations

Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animations
Defer offscreen images

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Use HTTP/2

HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more about HTTP/2.
User Timing marks and measures

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
Uses passive listeners to improve scrolling performance

Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Avoids document.write()

For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().

Accessibility 85

Contrast (1)

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

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements

div#navbarTop > ul.navbar-nav > li.nav-item > a.nav-link Fix any of the following:
Element has insufficient color contrast of 3.94 (foreground color: #808080, background color: #ffffff, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

Related Node
body

Related Node
body

Related Node
body

Related Node
body

Related Node
body

Related Node
body

Related Node
body

Related Node
body

Related Node
body

Related Node
body

Related Node
body

div.sidebar-nav > ul.list-group > li.list-group-item > a Fix any of the following:
Element has insufficient color contrast of 3.13 (foreground color: #28a745, background color: #ffffff, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

Related Node
div.d-none > div.sidebar-nav > ul.list-group > li.list-group-item

Related Node
div.d-none > div.sidebar-nav > ul.list-group > li.list-group-item

Related Node
div.d-none > div.sidebar-nav > ul.list-group > li.list-group-item

Related Node
div.d-none > div.sidebar-nav > ul.list-group > li.list-group-item

Related Node
div.d-none > div.sidebar-nav > ul.list-group > li.list-group-item

div.col-lg-9 > div.text-area > p > a Fix any of the following:
Element has insufficient color contrast of 3.13 (foreground color: #28a745, background color: #ffffff, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

Related Node
body > div.container > div.bg-white

Related Node
body > div.container > div.bg-white

Related Node
body > div.container > div.bg-white

form#kbrechnerStart > div.card-body > div.form-group > input#submit Fix any of the following:
Element has insufficient color contrast of 3.13 (foreground color: #ffffff, background color: #28a745, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

Related Node
body > div.container > div.bg-white

Related Node
body > div.container > div.bg-white

div.col-xs-12 > ol > li > a Fix any of the following:
Element has insufficient color contrast of 3.13 (foreground color: #28a745, background color: #ffffff, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

Related Node
body > div.container > div.bg-white

Related Node
body > div.container > div.bg-white

Related Node
body > div.container > div.bg-white

Related Node
body > div.container > div.bg-white

Related Node
body > div.container > div.bg-white

Related Node
body > div.container > div.bg-white

div.text-area > ul > li > a Fix any of the following:
Element has insufficient color contrast of 3.13 (foreground color: #28a745, background color: #ffffff, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

Related Node
body > div.container > div.bg-white

div.card > div#h2818a2f0de163ab89bf8ca2a41f830e2 > span.panel-title > a.collapsed Fix any of the following:
Element has insufficient color contrast of 2.92 (foreground color: #28a745, background color: #f7f7f7, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

Related Node
div.text-area > div#acc7875480 > div.card > div#h2818a2f0de163ab89bf8ca2a41f830e2
div.col-lg-9 > div.text-area > div#acc7875480 > div.card

div.card > div#h51ba81607e083cc1ccc1ff33f1cdd590 > span.panel-title > a.collapsed Fix any of the following:
Element has insufficient color contrast of 2.92 (foreground color: #28a745, background color: #f7f7f7, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

Related Node
div.text-area > div#acc7875480 > div.card > div#h51ba81607e083cc1ccc1ff33f1cdd590
div.col-lg-9 > div.text-area > div#acc7875480 > div.card

div.card > div#h05d18603139781fe35c2fb8ff930fc47 > span.panel-title > a.collapsed Fix any of the following:
Element has insufficient color contrast of 2.92 (foreground color: #28a745, background color: #f7f7f7, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

Related Node
div.text-area > div#acc7875480 > div.card > div#h05d18603139781fe35c2fb8ff930fc47
div.col-lg-9 > div.text-area > div#acc7875480 > div.card

div.card > div#h4abf40649884079fd5e50e2b87971ed0 > span.panel-title > a.collapsed Fix any of the following:
Element has insufficient color contrast of 2.92 (foreground color: #28a745, background color: #f7f7f7, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

Related Node
div.text-area > div#acc7875480 > div.card > div#h4abf40649884079fd5e50e2b87971ed0
div.col-lg-9 > div.text-area > div#acc7875480 > div.card

div.card > div#hdfc25cfecc8a7f62148838728c21f438 > span.panel-title > a.collapsed Fix any of the following:
Element has insufficient color contrast of 2.92 (foreground color: #28a745, background color: #f7f7f7, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

Related Node
div.text-area > div#acc7875480 > div.card > div#hdfc25cfecc8a7f62148838728c21f438
div.col-lg-9 > div.text-area > div#acc7875480 > div.card

div.row > div.col-xs-12 > p > a Fix any of the following:
Element has insufficient color contrast of 3.13 (foreground color: #28a745, background color: #ffffff, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

Related Node
body > div.container > div.bg-white

Related Node
body > div.container > div.bg-white

Related Node
body > div.container > div.bg-white

Related Node
body > div.container > div.bg-white

div.well > p > strong > a Fix any of the following:
Element has insufficient color contrast of 3.13 (foreground color: #28a745, background color: #ffffff, font size: 12.0pt (16px), font weight: bold). Expected contrast ratio of 4.5:1

Related Node
body > div.container > div.bg-white

div.well > ul > li > a Fix any of the following:
Element has insufficient color contrast of 2.63 (foreground color: #28a745, background color: #c9f7c9, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

Related Node
div.row > div.col-lg-9 > div.text-area > div.well

Related Node
div.row > div.col-lg-9 > div.text-area > div.well

Related Node
body > div.container > div.bg-white

Related Node
body > div.container > div.bg-white

Related Node
body > div.container > div.bg-white

Related Node
body > div.container > div.bg-white

div > ul.nav > li > a.nav-link Fix any of the following:
Element has insufficient color contrast of 3.68 (foreground color: #6c757d, background color: #e4e4e4, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

div > ul.nav > li > a.nav-link Fix any of the following:
Element has insufficient color contrast of 3.13 (foreground color: #ffffff, background color: #28a745, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

Related Node
body > div.container > div.bg-white

div.card > div#hb5ea5a14509e2ec43cd474a94fd412ff > span.panel-title > a.collapsed Fix any of the following:
Element has insufficient color contrast of 2.92 (foreground color: #28a745, background color: #f7f7f7, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

Related Node
div.text-area > div#acc3977022 > div.card > div#hb5ea5a14509e2ec43cd474a94fd412ff
div.col-lg-9 > div.text-area > div#acc3977022 > div.card

div.card > div#h093370edddc755eefd92aa3fb8fd5831 > span.panel-title > a.collapsed Fix any of the following:
Element has insufficient color contrast of 2.92 (foreground color: #28a745, background color: #f7f7f7, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

Related Node
div.text-area > div#acc3977022 > div.card > div#h093370edddc755eefd92aa3fb8fd5831
div.col-lg-9 > div.text-area > div#acc3977022 > div.card

div.card > div#he7436347688ba78fc5e8c1797e77915a > span.panel-title > a.collapsed Fix any of the following:
Element has insufficient color contrast of 2.92 (foreground color: #28a745, background color: #f7f7f7, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

Related Node
div.text-area > div#acc3977022 > div.card > div#he7436347688ba78fc5e8c1797e77915a
div.col-lg-9 > div.text-area > div#acc3977022 > div.card

footer.bg-white > div.row > div.col-sm > a.nav-link Fix any of the following:
Element has insufficient color contrast of 3.13 (foreground color: #28a745, background color: #ffffff, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

Related Node
body > div.container > footer.bg-white

Names and labels (2)

Links do not have a discernible name

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Failing Elements

body > div.container > nav.navbar > a.navbar-brand Fix all of the following:
Element is in tab order and does not have accessible text

Fix any of the following:
Element does not have text that is visible to screen readers
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute

Select elements do not have associated label elements.

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.

Failing Elements

div.card-body > div.form-group > div.col-sm-10 > select#activity Fix any of the following:
Form element does not have an implicit (wrapped) <label>
Form element does not have an explicit <label>
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
Element's default semantics were not overridden with role="none" or role="presentation"

ARIA (1)

[aria-*] attributes do not match their roles

Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.

Failing Elements
div.row > div.col-lg-9 > div.text-area > div#acc7875480 Fix all of the following: ARIA attribute is not allowed: aria-multiselectable="true"
div.row > div.col-lg-9 > div.text-area > div#acc3977022 Fix all of the following: ARIA attribute is not allowed: aria-multiselectable="true"

Additional Items to Check Manually (10)

Interactive controls are keyboard focusable

Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state

Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order

Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order

DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region

A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page

If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation

Landmark elements (`<main>`, `<nav>`, etc.) are used to improve the keyboard navigation of the page for assistive technology.
Offscreen content is hidden from assistive technology

Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels

Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles

Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.

Passed Audits (24)

Values assigned to role="" are valid ARIA roles.

ARIA roles enable assistive technologies to know the role of each element on the web page. If the role values are misspelled, not existing ARIA role values, or abstract roles, then the purpose of the element will not be communicated to users of assistive technologies. Learn more about ARIA roles.
[aria-hidden="true"] is not present on the document <body>

Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes

Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
[role] values are valid

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
[aria-*] attributes have valid values

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Document has a <title> element

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
[id] attributes on active, focusable elements are unique

All focusable elements must have a unique id to ensure that they're visible to assistive technologies. Learn how to fix duplicate ids.
<frame> or <iframe> elements have a title

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Heading elements appear in a sequentially-descending order

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
<html> element has a [lang] attribute

If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute

Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Image elements have [alt] attributes

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Image elements do not have [alt] attributes that are redundant text.

Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Input buttons have discernible text.

Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
Form elements have associated labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Links are distinguishable without relying on color.

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Lists contain only <li> elements and script supporting elements (<script> and <template>).

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements

Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Tables have different content in the summary attribute and <caption>.

The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.

Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.

Not Applicable (26)

[accesskey] values are unique

Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
button, link, and menuitem elements have accessible names

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
Elements with role="dialog" or role="alertdialog" have accessible names.

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
[aria-hidden="true"] elements do not contain focusable descendents

Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
ARIA input fields have accessible names

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names

When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names

When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with the role=text attribute do not have focusable descendents.

Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names

When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names

When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names

When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
Buttons have an accessible name

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
The page contains a heading, skip link, or landmark region

Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements

Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
ARIA IDs are unique

The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels

Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.

If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<input type="image"> elements have [alt] text

When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">

Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text

Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Skip links are focusable.

Including a skip link can help users skip to the main content to save time. Learn more about skip links.
No element has a [tabindex] value greater than 0

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.

Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
[lang] attributes have a valid value

Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
<video> elements contain a <track> element with [kind="captions"]

When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.

Best Practices 74

Trust and Safety (1)

Ensure CSP is effective against XSS attacks

A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS

Description	Directive	Severity
No CSP found in enforcement mode		High

General (4)

Detected JavaScript libraries

All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.

Name	Version
Bootstrap	4.1.1
jQuery	3.3.1
core-js	core-js-global@3.6.1; core-js-global@3.10.2

Uses third-party cookies

1 cookie found

Support for third-party cookies will be removed in a future version of Chrome. Learn more about phasing out third-party cookies.

Name	URL
test_cookie	https://td.doubleclick.net/td/ga/rul?tid=G-WPRXLZTDXY&gacid=548955045.1731117217&gtm=45je4b70v883264746z89117919079za200zb9117919079&dma=0&gcd=13l3l3l3l1l1&npa=0&pscdl=noapi&aip=1&fledge=1&frm=0&tag_exp=101823848~101925629&z=1553344338

Browser errors were logged to the console

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Source	Description
URL: https://gdpr-tcfv2.sp-prod.net/wrapperMessagingWithoutDetection.js Line: 0 Column: 190083	ERROR in messagingWithoutDetection: RequestError: Server request error: 0 () at XMLHttpRequest.<anonymous> (https://gdpr-tcfv2.sp-prod.net/wrapperMessagingWithoutDetection.js:1:196104)
URL: https://consent.kalorienbedarf.de/mms/v2/get_site_data?hasCsp=true&href=https%3A%2F%2Fwww.kalorienbedarf.de%2F&account_id=1061 Line: 0 Column: 0	Failed to load resource: net::ERR_NAME_NOT_RESOLVED

Issues were logged in the Issues panel in Chrome Devtools

Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Issue type

URL
https://td.doubleclick.net/td/ga/rul?tid=G-WPRXLZTDXY&gacid=548955045.1731117217&gtm=45je4b70v883264746z89117919079za200zb9117919079&dma=0&gcd=13l3l3l3l1l1&npa=0&pscdl=noapi&aip=1&fledge=1&frm=0&tag_exp=101823848~101925629&z=1553344338

Passed Audits (11)

Uses HTTPS

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Avoids requesting the geolocation permission on page load

Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Allows users to paste into input fields

Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Displays images with correct aspect ratio

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Page has the HTML doctype

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset

A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
Avoids unload event listeners

The unload event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use pagehide or visibilitychange events instead. Learn more about unload event listeners
Avoids deprecated APIs

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Page has valid source maps

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

URL

Map URL

https://www.kalorienbedarf.de/assets/js/bootstrap.min.js

https://www.kalorienbedarf.de/assets/js/bootstrap.min.js.map

Error
Error: Failed fetching source map (500)

Not Applicable (1)

Fonts with font-display: optional are preloaded

Preload optional fonts so first-time visitors may use them. Learn more about preloading fonts

SEO 100

Additional Items to Check Manually (1)

Structured data is valid

Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.

Passed Audits (12)

Has a <meta name="viewport"> tag with width or initial-scale

A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Document has a <title> element

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code

Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links have descriptive text

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Links are crawlable

Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Page isn’t blocked from indexing

Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
robots.txt is valid

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Image elements have [alt] attributes

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Document has a valid hreflang

hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical

Canonical links suggest which URL to show in search results. Learn more about canonical links.
Document avoids plugins

Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more about avoiding plugins.

Not Applicable (2)

Document uses legible font sizes

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
Tap targets are sized appropriately

Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.

PWA 43

Installable (1)

Web app manifest or service worker do not meet the installability requirements

2 reasons

Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more about manifest installability requirements.

Failure reason
Manifest start URL is not valid
Manifest does not contain a `name` or `short_name` field

PWA Optimized (5)

Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more about splash screens.

Failures:
- Manifest does not have name
Sets a theme color for the address bar.

The browser address bar can be themed to match your site. Learn more about theming the address bar.
Content is sized correctly for the viewport

If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn how to size content for the viewport.
Has a <meta name="viewport"> tag with width or initial-scale

A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Manifest doesn't have a maskable icon

A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn about maskable manifest icons.

Additional Items to Check Manually (3)

Site works cross-browser

To reach the most number of users, sites should work across every major browser. Learn about cross-browser compatibility.
Page transitions don't feel like they block on the network

Transitions should feel snappy as you tap around, even on a slow network. This experience is key to a user's perception of performance. Learn more about page transitions.
Each page has a URL

Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on social media. Learn more about providing deep links.