| Avoid slowing down the critical rendering path (avoidRenderBlocking) | The page has 2 blocking requests and 7 in body parser blocking (9 JavaScript and 0 CSS). There are 1 potentially render blocking requests. You need to verify if it is render blocking: https://www.chronobalance.de/wp-content/plugins/wp-rocket/assets/js/lazyload/17.5/lazyload.min.js | 9 |
| Description: The critical rendering path is what the browser needs to do to start rendering the page. Every file requested inside of the head element will postpone the rendering of the page, because the browser need to do the request. Avoid loading JavaScript synchronously inside of the head (you should not need JavaScript to render the page), request files from the same domain as the main document (to avoid DNS lookups) and inline CSS for really fast rendering and a short rendering path. |
| Offenders: https://www.chronobalance.de/wp-includes/js/jquery/jquery.min.js?ver=3.6.0 https://www.chronobalance.de/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.3.2 https://www.chronobalance.de/wp-content/plugins/woocommerce/assets/js/jquery-blo...ry.blockUI.min.js https://www.chronobalance.de/wp-content/plugins/b2b-wholesale-suite/includes/ass...dataTables.min.js https://www.chronobalance.de/wp-content/themes/Divi/js/scripts.min.js?ver=4.17.3 https://www.chronobalance.de/wp-content/cache/min/1/wp-content/themes/Divi/inclu...jquery.fitvids.js https://www.chronobalance.de/wp-content/cache/min/1/wp-content/themes/Divi/inclu.../jquery.mobile.js https://www.chronobalance.de/wp-content/plugins/woocommerce/assets/js/zoom/jquer...query.zoom.min.js https://www.chronobalance.de/wp-content/plugins/woocommerce/assets/js/flexslider...flexslider.min.js |
| Don't scale images in the browser (avoidScalingImages) | The page has 7 images that are scaled more than 100 pixels. It would be better if those images are sent so the browser don't need to scale them. | 30 |
| Description: It's easy to scale images in the browser and make sure they look good in different devices, however that is bad for performance! Scaling images in the browser takes extra CPU time and will hurt performance on mobile. And the user will download extra kilobytes (sometimes megabytes) of data that could be avoided. Don't do that, make sure you create multiple version of the same image server-side and serve the appropriate one. |
| Offenders: https://www.chronobalance.de/wp-content/uploads/2021/03/CB_Logo.svg https://www.chronobalance.de/wp-content/uploads/2021/04/Hundefutter.jpg https://www.chronobalance.de/wp-content/uploads/2021/04/Nahrungsergaenzung.jpg https://www.chronobalance.de/wp-content/uploads/2021/04/Hundesnacks.jpg https://www.chronobalance.de/wp-content/uploads/2021/04/Hundepflege.jpg data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%201920%201074'%3E%3C/svg%3Edata:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%20150%2033'%3E%3C/svg%3E |
| Inline CSS for faster first render (inlineCss) | The page has both inline CSS and CSS requests even though it uses a HTTP/2-ish connection. If you have many users on slow connections, it can be better to only inline the CSS. Run your own tests and check the waterfall graph to see what happens. | 95 |
| Description: In the early days of the Internet, inlining CSS was one of the ugliest things you can do. That has changed if you want your page to start rendering fast for your user. Always inline the critical CSS when you use HTTP/1 and HTTP/2 (avoid doing CSS requests that block rendering) and lazy load and cache the rest of the CSS. It is a little more complicated when using HTTP/2. Does your server support HTTP push? Then maybe that can help. Do you have a lot of users on a slow connection and are serving large chunks of HTML? Then it could be better to use the inline technique, becasue some servers always prioritize HTML content over CSS so the user needs to download the HTML first, before the CSS is downloaded. |
| Avoid CPU Long Tasks (longTasks) | The page has 3 CPU long tasks with the total of 253 ms. The total blocking time is 103 ms . However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. Use Geckoprofiler for Firefox or Chromes tracelog to debug your long tasks. | 40 |
| Description: Long CPU tasks locks the thread. To the user this is commonly visible as a "locked up" page where the browser is unable to respond to user input; this is a major source of bad user experience on the web today. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. To debug you should use the Chrome timeline log and drag/drop it into devtools or use Firefox Geckoprofiler. |
| Offenders: unknownselfself |
| Avoid doing redirects (assetsRedirects) | The page has 1 redirect. 1 of the redirects are from the base domain, please fix them! | 90 |
| Description: A redirect is one extra step for the user to download the asset. Avoid that if you want to be fast. Redirects are even more of a showstopper on mobile. |
| Offenders: https://www.chronobalance.de/favicon.ico |
| Avoid extra requests by setting cache headers (cacheHeaders) | The page has 34 requests that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 1.5 MB the next access. | 0 |
| Description: The easiest way to make your page fast is to avoid doing requests to the server. Setting a cache header on your server response will tell the browser that it doesn't need to download the asset again during the configured cache time! Always try to set a cache time if the content doesn't change for every request. |
| Offenders: https://www.chronobalance.de/wp-content/cache/min/1/26c3fdc92cb91c06165d18b6f2901aff.css https://www.chronobalance.de/wp-content/cache/borlabs-cookie/borlabs-cookie_1_de.css?ver=2.2.53-59 https://www.chronobalance.de/wp-includes/js/jquery/jquery.min.js?ver=3.6.0 https://www.chronobalance.de/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.3.2 https://www.chronobalance.de/wp-content/plugins/woocommerce/assets/js/jquery-blo...ry.blockUI.min.js https://www.chronobalance.de/wp-content/plugins/b2b-wholesale-suite/includes/ass...dataTables.min.js https://www.chronobalance.de/wp-content/themes/Divi/js/scripts.min.js?ver=4.17.3 https://www.chronobalance.de/wp-content/cache/min/1/wp-content/themes/Divi/inclu...jquery.fitvids.js https://www.chronobalance.de/wp-content/cache/min/1/wp-content/themes/Divi/inclu.../jquery.mobile.js https://www.chronobalance.de/wp-content/plugins/woocommerce/assets/js/zoom/jquer...query.zoom.min.js https://www.chronobalance.de/wp-content/plugins/woocommerce/assets/js/flexslider...flexslider.min.js https://www.chronobalance.de/wp-content/plugins/ewww-image-optimizer/includes/la.../lazysizes.min.js https://www.chronobalance.de/wp-content/plugins/wp-rocket/assets/js/lazyload/17.5/lazyload.min.js https://www.chronobalance.de/wp-content/uploads/2021/03/local-phone-material@3x.png https://www.chronobalance.de/wp-content/uploads/2021/03/user-login-icon-14.png https://www.chronobalance.de/wp-content/uploads/2021/03/ChronoBalance_Icons_Hunde_Icon_V4.svg https://www.chronobalance.de/wp-content/uploads/2021/03/ChronoBalance_Icons_Katzen_Icon_V4.svg https://www.chronobalance.de/wp-content/uploads/sgf-css/6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2 https://www.chronobalance.de/wp-content/themes/Divi/core/admin/fonts/modules/all/modules.ttf https://www.chronobalance.de/wp-content/uploads/sgf-css/6xKydSBYKcSV-LCoeQqfX1RY...wlxdu3cOWxw.woff2 https://www.chronobalance.de/wp-content/uploads/2022/04/ChronoBalance-FrischesTr...l-verkleinert.jpg https://www.chronobalance.de/wp-content/uploads/sgf-css/1Ptpg8LJRfWJmhDAuUsw9qR_AtCb71ka4Q.woff2 https://www.chronobalance.de/wp-content/uploads/sgf-css/6xKydSBYKcSV-LCoeQqfX1RY...wlxdu3cOWxw.woff2 https://www.chronobalance.de/wp-content/uploads/sgf-css/1Ptsg8LJRfWJmhDAuUs4TYFqL_KWxQ.woff2 https://www.chronobalance.de/wp-content/uploads/sgf-css/6xK1dSBYKcSV-LCoeQqfX1RY...Z7nsDJB9cme.woff2 https://www.chronobalance.de/wp-content/uploads/2021/03/local-phone-red.png https://www.chronobalance.de/wp-content/uploads/2022/05/bactofacto-desktop-slider.jpg https://www.chronobalance.de/wp-content/uploads/2021/03/CB_Logo.svg https://www.chronobalance.de/wp-content/uploads/2021/04/Hundefutter.jpg https://www.chronobalance.de/wp-content/uploads/2021/04/Nahrungsergaenzung.jpg https://www.chronobalance.de/wp-content/uploads/2021/04/Hundesnacks.jpg https://www.chronobalance.de/wp-content/uploads/2021/04/Hundepflege.jpg https://www.chronobalance.de/favicon.ico https://www.chronobalance.de/wp-content/uploads/2020/07/cb_favicon_50x50px.jpg |
| Total CSS size shouldn't be too big (cssSize) | The total CSS transfer size is 86.7 kB and uncompressed size is 854 kB. That is big and the CSS could most probably be smaller. | 50 |
| Description: Delivering a massive amount of CSS to the browser is not the best thing you can do, because it means more work for the browser when parsing the CSS against the HTML and that makes the rendering slower. Try to send only the CSS that is used on that page. And make sure to remove CSS rules when they aren't used anymore. |
| Offenders: |
| Avoid too many fonts (fewFonts) | The page has 7 font requests. Do you really need them? What value does the fonts give the user? | 30 |
| Description: How many fonts do you need on a page for the user to get the message? Fonts can slow down the rendering of content, try to avoid loading too many of them because worst case it can make the text invisible until they are loaded (FOIT—flash of invisible text), best case they will flicker the text content when they arrive. |
| Offenders: https://www.chronobalance.de/wp-content/uploads/sgf-css/6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2 https://www.chronobalance.de/wp-content/themes/Divi/core/admin/fonts/modules/all/modules.ttf https://www.chronobalance.de/wp-content/uploads/sgf-css/6xKydSBYKcSV-LCoeQqfX1RY...wlxdu3cOWxw.woff2 https://www.chronobalance.de/wp-content/uploads/sgf-css/1Ptpg8LJRfWJmhDAuUsw9qR_AtCb71ka4Q.woff2 https://www.chronobalance.de/wp-content/uploads/sgf-css/6xKydSBYKcSV-LCoeQqfX1RY...wlxdu3cOWxw.woff2 https://www.chronobalance.de/wp-content/uploads/sgf-css/1Ptsg8LJRfWJmhDAuUs4TYFqL_KWxQ.woff2 https://www.chronobalance.de/wp-content/uploads/sgf-css/6xK1dSBYKcSV-LCoeQqfX1RY...Z7nsDJB9cme.woff2 |
| Total image size shouldn't be too big (imageSize) | The page total image size is 1.1 MB. It's really big. Is the page using the right format for the images? Can they be lazy loaded? Are they compressed as good as they can be? Make them smaller by using https://imageoptim.com/. | 50 |
| Description: Avoid having too many large images on the page. The images will not affect the first paint of the page, but it will eat bandwidth for the user. |
| Total JavaScript size shouldn't be too big (javascriptSize) | The total JavaScript transfer size is 141.6 kB and the uncompressed size is 524.8 kB. This is quite large. | 0 |
| Description: A lot of JavaScript often means you are downloading more than you need. How complex is the page and what can the user do on the page? Do you use multiple JavaScript frameworks? |
| Offenders: |
| Make each CSS response small (optimalCssSize) | https://www.chronobalance.de/wp-content/cache/min/1/26c3fdc92cb91c06165d18b6f2901aff.css size is 80.7 kB (80705) and that is bigger than the limit of 14.5 kB. Try to make the CSS files fit into 14.5 KB. | 90 |
| Description: Make CSS responses small to fit into the magic number TCP window size of 14.5 KB. The browser can then download the CSS faster and that will make the page start rendering earlier. |
| Offenders: |
0 s
0.3 sCPU Long Task duration 70 msFirst Contentful Paint 282 msFirst Visual Change 300 ms
0.4 sCPU Long Task duration 59 msLayout Shift 0.00073 373 ms
0.6 sLCP <DIV> 517 msVisual Complete 85% 533 msVisual Complete 95% 533 msVisual Complete 99% 533 ms
0.8 s
1.4 s
1.5 s
1.6 s
1.7 s
1.8 s
1.9 s
2 sLast Visual Change 1.933 s
