Gilgandra Shire Council
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
- 33%
- Desktop Performance
- 54%
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 | 12.7 s | 7.7 s | < 2.5 s |
| First Input Delay | 630 ms | 100 ms | < 100ms |
| Cumulative Layout Shift | 0.001 | 0.022 | 0.1 |
Tracking scripts
All the tracking scripts on the site generated ~287 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
| google-analytics.com | 4 | 43 KB |
| googletagmanager.com | 3 | 216 KB |
| js-agent.newrelic.com | 1 | 28 KB |
| bam.nr-data.net | 2 | 885 B |
Opportunities
Remove autoplaying or preloaded media files1 video105.2 KB0.02g CO2
By removing 1 autoplaying or preloaded videos, roughly 105.2 KB could be removed from the page load.
This would reduce the page transfer size by 1% and reduce the pages emissions from 2.44 grams of CO2 to 2.42 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
| Telerik.Web.UI.WebResource.axd | 105 KB | 1% |
Assets that need text compression enabled18 KB0.004g
By enabling text compression on 4 items, , roughly 18.4 KB could be removed from the page load.
View details
| WebResource.axd | 10 KB | 8 KB |
| WebResource.axd | 6 KB | 4 KB |
| WebResource.axd | 5 KB | 4 KB |
| WebResource.axd | 3 KB | 2 KB |
Optimise images8 MB1.847g
By optimising the following images, roughly 8 MB could be removed from the transfer size, about 76%. This would reduce the CO2 generated per page load from 2.44g grams to 0.59 grams.
Images should be optimised for the web for several reasons:
- 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.
- Improved user experience: Optimising images can help to improve the overall user experience, as pages with optimised images load faster and are more responsive.
- Lower emissions: Optimising images can help to reduce the emissions associated with data transfer, as less data needs to be transmitted over the network.
- Better accessibility: Optimising images can make them more accessible to users with slower connections or limited data plans.
View details
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 | 6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2 |
| fonts.gstatic.com | 6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdu3cOWxw.woff2 |
| fonts.gstatic.com | 6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdu3cOWxw.woff2 |
| fonts.gstatic.com | UqyNK9UOIntux_czAvDQx_ZcHqZXBNQzdcD55TecYQ.woff2 |
| fonts.gstatic.com | 6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdu3cOWxw.woff2 |
Replace jQuery and jQuery libraries with more modern code169 KB0.04g
jQuery is a popular and widely-used JavaScript library that simplifies web development by providing a set of tools and functions to interact with HTML documents, handle events, create animations, and make asynchronous HTTP requests.
In the past, jQuery was a very popular choice for web development because it simplified many common tasks and provided a consistent and cross-browser-compatible API. However, with the advancement of modern web technologies and improvements in browser capabilities, the need for jQuery has decreased.
Many modern web frameworks and libraries, such as React and Angular, provide their own set of tools for handling common tasks and interacting with the DOM, making jQuery less necessary in many cases. The Javascript engine in modern browsers have also become more consistent in the feature implementations often eliminating the need for a library like jQuery.
jQuery represents an opportunity because:
- Performance: While jQuery is a powerful and useful library, it can slow down website performance due to its large size and complex code. Modern browsers have also improved their native support for many of the features that jQuery provides, reducing the need for it.
- Maintainability: jQuery code can be difficult to maintain and update, particularly as web technologies evolve and change. This can make it harder for developers to keep up with best practices and standards for web development.
- Accessibility: Some jQuery plugins and features can create accessibility issues, particularly for users who rely on assistive technologies. This can make it harder for people with disabilities to use and access websites.
View details
| jquery.min.js | 34 KB |
| jquery.min.js | 31 KB |
| jquery-migrate.js | 6 KB |
| jquery.main.js | 98 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:
- 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 | 1% | 1% |
| Timing | 7.5 s | 3.9 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 | 0% | 1% |
| Timing | 12.7 s | 7.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 | 24% | 95% |
| Timing | 1,090 ms | 110 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 | 2% | 2% |
| Timing | 13.4 s | 5.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 | 5% | 16% |
| Timing | 16.4 s | 7.1 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 | 3% | 96% |
| Timing | 630 ms | 100 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 | 6% | 1% |
| Timing | 7.5 s | 3.9 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 | 17% | 28% |
| Insight | Potential savings of 3,460 ms | Potential savings of 2,130 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 | 100% | 35% |
| Insight | Potential savings of 662 KiB |
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
| Mobile | Desktop | |
|---|---|---|
| Score | 89% | 100% |
| Insight | Potential savings of 18 KiB | Potential savings of 18 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 | 35% | 85% |
| Insight | Potential savings of 154 KiB | Potential savings of 155 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 | 27% | 72% |
| Insight | Potential savings of 384 KiB | Potential savings of 383 KiB |
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
| Mobile | Desktop | |
|---|---|---|
| Score | 77% | 80% |
| Insight | Potential savings of 26 KiB | Potential savings of 156 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 | 1% | 19% |
| Insight | Potential savings of 3,613 KiB | Potential savings of 4,051 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 | 75% | 96% |
| Insight | Potential savings of 18 KiB | Potential savings of 18 KiB |
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
| Mobile | Desktop | |
|---|---|---|
| Score | 40% | 63% |
| Insight | Potential savings of 1,340 ms | Potential savings of 580 ms |
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.
| Mobile | Desktop | |
|---|---|---|
| Score | 0% | 0% |
| Insight | Total size was 10,154 KiB | Total size was 10,912 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 | 35% | 26% |
| Insight | 20 resources found | 22 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 | 84% | 85% |
| Insight | 907 elements | 905 elements |
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 | 45% | 96% |
| Timing | 3.8 s | 0.9 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 | 19% | 82% |
| Timing | 6.3 s | 2.4 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 |
Minimize third-party usage
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 | Pass |
| Insight | Third-party code blocked the main thread for 900 ms | Third-party code blocked the main thread for 10 ms |
Does not use 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.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
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 | 92% | 94% |
| CO2 per page load | 2.27g | 2.44g |
| CO2 wasted per page load | ~1.8g | ~1.9g |
| Transfer size | 9.92MB | 10.66MB |
| Transfer size percentile | 92% | 92% |
| Size wasted | 7.98 MB | 8.17 MB |
Sustainable hosting
By hosting this site on a server powered by renewable energy, this page generated ~2.44grams of CO2 instead of ~2.81grams 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 ~287 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
| google-analytics.com | 4 | 43 KB |
| googletagmanager.com | 3 | 216 KB |
| js-agent.newrelic.com | 1 | 28 KB |
| bam.nr-data.net | 2 | 885 B |
Opportunities
Remove autoplaying or preloaded media files1 video105.2 KB0.02g CO2
By removing 1 autoplaying or preloaded videos, roughly 105.2 KB could be removed from the page load.
This would reduce the page transfer size by 1% and reduce the pages emissions from 2.44 grams of CO2 to 2.42 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
| Telerik.Web.UI.WebResource.axd | 105 KB | 1% |
Assets that need text compression enabled18 KB0.004g
By enabling text compression on 4 items, , roughly 18.4 KB could be removed from the page load.
View details
| WebResource.axd | 10 KB | 8 KB |
| WebResource.axd | 6 KB | 4 KB |
| WebResource.axd | 5 KB | 4 KB |
| WebResource.axd | 3 KB | 2 KB |
Optimise images8 MB1.847g
By optimising the following images, roughly 8 MB could be removed from the transfer size, about 76%. This would reduce the CO2 generated per page load from 2.44g grams to 0.59 grams.
Images should be optimised for the web for several reasons:
- 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.
- Improved user experience: Optimising images can help to improve the overall user experience, as pages with optimised images load faster and are more responsive.
- Lower emissions: Optimising images can help to reduce the emissions associated with data transfer, as less data needs to be transmitted over the network.
- Better accessibility: Optimising images can make them more accessible to users with slower connections or limited data plans.
View details
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 | 6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2 |
| fonts.gstatic.com | 6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdu3cOWxw.woff2 |
| fonts.gstatic.com | 6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdu3cOWxw.woff2 |
| fonts.gstatic.com | UqyNK9UOIntux_czAvDQx_ZcHqZXBNQzdcD55TecYQ.woff2 |
| fonts.gstatic.com | 6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdu3cOWxw.woff2 |
Replace jQuery and jQuery libraries with more modern code169 KB0.04g
jQuery is a popular and widely-used JavaScript library that simplifies web development by providing a set of tools and functions to interact with HTML documents, handle events, create animations, and make asynchronous HTTP requests.
In the past, jQuery was a very popular choice for web development because it simplified many common tasks and provided a consistent and cross-browser-compatible API. However, with the advancement of modern web technologies and improvements in browser capabilities, the need for jQuery has decreased.
Many modern web frameworks and libraries, such as React and Angular, provide their own set of tools for handling common tasks and interacting with the DOM, making jQuery less necessary in many cases. The Javascript engine in modern browsers have also become more consistent in the feature implementations often eliminating the need for a library like jQuery.
jQuery represents an opportunity because:
- Performance: While jQuery is a powerful and useful library, it can slow down website performance due to its large size and complex code. Modern browsers have also improved their native support for many of the features that jQuery provides, reducing the need for it.
- Maintainability: jQuery code can be difficult to maintain and update, particularly as web technologies evolve and change. This can make it harder for developers to keep up with best practices and standards for web development.
- Accessibility: Some jQuery plugins and features can create accessibility issues, particularly for users who rely on assistive technologies. This can make it harder for people with disabilities to use and access websites.
View details
| jquery.min.js | 34 KB |
| jquery.min.js | 31 KB |
| jquery-migrate.js | 6 KB |
| jquery.main.js | 98 KB |
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
- 97%
- Desktop Accessibility
- 97%
Opportunities
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
| 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
- 68%
- Desktop Best Practices
- 68%
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
- 79%
- Desktop SEO
- 75%
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
- 63%
- Desktop PWA
- 57%
Tracking scripts
All the tracking scripts on the site generated ~287 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
| google-analytics.com | 4 | 43 KB |
| googletagmanager.com | 3 | 216 KB |
| js-agent.newrelic.com | 1 | 28 KB |
| bam.nr-data.net | 2 | 885 B |
Cost to load
| Price per GB (USD) | $3.12 |
|---|---|
| Price per GB (Local) | 3.12 USD |
| Price to load PPV (USD) | $0.03 |
| Price to load PPV (Local) | 0.03 USD |
2022 Mobile data pricing sourced from cable.co.uk
Opportunities
Security headers to set5/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 |
Links do not have descriptive text
Links with descriptive text can provide users with more context about the content they are clicking on, which can help them to make informed decisions about whether to follow the link or not. This is especially important for users with disabilities, as screen readers can use the link text to provide an audio description of the content.
In addition, links with descriptive text can also improve the overall user experience, as users are more likely to know what to expect when they follow a link. This can reduce the likelihood of users bouncing back from a page after finding that it’s not what they were looking for, which can help to improve the user engagement and retention on a website.
Furthermore, descriptive links can also help to improve a website\’s search engine optimisation (SEO). Search engines use the link text and surrounding context to understand the content of a page, and this information is used to determine the relevance of a page for specific search queries. Descriptive links can help search engines to understand the content of a page more accurately, which can improve its visibility and ranking in search results.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
| Insight | 1 link found | 1 link found |
robots.txt is not valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
| Insight | 191 errors found | 191 errors found |
Does not use 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 | Fail |
| Insight | 1 insecure request found | 1 insecure request found |
Registers an unload listener
The unload event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use pagehide or visibilitychange events instead. Learn more about unload event listeners
| 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 |