- URL: https://newworkhub.de
- Date: 08/10/24 17:23:34
Webpage Performance Test Result
- Settings: Desktop
v127
Cable
Frankfurt, GermanyMore
- Test runs: 1
- Connectivity: 5000/1000 Kbps, 28ms Latency
- Custom Metrics
View:
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 98
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 |
|---|---|---|---|---|---|
| 0.7s | 0.9s | 1.0s | 0.8s | 10ms | 0 |
Aiming to improve? check out our Opportunities & Experiments for suggestions and run No-Code Experiments to see how changes impact this site!
Filmstrip
Opportunities (3)
-
Initial server response time was short
Root document took 70 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://newworkhub.de/ 70 Properly size images
Potential savings of 13 KiB
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://newworkhub.de/media/site/c7b4868344-1660042750/logo_nwh_white.png 13219 13182 Serve images in next-gen formats
Potential savings of 59 KiB
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://newworkhub.de/media/pages/home/d13ccc796a-1720168638/nwh-stellt-sich-vor.jpg 220650 60540 Diagnostics (10)
-
Avoid chaining critical requests
5 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.
-
https://newworkhub.de/
5kb
-
https://newworkhub.de/assets/css/style.css?1720170564
6kb
- https://newworkhub.de/assets/css/fonts/roboto-v30-latin-regular.woff2 16kb
- https://newworkhub.de/assets/css/fonts/roboto-v30-latin-900.woff2 16kb
- https://newworkhub.de/assets/css/fonts/roboto-v30-latin-500.woff2 16kb
- https://newworkhub.de/assets/css/fonts/roboto-v30-latin-700.woff2 16kb
- https://newworkhub.de/media/plugins/michnhokn/cookie-banner/cookie-modal.css 1kb
-
https://newworkhub.de/assets/css/style.css?1720170564
6kb
Ensure text remains visible during webfont load
View Experiment!Leverage the
font-displayCSS feature to ensure text is user-visible while webfonts are loading. Learn more aboutfont-display.URL Potential Savings https://newworkhub.de/assets/css/fonts/roboto-v30-latin-regular.woff2 105 https://newworkhub.de/assets/css/fonts/roboto-v30-latin-900.woff2 112 https://newworkhub.de/assets/css/fonts/roboto-v30-latin-500.woff2 115 https://newworkhub.de/assets/css/fonts/roboto-v30-latin-700.woff2 68 Largest Contentful Paint element
1,010 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 331 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://newworkhub.de/media/pages/home/d13ccc796a-1720168638/nwh-stellt-sich-vor.jpg 221116 https://newworkhub.de/assets/css/fonts/roboto-v30-latin-500.woff2 16159 https://newworkhub.de/assets/css/fonts/roboto-v30-latin-700.woff2 16099 https://newworkhub.de/assets/css/fonts/roboto-v30-latin-900.woff2 15991 https://newworkhub.de/assets/css/fonts/roboto-v30-latin-regular.woff2 15983 https://newworkhub.de/assets/img/favicon/favicon.ico?230506 15334 https://newworkhub.de/media/site/c7b4868344-1660042750/logo_nwh_white.png 13457 https://newworkhub.de/media/pages/home/169fa71aeb-1720170211/nwh-referenzen.png 7014 https://newworkhub.de/assets/css/style.css?1720170564 6570 https://newworkhub.de/ 4615 Avoid long main-thread tasks
3 long tasks 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://newworkhub.de/ 309 198 https://newworkhub.de/stats/js/script.tagged-events.outbound-links.js 579 160 https://newworkhub.de/ 760 54 JavaScript execution time
0.0 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://newworkhub.de/ 431 9 1 Unattributable 142 2 0 Minimizes main-thread work
0.6 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 Style & Layout 331 Other 220 Script Evaluation 38 Parse HTML & CSS 15 Rendering 9 Script Parsing & Compilation 2 Avoids an excessive DOM size
176 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 label.cookie-modal__option > span.cookie-modal__check > svg > path Maximum Child Elements body.home Avoid large layout shifts
4 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 nav > div.navigation-container > ul > li 0 nav > div.navigation-container > ul > li 0 nav > div.navigation-container > ul > li 0 nav > div.navigation-container > ul > li 0 Image elements do not have explicit
View Experiment!widthandheightSet an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
URL https://newworkhub.de/media/site/c7b4868344-1660042750/logo_nwh_white.png https://newworkhub.de/media/pages/home/169fa71aeb-1720170211/nwh-referenzen.png Passed Audits (26)
-
Eliminate render-blocking resources
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.
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Preconnect to required origins
Consider adding
preconnectordns-prefetchresource 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.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.
Reduce unused CSS
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.
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.
Reduce unused JavaScript
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
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.
Element body.home > section.container Minimize third-party usage
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.
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.
Avoid serving legacy JavaScript to modern browsers
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
Has a
<meta name="viewport">tag withwidthorinitial-scaleA
<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.
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Use HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more about HTTP/2.
Uses efficient cache policy on static assets
0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
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
passiveto 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().Page didn't prevent back/forward cache restoration
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
Accessibility 94
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.navigation-container > ul > li > a Fix any of the following:
Element has insufficient color contrast of 4 (foreground color: #ffffff, background color: #f2295b, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1Related Node body.home > div.container div.navigation-container > ul > li > a Fix any of the following:
Element has insufficient color contrast of 4 (foreground color: #ffffff, background color: #f2295b, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1Related Node body.home > div.container div.navigation-container > ul > li > a Fix any of the following:
Element has insufficient color contrast of 4 (foreground color: #ffffff, background color: #f2295b, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1Related Node body.home > div.container div.navigation-container > ul > li > a Fix any of the following:
Element has insufficient color contrast of 4 (foreground color: #ffffff, background color: #f2295b, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1Related Node body.home > div.container div.wrapper > div.column > div.blocks > p Fix any of the following:
Element has insufficient color contrast of 4 (foreground color: #ffffff, background color: #f2295b, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1Related Node body.home > section.container div.wrapper > div.column > div.blocks > p Fix any of the following:
Element has insufficient color contrast of 4 (foreground color: #ffffff, background color: #f2295b, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1Related Node body.home > section.container div.wrapper > div.column > div.blocks > p Fix any of the following:
Element has insufficient color contrast of 4 (foreground color: #ffffff, background color: #f2295b, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1Related Node section#home-was > div.wrapper > div.column > div.blocks div.column > div.blocks > p > a Fix any of the following:
Element has insufficient color contrast of 4 (foreground color: #ffffff, background color: #f2295b, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1Related Node section#home-was > div.wrapper > div.column > div.blocks div.column > div.blocks > p > a Fix any of the following:
Element has insufficient color contrast of 4 (foreground color: #ffffff, background color: #f2295b, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1Related Node section#home-was > div.wrapper > div.column > div.blocks div.wrapper > div.column > div.blocks > p Fix any of the following:
Element has insufficient color contrast of 4 (foreground color: #ffffff, background color: #f2295b, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1Related Node section#home-was > div.wrapper > div.column > div.blocks div.column > div.blocks > p > a Fix any of the following:
Element has insufficient color contrast of 4 (foreground color: #ffffff, background color: #f2295b, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1Related Node section#home-was > div.wrapper > div.column > div.blocks div.column > div.blocks > p > a Fix any of the following:
Element has insufficient color contrast of 4 (foreground color: #ffffff, background color: #f2295b, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1Related Node section#home-was > div.wrapper > div.column > div.blocks div.column > div.blocks > div.cookie-error > p Fix any of the following:
Element has insufficient color contrast of 4 (foreground color: #ffffff, background color: #f2295b, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1Related Node div.wrapper > div.column > div.blocks > div.cookie-error div.column > div.blocks > div.cookie-error > button Fix any of the following:
Element has insufficient color contrast of 3 (foreground color: #ffffff, background color: #009ee3, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1div.column > div.blocks > div.cookie-error > p Fix any of the following:
Element has insufficient color contrast of 4 (foreground color: #ffffff, background color: #f2295b, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1Related Node div.wrapper > div.column > div.blocks > div.cookie-error div.blocks > div.cookie-error > p > a Fix any of the following:
Element has insufficient color contrast of 4 (foreground color: #ffffff, background color: #f2295b, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1Related Node div.wrapper > div.column > div.blocks > div.cookie-error div.cookie-modal__content > div.cookie-modal__buttons > a#cookie-accept > span Fix any of the following:
Element has insufficient color contrast of 4 (foreground color: #ffffff, background color: #f2295b, font size: 11.3pt (15.0038px), font weight: normal). Expected contrast ratio of 4.5:1Related Node div#cookie-modal > div.cookie-modal__content > div.cookie-modal__buttons > a#cookie-accept div.cookie-modal__content > div.cookie-modal__buttons > a#cookie-deny > span Fix any of the following:
Element has insufficient color contrast of 1.78 (foreground color: #c2c2c2, background color: #ffffff, font size: 11.3pt (15.0038px), font weight: normal). Expected contrast ratio of 4.5:1Related Node div#cookie-modal > div.cookie-modal__content > div.cookie-modal__buttons > a#cookie-deny 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 (15)
-
[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 howaria-hiddenaffects the document body.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.
Document has a
<title>elementThe 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 uniqueAll focusable elements must have a unique
idto ensure that they're visible to assistive technologies. Learn how to fix duplicateids.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]attributeIf a page doesn't specify a
langattribute, 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 thelangattribute.<html>element has a valid value for its[lang]attributeSpecifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the
langattribute.Image elements have
[alt]attributesInformative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the
altattribute.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
altattribute.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.
Links 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.
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 elementsScreen 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.
Not Applicable (38)
-
[accesskey]values are uniqueAccess keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
[aria-*]attributes match their rolesEach ARIA
rolesupports a specific subset ofaria-*attributes. Mismatching these invalidates thearia-*attributes. Learn how to match ARIA attributes to their roles.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 therolevalues are misspelled, not existing ARIArolevalues, or abstract roles, then the purpose of the element will not be communicated to users of assistive technologies. Learn more about ARIA roles.button,link, andmenuitemelements have accessible namesWhen 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"orrole="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 descendentsFocusable descendents within an
[aria-hidden="true"]element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn howaria-hiddenaffects 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
meterelements have accessible namesWhen 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
meterelements.ARIA
progressbarelements have accessible namesWhen a
progressbarelement 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 labelprogressbarelements.[role]s have all required[aria-*]attributesSome 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 elementSome 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.
-
-
https://newworkhub.de/
5kb