Website review, no card needed

barrelny.com logo

barrelny.com website review

Visit site (opens in a new tab)Reviewed 20 October 202633 issues · 81 checks

This review found 33 issues worth fixing on barrelny.com, 12 of them high impact, across 81 checks. The most urgent: improve image delivery. 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.6 s1.2 sMay 2Oct 101.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.9 s
May 9, 20262.2 s
May 23, 20261.7 s
Jun 13, 20262.0 s
Jun 20, 20262.4 s
Jun 27, 20262.1 s
Jul 4, 20262.2 s
Jul 11, 20262.0 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20261.8 s
Sep 26, 20261.7 s
Oct 3, 20261.4 s
Oct 10, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
158 ms96 msJun 13Oct 10104 ms
Show as table
DateReal-visitor tap response (INP)
Jun 13, 2026151 ms
Jun 20, 2026138 ms
Jun 27, 2026142 ms
Jul 4, 2026132 ms
Jul 11, 2026130 ms
Jul 25, 2026109 ms
Aug 1, 2026112 ms
Aug 8, 2026115 ms
Aug 15, 2026115 ms
Aug 22, 2026122 ms
Aug 29, 2026135 ms
Sep 5, 2026142 ms
Sep 12, 2026144 ms
Sep 19, 2026144 ms
Sep 26, 2026131 ms
Oct 3, 2026103 ms
Oct 10, 2026104 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 barrelny.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. barrelny.com at 0.5 s0.5 s
  2. barrelny.com at 1.0 s1.0 s
  3. barrelny.com at 1.5 s1.5 s
  4. barrelny.com at 2.0 s2.0 s
  5. barrelny.com at 2.6 s2.6 s
  6. barrelny.com at 3.1 s3.1 s
  7. barrelny.com at 3.6 s3.6 s
  8. barrelny.com at 4.1 s4.1 s

Speed

7 to fix63
  • Improve image delivery

    1.4 s · 5.7 MB

    31 images could be 5.7 MB 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.

  • Render-blocking requests

    2.0 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 2.0 s.

  • Reduce unused JavaScript

    1.2 s · 230 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (website-files.com, Google Tag Manager and cloudfront.net and others), adding 6.8 MB and 622 ms of main-thread time.

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63 (desktop: 95). Pages that score under 90 lose visitors before the first paint.

  • website-files.com adds 227 ms

    227 ms

    website-files.com costs a phone 227 ms of main-thread work and 6.3 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.

  • Use efficient cache lifetimes

    600 ms · 129 KiB

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

  • Reduce unused CSS

    150 ms · 30 KiB

    About 30 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

    150 ms · 11 KiB

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

  • 7 long tasks on the main thread

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

  • Phones get a much slower page than desktops

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

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

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 810 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

5 to fix64
  • Largest Contentful Paint: 8.4 s

    8.4 s

    Your largest element takes 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We partner with DTC-led and retail-first CPG brands on stra…”.

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Time to Interactive: 8.7 s

    8.7 s

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

  • Speed Index: 4.5 s

    4.5 s

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

  • 7 images without width and height

    7 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

4 checks passed
  • Tap response (INP) got 28% faster for real visitors

    -28%

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

  • Largest content (LCP) got 32% faster for real visitors

    -32%

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

  • Total Blocking Time: 168 ms

    168 ms

    Scripts block the page for only 168 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.072

    0.072

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

Images and page weight

5 to fix18
  • Page weight: 6.8 MB in 74 requests

    6.8 MB

    Your homepage downloads 6.8 MB in 74 requests on a phone: images 6.0 MB (47), scripts 530 KiB (16) and fonts 169 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 7 images far larger than shown

    4.8 MB

    7 images are downloaded at several times the size a phone draws them, for example 6841d0c1e5a9756656a97971_McC-Hero.jpg at 2,880 px wide, shown at 153 px. Resized copies would save about 4.8 MB.

  • 2 images over 500 KB

    2 images weigh 4.0 MB together. On a phone connection a single image that size takes seconds.

  • 12 images in older formats

    12 images (5.3 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.

  • 7 images below the first screen load straight away

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

  • About 1.9 g of CO₂ per visit

    1.92 g

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

Accessibility

5 to fixGoogle 9093
  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (19 elements)

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

2 checks passed
  • Every image has alt text

    All 61 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Title is short (28 characters)

    Your title is only 28 characters: “Barrel — CPG Commerce Agency”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (174 characters)

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

  • 1 link with vague text

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

  • 58 internal links, 8 external

    The homepage links to 58 pages on barrelny.com and 8 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Your CPG Brand's Digital Ecosystem, Unified”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: LocalBusiness and Organization.

  • 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.barrelny.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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix93
  • 9 pages share a meta description

    https://www.barrelny.com/about, https://www.barrelny.com/work/all, https://www.barrelny.com/blog/all, https://www.barrelny.com/careers, https://www.barrelny.com/contact and https://www.barrelny.com/work/waterloo and 3 others use the same meta description. A description written for each page earns more clicks.

  • 11 pages without an H1

    https://www.barrelny.com/about, https://www.barrelny.com/work/all, https://www.barrelny.com/services, https://www.barrelny.com/blog/all, https://www.barrelny.com/careers and https://www.barrelny.com/contact and 5 others have 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 40 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

3 to fixGoogle 9671
  • 3 broken images

    3 images failed to load on a phone, for example https://www.barrelny.com/.

  • 5 small tap targets

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

  • 2 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix89
  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • 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 626 words of copy

    The homepage carries about 626 words of visible text.

7 checks passed
  • Clear next step on the first screen

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

  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact” and “Get Started”.

  • 2 short forms

    2 short forms (3 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 33 testimonial or review blocks, 33 customer or partner logos and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (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.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 12 other companies contacted

    Loading the homepage contacts 12 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 barrelny.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Webflow
Framework
jQuery
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on barrelny.com, including 12 speed issues, 3 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