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
- 29%
- Desktop Performance
- 23%
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 | 59.6 s | 8.2 s | < 2.5 s |
| First Input Delay | 460 ms | 450 ms | < 100ms |
| Cumulative Layout Shift | 0.081 | 0.257 | 0.1 |
Tracking scripts
All the tracking scripts on the site generated ~1 MB of data
A tracking script is a code snippet designed to track the flow of visitors who visit a website. Media, advertising, and analytics organisations will provide a script to add to your website that sends data directly to their servers. This data can then be used to measure goals and conversions, analyse user behaviour, and influence advertising campaigns.
Consider how much of this data you actually need and use? How often do you review the analytics data, and does this inform genuine change? Are you actively running social media campaigns? Consider pausing or removing tracking scripts that aren’t being actively used.
View details
| idgets.outbrain.com | 9 | 120 KB |
| securepubads.g.doubleclick.net | 19 | 700 KB |
| idget-pixels.outbrain.com | 1 | 577 B |
| mv.outbrain.com | 1 | 7 KB |
| static.cloudflareinsights.com | 1 | 7 KB |
| c.amazon-adsystem.com | 3 | 95 KB |
| ib.adnxs.com | 8 | 6 KB |
| match.adsrvr.org | 9 | 6 KB |
| aa.agkn.com | 2 | 2 KB |
| x.bidswitch.net | 7 | 5 KB |
| dis.criteo.com | 1 | 432 B |
| cm.g.doubleclick.net | 16 | 11 KB |
| dsp-cookie.adfarm1.adition.com | 1 | 631 B |
| ps.eyeota.net | 6 | 4 KB |
| pixel.rubiconproject.com | 12 | 19 KB |
| loadus.exelator.com | 3 | 3 KB |
| ssum-sec.casalemedia.com | 2 | 3 KB |
| image8.pubmatic.com | 3 | 3 KB |
| u.openx.net | 2 | 2 KB |
| ups.analytics.yahoo.com | 4 | 3 KB |
| ad.360yield.com | 2 | 1 KB |
| s.ad.smaato.net | 1 | 633 B |
| ssbsync.smartadserver.com | 1 | 575 B |
| c.bing.com | 2 | 2 KB |
| pixel-sync.sitescout.com | 2 | 2 KB |
| cms.quantserve.com | 2 | 1 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 | 938 B |
| sync.1rx.io | 1 | 427 B |
| cs.media.net | 1 | 751 B |
| cs.admanmedia.com | 1 | 0 B |
| csync.loopme.me | 1 | 569 B |
| temu.com | 1 | 894 B |
| sync.teads.tv | 1 | 704 B |
| sync.outbrain.com | 28 | 6 KB |
| pippio.com | 2 | 1 KB |
| config.aps.amazon-adsystem.com | 1 | 928 B |
| aax.amazon-adsystem.com | 2 | 1 KB |
| htlb.casalemedia.com | 2 | 2 KB |
| rtb.openx.net | 2 | 1 KB |
| tlx.3lift.com | 2 | 0 B |
| hbopenbid.pubmatic.com | 2 | 860 B |
| image2.pubmatic.com | 7 | 5 KB |
| ad.doubleclick.net | 1 | 849 B |
| image4.pubmatic.com | 2 | 1,001 B |
| s.amazon-adsystem.com | 6 | 5 KB |
| google.com | 4 | 1 KB |
| eventlog.outbrain.com | 1 | 331 B |
| jadserve.postrelease.com | 1 | 706 B |
| ads.pubmatic.com | 2 | 14 KB |
| eb2.3lift.com | 10 | 7 KB |
| microsoft-aunz-d.openx.net | 1 | 1 KB |
| acdn.adnxs.com | 1 | 17 KB |
| image6.pubmatic.com | 2 | 6 KB |
| us-u.openx.net | 3 | 1 KB |
| aax-eu.amazon-adsystem.com | 2 | 1 KB |
| jp-u.openx.net | 2 | 792 B |
| c1.adform.net | 2 | 2 KB |
| uipglob.semasio.net | 3 | 2 KB |
| um.simpli.fi | 1 | 989 B |
| simage2.pubmatic.com | 5 | 4 KB |
| px.ads.linkedin.com | 2 | 1 KB |
| cms.analytics.yahoo.com | 1 | 372 B |
| sg.semasio.net | 2 | 1 KB |
| sync.ipredictive.com | 2 | 1 KB |
| pixel.tapad.com | 4 | 5 KB |
| simage4.pubmatic.com | 2 | 712 B |
| sync-tm.everesttech.net | 4 | 2 KB |
| p.rfihub.com | 1 | 853 B |
| pixel.onaudience.com | 1 | 358 B |
| d.turn.com | 1 | 624 B |
| dpm.demdex.net | 1 | 1 KB |
Opportunities
Assets that need text compression enabled502 KB0.112g
By enabling text compression on 2 items, , roughly 502.5 KB could be removed from the page load.
View details
| pubads_impl.js | 536 KB | 352 KB |
| ufs_web_display.js | 221 KB | 150 KB |
Optimise images10 MB2.395g
By optimising the following images, roughly 10 MB could be removed from the transfer size, about 62%. This would reduce the CO2 generated per page load from 3.88g grams to 1.49 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
Subset large font files57 KB0.013g
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
| c4250770ab8708b6-s.p.woff2 | ~35 KB | ~18 KB |
| hurme-black.woff | ~31 KB | ~13 KB |
| proximanova-bold.woff | ~28 KB | ~10 KB |
| proximanova-semibold.woff | ~27 KB | ~10 KB |
| b2142359fe988546-s.p.woff2 | ~20 KB | ~2 KB |
| ibm-plex-sans-v13-latin-600.woff2 | ~19 KB | ~2 KB |
| proximanova-regular.woff | ~19 KB | ~1 KB |
| ibm-plex-sans-v13-latin-regular.woff2 | ~18 KB | ~662 B |
Convert font files to woff215 KB
WOFF2 is considered to be the best font format for web use because it provides a good balance of file size and compatibility. Some specific reasons why WOFF2 is a good font format include:
- Small file size: WOFF2 is a compressed font format, which means that it has a smaller file size compared to other font formats like TTF or OTF. This is important for web use because smaller file sizes can help to reduce the amount of data that needs to be downloaded, leading to faster page load times.
- High-quality font rendering: WOFF2 provides high-quality font rendering, making it a good choice for use on the web.
It’s worth noting that WOFF2 is not the only font format that can be used on the web, and there may be cases where other formats like WOFF or TTF are more suitable, depending on the specific requirements of the website. However, for most cases, WOFF2 is considered to be the best font format for web use due to its combination of small file size, good browser support, and high-quality font rendering.
View details
| proximanova-semibold.woff | woff |
| proximanova-bold.woff | woff |
| hurme-black.woff | woff |
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
| www.drive.com.au | ibm-plex-sans-v13-latin-regular.woff2 |
| www.drive.com.au | ibm-plex-sans-v13-latin-600.woff2 |
| www.drive.com.au | b2142359fe988546-s.p.woff2 |
| www.drive.com.au | c4250770ab8708b6-s.p.woff2 |
| fonts.gstatic.com | 6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.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 | 38% | 100% |
| Timing | 3.4 s | 0.4 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 | 59.6 s | 8.2 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 | 5% | 1% |
| Timing | 2,370 ms | 1,490 ms |
Cumulative Layout Shift
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
| Mobile | Desktop | |
|---|---|---|
| Score | 94% | 48% |
| Timing | 0.081 | 0.257 |
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 | 1% | 4% |
| Timing | 14.8 s | 4.8 s |
Layout shift culprits
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
| Mobile | Desktop | |
|---|---|---|
| Score | 100% | 0% |
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% | 0% |
Forced reflow
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about forced reflow and its mitigations.
| Mobile | Desktop | |
|---|---|---|
| Score | 0% | 0% |
LCP request discovery
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
| Mobile | Desktop | |
|---|---|---|
| Score | 0% | 0% |
Network dependency tree
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
| Mobile | Desktop | |
|---|---|---|
| Score | 0% | 0% |
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% | 2% |
| Timing | 59.6 s | 11.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 | 11% | 12% |
| Timing | 460 ms | 450 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 | Yes | Yes |
| Dirtier than | 96% | 96% |
| CO2 per page load | 3.95g | 3.88g |
| CO2 wasted per page load | ~2.7g | ~2.5g |
| Transfer size | 17.24MB | 16.96MB |
| Transfer size percentile | 96% | 96% |
| Size wasted | 11.74 MB | 11.13 MB |
Sustainable hosting
By hosting this site on a server powered by renewable energy, this page generated ~3.88grams of CO2 instead of ~4.48grams 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 ~1 MB of data
A tracking script is a code snippet designed to track the flow of visitors who visit a website. Media, advertising, and analytics organisations will provide a script to add to your website that sends data directly to their servers. This data can then be used to measure goals and conversions, analyse user behaviour, and influence advertising campaigns.
Consider how much of this data you actually need and use? How often do you review the analytics data, and does this inform genuine change? Are you actively running social media campaigns? Consider pausing or removing tracking scripts that aren’t being actively used.
View details
| idgets.outbrain.com | 9 | 120 KB |
| securepubads.g.doubleclick.net | 19 | 700 KB |
| idget-pixels.outbrain.com | 1 | 577 B |
| mv.outbrain.com | 1 | 7 KB |
| static.cloudflareinsights.com | 1 | 7 KB |
| c.amazon-adsystem.com | 3 | 95 KB |
| ib.adnxs.com | 8 | 6 KB |
| match.adsrvr.org | 9 | 6 KB |
| aa.agkn.com | 2 | 2 KB |
| x.bidswitch.net | 7 | 5 KB |
| dis.criteo.com | 1 | 432 B |
| cm.g.doubleclick.net | 16 | 11 KB |
| dsp-cookie.adfarm1.adition.com | 1 | 631 B |
| ps.eyeota.net | 6 | 4 KB |
| pixel.rubiconproject.com | 12 | 19 KB |
| loadus.exelator.com | 3 | 3 KB |
| ssum-sec.casalemedia.com | 2 | 3 KB |
| image8.pubmatic.com | 3 | 3 KB |
| u.openx.net | 2 | 2 KB |
| ups.analytics.yahoo.com | 4 | 3 KB |
| ad.360yield.com | 2 | 1 KB |
| s.ad.smaato.net | 1 | 633 B |
| ssbsync.smartadserver.com | 1 | 575 B |
| c.bing.com | 2 | 2 KB |
| pixel-sync.sitescout.com | 2 | 2 KB |
| cms.quantserve.com | 2 | 1 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 | 938 B |
| sync.1rx.io | 1 | 427 B |
| cs.media.net | 1 | 751 B |
| cs.admanmedia.com | 1 | 0 B |
| csync.loopme.me | 1 | 569 B |
| temu.com | 1 | 894 B |
| sync.teads.tv | 1 | 704 B |
| sync.outbrain.com | 28 | 6 KB |
| pippio.com | 2 | 1 KB |
| config.aps.amazon-adsystem.com | 1 | 928 B |
| aax.amazon-adsystem.com | 2 | 1 KB |
| htlb.casalemedia.com | 2 | 2 KB |
| rtb.openx.net | 2 | 1 KB |
| tlx.3lift.com | 2 | 0 B |
| hbopenbid.pubmatic.com | 2 | 860 B |
| image2.pubmatic.com | 7 | 5 KB |
| ad.doubleclick.net | 1 | 849 B |
| image4.pubmatic.com | 2 | 1,001 B |
| s.amazon-adsystem.com | 6 | 5 KB |
| google.com | 4 | 1 KB |
| eventlog.outbrain.com | 1 | 331 B |
| jadserve.postrelease.com | 1 | 706 B |
| ads.pubmatic.com | 2 | 14 KB |
| eb2.3lift.com | 10 | 7 KB |
| microsoft-aunz-d.openx.net | 1 | 1 KB |
| acdn.adnxs.com | 1 | 17 KB |
| image6.pubmatic.com | 2 | 6 KB |
| us-u.openx.net | 3 | 1 KB |
| aax-eu.amazon-adsystem.com | 2 | 1 KB |
| jp-u.openx.net | 2 | 792 B |
| c1.adform.net | 2 | 2 KB |
| uipglob.semasio.net | 3 | 2 KB |
| um.simpli.fi | 1 | 989 B |
| simage2.pubmatic.com | 5 | 4 KB |
| px.ads.linkedin.com | 2 | 1 KB |
| cms.analytics.yahoo.com | 1 | 372 B |
| sg.semasio.net | 2 | 1 KB |
| sync.ipredictive.com | 2 | 1 KB |
| pixel.tapad.com | 4 | 5 KB |
| simage4.pubmatic.com | 2 | 712 B |
| sync-tm.everesttech.net | 4 | 2 KB |
| p.rfihub.com | 1 | 853 B |
| pixel.onaudience.com | 1 | 358 B |
| d.turn.com | 1 | 624 B |
| dpm.demdex.net | 1 | 1 KB |
Opportunities
Assets that need text compression enabled502 KB0.112g
By enabling text compression on 2 items, , roughly 502.5 KB could be removed from the page load.
View details
| pubads_impl.js | 536 KB | 352 KB |
| ufs_web_display.js | 221 KB | 150 KB |
Optimise images10 MB2.395g
By optimising the following images, roughly 10 MB could be removed from the transfer size, about 62%. This would reduce the CO2 generated per page load from 3.88g grams to 1.49 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
Subset large font files57 KB0.013g
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
| c4250770ab8708b6-s.p.woff2 | ~35 KB | ~18 KB |
| hurme-black.woff | ~31 KB | ~13 KB |
| proximanova-bold.woff | ~28 KB | ~10 KB |
| proximanova-semibold.woff | ~27 KB | ~10 KB |
| b2142359fe988546-s.p.woff2 | ~20 KB | ~2 KB |
| ibm-plex-sans-v13-latin-600.woff2 | ~19 KB | ~2 KB |
| proximanova-regular.woff | ~19 KB | ~1 KB |
| ibm-plex-sans-v13-latin-regular.woff2 | ~18 KB | ~662 B |
Convert font files to woff215 KB
WOFF2 is considered to be the best font format for web use because it provides a good balance of file size and compatibility. Some specific reasons why WOFF2 is a good font format include:
- Small file size: WOFF2 is a compressed font format, which means that it has a smaller file size compared to other font formats like TTF or OTF. This is important for web use because smaller file sizes can help to reduce the amount of data that needs to be downloaded, leading to faster page load times.
- High-quality font rendering: WOFF2 provides high-quality font rendering, making it a good choice for use on the web.
It’s worth noting that WOFF2 is not the only font format that can be used on the web, and there may be cases where other formats like WOFF or TTF are more suitable, depending on the specific requirements of the website. However, for most cases, WOFF2 is considered to be the best font format for web use due to its combination of small file size, good browser support, and high-quality font rendering.
View details
| proximanova-semibold.woff | woff |
| proximanova-bold.woff | woff |
| hurme-black.woff | woff |
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
| www.drive.com.au | ibm-plex-sans-v13-latin-regular.woff2 |
| www.drive.com.au | ibm-plex-sans-v13-latin-600.woff2 |
| www.drive.com.au | b2142359fe988546-s.p.woff2 |
| www.drive.com.au | c4250770ab8708b6-s.p.woff2 |
| fonts.gstatic.com | 6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2 |
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
- 63%
- Desktop Accessibility
- 54%
Opportunities
Elements use prohibited ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
| 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 |
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
<html> element does not have a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
Image elements have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
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 |
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
List items (<li>) are not contained within <ul>, <ol> or <menu> parent elements.
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
| Mobile | Desktop | |
|---|---|---|
| Grade | Pass | Fail |
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
| 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 | Pass | 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
- 54%
- Desktop Best Practices
- 70%
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
- 92%
- Desktop SEO
- 92%
Tracking scripts
All the tracking scripts on the site generated ~1 MB of data
A tracking script is a code snippet designed to track the flow of visitors who visit a website. Media, advertising, and analytics organisations will provide a script to add to your website that sends data directly to their servers. This data can then be used to measure goals and conversions, analyse user behaviour, and influence advertising campaigns.
Consider how much of this data you actually need and use? How often do you review the analytics data, and does this inform genuine change? Are you actively running social media campaigns? Consider pausing or removing tracking scripts that aren’t being actively used.
View details
| idgets.outbrain.com | 9 | 120 KB |
| securepubads.g.doubleclick.net | 19 | 700 KB |
| idget-pixels.outbrain.com | 1 | 577 B |
| mv.outbrain.com | 1 | 7 KB |
| static.cloudflareinsights.com | 1 | 7 KB |
| c.amazon-adsystem.com | 3 | 95 KB |
| ib.adnxs.com | 8 | 6 KB |
| match.adsrvr.org | 9 | 6 KB |
| aa.agkn.com | 2 | 2 KB |
| x.bidswitch.net | 7 | 5 KB |
| dis.criteo.com | 1 | 432 B |
| cm.g.doubleclick.net | 16 | 11 KB |
| dsp-cookie.adfarm1.adition.com | 1 | 631 B |
| ps.eyeota.net | 6 | 4 KB |
| pixel.rubiconproject.com | 12 | 19 KB |
| loadus.exelator.com | 3 | 3 KB |
| ssum-sec.casalemedia.com | 2 | 3 KB |
| image8.pubmatic.com | 3 | 3 KB |
| u.openx.net | 2 | 2 KB |
| ups.analytics.yahoo.com | 4 | 3 KB |
| ad.360yield.com | 2 | 1 KB |
| s.ad.smaato.net | 1 | 633 B |
| ssbsync.smartadserver.com | 1 | 575 B |
| c.bing.com | 2 | 2 KB |
| pixel-sync.sitescout.com | 2 | 2 KB |
| cms.quantserve.com | 2 | 1 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 | 938 B |
| sync.1rx.io | 1 | 427 B |
| cs.media.net | 1 | 751 B |
| cs.admanmedia.com | 1 | 0 B |
| csync.loopme.me | 1 | 569 B |
| temu.com | 1 | 894 B |
| sync.teads.tv | 1 | 704 B |
| sync.outbrain.com | 28 | 6 KB |
| pippio.com | 2 | 1 KB |
| config.aps.amazon-adsystem.com | 1 | 928 B |
| aax.amazon-adsystem.com | 2 | 1 KB |
| htlb.casalemedia.com | 2 | 2 KB |
| rtb.openx.net | 2 | 1 KB |
| tlx.3lift.com | 2 | 0 B |
| hbopenbid.pubmatic.com | 2 | 860 B |
| image2.pubmatic.com | 7 | 5 KB |
| ad.doubleclick.net | 1 | 849 B |
| image4.pubmatic.com | 2 | 1,001 B |
| s.amazon-adsystem.com | 6 | 5 KB |
| google.com | 4 | 1 KB |
| eventlog.outbrain.com | 1 | 331 B |
| jadserve.postrelease.com | 1 | 706 B |
| ads.pubmatic.com | 2 | 14 KB |
| eb2.3lift.com | 10 | 7 KB |
| microsoft-aunz-d.openx.net | 1 | 1 KB |
| acdn.adnxs.com | 1 | 17 KB |
| image6.pubmatic.com | 2 | 6 KB |
| us-u.openx.net | 3 | 1 KB |
| aax-eu.amazon-adsystem.com | 2 | 1 KB |
| jp-u.openx.net | 2 | 792 B |
| c1.adform.net | 2 | 2 KB |
| uipglob.semasio.net | 3 | 2 KB |
| um.simpli.fi | 1 | 989 B |
| simage2.pubmatic.com | 5 | 4 KB |
| px.ads.linkedin.com | 2 | 1 KB |
| cms.analytics.yahoo.com | 1 | 372 B |
| sg.semasio.net | 2 | 1 KB |
| sync.ipredictive.com | 2 | 1 KB |
| pixel.tapad.com | 4 | 5 KB |
| simage4.pubmatic.com | 2 | 712 B |
| sync-tm.everesttech.net | 4 | 2 KB |
| p.rfihub.com | 1 | 853 B |
| pixel.onaudience.com | 1 | 358 B |
| d.turn.com | 1 | 624 B |
| dpm.demdex.net | 1 | 1 KB |
Cost to load
| Price per GB (USD) | $3.12 |
|---|---|
| Price per GB (Local) | 3.12 USD |
| Price to load PPV (USD) | $0.053 |
| Price to load PPV (Local) | 0.053 USD |
2022 Mobile data pricing sourced from cable.co.uk
Opportunities
Security headers to set0/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.
Links are not crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Pass |
| Insight | 1 warning 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 |