Website review, no card needed

blockandcompany.com logo

blockandcompany.com website review

Visit site (opens in a new tab)Reviewed 25 October 202644 issues · 83 checks

This review found 44 issues worth fixing on blockandcompany.com, 14 of them high impact, across 83 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
3.3 s2.5 sMay 23Aug 222.6 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.9 s
May 30, 20263.2 s
Jun 6, 20263.2 s
Jun 13, 20263.2 s
Jun 20, 20262.9 s
Aug 22, 20262.6 s

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 blockandcompany.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. blockandcompany.com at 0.4 s0.4 s
  2. blockandcompany.com at 0.8 s0.8 s
  3. blockandcompany.com at 1.1 s1.1 s
  4. blockandcompany.com at 1.5 s1.5 s
  5. blockandcompany.com at 1.9 s1.9 s
  6. blockandcompany.com at 2.3 s2.3 s
  7. blockandcompany.com at 2.6 s2.6 s
  8. blockandcompany.com at 3.0 s3.0 s

Speed

13 to fix41
  • Render-blocking requests

    8.3 s

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

  • Reduce unused JavaScript

    3.0 s · 1,006 KiB

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

  • Use efficient cache lifetimes

    1.4 s · 536 KiB

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

  • Mobile performance score: 41

    41/100

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

  • 8 third-party services on the page

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

  • Reduce unused CSS

    750 ms · 142 KiB

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

  • Google CDN adds 620 ms

    620 ms

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

  • Nexcess.Net adds 320 ms

    320 ms

    Nexcess.Net costs a phone 320 ms of main-thread work and 2.2 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.

  • Minify JavaScript

    450 ms · 90 KiB

    90 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    450 ms · 51 KiB

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

  • Google Tag Manager adds 359 ms

    359 ms

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

  • Main-thread work: 3.5 s

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

  • 2,351 HTML elements

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

  • Minify CSS

    150 ms · 15 KiB

    15 KiB could be saved by minifying CSS.

  • 14 long tasks on the main thread

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

  • Improve image delivery

    160 KiB

    3 images could be 160 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Font display

    150 ms

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

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

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

6 to fix48
  • Largest Contentful Paint: 13.5 s

    13.5 s

    Your largest element takes 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Block and Company is now a subsidiary of BankSupplies Inc.,…”.

  • Time to Interactive: 22.6 s

    22.6 s

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

  • First Contentful Paint: 6.2 s

    6.2 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • Total Blocking Time: 668 ms

    668 ms

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

  • 3 images without width and height

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

2 checks passed
  • Largest content (LCP) got 10% faster for real visitors

    -10%

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

  • Cumulative Layout Shift: 0.003

    0.003

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

Images and page weight

3 to fix50
  • Page weight: 4.8 MB in 198 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 198 requests on a phone: scripts 2.3 MB (99), images 1.7 MB (45) and other files 366 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • 13 images in older formats

    13 images (1.4 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.

  • 2 images far larger than shown

    85 KiB

    2 images are downloaded at several times the size a phone draws them, for example Accubanker_Carousel.jpg at 825 px wide, shown at 195 px. Resized copies would save about 85 KiB.

  • About 1.4 g of CO₂ per visit

    1.36 g

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

1 checks passed
  • Images load when needed

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

Accessibility

6 to fixGoogle 8591
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 8 images without alt text

    8 images have no alt text, which hurts accessibility and image search.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 39 automated accessibility rules passed

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

SEO

5 to fixGoogle 10077
  • Title is short (22 characters)

    Your title is only 22 characters: “Block and Company Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (163 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 496 internal links, 0 external

    The homepage links to 496 pages on blockandcompany.com and 0 external pages.

3 checks passed
  • One H1 headline

    Your main headline reads: “Acquisition Announcement”.

  • 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://banksupplies.com/sitemaps/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.blockandcompany.com/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.

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

Other pages

3 to fix86
  • 9 linked pages hidden from search

    https://www.blockandcompany.com/shop-by-industry, https://www.blockandcompany.com/shop-by-industry/retail, https://www.blockandcompany.com/shop-by-industry/banks-credit-union-products, https://www.blockandcompany.com/shop-by-industry/banks-credit-union-products/banks-credit-unions-mandatory-signage, https://www.blockandcompany.com/shop-by-industry/banks-credit-union-products/teller-vault and https://www.blockandcompany.com/bags-accessories and 3 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 5 pages share a meta description

    https://www.blockandcompany.com/shop-by-industry, https://www.blockandcompany.com/shop-by-industry/retail, https://www.blockandcompany.com/shop-by-industry/banks-credit-union-products/cash-handling, https://www.blockandcompany.com/shop-by-industry/banks-credit-union-products/teller-vault and https://www.blockandcompany.com/bags-accessories/deposit-bags/universal-transaction-two-pocket-bags use the same meta description. A description written for each page earns more clicks.

  • 13 pages without an H1

    https://www.blockandcompany.com/shop-by-industry, https://www.blockandcompany.com/shop-by-industry/retail, https://www.blockandcompany.com/shop-by-industry/banks-credit-union-products/plastic-tamper-evident-deposit-bags, https://www.blockandcompany.com/shop-by-industry/banks-credit-union-products/cash-handling, https://www.blockandcompany.com/shop-by-industry/banks-credit-union-products/check-handling and https://www.blockandcompany.com/shop-by-industry/banks-credit-union-products/teller-vault and 7 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 191 found) and read each the way a search engine does.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9274
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=27031250&Ver=2&mid=e1e20070-7e70-4b4e-aa01-feab4c854363&bo=1&sid=b6dc7780d07511f1a9590180474144b5&vid=b6dc8ac0d07511f1950b390a75f5fe99&vids=1&msclkid=N&pi=918639831&lg.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://nxtcfm.s3.amazonaws.com/537eb14738924767c6219f10eb70cea8-ac.css' from origin 'http…”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • No call to action on the first screen

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

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

  • Thin social proof

    Social proof on the homepage: 30 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 100 words

    The homepage has only about 100 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

4 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop by Industry” and “All Shop by Industry”.

  • 16 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 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.

  • 29 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Magento
Analytics
Google 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 44 issues on blockandcompany.com, including 19 speed issues, 5 SEO issues and 4 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