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
37%
Desktop Performance
62%

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.

Pass or fail?

MobileFail
DesktopFail

CWV Breakdown

VitalMobileDesktopTarget
Largest Contentful Paint11.8 s3.1 s< 2.5 s
First Input Delay1,550 ms530 ms< 100ms
Cumulative Layout Shift0.0140.002 0.1

Tracking scripts

All the tracking scripts on the site generated ~92 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.

View details
googletagmanager.com 1 92 KB
google-analytics.com 2 0 B

Opportunities

Assets that need text compression enabled272 KB0.07g

By enabling text compression on 101 items, , roughly 271.8 KB could be removed from the page load.

View details
1901 13 KB 11 KB
1901 13 KB 11 KB
1680 10 KB 9 KB
1679 10 KB 9 KB
1679 10 KB 9 KB
1677 10 KB 9 KB
1785 9 KB 8 KB
1785 9 KB 8 KB
1889 8 KB 7 KB
1730 7 KB 6 KB
1813 5 KB 4 KB
1854 5 KB 4 KB
1854 5 KB 4 KB
1665 5 KB 4 KB
1895 4 KB 3 KB
1858 4 KB 3 KB
1731 4 KB 3 KB
1727 4 KB 3 KB
1727 4 KB 3 KB
1536 3 KB 2 KB
1536 3 KB 2 KB
1734 3 KB 2 KB
1789 3 KB 2 KB
1789 3 KB 2 KB
1719 3 KB 2 KB
1719 3 KB 2 KB
1720 3 KB 2 KB
1902 3 KB 2 KB
1861 3 KB 2 KB
1729 3 KB 2 KB
1729 3 KB 2 KB
1896 3 KB 2 KB
1867 3 KB 2 KB
1704 3 KB 2 KB
1710 3 KB 2 KB
1666 3 KB 2 KB
1534 3 KB 2 KB
1534 3 KB 2 KB
1533 3 KB 2 KB
1533 3 KB 2 KB
1535 3 KB 2 KB
1535 3 KB 2 KB
1577 3 KB 2 KB
1577 3 KB 2 KB
1626 3 KB 2 KB
1598 3 KB 2 KB
1598 3 KB 2 KB
1856 3 KB 2 KB
1856 3 KB 2 KB
1811 3 KB 2 KB
1811 3 KB 2 KB
1897 3 KB 2 KB
1732 3 KB 2 KB
1809 3 KB 2 KB
1809 3 KB 2 KB
1791 3 KB 2 KB
1793 3 KB 2 KB
1859 3 KB 2 KB
1790 3 KB 2 KB
1799 3 KB 2 KB
1875 3 KB 2 KB
1810 3 KB 2 KB
1810 3 KB 2 KB
1830 3 KB 2 KB
1830 3 KB 2 KB
1735 3 KB 2 KB
1869 3 KB 2 KB
1847 3 KB 2 KB
1771 3 KB 2 KB
1724 3 KB 2 KB
1792 3 KB 2 KB
1876 3 KB 2 KB
1876 3 KB 2 KB
1871 2 KB 2 KB
1828 2 KB 2 KB
1828 2 KB 2 KB
1698 2 KB 2 KB
1698 2 KB 2 KB
1827 2 KB 2 KB
1748 2 KB 2 KB
1661 2 KB 2 KB
1736 2 KB 2 KB
1803 2 KB 2 KB
1803 2 KB 2 KB
1696 2 KB 2 KB
1696 2 KB 2 KB
1800 2 KB 2 KB
1800 2 KB 2 KB
1874 2 KB 2 KB
1641 2 KB 2 KB
1868 2 KB 2 KB
1751 2 KB 2 KB
1751 2 KB 2 KB
1870 2 KB 2 KB
1836 2 KB 2 KB
1836 2 KB 2 KB
1642 2 KB 2 KB
1642 2 KB 2 KB
1865 2 KB 2 KB
1865 2 KB 2 KB
1683 2 KB 2 KB
Optimise images6 MB1.568g

By optimising the following images, roughly 6 MB could be removed from the transfer size, about 61%. This would reduce the CO2 generated per page load from 2.56g grams to 0.99 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.
View details
Credit_Tiny_Empire_Collective.2e16d0ba.fill-560x654.png 648 KB 7% 598 KB
The_Stroy_House_-_Credit_Peter_Foster.width-1719.jpg 524 KB 5% 280 KB
Addams_Family_Clonard_College_WebB.2e16d0ba.fill-550x375.png 436 KB 4% 400 KB
Facebook_1200_x_630_px.2e16d0ba.fill-550x375.png 426 KB 4% 391 KB
bohemian-rhapsody-starring-thomas-.2e16d0ba.fill-550x375.png 410 KB 4% 370 KB
western_beach_feb_27th_3.width-1719.jpg 381 KB 4% 137 KB
Jaime_conducts_-_2880_x_1966.2e16d0ba.fill-550x375.png 357 KB 4% 319 KB
Geelong_Arts_Centre_-_Credit_Ferne_Millen_2.width-1719.jpg 356 KB 4% 125 KB
Handels_Messiah_-_2880_x_1966.2e16d0ba.fill-550x375.png 345 KB 3% 316 KB
Dvorak_and_Bruckner_-_2880_x_1966.2e16d0ba.fill-550x375.png 314 KB 3% 292 KB
WEB_RESIZE_-_CHORUS.2e16d0ba.fill-550x375.png 313 KB 3% 297 KB
WIL24_AFF_1200x600.2e16d0ba.fill-550x375.png 309 KB 3% 290 KB
GAC-May23-1-362.width-1719.jpg 300 KB 3% 131 KB
GLE23_CAM_1920x1080.2e16d0ba.fill-550x375.png 275 KB 3% 261 KB
1920x1080.2e16d0ba.fill-550x375.png 268 KB 3% 253 KB
Heritage_Legends_1920_x_1080_px_.2e16d0ba.fill-550x375.png 251 KB 3% 216 KB
Mozart_and_Tchaikovsky_-_2880_x_19.2e16d0ba.fill-550x375.png 234 KB 2% 219 KB
web_resize_-_the-magic-flute---syd.2e16d0ba.fill-550x375.png 233 KB 2% 222 KB
MHSS_LANDSCAPE_CLEAN.2e16d0ba.fill-550x375.png 214 KB 2% 193 KB
deakin_university.width-1719.jpg 201 KB 2% 60 KB
Web_Hero_Image_Wonder.width-1500.jpg 177 KB 2% 75 KB
MUSIC_THEATRE.2e16d0ba.fill-550x375.png 136 KB 1% 130 KB
GPAC_1_442_LoRes.width-1719.jpg 115 KB 1% 45 KB
PS_Promo_Pic_landscape.2e16d0ba.fill-550x375.jpg 70 KB 1% 22 KB
GAC_WEB_PF_230804_114038.2e16d0ba.fill-550x375.jpg 64 KB 1% 21 KB
Wizard_of_Oz_Web_Banner.2e16d0ba.fill-550x375.jpg 63 KB 1% 20 KB
CROP_FOR_WEB.2e16d0ba.fill-560x654.jpg 63 KB 1% 25 KB
DCoggan-denver-no-text-1920x1080.2e16d0ba.fill-550x375.jpg 60 KB 1% 19 KB
WOM_Web_Crop.2e16d0ba.fill-550x375.jpg 60 KB 1% 20 KB
COME_FROM_AWAY_WEB_BANNER.2e16d0ba.fill-550x375.jpg 60 KB 1% 19 KB
Geelong_Arts_Centre_-_Trophy_Boys_.2e16d0ba.fill-550x375.jpg 58 KB 1% 21 KB
CROPPED_FOR_WEB_Hero_Arterial__-_C.2e16d0ba.fill-550x375.jpg 57 KB 1% 18 KB
Landscape_2880_W_X_1966_H.2e16d0ba.fill-550x375.jpg 56 KB 1% 20 KB
Animals_Geelong_Story_House_2880x1.2e16d0ba.fill-550x375.jpg 50 KB 1% 19 KB
Misery_-_Crop_2.2e16d0ba.fill-550x375.jpg 50 KB 1% 16 KB
Silent_Sky_H_-_Copy.2e16d0ba.fill-550x375.jpg 48 KB 0% 14 KB
Seventh_Wonder-8.2e16d0ba.fill-550x375.jpg 46 KB 0% 17 KB
Tubular-Bells_Webpage_Banner.2e16d0ba.fill-550x375.jpg 43 KB 0% 17 KB
2880x1966_.2e16d0ba.fill-550x375.jpg 42 KB 0% 15 KB
Education-Header_2500x1780-1.2e16d0ba.fill-550x375.jpg 41 KB 0% 16 KB
671_TGC_Marketing_Assets_Generic_K.2e16d0ba.fill-550x375.jpg 41 KB 0% 15 KB
Geelong_Arts_Centre_-_How_To_Catch.2e16d0ba.fill-550x375.jpg 39 KB 0% 16 KB
mystique_GPAC_2880x1966.2e16d0ba.fill-550x375.jpg 38 KB 0% 15 KB
Babba_Web_Crop.2e16d0ba.fill-550x375.jpg 38 KB 0% 14 KB
Bee_Gees_Web_Banner_Update1.2e16d0ba.fill-550x375.jpg 37 KB 0% 15 KB
CROPPED_FOR_WEB_Geelong_Arts_Centr.3d35c509.fill-550x375.jpg 36 KB 0% 14 KB
VL_Tour_master_image_for_artwork__.2e16d0ba.fill-550x375.jpg 35 KB 0% 14 KB
Tutti-Wine.2e16d0ba.fill-560x654.jpg 33 KB 0% 16 KB
Combined_shot_2_x_1.2e16d0ba.fill-550x375.jpg 31 KB 0% 12 KB
CROPPED_Fourteen_Hero_NoPaper.2e16d0ba.fill-550x375.jpg 31 KB 0% 13 KB
Subset large font files122 KB0.031g

Fonts should be subsetted to reduce the file size, improve performance, and reduce emissions. Subsetting a font involves removing any characters that are not needed for a particular use case, resulting in a smaller file size and faster page load times. Some specific reasons why fonts should be subsetted include:

  1. Reduced file size: Subsetting a font removes any unused characters, which can result in a smaller file size. This can help to reduce the amount of data that needs to be downloaded, leading to faster page load times and lower emissions.
  2. Improved performance: Fonts that are subsetted are faster to load and render than fonts that are not subsetted. This can help to improve the overall performance of a website, leading to a better user experience.

Overall, subsetting fonts is a good practice for anyone looking to optimize the performance and reduce the emissions of a website of a website.

View details
GT-America-Extended-Medium.c14acd03.woff2 ~48 KB ~31 KB
GT-America-Standard-Bold.271e67bc.woff2 ~47 KB ~29 KB
GT-America-Standard-Regular.5b08b72f.woff2 ~44 KB ~26 KB
GT-America-Mono-Bold.5484cae9.woff2 ~36 KB ~18 KB
GT-America-Mono-Regular.a649f781.woff2 ~35 KB ~17 KB
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.
View details
cdn.geelongartscentre.org.au GT-America-Mono-Bold.5484cae9.woff2
cdn.geelongartscentre.org.au GT-America-Mono-Regular.a649f781.woff2
cdn.geelongartscentre.org.au GT-America-Standard-Bold.271e67bc.woff2
cdn.geelongartscentre.org.au GT-America-Extended-Medium.c14acd03.woff2
cdn.geelongartscentre.org.au GT-America-Standard-Regular.5b08b72f.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
Score21%79%
Timing4.1 s1.1 s
Largest Contentful Paint

Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric

MobileDesktop
Score0%32%
Timing11.8 s3.1 s
Total Blocking Time

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.

MobileDesktop
Score34%69%
Timing840 ms250 ms
Speed Index

Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.

MobileDesktop
Score0%1%
Timing15.4 s5.9 s
Time to Interactive

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

MobileDesktop
Score12%66%
Timing13.1 s3.7 s
Max Potential First Input Delay

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

MobileDesktop
Score0%6%
Timing1,550 ms530 ms
First Meaningful Paint

First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.

MobileDesktop
Score18%51%
Timing5.8 s1.6 s