oldstylebeer.com website review

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

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

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

About 348 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

A phone's processor spends 2.5 s on main-thread work while loading, 686 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

3 third-party services load with your homepage (Shopify, Mailchimp and shop.app), adding 100 KiB and 144 ms of main-thread time.

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

5 files are served with short cache lifetimes, so returning visitors download them again (11 KiB).

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.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

Your homepage downloads 33.5 MB in 160 requests on a phone: media 30.7 MB (1), images 1.6 MB (22) and other files 640 KiB (68). Under 2 MB keeps phones on slow connections fast.

Screenshot_2026-03-23_at_12.35.26_PM.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

4 images (228 KiB) 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.

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

3 tap targets are too small or too close together to hit reliably with a finger.

2 elements have a tabindex above 0, which scrambles the keyboard order.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 image has no alt text, which hurts accessibility and image search.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 55 characters: “Welcome to the official online store of Old Style Beer!”. 70 to 160 characters is enough to sell the click.

There are 2 <h1> headlines (“.logo_image { max-height: unset!important; width:…” and “.logo_image { max-height: unset!important; width:…”). One clear main headline is easier for people and search engines.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 98 pages on oldstylebeer.com and 12 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://oldstylebeer.com/collections/baseball-collection/products/old-style-baseball-champions-navy and https://oldstylebeer.com/products/old-style-baseball-champions-navy all use the title “Old Style Baseball Champions Tee | Old Style – Old Style Beer Store”. Search engines can't tell which page to show for a search, so each competes with the others.

https://oldstylebeer.com/collections/all-items, https://oldstylebeer.com/collections/new-arrivals, https://oldstylebeer.com/collections/t-shirts, https://oldstylebeer.com/collections/hockey-collection, https://oldstylebeer.com/collections/baseball-collection and https://oldstylebeer.com/collections/outerwear and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://oldstylebeer.com/collections/baseball-collection/products/old-style-baseball-champions-navy and https://oldstylebeer.com/products/old-style-baseball-champions-navy use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://oldstylebeer.com/collections/baseball-collection/products/old-style-baseball-champions-navy, whose canonical is https://oldstylebeer.com/products/old-style-baseball-champions-navy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://oldstylebeer.com/pages/heilemans-old-style-beer and https://oldstylebeer.com/pages/chicago-handshake have no <h1> headline, so visitors and search engines get no clear main topic.

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

8 of 40 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 273 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 9 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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