sleemanbreweries.ca website review

21 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.

About 231 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.

5 images could be 750 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

Polyfills for old browsers add 51 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

4 third-party services load with your homepage (juicer.io, Google Tag Manager and cdn-cookieyes.com and others), adding 453 KiB and 251 ms of main-thread time.

About 19 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 90 ms faster on a phone.

3 long tasks block the main thread while loading, the longest for 100 ms. During a long task the page ignores taps.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

For real visitors the layout shifts by 0.92 (75th percentile). Good is under 0.1.

Your largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to enhance your browsing experience, serve p…”. Most of its time is element render delay (6.4 s).

Visually, the page fills in at 10.7 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 11.6 s. Good is under 3.8 s.

The first text or image appears after 3.3 s on a phone. Good is under 1.8 s.

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

2 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 82 ms to 98 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 images are downloaded at several times the size a phone draws them, for example Sleeman_180418_0110_LoRes.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 1.6 MB.

Sleeman_180418_0110_LoRes.jpg weighs 743 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.9 MB in 39 requests on a phone: images 2.3 MB (16), scripts 439 KiB (7) and fonts 81 KiB (5). Under 2 MB keeps phones on slow connections fast.

11 images (2.3 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

2 images further down the page (894 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 0.82 g of CO₂e: 98.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 18 characters: “Sleeman - Homepage”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Hey, we gotta ask” and “Our Passion Is Always On Tap”). One clear main headline is easier for people and search engines.

Structured data found (BreadcrumbList, Organization and WebPage) but with 2 problems, for example “Organization: missing name”.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

There is no robots.txt at sleemanbreweries.ca/robots.txt, the first file search crawlers ask for.

The homepage links to 97 pages on sleemanbreweries.ca and 12 external pages.

Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.sleemanbreweries.ca/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.sleemanbreweries.ca/news-and-events/notice-of-january-cybersecurity-incident, https://www.sleemanbreweries.ca/about, https://www.sleemanbreweries.ca/sustainability, https://www.sleemanbreweries.ca/breweries, https://www.sleemanbreweries.ca/brands and https://www.sleemanbreweries.ca/contact-us and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 84 found) and read each the way a search engine does.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,009 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 1 cookie (measured from a US location before any click).

Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.