The Guardian – Australia

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.

Pass or fail?


CWV Breakdown

Largest Contentful Paint6.2 s1.6 s< 2.5 s
First Input Delay810 ms250 ms< 100ms
Cumulative Layout Shift0.3170.241 0.1

Tracking scripts

All the tracking scripts on the site generated ~394 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 2 21 KB 3 69 KB 4 4 KB 5 191 KB 1 17 KB 1 575 B 1 868 B 1 2 KB 1 672 B 3 1 KB 4 3 KB 1 595 B 1 388 B 1 201 B 1 754 B 10 8 KB 1 597 B 1 245 B 3 4 KB 3 18 KB 2 2 KB 11 7 KB 5 3 KB 10 7 KB 5 5 KB 5 2 KB 2 2 KB 2 972 B 2 770 B 1 3 KB 3 3 KB 1 974 B 2 1 KB 3 2 KB 1 762 B 1 356 B 1 869 B 1 577 B 1 7 KB 1 813 B 1 356 B 1 310 B


Subset large font files15 KB0.003g

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
GHGuardianHeadline-Light.woff2 ~24 KB ~6 KB
GuardianTextEgyptian-BoldItalic.woff2 ~20 KB ~2 KB
GHGuardianHeadline-MediumItalic.woff2 ~20 KB ~2 KB
GuardianTextSans-Bold.woff2 ~18 KB ~717 B
GuardianTextSans-Bold.woff2 ~18 KB ~706 B
GuardianTextSans-Bold.woff2 ~18 KB ~706 B
GuardianTextSans-Bold.woff2 ~18 KB ~706 B
GuardianTextSans-Bold.woff2 ~18 KB ~706 B
GuardianTextEgyptian-Bold.woff2 ~18 KB ~393 B
GuardianTextEgyptian-Regular.woff2 ~18 KB ~156 B
GuardianTextEgyptian-Regular.woff2 ~18 KB ~133 B
GuardianTextEgyptian-Regular.woff2 ~18 KB ~133 B
GuardianTextEgyptian-Regular.woff2 ~18 KB ~133 B
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 GHGuardianHeadline-Bold.woff2 GuardianTextEgyptian-Regular.woff2 GuardianTextSans-Regular.woff2 GuardianTextSans-Bold.woff2 GHGuardianHeadline-Light.woff2 GHGuardianHeadline-Medium.woff2 GHGuardianHeadline-MediumItalic.woff2 GuardianTextSans-Regular.woff2 GHGuardianHeadline-Bold.woff2 GuardianTextSans-Bold.woff2 GHGuardianHeadline-Light.woff2 GuardianTextEgyptian-BoldItalic.woff2 GuardianTextEgyptian-Bold.woff2 GHGuardianHeadline-Bold.woff2 GuardianTextSans-Regular.woff2 GuardianTextSans-Bold.woff2 GHGuardianHeadline-Bold.woff2 GuardianTextSans-Regular.woff2 GuardianTextSans-Bold.woff2 GHGuardianHeadline-Bold.woff2 GuardianTextSans-Regular.woff2 GuardianTextSans-Bold.woff2 GuardianTextEgyptian-Regular.woff2 GuardianTextEgyptian-Regular.woff2 GuardianTextEgyptian-Regular.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.
Timing3.4 s1.0 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

Timing6.2 s1.6 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.

Timing3,510 ms2,290 ms
Cumulative Layout Shift

Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.

Speed Index

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

Timing8.0 s4.2 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.

Timing20.9 s8.9 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.

Timing810 ms250 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.

Timing3.4 s1.0 s
Properly size images

Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.

InsightPotential savings of 122 KiBPotential savings of 222 KiB
Defer offscreen images

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.

InsightPotential savings of 364 KiBPotential savings of 385 KiB
Minify JavaScript

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

InsightPotential savings of 8 KiBPotential savings of 10 KiB
Reduce unused JavaScript

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

InsightPotential savings of 586 KiBPotential savings of 549 KiB
Efficiently encode images

Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.

InsightPotential savings of 337 KiBPotential savings of 337 KiB
Serve images in next-gen formats

Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.

InsightPotential savings of 512 KiBPotential savings of 512 KiB
Use video formats for animated content

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formats

InsightPotential savings of 45 KiB
Remove duplicate modules in JavaScript bundles

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

InsightPotential savings of 50 KiBPotential savings of 50 KiB
Avoid serving legacy JavaScript to modern browsers

Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript

InsightPotential savings of 54 KiBPotential savings of 70 KiB
Avoid enormous network payloads

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

InsightTotal size was 3,102 KiBTotal size was 3,928 KiB
Serve static assets with an efficient cache policy

A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.

Insight31 resources found39 resources found
Avoid an excessive DOM size

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.

Insight4,152 elements4,131 elements
Reduce JavaScript execution time

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Timing8.4 s6.1 s
Minimize main-thread work

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Timing14.5 s11.9 s
Ensure text remains visible during webfont load

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.

Reduce the impact of third-party code

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.

InsightThird-party code blocked the main thread for 3,900 msThird-party code blocked the main thread for 1,560 ms
Avoid document.write()

For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().

Image elements do not have explicit width and height

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions