Capital Brewing Company

The Index

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
50%
Desktop Performance
63%

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 PaintFirst Input Delay, and Cumulative Layout Shift.

VitalMobileDesktopTarget
Largest Contentful Paint10.5 s5.0 s< 2.5 s
First Input Delay240 ms230 ms< 100ms
Cumulative Layout Shift0.0830.024 0.1

Tracking scripts

All the tracking scripts on the site generated ~428 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.

google-analytics.com 3 21 KB
stats.wp.com 2 7 KB
googletagmanager.com 3 141 KB
connect.facebook.net 5 250 KB
stats.g.doubleclick.net 2 1 KB
google.com 3 3 KB
googleadservices.com 1 2 KB
googleads.g.doubleclick.net 1 2 KB
google.com.au 1 620 B
facebook.com 2 328 B
pixel.wp.com 1 218 B

Opportunities

Remove autoplaying or preloaded media files

By removing 3 autoplaying or preloaded videos, roughly 10.6 MB could be removed from the page load.

This would reduce the page transfer size by 55% and reduce the pages emissions from 5.11 grams of CO2 to 2.31 grams of CO2.

Autoplaying videos can have a negative impact on the user experience for several reasons:

  1. 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.
  2. 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.
  3. Reduced accessibility: Autoplaying videos can be a problem for users with accessibility needs, such as users who are blind or have hearing difficulties.
  4. Increased page load time: Autoplaying videos can increase the overall page load time, leading to a slower user experience.
  5. 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.

Optimise images

By optimising the following images, roughly 4 MB could be removed from the transfer size, about 20%. This would reduce the CO2 generated per page load from 5.11g grams to 4.1 grams.

Images should be optimised for the web for several reasons:

  1. 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.
  2. Improved user experience: Optimising images can help to improve the overall user experience, as pages with optimised images load faster and are more responsive.
  3. Lower emissions: Optimising images can help to reduce the emissions associated with data transfer, as less data needs to be transmitted over the network.
  4. Better accessibility: Optimising images can make them more accessible to users with slower connections or limited data plans.
XPA-2-1536x1536.png 686 KB 3% 602 KB
ALC-LESS-1536x1536.png 584 KB 3% 493 KB
DJI_0041-2-2-1536x1024.jpg 436 KB 2% 140 KB
DJI_0041-2-2-1536x1024.jpg 436 KB 2% 140 KB
XPA-home-page-slider.jpg 430 KB 2% 258 KB
MangoTango-Can-Tile-522x1024.png 420 KB 2% 368 KB
home_location_4.jpg 412 KB 2% 132 KB
home_location_4.jpg 412 KB 2% 132 KB
DSC07895-1-1536x1024.jpg 408 KB 2% 141 KB
DSC07895-1-1536x1024.jpg 408 KB 2% 141 KB
DSC07608-3-1536x1024.jpg 337 KB 2% 126 KB
ALC-LESS_can-glass_lowres_2.jpg 332 KB 2% 216 KB
card___Q2A5426-1025x1536.jpg 291 KB 1% 151 KB
HLJ-website-1536x1024.jpg 286 KB 1% 144 KB
home_good_natured_3.jpg 265 KB 1% 53 KB
DSC01554-2-1536x1024.jpg 247 KB 1% 102 KB
GABS-results-3-1536x1071.jpg 222 KB 1% 120 KB
Back-Hat-Background.jpg 220 KB 1% 134 KB
Brew-Zealand-Hazy-DIPA-768x768.png 190 KB 1% 93 KB
XPA_single-7-768x768.png 161 KB 1% 65 KB
Brew-Zealand-announcement-768x768.jpg 118 KB 1% 21 KB
B-Corp-Announcement-1-copy-768x436.jpg 94 KB 0% 39 KB
335933213_884890972583186_1380425700658913144_nfull.jpg 88 KB 0% 21 KB
summit_session_gallery_1-768x512.jpg 82 KB 0% 18 KB
card___Q2A5500-768x512.jpg 74 KB 0% 9 KB
logo-300x195.png 65 KB 0% 55 KB

Subset large font files

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:

  1. 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.
  2. 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.

Graphik-Semibold.woff2 ~39 KB ~22 KB
Graphik-Regular.woff2 ~37 KB ~19 KB
NorthernSoul-Caps.woff2 ~35 KB ~18 KB

Replace jQuery and jQuery libraries with more modern code

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:

  1. 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.
  2. 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.
  3. 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.

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:

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
MobileDesktop
Score13%62%
Timing4.7 s1.4 s

Largest Contentful Paint

MobileDesktop
Score0%8%
Timing10.5 s5.0 s

Total Blocking Time

MobileDesktop
Score85%98%
Timing250 ms90 ms

Cumulative Layout Shift

MobileDesktop
Score94%100%
Timing0.0830.024

Speed Index

MobileDesktop
Score0%0%
Timing20.3 s7.4 s

Time to Interactive

MobileDesktop
Score8%47%
Timing15.0 s4.7 s

Max Potential First Input Delay

MobileDesktop
Score52%56%
Timing240 ms230 ms

First Meaningful Paint

MobileDesktop
Score35%62%
Timing4.7 s1.4 s

Eliminate render-blocking resources

MobileDesktop
Score6%43%
InsightPotential savings of 4,500 msPotential savings of 1,320 ms

Properly size images

MobileDesktop
Score0%13%
InsightPotential savings of 1,709 KiBPotential savings of 4,924 KiB

Defer offscreen images

MobileDesktop
Score48%83%
InsightPotential savings of 180 KiBPotential savings of 178 KiB

Minify CSS

MobileDesktop
Score50%87%
InsightPotential savings of 95 KiBPotential savings of 95 KiB

Minify JavaScript

MobileDesktop
Score88%100%
InsightPotential savings of 30 KiBPotential savings of 30 KiB

Reduce unused CSS

MobileDesktop
Score38%74%
InsightPotential savings of 179 KiBPotential savings of 171 KiB

Reduce unused JavaScript

MobileDesktop
Score46%83%
InsightPotential savings of 246 KiBPotential savings of 261 KiB

Efficiently encode images

MobileDesktop
Score58%90%
InsightPotential savings of 116 KiBPotential savings of 168 KiB

Serve images in next-gen formats

MobileDesktop
Score0%26%
InsightPotential savings of 2,448 KiBPotential savings of 3,502 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 3,260 msRoot document took 3,090 ms

Use video formats for animated content

MobileDesktop
Score45%87%
InsightPotential savings of 176 KiBPotential savings of 176 KiB

Avoid enormous network payloads

MobileDesktop
Score0%0%
InsightTotal size was 16,135 KiBTotal size was 19,831 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score2%2%
Insight73 resources found74 resources found

Avoids an excessive DOM size

MobileDesktop
Score97%97%
Insight639 elements639 elements

JavaScript execution time

MobileDesktop
Score72%100%
Timing2.2 s0.4 s

Minimizes main-thread work

MobileDesktop
Score29%93%
Timing5.4 s1.8 s

Largest Contentful Paint image was lazily loaded

MobileDesktop
GradeFailFail

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail