NSW Government
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
- 66%
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.0 s | 2.7 s | < 2.5 s |
| First Input Delay | 680 ms | 240 ms | < 100ms |
| Cumulative Layout Shift | 0.001 | 0 | 0.1 |
Tracking scripts
All the tracking scripts on the site generated ~776 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
| assets.adobedtm.com | 1 | 145 KB |
| googletagmanager.com | 4 | 369 KB |
| cm.everesttech.net | 1 | 543 B |
| customerservice.tt.omtrdc.net | 1 | 9 KB |
| snap.licdn.com | 2 | 9 KB |
| connect.facebook.net | 2 | 189 KB |
| analytics.google.com | 3 | 0 B |
| stats.g.doubleclick.net | 4 | 570 B |
| google-analytics.com | 2 | 21 KB |
| cdn.linkedin.oribi.io | 1 | 468 B |
| px.ads.linkedin.com | 3 | 3 KB |
| facebook.com | 2 | 328 B |
| content.hotjar.io | 1 | 205 B |
| linkedin.com | 1 | 4 KB |
| google.com | 1 | 557 B |
| js-agent.newrelic.com | 1 | 24 KB |
| bam.nr-data.net | 1 | 463 B |
Opportunities
Assets that need text compression enabled100 KB0.022g
By enabling text compression on 1 items, , roughly 99.8 KB could be removed from the page load.
View details
| / | 134 KB | 100 KB |
Replace icon font files126 KB0.03g
Font icons can have a negative impact on performance and emissions because they can increase the size of the page and the amount of data that needs to be downloaded. Some specific reasons why font icons can be bad for performance and emissions include:
- Increased file size: Font icons are typically included as part of a web font, which can be a large file that needs to be downloaded. This can increase the overall size of the page, leading to slower load times and higher emissions.
- Inefficient rendering: Web fonts are sometimes loaded and rendered inefficiently, which can result in slow performance and higher emissions.
- Unused icons: Font icons often include a large number of icons that may not be used on a particular page, increasing the file size and leading to inefficient use of resources.
While icon fonts are still widely used on the web, and they can be a useful tool for adding icons to a website. it is a dated practice when there are better options such as SVG icons, which can be more efficient and have a lower impact on performance and emissions.
View details
| flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2 | 126 KB |
Subset large font files19 KB0.004g
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
| ijwTs572Xtc6ZYQws9YVwnNDTJzax8s3Jik.woff2 | ~28 KB | ~11 KB |
| ijwRs572Xtc6ZYQws9YVwnNGfJ7QwOk1.woff2 | ~26 KB | ~9 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
| fonts.gstatic.com | ijwRs572Xtc6ZYQws9YVwnNGfJ7QwOk1.woff2 |
| fonts.gstatic.com | flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2 |
| fonts.gstatic.com | ijwTs572Xtc6ZYQws9YVwnNDTJzax8s3Jik.woff2 |
| onegov.nsw.gov.au | ogf.ttf |
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 | 24% | 84% |
| Timing | 3.9 s | 1.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
| Mobile | Desktop | |
|---|---|---|
| Score | 27% | 41% |
| Timing | 5.0 s | 2.7 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 | 0% | 51% |
| Timing | 5,020 ms | 340 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 | 24% | 75% |
| Timing | 7.8 s | 1.7 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.
| Mobile | Desktop | |
|---|---|---|
| Score | 3% | 46% |
| Timing | 19.1 s | 4.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.
| Mobile | Desktop | |
|---|---|---|
| Score | 2% | 53% |
| Timing | 680 ms | 240 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.
| Mobile | Desktop | |
|---|---|---|
| Score | 51% | 62% |
| Timing | 3.9 s | 1.4 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.
| Mobile | Desktop | |
|---|---|---|
| Score | 29% | 65% |
| Insight | Potential savings of 2,030 ms | Potential savings of 530 ms |
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
| Mobile | Desktop | |
|---|---|---|
| Score | 45% | 80% |
| Insight | Potential savings of 222 KiB | Potential savings of 179 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.
| Mobile | Desktop | |
|---|---|---|
| Score | 45% | 99% |
| Insight | Potential savings of 342 KiB | Potential savings of 116 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.
| Mobile | Desktop | |
|---|---|---|
| Score | 100% | 81% |
| Insight | Potential savings of 25 KiB | Potential savings of 24 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.
| Mobile | Desktop | |
|---|---|---|
| Score | 21% | 82% |
| Insight | Potential savings of 499 KiB | Potential savings of 498 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.
| Mobile | Desktop | |
|---|---|---|
| Score | 45% | 71% |
| Insight | Potential savings of 241 KiB | Potential savings of 169 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.
| Mobile | Desktop | |
|---|---|---|
| Score | 68% | 94% |
| Insight | Potential savings of 100 KiB | Potential savings of 100 KiB |
Avoids enormous network payloads
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
| Mobile | Desktop | |
|---|---|---|
| Score | 91% | 93% |
| Insight | Total size was 2,615 KiB | Total size was 2,488 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.
| Mobile | Desktop | |
|---|---|---|
| Score | 15% | 15% |
| Insight | 13 resources found | 13 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.
| Mobile | Desktop | |
|---|---|---|
| Score | 57% | 57% |
| Insight | 1,297 elements | 1,292 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.
| Mobile | Desktop | |
|---|---|---|
| Score | 10% | 85% |
| Timing | 9.4 s | 1.5 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
| Mobile | Desktop | |
|---|---|---|
| Score | 0% | 64% |
| Timing | 17.8 s | 3.3 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.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
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.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
| Insight | Third-party code blocked the main thread for 3,930 ms | Third-party code blocked the main thread for 300 ms |
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
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
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 | |
|---|---|---|
| Grade | F | F |
| Green Hosting | Yes | Yes |
| Dirtier than | 63% | 61% |
| CO2 per page load | 0.58g | 0.56g |
| CO2 wasted per page load | ~0.1g | ~0.1g |
| Transfer size | 2.55MB | 2.43MB |
| Transfer size percentile | 59% | 52% |
| Size wasted | 616.17 KB | 503.18 KB |
Sustainable hosting
By hosting this site on a server powered by renewable energy, this page generated ~0.56grams of CO2 instead of ~0.64grams 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.
Tracking scripts
All the tracking scripts on the site generated ~776 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
| assets.adobedtm.com | 1 | 145 KB |
| googletagmanager.com | 4 | 369 KB |
| cm.everesttech.net | 1 | 543 B |
| customerservice.tt.omtrdc.net | 1 | 9 KB |
| snap.licdn.com | 2 | 9 KB |
| connect.facebook.net | 2 | 189 KB |
| analytics.google.com | 3 | 0 B |
| stats.g.doubleclick.net | 4 | 570 B |
| google-analytics.com | 2 | 21 KB |
| cdn.linkedin.oribi.io | 1 | 468 B |
| px.ads.linkedin.com | 3 | 3 KB |
| facebook.com | 2 | 328 B |
| content.hotjar.io | 1 | 205 B |
| linkedin.com | 1 | 4 KB |
| google.com | 1 | 557 B |
| js-agent.newrelic.com | 1 | 24 KB |
| bam.nr-data.net | 1 | 463 B |
Opportunities
Assets that need text compression enabled100 KB0.022g
By enabling text compression on 1 items, , roughly 99.8 KB could be removed from the page load.
View details
| / | 134 KB | 100 KB |
Replace icon font files126 KB0.03g
Font icons can have a negative impact on performance and emissions because they can increase the size of the page and the amount of data that needs to be downloaded. Some specific reasons why font icons can be bad for performance and emissions include:
- Increased file size: Font icons are typically included as part of a web font, which can be a large file that needs to be downloaded. This can increase the overall size of the page, leading to slower load times and higher emissions.
- Inefficient rendering: Web fonts are sometimes loaded and rendered inefficiently, which can result in slow performance and higher emissions.
- Unused icons: Font icons often include a large number of icons that may not be used on a particular page, increasing the file size and leading to inefficient use of resources.
While icon fonts are still widely used on the web, and they can be a useful tool for adding icons to a website. it is a dated practice when there are better options such as SVG icons, which can be more efficient and have a lower impact on performance and emissions.
View details
| flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2 | 126 KB |
Subset large font files19 KB0.004g
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
| ijwTs572Xtc6ZYQws9YVwnNDTJzax8s3Jik.woff2 | ~28 KB | ~11 KB |
| ijwRs572Xtc6ZYQws9YVwnNGfJ7QwOk1.woff2 | ~26 KB | ~9 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
| fonts.gstatic.com | ijwRs572Xtc6ZYQws9YVwnNGfJ7QwOk1.woff2 |
| fonts.gstatic.com | flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2 |
| fonts.gstatic.com | ijwTs572Xtc6ZYQws9YVwnNDTJzax8s3Jik.woff2 |
| onegov.nsw.gov.au | ogf.ttf |
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
- 95%
- Desktop Accessibility
- 95%
Opportunities
[aria-*] attributes do not match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
| 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
- 100%
- Desktop Best Practices
- 100%
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
- 90%
- Desktop SEO
- 92%
Google Lighthouse PWA
The Progressive Web App (PWA) score in Google Lighthouse is a metric that measures the quality of a website as a progressive web app. The score ranges from 0 to 100, with higher scores indicating better performance and functionality as a PWA.
A progressive web app is a type of web application that combines the best features of both web and native apps, providing users with a fast, reliable, and engaging experience on any device.
Google Lighthouse evaluates a website’s PWA performance based on several key factors, such as the availability of a service worker, the presence of a web app manifest, the ability to install the app on the home screen, and the performance of the app under poor network conditions.
- Mobile PWA
- 88%
- Desktop PWA
- 86%
Tracking scripts
All the tracking scripts on the site generated ~776 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
| assets.adobedtm.com | 1 | 145 KB |
| googletagmanager.com | 4 | 369 KB |
| cm.everesttech.net | 1 | 543 B |
| customerservice.tt.omtrdc.net | 1 | 9 KB |
| snap.licdn.com | 2 | 9 KB |
| connect.facebook.net | 2 | 189 KB |
| analytics.google.com | 3 | 0 B |
| stats.g.doubleclick.net | 4 | 570 B |
| google-analytics.com | 2 | 21 KB |
| cdn.linkedin.oribi.io | 1 | 468 B |
| px.ads.linkedin.com | 3 | 3 KB |
| facebook.com | 2 | 328 B |
| content.hotjar.io | 1 | 205 B |
| linkedin.com | 1 | 4 KB |
| google.com | 1 | 557 B |
| js-agent.newrelic.com | 1 | 24 KB |
| bam.nr-data.net | 1 | 463 B |
Cost to load
| Price per GB (USD) | $3.12 |
|---|---|
| Price per GB (Local) | 3.12 USD |
| Price to load PPV (USD) | $0.008 |
| Price to load PPV (Local) | 0.008 USD |
2022 Mobile data pricing sourced from cable.co.uk
Opportunities
Security headers to set4/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.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |