Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

boozephreaks.com

Boozephreaks: San Francisco Spirit Tastings, Cocktail Classes, Distillery Tours

Page Load Speed

2.6 sec in total

First Response

695 ms

Resources Loaded

1.8 sec

Page Rendered

75 ms

About Website

Visit boozephreaks.com now to see the best up-to-date Boozephreaks content and also check out these interesting facts you probably never knew about boozephreaks.com

Boozephreaks is a Bay Area, San Francisco-based cocktail class, spirits tasting, distillery tour, and event planning company. Dr Inkwell will be your guide as a spirits expert and mixologist, teaching...

Visit boozephreaks.com

Key Findings

We analyzed Boozephreaks.com page load time and found that the first response time was 695 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

boozephreaks.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value4.6 s

70/100

10%

TBT (Total Blocking Time)

Value1,080 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

www.boozephreaks.com

695 ms

minified.js

67 ms

focus-within-polyfill.js

109 ms

polyfill.min.js

111 ms

thunderbolt-commons.e52dfaaa.bundle.min.js

171 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Boozephreaks.com, 33% (14 requests) were made to Static.wixstatic.com and 31% (13 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (773 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 558.2 kB (44%)

Content Size

1.3 MB

After Optimization

706.1 kB

In fact, the total size of Boozephreaks.com main page is 1.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. HTML takes 596.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 475.5 kB

  • Original 596.6 kB
  • After minification 594.7 kB
  • After compression 121.1 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 475.5 kB or 80% of the original size.

Image Optimization

-10%

Potential reduce by 34.6 kB

  • Original 360.9 kB
  • After minification 326.3 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Boozephreaks images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 48.1 kB

  • Original 306.8 kB
  • After minification 306.8 kB
  • After compression 258.6 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 48.1 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (37%)

Requests Now

30

After Optimization

19

The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Boozephreaks. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

boozephreaks.com accessibility score

83

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Form elements do not have associated labels

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

boozephreaks.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

boozephreaks.com SEO score

99

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Boozephreaks.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Boozephreaks.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph data is detected on the main page of Boozephreaks. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: