fieldworkbrewing.com website review

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

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 2.1 MB and 1.6 s of main-thread time.

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

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

Google CDN costs a phone 522 ms of main-thread work and 764 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.

Google Tag Manager costs a phone 424 ms of main-thread work and 455 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.

Facebook costs a phone 253 ms of main-thread work and 252 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.

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

Klaviyo costs a phone 176 ms of main-thread work and 350 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.

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

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

1 image could be 74 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 71 KiB of CSS is downloaded but never applied on this page.

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.

4 KiB could be saved by minifying JavaScript.

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 133 ms to 133 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.0 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 13.6 MB in 166 requests on a phone: media 9.2 MB (7), scripts 2.1 MB (76) and images 1.5 MB (27). Under 2 MB keeps phones on slow connections fast.

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

2 images (252 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 3.84 g of CO₂e: 461.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is 66 characters, so Google will cut it off around 60: “Fieldwork Brewing Co. | Northern California Craft Beer & Beverages”.

There are 5 <h1> headlines (“”, “Member Login” and “Become a Member”). One clear main headline is easier for people and search engines.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 41 pages on fieldworkbrewing.com and 14 external pages.

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.

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

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

1 link from your homepage to your own site is broken, for example https://fieldworkbrewing.com/cdn-cgi/content?id=ug6Um9GwdwHWBMPsHiEGoZwFhmahqT4d1CXN9S4Q3MQ-1793962351.7790742-1.2.1.1-uO9Ea9Lxmzgtg0wFWOSMhreI.oiN5KM_tj_DhpuAkVeJrhIDoOZa_IdQSC1lsO48 (404).

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

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

fieldworkbrewing.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.

fieldworkbrewing.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.

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

DMARC is set to p=none, so mail pretending to be fieldworkbrewing.com is still delivered. Reports are on, so moving to quarantine is the next step.

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, Hotjar and Klaviyo and 1 more (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 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.