Website review, no card needed

alliedbrass.com logo

alliedbrass.com website review

Visit site (opens in a new tab)Reviewed 5 November 202630 issues · 84 checks

This review found 30 issues worth fixing on alliedbrass.com, 9 of them high impact, across 84 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.0 s1.6 sMay 16Oct 311.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.8 s
Sep 19, 20261.9 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
112 ms75 msMay 16Oct 31101 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202679 ms
May 23, 202679 ms
May 30, 202679 ms
Jun 6, 202679 ms
Jun 13, 202679 ms
Jun 20, 202681 ms
Jun 27, 202687 ms
Jul 4, 202693 ms
Jul 11, 202697 ms
Jul 18, 2026104 ms
Jul 25, 2026105 ms
Aug 1, 2026108 ms
Aug 8, 2026105 ms
Aug 15, 2026104 ms
Aug 22, 2026103 ms
Aug 29, 2026103 ms
Sep 5, 2026104 ms
Sep 12, 2026103 ms
Sep 19, 2026104 ms
Sep 26, 2026104 ms
Oct 3, 2026104 ms
Oct 10, 2026104 ms
Oct 17, 2026102 ms
Oct 24, 202697 ms
Oct 31, 2026101 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of alliedbrass.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alliedbrass.com at 0.8 s0.8 s
  2. alliedbrass.com at 1.5 s1.5 s
  3. alliedbrass.com at 2.3 s2.3 s
  4. alliedbrass.com at 3.0 s3.0 s
  5. alliedbrass.com at 3.8 s3.8 s
  6. alliedbrass.com at 4.6 s4.6 s
  7. alliedbrass.com at 5.3 s5.3 s
  8. alliedbrass.com at 6.1 s6.1 s

Speed

10 to fix61
  • Render-blocking requests

    1.0 s

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

  • 8 third-party services on the page

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

  • Mobile performance score: 61

    61/100

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

  • Reduce unused JavaScript

    654 KiB

    About 654 KiB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 429 ms

    429 ms

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

  • Improve image delivery

    150 ms · 284 KiB

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

  • Main-thread work: 3.7 s

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

  • 12 long tasks on the main thread

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

  • Shopify adds 169 ms

    169 ms

    Shopify costs a phone 169 ms of main-thread work and 822 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.

  • 2,256 HTML elements

    The page has 2,256 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Use efficient cache lifetimes

    222 KiB

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

  • Minify JavaScript

    160 ms · 23 KiB

    23 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    150 ms · 23 KiB

    About 23 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.

  • Legacy JavaScript

    21 KiB

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

  • Chained critical requests

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

  • Forced reflow

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

1 checks passed
  • Server response: 9 ms

    9 ms

    Your server sent the HTML in 9 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Time to Interactive: 20.4 s

    20.4 s

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

  • Largest Contentful Paint: 4.6 s

    4.6 s

    Your largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Functionality Wrapped in Style”.

  • Total Blocking Time: 711 ms

    711 ms

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

  • Tap response (INP) got 25% slower for real visitors

    +25%

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Speed Index: 4.1 s

    4.1 s

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 97 ms

    97 ms

    Real visitors wait 97 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.5 s

    1.5 s

    Real visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 730 ms

    730 ms

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix75
  • Page weight: 3.7 MB in 413 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 413 requests on a phone: scripts 1.8 MB (136), other files 1.1 MB (190) and images 546 KiB (66). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    78 KiB

    1 image is downloaded at several times the size a phone draws it, for example home-category-cabinet-hardware.jpg at 2,048 px wide, shown at 342 px. Resized copies would save about 78 KiB.

  • About 1.0 g of CO₂ per visit

    1.04 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 9394
  • 43 text elements with low contrast

    43 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • Alternative text of images should not be repeated as text (6 elements)

    Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

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

2 checks passed
  • Every image has alt text

    All 29 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10085
  • No H1 headline

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

  • Meta description is long (262 characters)

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

  • 264 internal links, 3 external

    The homepage links to 264 pages on alliedbrass.com and 3 external pages.

6 checks passed
  • Title: 65 characters

    Your title is a healthy 65 characters: “Allied Brass | Premium Bathroom Hardware, Handcrafted in Virginia”.

  • Canonical URL set

    The canonical URL is https://www.alliedbrass.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.alliedbrass.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, description and contact details; logo and sameAs (social profiles) would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,339 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.alliedbrass.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 page without an H1

    https://www.alliedbrass.com/collections/towel-bars has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 5 broken images

    5 images failed to load on a phone, for example https://d.adroll.com/uev/GMTTBR5ZTNEPTMJRSTYC7W/VMITCKN2EBAZ3H35HOKAT2/?af0=0fe6f973&adroll_fpc=a4332272051b61b7870ee497204f3016-1793860825794&pv=33900194192.955498&arrfrr=https%3A%2F%2Fwww.alliedbras.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.

2 checks passed
  • Tap targets are thumb-sized

    46 of 51 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • No social proof

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

  • Local business without LocalBusiness data

    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 opening hours

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

  • No map or directions link

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

  • No risk reducer

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

  • About 687 words of copy

    The homepage carries about 687 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP COLLECTIONS”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Reserve Toilet Paper Holders”, “Shop Collections” and “Bathroom Shop the Look →”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads 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.

  • 28 cookies set on arrival

    28

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

  • No consent tool detected

    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.

  • 32 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at alliedbrass.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Warnify Pro Warnings · Inbox · Analyzify Ga4 Ads Tracking · Product Warnings · Forms · Affirm · Kickflip · adroll.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

Company

Headquarters
Louisa

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on alliedbrass.com, including 16 speed issues, 2 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25