https://afl.com.au

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
22%
Desktop Performance
50%

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 Paint6.8 s2.8 s< 2.5 s
First Input Delay630 ms220 ms< 100ms
Cumulative Layout Shift0.2130.042 0.1

Tracking scripts

All the tracking scripts on the site generated ~1 MB 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
assets.adobedtm.com 9 150 KB
s.go-mpulse.net 1 51 KB
c.go-mpulse.net 1 323 B
securepubads.g.doubleclick.net 9 213 KB
googletagmanager.com 3 277 KB
cm.everesttech.net 1 565 B
googleads.g.doubleclick.net 2 4 KB
google-analytics.com 5 21 KB
connect.facebook.net 2 89 KB
analytics.tiktok.com 6 131 KB
js.adsrvr.org 2 4 KB
5439204.fls.doubleclick.net 2 2 KB
google.com 5 2 KB
stats.g.doubleclick.net 2 1 KB
cm.g.doubleclick.net 2 1 KB
5083706.fls.doubleclick.net 2 2 KB
facebook.com 2 328 B
rtd.tubemogul.com 1 497 B
image5.pubmatic.com 1 623 B
rtd-tm.everesttech.net 2 1 KB
ps.eyeota.net 2 1 KB
sync-tm.everesttech.net 16 9 KB
ib.adnxs.com 1 700 B
js-agent.newrelic.com 1 17 KB
beacon.krxd.net 1 290 B
insight.adsrvr.org 1 608 B
bam.nr-data.net 1 627 B
match.adsrvr.org 3 3 KB
pixel.rubiconproject.com 1 959 B
ups.analytics.yahoo.com 3 2 KB
s2.adform.net 2 35 KB
asia.adform.net 3 6 KB
dmp.adform.net 2 686 B

Opportunities

Assets that need text compression enabled15 KB0.004g

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

View details
lib.js 18 KB 12 KB
afl.js 5 KB 3 KB
Replace inlined font files

There is 1 inlined font that should converted to a subresource.

Subset large font files2 MB0.62g

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
Inter.var.woff2 ~318 KB ~301 KB
Inter.var.woff2 ~318 KB ~301 KB
Inter.var.woff2 ~318 KB ~301 KB
Inter.var.woff2 ~318 KB ~301 KB
Inter.var.woff2 ~318 KB ~301 KB
Inter.var.woff2 ~318 KB ~301 KB
Inter.var.woff2 ~318 KB ~301 KB
Inter.var.woff2 ~318 KB ~301 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.
MobileDesktop
Score58%96%
Timing2.8 s0.8 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
Score7%38%
Timing6.8 s2.8 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
Score0%21%
Timing4,990 ms590 ms
Cumulative Layout Shift

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

MobileDesktop
Score58%99%
Timing0.2130.042
Speed Index

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

MobileDesktop
Score0%3%
Timing24.7 s5.0 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
Score0%1%
Timing45.9 s12.0 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
Score3%60%
Timing630 ms220 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
Score66%96%
Timing3.3 s0.8 s
Eliminate render-blocking resources

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.

MobileDesktop
Score58%95%
InsightPotential savings of 680 msPotential savings of 90 ms
Properly size images

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

MobileDesktop
Score39%100%
InsightPotential savings of 236 KiBPotential savings of 65 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.

MobileDesktop
Score56%100%
InsightPotential savings of 150 KiBPotential savings of 31 KiB
Minify JavaScript

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

MobileDesktop
Score12%45%
InsightPotential savings of 365 KiBPotential savings of 360 KiB
Reduce unused CSS

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

MobileDesktop
Score59%93%
InsightPotential savings of 129 KiBPotential savings of 129 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.

MobileDesktop
Score2%24%
InsightPotential savings of 1,914 KiBPotential savings of 1,617 KiB
Efficiently encode images

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

MobileDesktop
Score78%100%
InsightPotential savings of 28 KiBPotential savings of 30 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.

MobileDesktop
Score35%97%
InsightPotential savings of 222 KiBPotential savings of 108 KiB
Enable text compression

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.

MobileDesktop
Score85%98%
InsightPotential savings of 15 KiBPotential savings of 15 KiB
Remove duplicate modules in JavaScript bundles

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

MobileDesktop
Score90%98%
InsightPotential savings of 19 KiBPotential savings of 19 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.

MobileDesktop
Score6%2%
InsightTotal size was 6,394 KiBTotal size was 7,326 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.

MobileDesktop
Score0%2%
Insight100 resources found37 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.

MobileDesktop
Score0%0%
Insight4,024 elements4,211 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.

MobileDesktop
Score3%53%
Timing14.9 s3.2 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

MobileDesktop
Score0%17%
Timing25.9 s6.6 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.

MobileDesktop
GradeFailFail
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.

MobileDesktop
GradeFailFail
InsightThird-party code blocked the main thread for 3,580 msThird-party code blocked the main thread for 450 ms
Uses passive listeners to improve scrolling performance

Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.

MobileDesktop
GradeFailPass
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().

MobileDesktop
GradeFailFail
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

MobileDesktop
GradeFailFail