| Avoid slowing down the critical rendering path (fastRender) | The page has 23 render blocking CSS requests and 36 blocking JavaScript requests inside of head. | 0 |
| 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 or use server push for really fast rendering and a short rendering path. |
| Offenders: |
| Inline CSS for faster first render (inlineCss) | The page loads 23 CSS requests inside of head, try to inline the CSS for the first render and lazy load the rest. | 0 |
| 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. |
| Offenders: |
| Avoid CPU Long Tasks (longTasks) | The page has 9 CPU long tasks with the total of 854 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 Task. | 0 |
| 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. |
Offenders: - self
- self
- self
- self
- self
- self
- self
- self
- self
|
| Avoid Frontend single point of failures (spof) | The page has 42 requests inside of the head that can cause a SPOF (single point of failure). Load them asynchronously or move them outside of the document head. | 70 |
| Description: A page can be stopped from loading in the browser if a single JavaScript, CSS, and in some cases a font, couldn't be fetched or is loading really slowly (the white screen of death). That is a scenario you really want to avoid. Never load 3rd-party components synchronously inside of the head tag. |
| Offenders: |
| Always load third-party JavaScript asynchronously (thirdPartyAsyncJs) | The page has 1 synchronous 3rd-party JavaScript request. Change it to be asynchronous instead. | 90 |
| Description: Use JavaScript snippets that load the JS files asynchronously in order to speed up the user experience and avoid blocking the initial load. |
| Offenders: |
| Avoid extra requests by setting cache headers (cacheHeaders) | The page has 16 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 923.9 kB 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: |
| Long cache headers is good (cacheHeadersLong) | The page has 51 requests that have a shorter cache time than 30 days (but still a cache time). | 49 |
| Description: Setting a cache header is good. Setting a long cache header (at least 30 days) is even better beacause then it will stay long in the browser cache. But what do you do if that asset change? Rename it and the browser will pick up the new version. |
| Offenders: |
| Total CSS size shouldn't be too big (cssSize) | The total CSS transfer size is 219.1 kB and uncompressed size is 1.2 MB. That is big and the CSS could most probably be smaller. | 0 |
| 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. |
| Avoid too many fonts (fewFonts) | The page has 5 font requests. Do you really need them? What value does the fonts give the user? | 50 |
| 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: |
| Avoid too many requests per domain [HTTP/1] (fewRequestsPerDomain) | The page has 1 domain that serves more than 30 requests. static.aecdaily.com got 43 requests. Improve performance by sharding those or move to HTTP/2. | 90 |
| Description: Browsers have a limit on how many concurrent requests they can do per domain when using HTTP/1. When you hit the limit, the browser will wait before it can download more assets on that domain. So avoid having too many requests per domain. |
| Offenders: |
| Total image size shouldn't be too big (imageSize) | The page total image size is 874.5 kB. It's really big. Is the page using the right format for the images? 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 1.1 MB and the uncompressed size is 3.5 MB. This is totally crazy! There is really room for improvement here. | 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? |
| Avoid using incorrect mime types (mimeTypes) | The page has 3 misconfigured mime types. | 97 |
| Description: It's not a great idea to let browsers guess content types (content sniffing), in some cases it can actually be a security risk. |
| Offenders: |
| Make each CSS response small (optimalCssSize) | https://static.aecdaily.com/bootstrap/5.3.0-alpha3/bootstrap-5.3.0-alpha3-dist/css/bootstrap.min.css size is 31.3 kB (31259) and that is bigger than the limit of 14.5 kB. https://static.aecdaily.com/datatables/DataTables-2.0.2/datatables.min.css size is 15.8 kB (15783) and that is bigger than the limit of 14.5 kB. https://static.aecdaily.com/fontawesome_pkgs/fontawesome-pro-6.4.2-web/css/all.min.css size is 100.2 kB (100246) and that is bigger than the limit of 14.5 kB. https://static.aecdaily.com/ag-grid/styles/ag-grid.min.css size is 22.6 kB (22554) and that is bigger than the limit of 14.5 kB. Try to make the CSS files fit into 14.5 KB. | 60 |
| 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: |
| Total page size shouldn't be too big (pageSize) | The page total transfer size is 3.1 MB, which is more than the coach limit of 2 MB. That is really big and you need to make it smaller. | 0 |
| Description: Avoid having pages that have a transfer size over the wire of more than 2 MB (desktop) and 1 MB (mobile) because that is really big and will hurt performance and will make the page expensive for the user if she/he pays for the bandwidth. |
| Don't use private headers on static content (privateAssets) | The page has 1 request with private headers. Make sure that the assets really should be private and only used by one user. Otherwise, make it cacheable for everyone. | 90 |
| Description: If you set private headers on content, that means that the content are specific for that user. Static content should be able to be cached and used by everyone. Avoid setting the cache header to private. |
| Offenders: |
0 s
2.2 sLayout Shift 0.10148 2.148 sFirst Visual Change 2.167 s
2.3 sLayout Shift 0.00018 2.260 s
2.4 sCPU Long Task duration 52 msPage Load Time 2.384 s
2.5 sFully Loaded 2.435 sLCP <DIV> 2.436 sLast Visual Change 2.467 sVisual Complete 85% 2.467 sVisual Complete 95% 2.467 sVisual Complete 99% 2.467 sLargest Image 2.467 s
