brusters.com website review

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, here.com and Facebook and others), adding 2.6 MB and 1.5 s of main-thread time.

14 long tasks block the main thread while loading, the longest for 1.7 s. During a long task the page ignores taps.

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

here.com costs a phone 373 ms of main-thread work and 1.5 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.

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

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

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

Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need.

21 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

Your homepage downloads 24.2 MB in 176 requests on a phone: images 12.4 MB (34), media 7.8 MB (1) and scripts 2.5 MB (69). Under 2 MB keeps phones on slow connections fast.

4 images weigh 9.1 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 aspot_26-11_nov_3_thanksgivingcakespies.jpg at 3,813 px wide, shown at 390 px. Resized copies would save about 8.1 MB.

8 images (9.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.

4 images further down the page (2.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

aspot_26-11_nov_3_thanksgivingcakespies.jpg 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).

By the Sustainable Web Design model, a visit to your homepage emits about 6.86 g of CO₂e: 823.1 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.

Page should contain a level-one heading: 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.

Elements with visible text labels do not have matching accessible names. (4 elements).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 19 characters: “Bruster's Ice Cream”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

No XML sitemap at https://brusters.com/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 43 pages on brusters.com and 29 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.

/gift-cards has no meta description, so Google writes the search snippet from whatever text it finds.

/gift-cards has no <h1> headline, so visitors and search engines get no clear main topic.

/gift-cards has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56348922&tm=gtm002&Ver=2&mid=37147f68-48d4-462b-af11-8495ed8a07e0&bo=2&sid=f818e700d7df11f19ea26fc072656e78&vid=f818d9c0d7df11f193d5d545b45f3144&vids=1&msclkid=N&pi=91.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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 ()”.

Requests the geolocation permission on page load.

Chrome logged issues while loading the page (“Cookie”).

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

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

HSTS is set, but max-age is 30 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://brusters.com/gift-cards/.

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.

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

brusters.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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

brusters.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

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, Meta Pixel and Microsoft Ads and 1 more (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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