The University of Queensland

The Index

Insights

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
30%
Desktop Performance
60%

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.

VitalMobileDesktopTarget
Largest Contentful Paint8.3 s1.8 s< 2.5 s
First Input Delay990 ms290 ms< 100ms
Cumulative Layout Shift0.0530.035 0.1

Tracking scripts

All the tracking scripts on the site generated ~521 KB of data

A tracking script is a code snippet designed to track the flow of visitors who visit a website. Media, advertising, and analytics organisations will provide a script to add to your website that sends data directly to their servers. This data can then be used to measure goals and conversions, analyse user behaviour, and influence advertising campaigns.

Consider how much of this data you actually need and use? How often do you review the analytics data, and does this inform genuine change? Are you actively running social media campaigns? Consider pausing or removing tracking scripts that aren’t being actively used.

googletagmanager.com 2 184 KB
googleoptimize.com 1 44 KB
google-analytics.com 3 21 KB
bat.bing.com 4 13 KB
snap.licdn.com 1 5 KB
analytics.tiktok.com 4 101 KB
stats.g.doubleclick.net 3 1 KB
cdn.linkedin.oribi.io 1 467 B
px.ads.linkedin.com 3 3 KB
google.com 2 1 KB
linkedin.com 1 2 KB
6735941.fls.doubleclick.net 2 2 KB
connect.facebook.net 2 137 KB
analytics.google.com 1 0 B
in.hotjar.com 1 407 B
facebook.com 2 656 B
googleads.g.doubleclick.net 4 3 KB
static.doubleclick.net 2 1 KB

Opportunities

Remove third party font files

Font files should be loaded from the same hosting as the website because

  1. Increased loading time: Third-party sub-resources, such as scripts, fonts, or images, need to be downloaded from a separate server before they can be displayed on the website. This can increase the overall loading time of the page, leading to a slower user experience.
  2. Dependence on external servers: The loading of third-party subresources is dependent on the availability and performance of the external servers that host them. If these servers are slow or unavailable, it can result in slow page loading times or even errors.
  3. Increased risk of security threats: Third-party subresources can introduce security risks to a website, as they can contain malicious code or be used to track user activity.
HostFont
fonts.gstatic.comKFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
fonts.gstatic.comKFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
fonts.gstatic.comJTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXx-p7K4KLg.woff
fonts.gstatic.comKFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
fonts.gstatic.comKFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
fonts.gstatic.comKFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
fonts.gstatic.comKFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2

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.
MobileDesktop
Score32%81%
Timing3.6 s1.1 s

Largest Contentful Paint

MobileDesktop
Score2%69%
Timing8.3 s1.8 s

Total Blocking Time

MobileDesktop
Score4%24%
Timing2,460 ms560 ms

Cumulative Layout Shift

MobileDesktop
Score98%100%
Timing0.0530.035

Speed Index

MobileDesktop
Score3%22%
Timing12.3 s3.2 s

Time to Interactive

MobileDesktop
Score1%34%
Timing23.8 s5.4 s

Max Potential First Input Delay

MobileDesktop
Score0%39%
Timing990 ms290 ms

First Meaningful Paint

MobileDesktop
Score49%70%
Timing4.0 s1.3 s

Eliminate render-blocking resources

MobileDesktop
Score42%80%
InsightPotential savings of 1,420 msPotential savings of 240 ms

Properly size images

MobileDesktop
Score48%67%
InsightPotential savings of 223 KiBPotential savings of 488 KiB

Reduce unused CSS

MobileDesktop
Score46%65%
InsightPotential savings of 129 KiBPotential savings of 135 KiB

Reduce unused JavaScript

MobileDesktop
Score0%34%
InsightPotential savings of 1,224 KiBPotential savings of 1,228 KiB

Serve images in next-gen formats

MobileDesktop
Score43%77%
InsightPotential savings of 211 KiBPotential savings of 265 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 1,400 msRoot document took 1,410 ms

Avoid enormous network payloads

MobileDesktop
Score72%65%
InsightTotal size was 3,296 KiBTotal size was 3,538 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score45%45%
Insight10 resources found10 resources found

Avoid an excessive DOM size

MobileDesktop
Score79%79%
Insight988 elements988 elements

Reduce JavaScript execution time

MobileDesktop
Score13%63%
Timing8.2 s2.7 s

Minimize main-thread work

MobileDesktop
Score2%41%
Timing11.5 s4.5 s

Ensure text remains visible during webfont load

MobileDesktop
GradeFailFail

Reduce the impact of third-party code

MobileDesktop
GradeFailFail
InsightThird-party code blocked the main thread for 5,540 msThird-party code blocked the main thread for 1,560 ms

Some third-party resources can be lazy loaded with a facade

MobileDesktop
GradeFailFail
Insight1 facade alternative available1 facade alternative available

Does not use passive listeners to improve scrolling performance

MobileDesktop
GradeFailFail

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail