A decade ago, a company website was a brochure. Finance signed off on a one-time build, marketing owned the copy, and the site sat there for years while the business ran on phone calls, field sales, and email. That same page is now a storefront, a lead qualifier, a support desk, a hiring channel, and for regulated industries, a compliance surface. Money moves through it whether anyone is watching or not.

An aging site is a finance problem now, not a marketing one. Slow pages, broken forms, and inaccessible layouts do more than annoy visitors. They erode conversion, inflate customer acquisition cost, and expose the balance sheet to legal risk that never appeared in the original scope. The categories below are the ones CFOs and controllers keep discovering too late, along with the questions to put to the web team before the next quarter closes.

Slow Pages Are a Direct Hit to Conversion

Speed is the leak most finance leaders underestimate, because the loss never appears on an invoice. Visitors who bounce before the page paints are invisible in the CRM. They were rarely captured. Every second of delay past that compounds the loss.

Put three questions to your web team. What are our current Core Web Vitals scores on mobile, measured on real user data and not a lab test? Which pages in the top ten by revenue fail those thresholds? And what is the projected lift, in orders or qualified leads, if we bring the worst offenders into the green? Google's case studies on this show the connection between speed metrics and measurable revenue outcomes, and the same math applies to your site.

Broken Forms and Dead Ends Cost More Than You Think

The contact form, the demo request, the quote builder. These are the cash registers of a B2B site. When they break, nothing tells the CFO. The lead never arrives, and the person who tried to submit it moves on.

Common failure modes are boring and expensive:

• Silent submission errors. A form throws an error the user cannot see, or sends the payload nowhere. Nobody notices until a sales rep asks why last month's inbound dried up.
• Fields that fail on mobile. A date picker that will not open on iOS, a dropdown that stretches off-screen, an autofill that overwrites the wrong field. Every one of these ends the session.
• Routing that goes nowhere. The lead lands in an inbox nobody monitors, or a CRM field that was renamed six months ago and no longer maps to a workflow.
• Payment friction. Checkout pages that reload, coupon fields that fail validation, or credit card forms that reject legitimate cards for cosmetic reasons.

Ask when each conversion path was last tested end-to-end, on a real phone, with a real card or a real submission. Ask what monitoring is in place to catch a form that stops firing. If the answer is "we would notice," the answer is no.

An Inaccessible Site Is a Legal Line Item

Accessibility used to sit under "nice to have." It sits under "litigation risk" now, and the finance team is usually the last to hear about it.

Beyond the legal exposure, an inaccessible site turns away paying customers who use screen readers, keyboard navigation, or high-contrast modes. Ask the web team for the most recent accessibility audit and its remediation status. Ask whether alt text, form labels, focus states, and color contrast meet WCAG 2.1 AA across the templates that generate the majority of traffic. If no audit exists, budget one this quarter.

Outdated Design Erodes Buyer Trust Before a Sales Call Happens

Prospects size up a company in seconds. A dated layout, mismatched fonts, stock imagery from three redesigns ago. These signal a business that stopped investing in itself. That impression carries into pricing conversations, procurement reviews, and vendor scorecards long before anyone speaks to sales.

The fix is not a vanity rebrand. It's a disciplined refresh guided by current development standards: clean information architecture, consistent components, and copy that answers the questions a buyer asks. Ask when the site was last reviewed against the way your ideal customer buys today, not the way they bought when the templates were chosen.

Aging Tech Debt Makes Every Future Change Slower

Old sites are expensive to change. A plugin stack that has not been updated in three years, a CMS on a version the vendor no longer patches, custom code nobody on the current team wrote. Each one turns a routine update into a project. Marketing asks for a landing page and gets a two-week estimate. Legal asks for a privacy update and gets a quote.

This is the leak that shows up as a rising line in the agency invoice. Ask the web team for a short inventory: platform version, plugin and dependency status, hosting configuration, and the average time to ship a simple content change. If simple changes take days, complex ones are going unmade, and the revenue programs that depend on them are running below capacity.

The Questions Worth Standing Up in the Next Review

A finance leader doesn't need to read code to close these leaks. A short list of questions, asked on a schedule, is enough to surface most of them:

1. What did the site earn or generate last quarter, and which pages drove it?
2. Which of those pages fail on speed, mobile usability, or accessibility today?
3. When was each revenue-critical form last tested end-to-end, and what monitors it?
4. What is our documented plan to reach WCAG 2.1 AA, and who owns it?
5. How long does a routine content change take, and why?

The site is no longer a fixed asset that depreciates in the background. It is an operating channel, and the leaks in it are line items waiting to be found. The teams that run it that way close the quarter with the revenue their marketing spend was supposed to produce.