News.com.au
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
- 41%
- Desktop Performance
- 59%
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 Paint, First Input Delay, and Cumulative Layout Shift.
Pass or fail?
| Mobile | Fail |
|---|---|
| Desktop | Fail |
CWV Breakdown
| Vital | Mobile | Desktop | Target |
|---|---|---|---|
| Largest Contentful Paint | 5.6 s | 1.3 s | < 2.5 s |
| First Input Delay | 420 ms | 190 ms | < 100ms |
| Cumulative Layout Shift | 0 | 0.019 | 0.1 |
Tracking scripts
All the tracking scripts on the site generated ~2 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
| securepubads.g.doubleclick.net | 13 | 648 KB |
| idgets.outbrain.com | 8 | 118 KB |
| idget-pixels.outbrain.com | 1 | 577 B |
| mv.outbrain.com | 4 | 16 KB |
| amplify.outbrain.com | 2 | 10 KB |
| tags.tiqcdn.com | 11 | 111 KB |
| ave.outbrain.com | 1 | 539 B |
| tr.outbrain.com | 1 | 293 B |
| connect.facebook.net | 2 | 92 KB |
| sb.scorecardresearch.com | 4 | 2 KB |
| googletagmanager.com | 6 | 489 KB |
| c.amazon-adsystem.com | 3 | 90 KB |
| 8228261.fls.doubleclick.net | 4 | 4 KB |
| snap.licdn.com | 1 | 15 KB |
| sc-static.net | 2 | 48 KB |
| acdn.adnxs.com | 2 | 26 KB |
| px.ads.linkedin.com | 6 | 5 KB |
| linkedin.com | 1 | 1 KB |
| google-analytics.com | 4 | 24 KB |
| tr.snapchat.com | 6 | 3 KB |
| ct.pinterest.com | 4 | 4 KB |
| ib.adnxs.com | 9 | 7 KB |
| match.adsrvr.org | 11 | 8 KB |
| beacon.krxd.net | 1 | 0 B |
| aa.agkn.com | 2 | 2 KB |
| x.bidswitch.net | 13 | 8 KB |
| dis.criteo.com | 2 | 1,006 B |
| cm.g.doubleclick.net | 15 | 10 KB |
| dsp-cookie.adfarm1.adition.com | 1 | 646 B |
| ps.eyeota.net | 8 | 5 KB |
| pixel.rubiconproject.com | 15 | 25 KB |
| loadus.exelator.com | 3 | 3 KB |
| ssum-sec.casalemedia.com | 5 | 7 KB |
| image8.pubmatic.com | 3 | 3 KB |
| u.openx.net | 2 | 2 KB |
| ups.analytics.yahoo.com | 3 | 2 KB |
| ad.360yield.com | 2 | 1 KB |
| s.ad.smaato.net | 1 | 618 B |
| ssbsync.smartadserver.com | 1 | 602 B |
| c.bing.com | 1 | 964 B |
| pixel-sync.sitescout.com | 2 | 2 KB |
| cms.quantserve.com | 4 | 2 KB |
| bh.contextweb.com | 1 | 2 KB |
| trace.mediago.io | 1 | 731 B |
| cm.rtbsystem.com | 1 | 2 KB |
| rtb.adentifi.com | 1 | 51 B |
| pxl.iqm.com | 1 | 953 B |
| sync.1rx.io | 1 | 454 B |
| cs.media.net | 1 | 814 B |
| cs.admanmedia.com | 1 | 0 B |
| csync.loopme.me | 2 | 1 KB |
| temu.com | 1 | 880 B |
| sync.teads.tv | 1 | 727 B |
| sync.outbrain.com | 28 | 6 KB |
| redditstatic.com | 2 | 20 KB |
| script.crazyegg.com | 2 | 4 KB |
| js.adsrvr.org | 3 | 9 KB |
| google.com | 5 | 4 KB |
| googleads.g.doubleclick.net | 4 | 10 KB |
| td.doubleclick.net | 5 | 7 KB |
| googleadservices.com | 1 | 3 KB |
| pippio.com | 2 | 1 KB |
| logx.optimizely.com | 1 | 566 B |
| image2.pubmatic.com | 13 | 8 KB |
| facebook.com | 1 | 447 B |
| 14643376.fls.doubleclick.net | 2 | 2 KB |
| ad.doubleclick.net | 1 | 2 KB |
| insight.adsrvr.org | 4 | 3 KB |
| alb.reddit.com | 1 | 846 B |
| google.com.au | 4 | 2 KB |
| image4.pubmatic.com | 2 | 1,001 B |
| config.aps.amazon-adsystem.com | 1 | 896 B |
| aax.amazon-adsystem.com | 1 | 580 B |
| newscorpau.sc.omtrdc.net | 1 | 418 B |
| cm.everesttech.net | 1 | 554 B |
| ads.pubmatic.com | 5 | 30 KB |
| htlb.casalemedia.com | 1 | 959 B |
| hbopenbid.pubmatic.com | 1 | 586 B |
| dsum-sec.casalemedia.com | 8 | 8 KB |
| s.amazon-adsystem.com | 14 | 10 KB |
| pixel.tapad.com | 5 | 6 KB |
| rtb.gumgum.com | 1 | 1 KB |
| eb2.3lift.com | 2 | 1 KB |
| secure.adnxs.com | 2 | 2 KB |
| image6.pubmatic.com | 7 | 14 KB |
| us-u.openx.net | 1 | 603 B |
| c1.adform.net | 4 | 3 KB |
| uipglob.semasio.net | 2 | 1 KB |
| um.simpli.fi | 2 | 2 KB |
| simage2.pubmatic.com | 21 | 13 KB |
| b1sync.outbrain.com | 1 | 786 B |
| dsp.360yield.com | 1 | 489 B |
| dsum.casalemedia.com | 2 | 2 KB |
| aax-eu.amazon-adsystem.com | 1 | 855 B |
| sync.ipredictive.com | 2 | 1 KB |
| pixel.onaudience.com | 1 | 349 B |
| simage4.pubmatic.com | 6 | 2 KB |
| d.turn.com | 1 | 612 B |
| ssum.casalemedia.com | 1 | 1 KB |
| sync-tm.everesttech.net | 20 | 12 KB |
| i.w55c.net | 1 | 806 B |
| pm.w55c.net | 2 | 2 KB |
| dpm.demdex.net | 1 | 1 KB |
| p.rfihub.com | 2 | 2 KB |
| beacon.lynx.cognitivlabs.com | 2 | 796 B |
| a.tribalfusion.com | 1 | 947 B |
| sync.mathtag.com | 1 | 951 B |
| s.tribalfusion.com | 1 | 510 B |
| usermatch.krxd.net | 1 | 0 B |
| tags.bluekai.com | 1 | 0 B |
| cs.iqzone.com | 1 | 629 B |
| trc.taboola.com | 1 | 589 B |
Opportunities
Remove autoplaying or preloaded media files2 videos1.6 MB0.41g CO2
By removing 2 autoplaying or preloaded videos, roughly 1.6 MB could be removed from the page load.
This would reduce the page transfer size by 19% and reduce the pages emissions from 2.17 grams of CO2 to 1.75 grams of CO2.
Autoplaying videos can have a negative impact on the user experience for several reasons:
- Increased data usage: Autoplaying videos can consume a lot of data, especially if they are set to play in high definition. This can be a problem for users with limited data plans or slow connections, who may experience slow or interrupted playback.
- Annoyance factor: Autoplaying videos can be annoying for users, especially if they are accompanied by sound. This can lead to a negative perception of the website and decreased engagement.
- Reduced accessibility: Autoplaying videos can be a problem for users with accessibility needs, such as users who are blind or have hearing difficulties.
- Increased page load time: Autoplaying videos can increase the overall page load time, leading to a slower user experience.
- Decreased battery life: Autoplaying videos can consume a lot of battery power, especially on mobile devices, leading to reduced battery life.
In order to minimise the impact of autoplaying videos on the user experience, it is recommended to use them sparingly and only when necessary. It is also important to provide users with the option to turn off autoplaying videos and to allow them to control the playback of videos on the page. Additionally, videos should be optimised for performance and should be accompanied by captions or transcripts to improve accessibility.
View details
| 5c5459a78d9ae543ef05aef9fea46987 | 2 MB | 19% |
| 5c5459a78d9ae543ef05aef9fea46987 | 29 KB | 0% |
Assets that need text compression enabled396 KB0.102g
By enabling text compression on 4 items, , roughly 396.2 KB could be removed from the page load.
View details
| pubads_impl.js | 529 KB | 348 KB |
| prebid-config.json | 51 KB | 44 KB |
| uid2SecureSignal.js | 3 KB | 2 KB |
| 3zcdIyo2Tk.js | 3 KB | 2 KB |
Subset large font files8 KB0.002g
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:
- 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.
- 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
| eva-bold.woff2 | ~25 KB | ~8 KB |
Remove third party font files
Font files should be loaded from the same hosting as the website because
- 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.
- 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.
- 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
| resourcesssl.newscdn.com.au | eva-bold.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:
- 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.
- 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.
- 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.
- 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.
- 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.
| Mobile | Desktop | |
|---|---|---|
| Score | 89% | 100% |
| Timing | 1.8 s | 0.5 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
| Mobile | Desktop | |
|---|---|---|
| Score | 18% | 87% |
| Timing | 5.6 s | 1.3 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.
| Mobile | Desktop | |
|---|---|---|
| Score | 4% | 8% |
| Timing | 2,610 ms | 850 ms |
Speed Index
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
| Mobile | Desktop | |
|---|---|---|
| Score | 9% | 3% |
| Timing | 9.9 s | 5.0 s |
Optimize DOM size
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size.
| Mobile | Desktop | |
|---|---|---|
| Score | 0% | 100% |
LCP request discovery
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
| Mobile | Desktop | |
|---|---|---|
| Score | 0% | 0% |
Third parties
Third party code can significantly impact load performance. Reduce and defer loading of third party code to prioritize your page's content.
| Mobile | Desktop | |
|---|---|---|
| Score | 0% | 0% |
Optimize viewport for mobile
Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.
| Mobile | Desktop | |
|---|---|---|
| Score | 0% | 100% |
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.
| Mobile | Desktop | |
|---|---|---|
| Score | 0% | 0% |
| Timing | 55.5 s | 13.5 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.
| Mobile | Desktop | |
|---|---|---|
| Score | 16% | 69% |
| Timing | 420 ms | 190 ms |
Insights
Carbon footprint
The carbon footprint of a website can be calculated by estimating the amount of energy consumed by the data center hosting the website, as well as the energy consumed by users accessing the site. Factors that can influence a website’s carbon footprint include the size of the site, the amount of traffic it receives, and the technology and hosting infrastructure used to host the site.
| Mobile | Desktop | |
|---|---|---|
| Rating | F | F |
| Green Hosting | No | No |
| Dirtier than | 89% | 90% |
| CO2 per page load | 2.02g | 2.17g |
| CO2 wasted per page load | ~0.7g | ~0.7g |
| Transfer size | 7.67MB | 8.20MB |
| Transfer size percentile | 88% | 88% |
| Size wasted | 1.82 MB | 1.71 MB |
Tracking scripts
All the tracking scripts on the site generated ~2 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
| securepubads.g.doubleclick.net | 13 | 648 KB |
| idgets.outbrain.com | 8 | 118 KB |
| idget-pixels.outbrain.com | 1 | 577 B |
| mv.outbrain.com | 4 | 16 KB |
| amplify.outbrain.com | 2 | 10 KB |
| tags.tiqcdn.com | 11 | 111 KB |
| ave.outbrain.com | 1 | 539 B |
| tr.outbrain.com | 1 | 293 B |
| connect.facebook.net | 2 | 92 KB |
| sb.scorecardresearch.com | 4 | 2 KB |
| googletagmanager.com | 6 | 489 KB |
| c.amazon-adsystem.com | 3 | 90 KB |
| 8228261.fls.doubleclick.net | 4 | 4 KB |
| snap.licdn.com | 1 | 15 KB |
| sc-static.net | 2 | 48 KB |
| acdn.adnxs.com | 2 | 26 KB |
| px.ads.linkedin.com | 6 | 5 KB |
| linkedin.com | 1 | 1 KB |
| google-analytics.com | 4 | 24 KB |
| tr.snapchat.com | 6 | 3 KB |
| ct.pinterest.com | 4 | 4 KB |
| ib.adnxs.com | 9 | 7 KB |
| match.adsrvr.org | 11 | 8 KB |
| beacon.krxd.net | 1 | 0 B |
| aa.agkn.com | 2 | 2 KB |
| x.bidswitch.net | 13 | 8 KB |
| dis.criteo.com | 2 | 1,006 B |
| cm.g.doubleclick.net | 15 | 10 KB |
| dsp-cookie.adfarm1.adition.com | 1 | 646 B |
| ps.eyeota.net | 8 | 5 KB |
| pixel.rubiconproject.com | 15 | 25 KB |
| loadus.exelator.com | 3 | 3 KB |
| ssum-sec.casalemedia.com | 5 | 7 KB |
| image8.pubmatic.com | 3 | 3 KB |
| u.openx.net | 2 | 2 KB |
| ups.analytics.yahoo.com | 3 | 2 KB |
| ad.360yield.com | 2 | 1 KB |
| s.ad.smaato.net | 1 | 618 B |
| ssbsync.smartadserver.com | 1 | 602 B |
| c.bing.com | 1 | 964 B |
| pixel-sync.sitescout.com | 2 | 2 KB |
| cms.quantserve.com | 4 | 2 KB |
| bh.contextweb.com | 1 | 2 KB |
| trace.mediago.io | 1 | 731 B |
| cm.rtbsystem.com | 1 | 2 KB |
| rtb.adentifi.com | 1 | 51 B |
| pxl.iqm.com | 1 | 953 B |
| sync.1rx.io | 1 | 454 B |
| cs.media.net | 1 | 814 B |
| cs.admanmedia.com | 1 | 0 B |
| csync.loopme.me | 2 | 1 KB |
| temu.com | 1 | 880 B |
| sync.teads.tv | 1 | 727 B |
| sync.outbrain.com | 28 | 6 KB |
| redditstatic.com | 2 | 20 KB |
| script.crazyegg.com | 2 | 4 KB |
| js.adsrvr.org | 3 | 9 KB |
| google.com | 5 | 4 KB |
| googleads.g.doubleclick.net | 4 | 10 KB |
| td.doubleclick.net | 5 | 7 KB |
| googleadservices.com | 1 | 3 KB |
| pippio.com | 2 | 1 KB |
| logx.optimizely.com | 1 | 566 B |
| image2.pubmatic.com | 13 | 8 KB |
| facebook.com | 1 | 447 B |
| 14643376.fls.doubleclick.net | 2 | 2 KB |
| ad.doubleclick.net | 1 | 2 KB |
| insight.adsrvr.org | 4 | 3 KB |
| alb.reddit.com | 1 | 846 B |
| google.com.au | 4 | 2 KB |
| image4.pubmatic.com | 2 | 1,001 B |
| config.aps.amazon-adsystem.com | 1 | 896 B |
| aax.amazon-adsystem.com | 1 | 580 B |
| newscorpau.sc.omtrdc.net | 1 | 418 B |
| cm.everesttech.net | 1 | 554 B |
| ads.pubmatic.com | 5 | 30 KB |
| htlb.casalemedia.com | 1 | 959 B |
| hbopenbid.pubmatic.com | 1 | 586 B |
| dsum-sec.casalemedia.com | 8 | 8 KB |
| s.amazon-adsystem.com | 14 | 10 KB |
| pixel.tapad.com | 5 | 6 KB |
| rtb.gumgum.com | 1 | 1 KB |
| eb2.3lift.com | 2 | 1 KB |
| secure.adnxs.com | 2 | 2 KB |
| image6.pubmatic.com | 7 | 14 KB |
| us-u.openx.net | 1 | 603 B |
| c1.adform.net | 4 | 3 KB |
| uipglob.semasio.net | 2 | 1 KB |
| um.simpli.fi | 2 | 2 KB |
| simage2.pubmatic.com | 21 | 13 KB |
| b1sync.outbrain.com | 1 | 786 B |
| dsp.360yield.com | 1 | 489 B |
| dsum.casalemedia.com | 2 | 2 KB |
| aax-eu.amazon-adsystem.com | 1 | 855 B |
| sync.ipredictive.com | 2 | 1 KB |
| pixel.onaudience.com | 1 | 349 B |
| simage4.pubmatic.com | 6 | 2 KB |
| d.turn.com | 1 | 612 B |
| ssum.casalemedia.com | 1 | 1 KB |
| sync-tm.everesttech.net | 20 | 12 KB |
| i.w55c.net | 1 | 806 B |
| pm.w55c.net | 2 | 2 KB |
| dpm.demdex.net | 1 | 1 KB |
| p.rfihub.com | 2 | 2 KB |
| beacon.lynx.cognitivlabs.com | 2 | 796 B |
| a.tribalfusion.com | 1 | 947 B |
| sync.mathtag.com | 1 | 951 B |
| s.tribalfusion.com | 1 | 510 B |
| usermatch.krxd.net | 1 | 0 B |
| tags.bluekai.com | 1 | 0 B |
| cs.iqzone.com | 1 | 629 B |
| trc.taboola.com | 1 | 589 B |
Opportunities
Remove autoplaying or preloaded media files2 videos1.6 MB0.41g CO2
By removing 2 autoplaying or preloaded videos, roughly 1.6 MB could be removed from the page load.
This would reduce the page transfer size by 19% and reduce the pages emissions from 2.17 grams of CO2 to 1.75 grams of CO2.
Autoplaying videos can have a negative impact on the user experience for several reasons:
- Increased data usage: Autoplaying videos can consume a lot of data, especially if they are set to play in high definition. This can be a problem for users with limited data plans or slow connections, who may experience slow or interrupted playback.
- Annoyance factor: Autoplaying videos can be annoying for users, especially if they are accompanied by sound. This can lead to a negative perception of the website and decreased engagement.
- Reduced accessibility: Autoplaying videos can be a problem for users with accessibility needs, such as users who are blind or have hearing difficulties.
- Increased page load time: Autoplaying videos can increase the overall page load time, leading to a slower user experience.
- Decreased battery life: Autoplaying videos can consume a lot of battery power, especially on mobile devices, leading to reduced battery life.
In order to minimise the impact of autoplaying videos on the user experience, it is recommended to use them sparingly and only when necessary. It is also important to provide users with the option to turn off autoplaying videos and to allow them to control the playback of videos on the page. Additionally, videos should be optimised for performance and should be accompanied by captions or transcripts to improve accessibility.
View details
| 5c5459a78d9ae543ef05aef9fea46987 | 2 MB | 19% |
| 5c5459a78d9ae543ef05aef9fea46987 | 29 KB | 0% |
Assets that need text compression enabled396 KB0.102g
By enabling text compression on 4 items, , roughly 396.2 KB could be removed from the page load.
View details
| pubads_impl.js | 529 KB | 348 KB |
| prebid-config.json | 51 KB | 44 KB |
| uid2SecureSignal.js | 3 KB | 2 KB |
| 3zcdIyo2Tk.js | 3 KB | 2 KB |
Subset large font files8 KB0.002g
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:
- 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.
- 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
| eva-bold.woff2 | ~25 KB | ~8 KB |
Remove third party font files
Font files should be loaded from the same hosting as the website because
- 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.
- 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.
- 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
| resourcesssl.newscdn.com.au | eva-bold.woff2 |
Dirty hosting0.29g CO2
This page generated ~2.17grams of CO2
By moving to a host using renewable energy, this could be reduced to ~1.88grams of CO2.
Sustainable web hosting refers to hosting services that are designed to minimise their impact on the environment and to promote sustainability. This can include using renewable energy sources, reducing waste and emissions, and implementing best practices for energy efficiency.
Sustainable web hosting providers aim to reduce their carbon footprint by using energy-efficient server hardware, data centres, and networking equipment, as well as implementing environmentally friendly policies and practices. For example, some providers may use renewable energy sources, such as wind or solar power, to power their data centres, or they may use high-efficiency cooling systems to reduce energy consumption.
Insights
Google Lighthouse Accessibility
The accessibility score in Google Lighthouse is a metric that measures how well a website is designed for users with disabilities. The score ranges from 0 to 100, with higher scores indicating better accessibility.
Google Lighthouse evaluates a website’s accessibility based on a number of different factors, such as the presence of alternative text for images, the use of semantic HTML, the ability to navigate the page using only a keyboard, and the use of appropriate color contrasts.
A high accessibility score in Google Lighthouse indicates that a website is well-designed for users with disabilities and provides an inclusive user experience. On the other hand, a low accessibility score can indicate that a website has barriers that make it difficult or impossible for some users to access and use the content.
In automated testing, this page scored 80% for accessibility on desktop. Keep in mind that automated accessibility testing is not perfect and that manual tests, use case testing, or usability testing should be completed as well.
- Mobile Accessibility
- 89%
- Desktop Accessibility
- 88%
Opportunities
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
<frame> or <iframe> elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
Insights
Google Lighthouse Best Practices
Google Lighthouse evaluates a website’s best practices based on a number of different factors, such as the use of HTTPS encryption, the use of efficient caching policies, the implementation of modern web technologies, and the avoidance of deprecated technologies.
A high best practices score in Google Lighthouse indicates that a website is well-designed and follows best practices for web development, which can lead to better performance, security, and accessibility. On the other hand, a low best practices score can indicate that a website has room for improvement in terms of following best practices.
- Mobile Best Practices
- 39%
- Desktop Best Practices
- 56%
Google Lighthouse SEO
Google Lighthouse evaluates a website’s SEO based on a number of different factors, such as the presence of title and description tags, the use of header tags, the presence of structured data, the use of image alt tags, and the use of crawlable links.
A high SEO score in Google Lighthouse indicates that a website is well-optimized for search engines, which can help to improve its visibility in search results and increase its organic traffic. On the other hand, a low SEO score can indicate that a website has room for improvement in terms of its optimization for search engines.
While a high SEO score can help to improve a website’s visibility in search results, it’s not a guarantee of higher rankings, as search engine algorithms take many other factors into account when determining the ranking of a website.
- Mobile SEO
- 100%
- Desktop SEO
- 100%
Tracking scripts
All the tracking scripts on the site generated ~2 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
| securepubads.g.doubleclick.net | 13 | 648 KB |
| idgets.outbrain.com | 8 | 118 KB |
| idget-pixels.outbrain.com | 1 | 577 B |
| mv.outbrain.com | 4 | 16 KB |
| amplify.outbrain.com | 2 | 10 KB |
| tags.tiqcdn.com | 11 | 111 KB |
| ave.outbrain.com | 1 | 539 B |
| tr.outbrain.com | 1 | 293 B |
| connect.facebook.net | 2 | 92 KB |
| sb.scorecardresearch.com | 4 | 2 KB |
| googletagmanager.com | 6 | 489 KB |
| c.amazon-adsystem.com | 3 | 90 KB |
| 8228261.fls.doubleclick.net | 4 | 4 KB |
| snap.licdn.com | 1 | 15 KB |
| sc-static.net | 2 | 48 KB |
| acdn.adnxs.com | 2 | 26 KB |
| px.ads.linkedin.com | 6 | 5 KB |
| linkedin.com | 1 | 1 KB |
| google-analytics.com | 4 | 24 KB |
| tr.snapchat.com | 6 | 3 KB |
| ct.pinterest.com | 4 | 4 KB |
| ib.adnxs.com | 9 | 7 KB |
| match.adsrvr.org | 11 | 8 KB |
| beacon.krxd.net | 1 | 0 B |
| aa.agkn.com | 2 | 2 KB |
| x.bidswitch.net | 13 | 8 KB |
| dis.criteo.com | 2 | 1,006 B |
| cm.g.doubleclick.net | 15 | 10 KB |
| dsp-cookie.adfarm1.adition.com | 1 | 646 B |
| ps.eyeota.net | 8 | 5 KB |
| pixel.rubiconproject.com | 15 | 25 KB |
| loadus.exelator.com | 3 | 3 KB |
| ssum-sec.casalemedia.com | 5 | 7 KB |
| image8.pubmatic.com | 3 | 3 KB |
| u.openx.net | 2 | 2 KB |
| ups.analytics.yahoo.com | 3 | 2 KB |
| ad.360yield.com | 2 | 1 KB |
| s.ad.smaato.net | 1 | 618 B |
| ssbsync.smartadserver.com | 1 | 602 B |
| c.bing.com | 1 | 964 B |
| pixel-sync.sitescout.com | 2 | 2 KB |
| cms.quantserve.com | 4 | 2 KB |
| bh.contextweb.com | 1 | 2 KB |
| trace.mediago.io | 1 | 731 B |
| cm.rtbsystem.com | 1 | 2 KB |
| rtb.adentifi.com | 1 | 51 B |
| pxl.iqm.com | 1 | 953 B |
| sync.1rx.io | 1 | 454 B |
| cs.media.net | 1 | 814 B |
| cs.admanmedia.com | 1 | 0 B |
| csync.loopme.me | 2 | 1 KB |
| temu.com | 1 | 880 B |
| sync.teads.tv | 1 | 727 B |
| sync.outbrain.com | 28 | 6 KB |
| redditstatic.com | 2 | 20 KB |
| script.crazyegg.com | 2 | 4 KB |
| js.adsrvr.org | 3 | 9 KB |
| google.com | 5 | 4 KB |
| googleads.g.doubleclick.net | 4 | 10 KB |
| td.doubleclick.net | 5 | 7 KB |
| googleadservices.com | 1 | 3 KB |
| pippio.com | 2 | 1 KB |
| logx.optimizely.com | 1 | 566 B |
| image2.pubmatic.com | 13 | 8 KB |
| facebook.com | 1 | 447 B |
| 14643376.fls.doubleclick.net | 2 | 2 KB |
| ad.doubleclick.net | 1 | 2 KB |
| insight.adsrvr.org | 4 | 3 KB |
| alb.reddit.com | 1 | 846 B |
| google.com.au | 4 | 2 KB |
| image4.pubmatic.com | 2 | 1,001 B |
| config.aps.amazon-adsystem.com | 1 | 896 B |
| aax.amazon-adsystem.com | 1 | 580 B |
| newscorpau.sc.omtrdc.net | 1 | 418 B |
| cm.everesttech.net | 1 | 554 B |
| ads.pubmatic.com | 5 | 30 KB |
| htlb.casalemedia.com | 1 | 959 B |
| hbopenbid.pubmatic.com | 1 | 586 B |
| dsum-sec.casalemedia.com | 8 | 8 KB |
| s.amazon-adsystem.com | 14 | 10 KB |
| pixel.tapad.com | 5 | 6 KB |
| rtb.gumgum.com | 1 | 1 KB |
| eb2.3lift.com | 2 | 1 KB |
| secure.adnxs.com | 2 | 2 KB |
| image6.pubmatic.com | 7 | 14 KB |
| us-u.openx.net | 1 | 603 B |
| c1.adform.net | 4 | 3 KB |
| uipglob.semasio.net | 2 | 1 KB |
| um.simpli.fi | 2 | 2 KB |
| simage2.pubmatic.com | 21 | 13 KB |
| b1sync.outbrain.com | 1 | 786 B |
| dsp.360yield.com | 1 | 489 B |
| dsum.casalemedia.com | 2 | 2 KB |
| aax-eu.amazon-adsystem.com | 1 | 855 B |
| sync.ipredictive.com | 2 | 1 KB |
| pixel.onaudience.com | 1 | 349 B |
| simage4.pubmatic.com | 6 | 2 KB |
| d.turn.com | 1 | 612 B |
| ssum.casalemedia.com | 1 | 1 KB |
| sync-tm.everesttech.net | 20 | 12 KB |
| i.w55c.net | 1 | 806 B |
| pm.w55c.net | 2 | 2 KB |
| dpm.demdex.net | 1 | 1 KB |
| p.rfihub.com | 2 | 2 KB |
| beacon.lynx.cognitivlabs.com | 2 | 796 B |
| a.tribalfusion.com | 1 | 947 B |
| sync.mathtag.com | 1 | 951 B |
| s.tribalfusion.com | 1 | 510 B |
| usermatch.krxd.net | 1 | 0 B |
| tags.bluekai.com | 1 | 0 B |
| cs.iqzone.com | 1 | 629 B |
| trc.taboola.com | 1 | 589 B |
Cost to load
| Price per GB (USD) | $3.12 |
|---|---|
| Price per GB (Local) | 3.12 USD |
| Price to load PPV (USD) | $0.023 |
| Price to load PPV (Local) | 0.023 USD |
2022 Mobile data pricing sourced from cable.co.uk
Opportunities
Security headers to set3/6
HTTP security headers are special HTTP headers that can be added to a website’s response to help improve its security. They are important because they can help to protect a website and its users from various security threats, such as cross-site scripting (XSS) attacks, cross-site request forgery (CSRF) attacks, and other types of malicious activity.
It’s important to note, however, that implementing HTTP security headers is just one aspect of a comprehensive security strategy, and that other measures, such as regular software updates, secure coding practices, and regular security audits, are also important for maintaining a secure website.
View details
It's important to note, however, that implementing HTTP security headers is just one aspect of a comprehensive security strategy, and that other measures, such as regular software updates, secure coding practices, and regular security audits, are also important for maintaining a secure website.
Switch to a privacy focussed analytics platform
Google Analytics collects data on website users and their behaviour, which can raise privacy concerns for some visitors. Website owners who use Google Analytics have access to a range of data points, including IP addresses, browser types, device information, and user behaviour on the site.
While Google Analytics does provide some tools to help website owners protect the privacy of their visitors, such as data retention controls and the ability to enable IP address anonymisation, it’s important for website owners to be transparent about the data they collect and how they use it. Website owners should also take steps to ensure that any third-party tools they use, including Google Analytics, comply with relevant privacy laws and regulations.
Additionally, some users may choose to block Google Analytics tracking using ad-blocking software or browser extensions that prevent tracking cookies from being set. This can impact the accuracy of website analytics, but website owners should respect the privacy preferences of their visitors and provide alternative means for users to access the site and its content.
The following alternatives to Google Analytics are privacy focussed, meaning they don’t compromise the visitors privacy for the sake of data collection and reporting.
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Pass |
| Insight | 1 insecure request found |
Uses deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
| Insight | 2 warnings found | 2 warnings found |
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
Issues were logged in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |