behrens.com website review

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

6 images could be 419 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

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

Your mobile performance score is 39 (desktop: 72). 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, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

Google Tag Manager costs a phone 759 ms of main-thread work and 645 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 335 ms of main-thread work and 312 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.

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

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

10 KiB could be saved by minifying JavaScript.

About 160 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 150 ms).

Desktop scores 72 but mobile only 39. 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.

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

Your largest element takes 15.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BEHRENS MANUFACTURING An American Tradition QUALITY METALWA…”.

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

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

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

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

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

Your homepage downloads 3.8 MB in 213 requests on a phone: scripts 1.7 MB (109), images 1.6 MB (46) and fonts 317 KiB (8). Under 2 MB keeps phones on slow connections fast.

3 images (136 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.

3 images further down the page (88 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 1.08 g of CO₂e: 129.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: 1 element on the page fails this check, rated moderate by axe-core.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

There are 2 <h1> headlines (“Behrens Manufacturing” and “Behrens Manufacturing”). One clear main headline is easier for people and search engines.

The homepage links to 76 pages on behrens.com and 16 external pages.

/products, /product-category/accessories, /product-category/cans, /product-category/pails-buckets, /product-category/tubs and /product-category/decorative and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 images failed to load on a phone, for example https://behrensstg.wpenginepowered.com/wp-content/uploads/vs-galvanized-sheet-new-1.jpg.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

7 resources load over plain http on your https page (for example http://behrensstg.wpenginepowered.com/wp-content/uploads/vs-galvanized-sheet-new-1.jpg); browsers block or warn about them.

1 link from your homepage to your own site is broken, for example https://www.behrens.com/cdn-cgi/l/email-protection (404).

2 links to other sites are dead, for example http://www.twitter.com/Behrensmfg (520).

1 link go through two or more redirects, for example https://www.behrens.com/wholesale/.

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

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

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 454 words of visible text.

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, LinkedIn Insight and Meta Pixel and 3 mores (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 21 cookies, 1 of them by other companies (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 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.