Victorian Institute of Forensic Mental Health (ForensiCare)

The Index


Google Lighthouse Performance

The Google Lighthouse performance score is a metric that measures the speed and performance of a website. It’s an overall score that ranges from 0 to 100 and is generated based on a number of different performance metrics, such as the time it takes for a website to load, the time it takes for a website to become interactive, the size of the resources used by the website, and other factors that impact the user experience.

A high performance score in Google Lighthouse indicates that a website is fast and responsive, which can lead to a better user experience and improved search engine rankings. On the other hand, a low performance score can indicate that a website is slow and unresponsive, and can negatively impact the user experience.

Mobile Performance
Desktop Performance

Core Web Vitals

Core Web Vitals are a set of specific factors that Google considers important in a webpage’s overall user experience. Core Web Vitals are made up of three specific page speed and user interaction measurements: Largest Contentful PaintFirst Input Delay, and Cumulative Layout Shift.

Largest Contentful Paint3.3 s1.0 s< 2.5 s
First Input Delay200 ms60 ms< 100ms
Cumulative Layout Shift00.002 0.1


Optimise images

By optimising the following images, roughly 6 MB could be removed from the transfer size, about 83%. This would reduce the CO2 generated per page load from 1.85g grams to 0.31 grams.

Images should be optimised for the web for several reasons:

  1. Reduced file size: Optimizing images can result in a smaller file size, which can help to reduce the amount of data that needs to be downloaded. This can lead to faster page load times and improved performance.
  2. Improved user experience: Optimising images can help to improve the overall user experience, as pages with optimised images load faster and are more responsive.
  3. Lower emissions: Optimising images can help to reduce the emissions associated with data transfer, as less data needs to be transmitted over the network.
  4. Better accessibility: Optimising images can make them more accessible to users with slower connections or limited data plans.
Foresnicare_Apsley-1985-4-1.jpg 2 MB 28% 2 MB
TEHBEP-Oct-22-1536x780.png 2 MB 26% 2 MB
Stephane-Shepherd-web.png 915 KB 13% 846 KB
Tessa-Maguire-web-graphic-1-1536x780.png 832 KB 12% 754 KB
forensicare_footerIMG.png 245 KB 3% 198 KB
forensicare_headerIMG.png 245 KB 3% 197 KB
CFBS-Annual-Research-Report-2021-22-1536x780.png 147 KB 2% 111 KB
Screen-Shot-2016-09-05-at-4.39.08-pm.png 138 KB 2% 125 KB
ResearchEducation.png 127 KB 2% 113 KB
OurServices.png 121 KB 2% 111 KB
forensicarelogo_col.png 33 KB 0% 15 KB

Replace icon font files

Font icons can have a negative impact on performance and emissions because they can increase the size of the page and the amount of data that needs to be downloaded. Some specific reasons why font icons can be bad for performance and emissions include:

  1. Increased file size: Font icons are typically included as part of a web font, which can be a large file that needs to be downloaded. This can increase the overall size of the page, leading to slower load times and higher emissions.
  2. Inefficient rendering: Web fonts are sometimes loaded and rendered inefficiently, which can result in slow performance and higher emissions.
  3. Unused icons: Font icons often include a large number of icons that may not be used on a particular page, increasing the file size and leading to inefficient use of resources.

While icon fonts are still widely used on the web, and they can be a useful tool for adding icons to a website. it is a dated practice when there are better options such as SVG icons, which can be more efficient and have a lower impact on performance and emissions.

fontawesome-webfont.woff271 KB
fa-solid-900.woff278 KB

First Contentful Paint

First Contentful Paint (FCP) is a performance metric that measures the time it takes for the first piece of content to be rendered on the screen when a user navigates to a web page. This content can be any visual element on the page, such as text, images, or a background color.

FCP is important because it directly affects the perceived speed of a website, and can impact user engagement and conversion rates. A faster FCP can lead to a better user experience and improved performance.

Here are a few ways you can optimise your FCP:

  1. Optimise images: Large, unoptimised images can slow down a page’s FCP. You can optimise images by compressing them, reducing their dimensions, and choosing the right format for each image.
  2. Minimise HTTP requests: Each resource requested by a web page, such as images, scripts, and stylesheets, requires a separate HTTP request. Minimising the number of HTTP requests can help to reduce the time it takes for a page to render.
  3. Prioritize critical content: Prioritizing critical content, such as above-the-fold content, can help to ensure that users see something on the screen quickly, even if the rest of the page is still loading.
  4. Reduce server response time: A slow server response time can significantly impact FCP. Optimizing server-side code and server settings can help to reduce response times and improve FCP.
  5. Use a performance monitoring tool: There are many tools available that can help you monitor your website’s performance, including FCP. These tools can help you identify performance issues and track your progress as you implement optimizations.
Timing2.6 s0.6 s

Largest Contentful Paint

Timing3.3 s1.0 s

Total Blocking Time

Timing70 ms10 ms

Speed Index

Timing5.5 s1.7 s

Time to Interactive

Timing3.5 s0.8 s

Max Potential First Input Delay

Timing200 ms60 ms

First Meaningful Paint

Timing2.6 s0.6 s

Eliminate render-blocking resources

InsightPotential savings of 1,530 msPotential savings of 230 ms

Properly size images

InsightPotential savings of 2,048 KiBPotential savings of 5,796 KiB

Reduce unused CSS

InsightPotential savings of 307 KiBPotential savings of 303 KiB

Serve images in next-gen formats

InsightPotential savings of 646 KiBPotential savings of 4,163 KiB

Reduce initial server response time

InsightRoot document took 940 msRoot document took 640 ms

Avoid enormous network payloads

InsightTotal size was 3,242 KiBTotal size was 7,187 KiB

Serve static assets with an efficient cache policy

Insight10 resources found16 resources found

Avoid an excessive DOM size

Insight823 elements823 elements

Largest Contentful Paint image was not lazily loaded