| Avoid slowing down the critical rendering path (avoidRenderBlocking) | The page has 1 blocking requests and 0 in body parser blocking (0 JavaScript and 1 CSS). There are 1 potentially render blocking requests. You need to verify if it is render blocking: https://www.scottish-enterprise.com/assets/js/main.js?v=1.106.0.0 | 99 |
| 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.scottish-enterprise.com/assets/css/styles.css?v=1.106.0.0 |
| Avoid using Google Tag Manager. (googleTagManager) | The page is using Google Tag Manager, this is a performance risk since non-tech users can add JavaScript to your page. | 0 |
| Description: Google Tag Manager makes it possible for non tech users to add scripts to your page that will downgrade performance. |
| Inline CSS for faster first render (inlineCss) | The page loads 1 CSS request inside of head, try to inline the CSS for the first render and lazy load the rest. | 90 |
| 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: https://www.scottish-enterprise.com/assets/css/styles.css?v=1.106.0.0 |
| Have a fast largest contentful paint (largestContentfulPaint) | You can add importance="high" to the image to increase the load priority that is rolling out soon in Chrome. | 95 |
| Description: Largest contentful paint is one of Google Web Vitals and reports the render time of the largest image or text block visible within the viewport, relative to when the page first started loading. To be fast according to Google, it needs to render before 2.5 seconds and results over 4 seconds is poor performance. |
| Avoid CPU Long Tasks (longTasks) | The page has 3 CPU long tasks with the total of 457 ms. The total blocking time is 165 ms and 1 long task before first contentful paint with total time of 192 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 14 redirects. 14 of the redirects are from the base domain, please fix them! | 0 |
| 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.scottish-enterprise.com/media/4077/carcinotech-compressed-hero4.jpg...pressed-hero4.jpg https://www.scottish-enterprise.com/media/4316/working-from-home.jpg?quality=100 https://www.scottish-enterprise.com/media/3872/taking-notes-beside-laptop-458x240.jpg?quality=100 https://www.scottish-enterprise.com/media/3809/woman-using-mobile-phone-458x245jpg.jpg?quality=100 https://www.scottish-enterprise.com/media/2621/icon-home-brexit.png?quality=100 https://www.scottish-enterprise.com/media/2620/icon-home-advice.png?quality=100 https://www.scottish-enterprise.com/media/2622/icon-home-develop.png?quality=100 https://www.scottish-enterprise.com/media/2624/icon-home-funding.png?quality=100 https://www.scottish-enterprise.com/media/2623/icon-home-export.png?quality=100 https://www.scottish-enterprise.com/media/2625/icon-home-skills.png?quality=100 https://www.scottish-enterprise.com/media/3355/icon-email.png?quality=100 https://www.scottish-enterprise.com/media/4106/wwd-card.jpg?quality=100 https://www.scottish-enterprise.com/media/4105/mc-card.jpg?quality=100 https://www.scottish-enterprise.com/media/4104/op-card.jpg?quality=100 |
| Avoid extra requests by setting cache headers (cacheHeaders) | The page has 5 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 5.6 kB the next access. | 50 |
| 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.youtube.com/iframe_api https://lo.v.liveperson.net/api/js/31817781...t/api/js/31817781 https://lo.v.liveperson.net/api/js/31817781...t/api/js/31817781 https://lo.v.liveperson.net/api/js/31817781...t/api/js/31817781 https://lo.v.liveperson.net/api/js/31817781...t/api/js/31817781 |
| Long cache headers is good (cacheHeadersLong) | The page has 7 requests that have a shorter cache time than 30 days (but still a cache time). | 93 |
| 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: https://www.googletagmanager.com/gtm.js?id=GTM-TD3K4KZ https://fonts.googleapis.com/css?family=Roboto%7CPoppins:300,400,500,600,700 https://lptag.liveperson.net/tag/tag.js?site=31817781 https://lptag.liveperson.net/lptag/api/account/31817781/configuration/applicatio...ns/taglets/.jsonp https://www.googletagmanager.com/gtag/js?id=G-8LHNSPWCG8&l=dataLayer&cx=c https://accdn.lpsnmedia.net/api/account/31817781/configuration/le-campaigns/camp...65450/revision/76 https://accdn.lpsnmedia.net/api/account/31817781/configuration/engagement-window...-confs/4472783150 |
| Always compress text content (compressAssets) | The page has 1 request that are served uncompressed. You could save a lot of bytes by sending them compressed instead. | 90 |
| Description: In the early days of the Internet there were browsers that didn't support compressing (gzipping) text content. They do now. Make sure you compress HTML, JSON, JavaScript, CSS and SVG. It will save bytes for the user; making the page load faster and use less bandwith. |
| Offenders: |
| Avoid too many fonts (fewFonts) | The page has 4 font requests. Do you really need them? What value does the fonts give the user? | 60 |
| 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://fonts.gstatic.com/s/poppins/v20/pxiByp8kv8JHgFVrLEj6Z1xlFQ.woff2 https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxK.woff2 https://fonts.gstatic.com/s/poppins/v20/pxiByp8kv8JHgFVrLGT9Z1xlFQ.woff2 https://fonts.gstatic.com/s/poppins/v20/pxiEyp8kv8JHgFVrJJfecg.woff2 |
| Total JavaScript size shouldn't be too big (javascriptSize) | The total JavaScript transfer size is 441 kB and the uncompressed size is 1.2 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? |
| Offenders: |
| Make each CSS response small (optimalCssSize) | https://www.scottish-enterprise.com/assets/css/styles.css?v=1.106.0.0 size is 37.6 kB (37603) 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: |
| Don't use private headers on static content (privateAssets) | The page has 6 requests with private headers. The main page has a private header. It could be right in some cases where the user can be logged in and served specific content. But if your asset is static it should never be private. Make sure that the assets really should be private and only used by one user. Otherwise, make it cacheable for everyone. | 50 |
| 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: https://www.scottish-enterprise.com/ https://www.googletagmanager.com/gtm.js?id=GTM-TD3K4KZ https://fonts.googleapis.com/css?family=Roboto%7CPoppins:300,400,500,600,700 https://www.google-analytics.com/gtm/optimize.js?id=GTM-WCCHR3X https://www.googletagmanager.com/gtag/js?id=G-8LHNSPWCG8&l=dataLayer&cx=c https://www.youtube.com/iframe_api |
0 s
0.9 sFirst Visual Change 900 ms
1 sLayout Shift 0.00092 922 ms
1.1 s
1.2 s
1.3 sLayout Shift 0.04889 1.286 s
1.4 sVisual Complete 85% 1.400 sVisual Complete 95% 1.400 sVisual Complete 99% 1.400 s
1.5 sCPU Long Task duration 69 ms
6.4 sFully Loaded 6.319 sLast Visual Change 6.333 s
