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
- 25%
- 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 | 8.5 s | 2.5 s | < 2.5 s |
| First Input Delay | 1,350 ms | 150 ms | < 100ms |
| Cumulative Layout Shift | 0.058 | 0.004 | 0.1 |
Tracking scripts
All the tracking scripts on the site generated ~640 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
| c.amazon-adsystem.com | 3 | 65 KB |
| ads.stickyadstv.com | 2 | 1 KB |
| ib.adnxs.com | 10 | 7 KB |
| sb.scorecardresearch.com | 3 | 4 KB |
| securepubads.g.doubleclick.net | 5 | 178 KB |
| idgets.outbrain.com | 5 | 94 KB |
| config.aps.amazon-adsystem.com | 1 | 870 B |
| aax.amazon-adsystem.com | 2 | 1 KB |
| logx.optimizely.com | 2 | 720 B |
| s.amazon-adsystem.com | 15 | 11 KB |
| idget-pixels.outbrain.com | 1 | 577 B |
| hbopenbid.pubmatic.com | 1 | 197 B |
| mv.outbrain.com | 2 | 7 KB |
| match.adsrvr.org | 10 | 8 KB |
| beacon.krxd.net | 1 | 444 B |
| aa.agkn.com | 1 | 857 B |
| x.bidswitch.net | 9 | 4 KB |
| dis.criteo.com | 3 | 2 KB |
| cm.g.doubleclick.net | 15 | 11 KB |
| ps.eyeota.net | 3 | 2 KB |
| loadus.exelator.com | 2 | 2 KB |
| ssum-sec.casalemedia.com | 4 | 5 KB |
| image8.pubmatic.com | 4 | 4 KB |
| u.openx.net | 2 | 1 KB |
| ups.analytics.yahoo.com | 6 | 4 KB |
| ice.360yield.com | 2 | 1 KB |
| s.ad.smaato.net | 1 | 771 B |
| ssbsync.smartadserver.com | 1 | 518 B |
| c.bing.com | 1 | 965 B |
| pixel-sync.sitescout.com | 2 | 1 KB |
| cms.quantserve.com | 2 | 2 KB |
| bh.contextweb.com | 1 | 1 KB |
| cm.rtbsystem.com | 1 | 1 KB |
| rtb.adentifi.com | 1 | 395 B |
| sync.outbrain.com | 17 | 2 KB |
| pippio.com | 4 | 2 KB |
| image2.pubmatic.com | 11 | 7 KB |
| ads.pubmatic.com | 5 | 111 KB |
| image6.pubmatic.com | 5 | 13 KB |
| image4.pubmatic.com | 3 | 1 KB |
| pm.w55c.net | 2 | 2 KB |
| sync-tm.everesttech.net | 2 | 1 KB |
| p.rfihub.com | 1 | 845 B |
| a.tribalfusion.com | 1 | 923 B |
| beacon.lynx.cognitivlabs.com | 1 | 383 B |
| csync.loopme.me | 1 | 447 B |
| pixel.tapad.com | 5 | 6 KB |
| eb2.3lift.com | 3 | 2 KB |
| um.simpli.fi | 3 | 2 KB |
| sync.ipredictive.com | 2 | 1 KB |
| c1.adform.net | 2 | 2 KB |
| ads.playground.xyz | 1 | 735 B |
| t.pubmatic.com | 1 | 305 B |
| simage2.pubmatic.com | 23 | 14 KB |
| secure.adnxs.com | 1 | 774 B |
| s.tribalfusion.com | 1 | 826 B |
| match.sharethrough.com | 1 | 837 B |
| dsum-sec.casalemedia.com | 4 | 4 KB |
| dsum.casalemedia.com | 2 | 2 KB |
| acdn.adnxs.com | 1 | 17 KB |
| aax-eu.amazon-adsystem.com | 1 | 855 B |
| simage4.pubmatic.com | 3 | 1 KB |
| pixel.rubiconproject.com | 11 | 9 KB |
| px.ads.linkedin.com | 1 | 968 B |
| px.owneriq.net | 4 | 3 KB |
| us-u.openx.net | 3 | 1 KB |
| sync.targeting.unrulymedia.com | 2 | 1 KB |
| sync.search.spotxchange.com | 1 | 0 B |
| eq97f.publishers.tremorhub.com | 2 | 1 KB |
Opportunities
Remove autoplaying or preloaded media files2 videos1.8 MB0.41g CO2
By removing 2 autoplaying or preloaded videos, roughly 1.8 MB could be removed from the page load.
This would reduce the page transfer size by 25% and reduce the pages emissions from 1.61 grams of CO2 to 1.2 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
| uaw0915.mp4 | 2 MB | 23% |
| as-equals-haiti-hp-loop-2.mp4 | 143 KB | 2% |
Assets that need text compression enabled142 KB0.032g
By enabling text compression on 5 items, , roughly 142.4 KB could be removed from the page load.
View details
| sca.17.6.2.js | 91 KB | 69 KB |
| pixel.js | 88 KB | 57 KB |
| psm_2_prod_full.json | 11 KB | 11 KB |
| PugMaster | 5 KB | 4 KB |
| pr | 2 KB | 2 KB |
Subset large font files195 KB0.044g
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
| woff2;charset=utf-8;base64,d09GMgABAAAAAgKoABEAAAAIrhAAAgJBAAEAAAAAAAAAAAAAAAAAAAAAAAAAAA… | ~129 KB | ~111 KB |
| woff2;charset=utf-8;base64,d09GMgABAAAAALh8ABIAAAABsoAAALgWAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA… | ~46 KB | ~29 KB |
| woff2;charset=utf-8;base64,d09GMgABAAAAALWAABIAAAABs6gAALUbAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA… | ~45 KB | ~28 KB |
| woff2;charset=utf-8;base64,d09GMgABAAAAALVIABIAAAABs0QAALTjAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA… | ~45 KB | ~28 KB |
Replace jQuery and jQuery libraries with more modern code32 KB0.01g
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-3.5.1.min.js | 32 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% | 54% |
| Timing | 6.8 s | 1.5 s |
Largest Contentful Paint
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
| Mobile | Desktop | |
|---|---|---|
| Score | 2% | 45% |
| Timing | 8.5 s | 2.5 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% | 36% |
| Timing | 12,650 ms | 440 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 | 98% | 100% |
| Timing | 0.058 | 0.004 |
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 | 3% | 12% |
| Timing | 12.7 s | 3.8 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 | 0% | 4% |
| Timing | 42.5 s | 10.2 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 | 0% | 82% |
| Timing | 1,350 ms | 150 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 | 9% | 54% |
| Timing | 7.0 s | 1.5 s |
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 | 37% | 45% |
| Insight | Potential savings of 385 KiB | Potential savings of 1,401 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 | 89% | 100% |
| Insight | Potential savings of 11 KiB | Potential savings of 8 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 | 97% | 100% |
| Insight | Potential savings of 209 KiB | Potential savings of 219 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 | 9% | 45% |
| Insight | Potential savings of 972 KiB | Potential savings of 1,005 KiB |
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
| Mobile | Desktop | |
|---|---|---|
| Score | 100% | 98% |
| Insight | Potential savings of 49 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 | 41% | 77% |
| Insight | Potential savings of 278 KiB | Potential savings of 626 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 | 37% | 89% |
| Insight | Potential savings of 85 KiB | Potential savings of 142 KiB |
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
| Mobile | Desktop | |
|---|---|---|
| Score | 86% | 100% |
| Insight | Potential savings of 89 KiB | Potential savings of 99 KiB |
Avoid enormous network payloads
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
| Mobile | Desktop | |
|---|---|---|
| Score | 10% | 3% |
| Insight | Total size was 5,945 KiB | Total size was 7,189 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 | 0% | 0% |
| Insight | 75 resources found | 93 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 | 5% | 10% |
| Insight | 2,769 elements | 2,372 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 | 0% | 61% |
| Timing | 23.3 s | 2.8 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% | 16% |
| Timing | 42.2 s | 6.7 s |
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 7,530 ms | Third-party code blocked the main thread for 170 ms |
Largest Contentful Paint image was lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.
| Mobile | Desktop | |
|---|---|---|
| Grade | Pass | Fail |
Avoid document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
| 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 | 85% | 88% |
| CO2 per page load | 1.33g | 1.61g |
| CO2 wasted per page load | ~0.6g | ~0.6g |
| Transfer size | 5.81MB | 7.02MB |
| Transfer size percentile | 83% | 85% |
| Size wasted | 2.54 MB | 2.84 MB |
Sustainable hosting
By hosting this site on a server powered by renewable energy, this page generated ~1.61grams of CO2 instead of ~1.85grams 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 ~640 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
| c.amazon-adsystem.com | 3 | 65 KB |
| ads.stickyadstv.com | 2 | 1 KB |
| ib.adnxs.com | 10 | 7 KB |
| sb.scorecardresearch.com | 3 | 4 KB |
| securepubads.g.doubleclick.net | 5 | 178 KB |
| idgets.outbrain.com | 5 | 94 KB |
| config.aps.amazon-adsystem.com | 1 | 870 B |
| aax.amazon-adsystem.com | 2 | 1 KB |
| logx.optimizely.com | 2 | 720 B |
| s.amazon-adsystem.com | 15 | 11 KB |
| idget-pixels.outbrain.com | 1 | 577 B |
| hbopenbid.pubmatic.com | 1 | 197 B |
| mv.outbrain.com | 2 | 7 KB |
| match.adsrvr.org | 10 | 8 KB |
| beacon.krxd.net | 1 | 444 B |
| aa.agkn.com | 1 | 857 B |
| x.bidswitch.net | 9 | 4 KB |
| dis.criteo.com | 3 | 2 KB |
| cm.g.doubleclick.net | 15 | 11 KB |
| ps.eyeota.net | 3 | 2 KB |
| loadus.exelator.com | 2 | 2 KB |
| ssum-sec.casalemedia.com | 4 | 5 KB |
| image8.pubmatic.com | 4 | 4 KB |
| u.openx.net | 2 | 1 KB |
| ups.analytics.yahoo.com | 6 | 4 KB |
| ice.360yield.com | 2 | 1 KB |
| s.ad.smaato.net | 1 | 771 B |
| ssbsync.smartadserver.com | 1 | 518 B |
| c.bing.com | 1 | 965 B |
| pixel-sync.sitescout.com | 2 | 1 KB |
| cms.quantserve.com | 2 | 2 KB |
| bh.contextweb.com | 1 | 1 KB |
| cm.rtbsystem.com | 1 | 1 KB |
| rtb.adentifi.com | 1 | 395 B |
| sync.outbrain.com | 17 | 2 KB |
| pippio.com | 4 | 2 KB |
| image2.pubmatic.com | 11 | 7 KB |
| ads.pubmatic.com | 5 | 111 KB |
| image6.pubmatic.com | 5 | 13 KB |
| image4.pubmatic.com | 3 | 1 KB |
| pm.w55c.net | 2 | 2 KB |
| sync-tm.everesttech.net | 2 | 1 KB |
| p.rfihub.com | 1 | 845 B |
| a.tribalfusion.com | 1 | 923 B |
| beacon.lynx.cognitivlabs.com | 1 | 383 B |
| csync.loopme.me | 1 | 447 B |
| pixel.tapad.com | 5 | 6 KB |
| eb2.3lift.com | 3 | 2 KB |
| um.simpli.fi | 3 | 2 KB |
| sync.ipredictive.com | 2 | 1 KB |
| c1.adform.net | 2 | 2 KB |
| ads.playground.xyz | 1 | 735 B |
| t.pubmatic.com | 1 | 305 B |
| simage2.pubmatic.com | 23 | 14 KB |
| secure.adnxs.com | 1 | 774 B |
| s.tribalfusion.com | 1 | 826 B |
| match.sharethrough.com | 1 | 837 B |
| dsum-sec.casalemedia.com | 4 | 4 KB |
| dsum.casalemedia.com | 2 | 2 KB |
| acdn.adnxs.com | 1 | 17 KB |
| aax-eu.amazon-adsystem.com | 1 | 855 B |
| simage4.pubmatic.com | 3 | 1 KB |
| pixel.rubiconproject.com | 11 | 9 KB |
| px.ads.linkedin.com | 1 | 968 B |
| px.owneriq.net | 4 | 3 KB |
| us-u.openx.net | 3 | 1 KB |
| sync.targeting.unrulymedia.com | 2 | 1 KB |
| sync.search.spotxchange.com | 1 | 0 B |
| eq97f.publishers.tremorhub.com | 2 | 1 KB |
Opportunities
Remove autoplaying or preloaded media files2 videos1.8 MB0.41g CO2
By removing 2 autoplaying or preloaded videos, roughly 1.8 MB could be removed from the page load.
This would reduce the page transfer size by 25% and reduce the pages emissions from 1.61 grams of CO2 to 1.2 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
| uaw0915.mp4 | 2 MB | 23% |
| as-equals-haiti-hp-loop-2.mp4 | 143 KB | 2% |
Assets that need text compression enabled142 KB0.032g
By enabling text compression on 5 items, , roughly 142.4 KB could be removed from the page load.
View details
| sca.17.6.2.js | 91 KB | 69 KB |
| pixel.js | 88 KB | 57 KB |
| psm_2_prod_full.json | 11 KB | 11 KB |
| PugMaster | 5 KB | 4 KB |
| pr | 2 KB | 2 KB |
Subset large font files195 KB0.044g
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
| woff2;charset=utf-8;base64,d09GMgABAAAAAgKoABEAAAAIrhAAAgJBAAEAAAAAAAAAAAAAAAAAAAAAAAAAAA… | ~129 KB | ~111 KB |
| woff2;charset=utf-8;base64,d09GMgABAAAAALh8ABIAAAABsoAAALgWAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA… | ~46 KB | ~29 KB |
| woff2;charset=utf-8;base64,d09GMgABAAAAALWAABIAAAABs6gAALUbAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA… | ~45 KB | ~28 KB |
| woff2;charset=utf-8;base64,d09GMgABAAAAALVIABIAAAABs0QAALTjAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA… | ~45 KB | ~28 KB |
Replace jQuery and jQuery libraries with more modern code32 KB0.01g
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-3.5.1.min.js | 32 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
- 96%
- Desktop Accessibility
- 96%
Opportunities
Values assigned to role="" are not valid ARIA roles.
ARIA roles enable assistive technologies to know the role of each element on the web page. If the role values are misspelled, not existing ARIA role values, or abstract roles, then the purpose of the element will not be communicated to users of assistive technologies. Learn more about ARIA roles.
| 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 |
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
- 41%
- Desktop Best Practices
- 41%
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
- 85%
- Desktop SEO
- 83%
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
- 38%
- Desktop PWA
- 29%
Tracking scripts
All the tracking scripts on the site generated ~640 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
| c.amazon-adsystem.com | 3 | 65 KB |
| ads.stickyadstv.com | 2 | 1 KB |
| ib.adnxs.com | 10 | 7 KB |
| sb.scorecardresearch.com | 3 | 4 KB |
| securepubads.g.doubleclick.net | 5 | 178 KB |
| idgets.outbrain.com | 5 | 94 KB |
| config.aps.amazon-adsystem.com | 1 | 870 B |
| aax.amazon-adsystem.com | 2 | 1 KB |
| logx.optimizely.com | 2 | 720 B |
| s.amazon-adsystem.com | 15 | 11 KB |
| idget-pixels.outbrain.com | 1 | 577 B |
| hbopenbid.pubmatic.com | 1 | 197 B |
| mv.outbrain.com | 2 | 7 KB |
| match.adsrvr.org | 10 | 8 KB |
| beacon.krxd.net | 1 | 444 B |
| aa.agkn.com | 1 | 857 B |
| x.bidswitch.net | 9 | 4 KB |
| dis.criteo.com | 3 | 2 KB |
| cm.g.doubleclick.net | 15 | 11 KB |
| ps.eyeota.net | 3 | 2 KB |
| loadus.exelator.com | 2 | 2 KB |
| ssum-sec.casalemedia.com | 4 | 5 KB |
| image8.pubmatic.com | 4 | 4 KB |
| u.openx.net | 2 | 1 KB |
| ups.analytics.yahoo.com | 6 | 4 KB |
| ice.360yield.com | 2 | 1 KB |
| s.ad.smaato.net | 1 | 771 B |
| ssbsync.smartadserver.com | 1 | 518 B |
| c.bing.com | 1 | 965 B |
| pixel-sync.sitescout.com | 2 | 1 KB |
| cms.quantserve.com | 2 | 2 KB |
| bh.contextweb.com | 1 | 1 KB |
| cm.rtbsystem.com | 1 | 1 KB |
| rtb.adentifi.com | 1 | 395 B |
| sync.outbrain.com | 17 | 2 KB |
| pippio.com | 4 | 2 KB |
| image2.pubmatic.com | 11 | 7 KB |
| ads.pubmatic.com | 5 | 111 KB |
| image6.pubmatic.com | 5 | 13 KB |
| image4.pubmatic.com | 3 | 1 KB |
| pm.w55c.net | 2 | 2 KB |
| sync-tm.everesttech.net | 2 | 1 KB |
| p.rfihub.com | 1 | 845 B |
| a.tribalfusion.com | 1 | 923 B |
| beacon.lynx.cognitivlabs.com | 1 | 383 B |
| csync.loopme.me | 1 | 447 B |
| pixel.tapad.com | 5 | 6 KB |
| eb2.3lift.com | 3 | 2 KB |
| um.simpli.fi | 3 | 2 KB |
| sync.ipredictive.com | 2 | 1 KB |
| c1.adform.net | 2 | 2 KB |
| ads.playground.xyz | 1 | 735 B |
| t.pubmatic.com | 1 | 305 B |
| simage2.pubmatic.com | 23 | 14 KB |
| secure.adnxs.com | 1 | 774 B |
| s.tribalfusion.com | 1 | 826 B |
| match.sharethrough.com | 1 | 837 B |
| dsum-sec.casalemedia.com | 4 | 4 KB |
| dsum.casalemedia.com | 2 | 2 KB |
| acdn.adnxs.com | 1 | 17 KB |
| aax-eu.amazon-adsystem.com | 1 | 855 B |
| simage4.pubmatic.com | 3 | 1 KB |
| pixel.rubiconproject.com | 11 | 9 KB |
| px.ads.linkedin.com | 1 | 968 B |
| px.owneriq.net | 4 | 3 KB |
| us-u.openx.net | 3 | 1 KB |
| sync.targeting.unrulymedia.com | 2 | 1 KB |
| sync.search.spotxchange.com | 1 | 0 B |
| eq97f.publishers.tremorhub.com | 2 | 1 KB |
Cost to load
| Price per GB (USD) | $3.12 |
|---|---|
| Price per GB (Local) | 3.12 USD |
| Price to load PPV (USD) | $0.018 |
| Price to load PPV (Local) | 0.018 USD |
2022 Mobile data pricing sourced from cable.co.uk
Opportunities
Security headers to set2/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 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 | 2 links found | 2 links found |
Document does not have a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
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 |
Uses deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
| Insight | 2 warnings found | 2 warnings found |
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
Issues were logged in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |