| 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://scottish-enterprise.com/media/nohh5yhq/innovation-robotics-technology-at...m-edinburgh-2.jpg https://scottish-enterprise.com/media/xk0htgwd/speakers-and-attendees-at-pathway...tel_-uphall-1.jpg https://scottish-enterprise.com/media/pj3dj4jf/yzanne-turbett-and-angus-hayhow-o...ce-cream-farm.jpg https://scottish-enterprise.com/media/ihklo3pa/welder-at-star-renewables-thornli...ornliebank-og.jpg https://scottish-enterprise.com/media/ufgacakx/scottish-enterprise-ceo-adrian-gi...of-scotland-4.jpg https://scottish-enterprise.com/media/3tphu0w2/exhibitors-and-guests-in-the-inno...discovery-hub.jpg https://scottish-enterprise.com/media/z11hkz1a/images-taken-at-business-meeting-...um-image_m964.jpg |
| 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 3 CSS requests inside of head, try to inline the CSS for the first render and lazy load the rest. | 70 |
| 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://fonts.googleapis.com/css2...ogleapis.com/css2 https://use.typekit.net/edy3lpy.css https://scottish-enterprise.com/assets/styles/site.css?v=0.78.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 8 CPU long tasks with the total of 807 ms. The total blocking time is 303 ms and 3 long tasks before first contentful paint with total time of 254 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. | 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. To debug you should use the Chrome timeline log and drag/drop it into devtools or use Firefox Geckoprofiler. |
| Offenders: selfselfunknownselfselfselfselfself |
| Avoid Frontend single point of failures (spof) | The page has 2 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. | 80 |
| 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: https://fonts.googleapis.com/css2...ogleapis.com/css2 https://use.typekit.net/edy3lpy.css |
| Avoid extra requests by setting cache headers (cacheHeaders) | The page has 13 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 32.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: https://www.scottish-enterprise.com/ https://scottish-enterprise.com/media/2qdbnryf/se_main_logo-colour.svg https://scottish-enterprise.com/media/v34lqa5i/funding.svg https://scottish-enterprise.com/media/zued3py4/checklist-requirements.svg https://scottish-enterprise.com/media/hqmf2lhb/innovation.svg https://scottish-enterprise.com/media/5c5bo1y0/exports-packaging-shipping.svg https://scottish-enterprise.com/media/hc5hw2he/productivity-3.svg https://scottish-enterprise.com/Assets/symbols/icons.svg#chevron https://scottish-enterprise.com/environment-settings https://scottish-enterprise.com/account/session https://scottish-enterprise.com/cookies/permissions https://scottish-enterprise.com/favicon/site.webmanifest?v=0.78.0.0 https://scottish-enterprise.com/favicon/favicon-32x32.png?v=0.78.0.0 |
| Long cache headers is good (cacheHeadersLong) | The page has 13 requests that have a shorter cache time than 30 days (but still a cache time). | 87 |
| 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://fonts.googleapis.com/css2...ogleapis.com/css2 https://use.typekit.net/edy3lpy.css https://scottish-enterprise.com/media/nohh5yhq/innovation-robotics-technology-at...m-edinburgh-2.jpg https://scottish-enterprise.com/media/xk0htgwd/speakers-and-attendees-at-pathway...tel_-uphall-1.jpg https://scottish-enterprise.com/media/pj3dj4jf/yzanne-turbett-and-angus-hayhow-o...ce-cream-farm.jpg https://js.monitor.azure.com/scripts/b/ai.2.min.js https://www.googletagmanager.com/gtm.js?id=GTM-WZF5B6RQ https://p.typekit.net/p.css?s=1&k=edy3lpy&ht=tk&f=47589&a=103666268&app=typekit&e=css https://scottish-enterprise.com/media/ihklo3pa/welder-at-star-renewables-thornli...ornliebank-og.jpg https://scottish-enterprise.com/media/ufgacakx/scottish-enterprise-ceo-adrian-gi...of-scotland-4.jpg https://scottish-enterprise.com/media/3tphu0w2/exhibitors-and-guests-in-the-inno...discovery-hub.jpg https://scottish-enterprise.com/media/z11hkz1a/images-taken-at-business-meeting-...um-image_m964.jpg https://www.googletagmanager.com/gtag/js?id=G-8LHNSPWCG8&l=dataLayer&cx=c |
| Always compress text content (compressAssets) | The page has 4 requests that are served uncompressed. You could save a lot of bytes by sending them compressed instead. | 60 |
| 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 redirecting the main document (documentRedirect) | The main document gets redirected 1 time(s). Remove those redirect and make the page faster! | 0 |
| Description: You should never ever redirect the main document, because it will make the page load slower for the user. Well, you should redirect the user if the user tries to use HTTP and there's an HTTPS version of the page. The coach checks for that. :) |
| Offenders: https://www.scottish-enterprise.com/ |
| Avoid too many fonts (fewFonts) | The page has 2 font requests. Do you really need them? What value does the fonts give the user? | 80 |
| 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/worksans/v19/QGYsz_wNahGAdqQ43Rh_fKDp.woff2 https://use.typekit.net/af/1c1b46/00000000000000007735ea44/30/l...00007735ea44/30/l |
| Total image size shouldn't be too big (imageSize) | The page total image size is 1.2 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 505.4 kB and the uncompressed size is 1.6 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: |
| 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: https://uksouth-0.in.applicationinsights.azure.com//v2/track https://scottish-enterprise.com/cookies/permissions https://scottish-enterprise.com/favicon/site.webmanifest?v=0.78.0.0 |
| Make each CSS response small (optimalCssSize) | https://scottish-enterprise.com/assets/styles/site.css?v=0.78.0.0 size is 58.8 kB (58820) 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 4 requests with private headers. Make sure that the assets really should be private and only used by one user. Otherwise, make it cacheable for everyone. | 60 |
| 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://fonts.googleapis.com/css2...ogleapis.com/css2 https://use.typekit.net/edy3lpy.css https://www.googletagmanager.com/gtm.js?id=GTM-WZF5B6RQ https://www.googletagmanager.com/gtag/js?id=G-8LHNSPWCG8&l=dataLayer&cx=c |
0 s
1.1 sCPU Long Task duration 194 msFirst Visual Change 1.100 s
1.2 s
1.3 sDOM Content Loaded Time 1.202 s
1.4 sLayout Shift 0.00058 1.328 sPage Load Time 1.384 sCPU Long Task duration 84 ms
1.5 s
1.6 sCPU Long Task duration 53 msCPU Long Task duration 157 ms
1.7 s
1.9 s
2 sVisual Complete 85% 1.934 sVisual Complete 95% 1.934 sVisual Complete 99% 1.934 s
2.1 sLast Visual Change 2.034 s
