abcbrew.com website review

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

14 images could be 3.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.2 s faster on a phone.

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

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

About 141 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 28 (desktop: 56). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, elfsightcdn.com and Facebook and others), adding 3.0 MB and 819 ms of main-thread time.

elfsightcdn.com costs a phone 292 ms of main-thread work and 1.8 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Google Tag Manager costs a phone 298 ms of main-thread work and 632 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

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

11 KiB could be saved by minifying CSS.

Desktop scores 56 but mobile only 28. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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.74 (75th percentile). Good is under 0.1.

Your largest element takes 32.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “It’s Our Beer That Makes Us Great! See Our Flagship Brew Se…”.

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

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

The layout shifts by 0.738 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

Scripts block taps and scrolling for 291 ms in total while the page loads. Good is under 200 ms.

9 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-17, real Chrome visitors' tap response (inp) went from 129 ms to 144 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 10.6 MB in 118 requests on a phone: images 8.4 MB (51), scripts 1.8 MB (30) and fonts 206 KiB (4). Under 2 MB keeps phones on slow connections fast.

4 images weigh 5.2 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example food-logo-shading.png at 1,920 px wide, shown at 390 px. Resized copies would save about 1.3 MB.

15 images (6.6 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.

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

4 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h1 → h4 and h3 → h6), which makes the page harder to scan with a screen reader.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 309 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 75 pages on abcbrew.com and 24 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.

There is no /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.

/mug-club, /join-the-team, /podcast, /harrisburg, /harrisburg/abbey-bar and /mechanicsburg and 9 others use the same meta description. A description written for each page earns more clicks.

/mug-club, /join-the-team, /podcast, /harrisburg, /harrisburg/abbey-bar and /mechanicsburg and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

/harrisburg/abbey-bar, /craft-beverages/soda and /spirits took over 3 s to send their HTML from our server.

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

10 of 41 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_CERT_COMMON_NAME_INVALID”.

2 links from your homepage to your own site are broken, for example https://abcbrew.com/images/food-menus/MENU-Paper-B&W-2023.pdf (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

1 link go through two or more redirects, for example http://eepurl.com/gOsRqv.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

abcbrew.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

abcbrew.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

The homepage has only about 186 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

DMARC is set to p=none, so mail pretending to be abcbrew.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, 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 12 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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.