Capital Brewing Company

The Index


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
Desktop Performance

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.

Pass or fail?


CWV Breakdown

Largest Contentful Paint34.7 s19.9 s< 2.5 s
First Input Delay230 ms80 ms< 100ms
Cumulative Layout Shift0.0840.034 0.1

Tracking scripts

All the tracking scripts on the site generated ~439 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 3 22 KB 1 4 KB 3 215 KB 3 1 KB 3 3 KB 1 218 B 2 189 KB 1 2 KB 1 2 KB 2 656 B 1 0 B 1 620 B


Remove autoplaying or preloaded media files3 videos10.6 MB2.8g CO2

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 46% and reduce the pages emissions from 6.12 grams of CO2 to 3.32 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.

Assets that need text compression enabled2 MB0.403g

By enabling text compression on 38 items, , roughly 1.5 MB could be removed from the page load.

View details
main.css 531 KB 424 KB
app.js 392 KB 315 KB
wc-blocks-style.css 262 KB 235 KB
bs.css 220 KB 180 KB
woocommerce.css 73 KB 64 KB
jquery.min.js 88 KB 57 KB
gsap.min.js 61 KB 37 KB
gravityforms.min.js 46 KB 32 KB
utils.min.js 38 KB 26 KB
sbi-styles.min.css 24 KB 21 KB
sbi-scripts.min.js 27 KB 19 KB
inklab.css 20 KB 16 KB
woocommerce-layout.css 17 KB 15 KB
ScrollTrigger.min.js 20 KB 11 KB
wp-polyfill.min.js 17 KB 11 KB
vendor-theme.min.js 17 KB 11 KB
site_main.js 10 KB 9 KB
jquery-migrate.min.js 13 KB 8 KB
wc-blocks-vendors-style.css 10 KB 8 KB
i18n.min.js 10 KB 6 KB
jquery.blockUI.min.js 9 KB 6 KB
woocommerce.css 8 KB 6 KB
woocommerce-smallscreen.css 7 KB 6 KB
wp-polyfill-inert.min.js 8 KB 6 KB
mailchimp-woocommerce-public.min.js 7 KB 5 KB
regenerator-runtime.min.js 6 KB 4 KB
hooks.min.js 5 KB 3 KB
placeholders.jquery.min.js 5 KB 3 KB
shortcodes.css 3 KB 2 KB
country-selector.js 4 KB 2 KB
fitty.min.js 4 KB 2 KB
scripts-theme.min.js 4 KB 2 KB
actions.js 3 KB 2 KB
awdr-dynamic-price.js 3 KB 2 KB
blocks.css 3 KB 2 KB
add-to-cart.min.js 3 KB 2 KB
ssba.js 3 KB 2 KB
a11y.min.js 2 KB 1 KB
Optimise images5 MB1.437g

By optimising the following images, roughly 5 MB could be removed from the transfer size, about 23%. This would reduce the CO2 generated per page load from 6.12g grams to 4.69 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.
View details
JonnyUtah_Square-768x767.png 1 MB 5% 1 MB
IMG-Jumper-2.png 1 MB 4% 995 KB
IMG-Jumper.png 999 KB 4% 939 KB
ALC-LESS-1536x1536.png 584 KB 2% 493 KB
Good-Drop-slider.jpg 457 KB 2% 246 KB
DJI_0041-2-2-1536x1024.jpg 436 KB 2% 191 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% 168 KB
DSC07895-1-1536x1024.jpg 408 KB 2% 164 KB
DSC07608-3-1536x1024.jpg 337 KB 1% 126 KB
ALC-LESS_can-glass_lowres_2.jpg 332 KB 1% 87 KB
HLJ-website-1536x1024.jpg 286 KB 1% 41 KB
home_good_natured_3.jpg 265 KB 1% 21 KB
DSC01554-2-1536x1024.jpg 247 KB 1% 2 KB
Jonny-Utah-Hazy-Pale-768x768.png 200 KB 1% 103 KB
XPA_single-7-768x768.png 161 KB 1% 65 KB
B-Corp-Announcement-1-copy-768x436.jpg 94 KB 0% 39 KB
summit_session_gallery_1-768x512.jpg 82 KB 0% 18 KB
375620612_828600088812025_1077149417715400941_nfull.jpg 81 KB 0% 14 KB
ANL-slider-768x437.jpg 78 KB 0% 23 KB
card___Q2A5500-768x512.jpg 74 KB 0% 9 KB
logo-300x195.png 65 KB 0% 55 KB
Subset large font files59 KB0.015g

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.

View details
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 code118 KB0.03g

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.
Timing13.7 s6.0 s
Largest Contentful Paint

Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric

Timing34.7 s19.9 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.

Timing220 ms20 ms
Cumulative Layout Shift

Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.

Speed Index

Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.

Timing31.0 s13.5 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.

Timing31.8 s16.8 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.

Timing230 ms80 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.

Timing13.7 s6.0 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.

InsightPotential savings of 13,590 msPotential savings of 6,870 ms
Properly size images

Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.

InsightPotential savings of 2,415 KiBPotential savings of 5,942 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.

InsightPotential savings of 201 KiBPotential savings of 201 KiB
Minify CSS

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

InsightPotential savings of 488 KiBPotential savings of 488 KiB
Minify JavaScript

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

InsightPotential savings of 144 KiBPotential savings of 144 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.

InsightPotential savings of 1,110 KiBPotential savings of 1,100 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.

InsightPotential savings of 624 KiBPotential savings of 616 KiB
Efficiently encode images

Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.

InsightPotential savings of 92 KiBPotential savings of 111 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.

InsightPotential savings of 4,066 KiBPotential savings of 5,429 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.

InsightPotential savings of 1,565 KiBPotential savings of 1,565 KiB
Reduce initial server response time

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

InsightRoot document took 2,060 msRoot document took 2,080 ms
Use video formats for animated content

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formats

InsightPotential savings of 176 KiBPotential savings of 176 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.

InsightTotal size was 19,484 KiBTotal size was 23,754 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.

Insight71 resources found72 resources found
Avoids 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.

Insight574 elements574 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.

Timing2.5 s1.0 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

Timing5.7 s2.6 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.

InsightThird-party code blocked the main thread for 440 msThird-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.

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