Building smarter, not harder: How one agency scales client websites with Duda

November 6, 2025
0 minute read

Jared Broussard often meets with prospects who own sites built on WordPress, the ubiquitous content management system that powers much of the web. It’s familiar, flexible, and, for many, often feels like the right choice. However, Broussard would be happy to tell you, maintaining the sites he does have on WordPress has been dramatically eroding his efficiency. “We were spending 75 percent of our time fixing WordPress problems,” Broussard recalled. “That’s time we could have been using to build content, run ads, or create something of value for our clients.”


Broussard’s agency, which manages about 70 to 80 websites today, has migrated almost all of his clients to Duda, a platform designed for agencies that need to build and manage client sites at scale. What began as a gradual shift born of frustration has evolved into a strategic overhaul of how his team works, and how they help their clients grow online.


The hidden costs of “free”


Like many marketers, Broussard’s journey with WordPress began in its promise of flexibility. But over time, that flexibility became a liability. No two sites were ever built the same. Plugins conflicted, themes broke, and a simple update could crash an entire site. “You could go outside and kick a tree three times, and who knows what will happen with a WordPress site,” he joked. “It’s like you never really know what you’re going to get.”


That unpredictability became more than just an annoyance—it was expensive. Broussard described one client incident where a security breach infiltrated a WordPress site with spam, requiring thirty hours of troubleshooting, cleanup, and reconfiguration. “I would have loved to spend those 30 hours on anything else,” he said. “I’m not a developer; I’m a marketer. That’s time that should’ve been spent on growth, not repairs.”


In contrast, his Duda sites rarely need that kind of intervention. After nearly eight years of using the platform, Broussard said he can “count on one hand” the number of maintenance issues they’ve encountered. “It’s night and day,” he said. “We can sleep at night knowing our clients’ sites are secure and running.”


What many clients fail to realize, he noted, is that the “free” nature of WordPress often comes with hidden costs. Plugin licenses, hosting, troubleshooting, and development time all add up. “We’ve calculated it,” Broussard explained. “Redesigning a WordPress site can cost two and a half times more than building a brand new one in Duda.” Once clients see the numbers, he added, “nine times out of ten, they’d rather start fresh on Duda.”


When every site is different, scale is impossible



The trouble, Broussard found, wasn’t just about bugs or security. It was about consistency, or, rather, the lack of it. “No two WordPress sites are built the same,” he said. “You have to get into the head of whoever developed it before you can even start working.” That means deciphering old code, figuring out theme structures, and hoping that the original developer didn’t leave behind a web of shortcuts and customizations.


By contrast, Duda’s uniformity has become one of its greatest advantages. “You can go into one Duda site and it’s going to look and behave the same as the next,” he said. “That consistency makes it so much easier to scale. My team can move from one project to another without losing hours just figuring out how something was built.”


That consistency also means predictable performance. Mobile optimization, plugin compatibility, and updates are no longer issues to manage. Broussard said his team can launch new pages or make edits in minutes; tasks that once took hours or required developer assistance. “With WordPress, adding a button to a mobile layout could take hours of custom coding,” he said. “In Duda, it takes five minutes.”


A more transparent pitch to clients


Shifting to Duda has transformed how Broussard sells websites. Most clients, he explained, come to his agency asking for a “redesign.” They’re accustomed to WordPress and assume that sticking with it will save money. That’s when he walks them through the math.


“I’ll show them two quotes side by side,” he said. “One for a WordPress redesign, and one for a brand-new Duda build. When they see that they’re saving a third of the hours—and getting a modern, easy-to-manage website—they almost always choose Duda.”


The key, he added, is helping clients understand what their money actually buys. “They’d rather invest in things that create value for their business—content, SEO, social media—than spend on troubleshooting and plugin updates,” he said. Once clients see how much time and cost goes into simply maintaining a WordPress site, they rarely look back.


Even clients deeply entrenched in the WordPress ecosystem are often surprised to learn how much of their frustration is avoidable. “A lot of them just think that’s how websites work,” Broussard said. “They’ve never experienced something different.”


From maintenance mode to growth mode


Broussard describes Duda as a future-facing platform, one that lets his agency focus on strategic growth rather than technical firefighting. “We want to build landing pages, run Google Ads, manage social media,” he said. “We want to do all the things that actually grow our clients’ businesses. Duda lets us do that without worrying about whether the site is going to crash.”


The result is a leaner, more profitable operation. Less time spent on maintenance means more time for value-creating work. For Broussard, it’s not just about the hours saved; it’s about what those hours can become. “If I can spend the same time building a campaign instead of fixing a broken plugin, my clients get more value, and we make more money,” he said.


He sees it as a strategic realignment. Agencies, he argues, shouldn’t be in the business of firefighting. “Our role is to grow our clients’ brands, not babysit websites,” he said. “Duda allows us to stay focused on that mission.”


The changing definition of customization


One of the biggest shifts Broussard has observed in recent years is how clients define a good website. “Years ago, everyone wanted something highly customized,” he said. “They wanted unique functionality, animations, integrations—the works.” But that approach, he believes, is becoming outdated.


“With AI and automation becoming mainstream, you just don’t need all of that anymore,” he said. “What you need is a site that works. A site that’s fast, modern, and always online.”


He often finds himself challenging clients’ assumptions. “They’ll say, ‘We need WordPress because it’s customizable,’ and I’ll ask, ‘Do you really need all that customization?’ Most of the time, the answer is no,” he said. “They just want a site that looks great and performs well.”


In that sense, Duda’s balance between flexibility and simplicity is its superpower. “It gives you everything you actually need, and nothing you don’t,” Broussard said. To him, It’s not about building the most complex website anymore. Rather, it’s about building the smartest one.


Educating clients through experience


For Broussard, one of the most effective ways to win clients over is to show, not tell. He’s developed a short presentation that compares WordPress and Duda side by side, highlighting not just features, but the real-world implications of each. “When I walk clients through it, I can see them nodding their heads,” he said. “They recognize their own frustrations in what I’m describing.”


The presentation outlines everything from plugin management to update risks to hidden development costs. But Broussard said the most compelling part is the math. “When we show them the number of hours they’ll save, and how much of their budget can go toward marketing instead of maintenance, it clicks,” he explained. “They get it.”


Once that realization happens, the conversation shifts from “What’s cheaper?” to “What’s smarter?” “It’s not even about selling Duda,” Broussard added. “It’s about helping them see what’s possible when their website just works.”


Putting results first


Broussard’s experience reflects a broader trend in the agency world. As technology advances and client expectations evolve, agencies are rethinking what they offer and how they deliver it. Speed, security, and scalability have become the new differentiators, and Duda’s model fits squarely into that shift.


“I think WordPress years ago was awesome because everyone wanted their websites customized, you know,” Broussard said. “But, in this day and age, you don't need that, right? You need something that works. That stays online.”


He believes this mindset will define the next generation of digital agencies. “Clients don’t care what CMS you use,” he said. “They care that their site works, that it loads when someone Googles them, and that it helps their business grow.”


Did you find this article interesting?


Thanks for the feedback!
By Shawn Davis April 16, 2026
Website builder analysed 69M AI crawler visits across over 850,000 websites in February 2026 to determine key trends and characteristics that increase local AEO
By Shawn Davis April 1, 2026
Core Web Vitals aren't new, Google introduced them in 2020 and made them a ranking factor in 2021. But the questions keep coming, because the metrics keep changing and the stakes keep rising. Reddit's SEO communities were still debating their impact as recently as January 2026, and for good reason: most agencies still don't have a clear, repeatable way to measure, diagnose, and fix them for clients. This guide cuts through the noise. Here's what Core Web Vitals actually measure, what good scores look like today, and how to improve them—without needing a dedicated performance engineer on every project. What Core Web Vitals measure Google evaluates three user experience signals to determine whether a page feels fast, stable, and responsive: Largest Contentful Paint (LCP) measures how long it takes for the biggest visible element on a page — usually a hero image or headline — to load. Google considers anything under 2.5 seconds good. Above 4 seconds is poor. Interaction to Next Paint (INP) replaced First Input Delay (FID) in March 2024. Where FID measures the delay before a user's first click is registered, INP tracks the full responsiveness of every interaction across the page session. A good INP score is under 200 milliseconds. Cumulative Layout Shift (CLS) measures visual stability — how much page elements unexpectedly move while content loads. A score below 0.1 is good. Higher scores signal that images, ads, or embeds are pushing content around after load, which frustrates users and tanks conversions. These three metrics are a subset of Google's broader Page Experience signals, which also include HTTPS, safe browsing, and mobile usability. Core Web Vitals are the ones you can most directly control and improve. Why your clients' scores may still be poor Core Web Vitals scores vary dramatically by platform, hosting, and how a site was built. Some of the most common culprits agencies encounter: Heavy above-the-fold content . A homepage with an autoplay video, a full-width image slider, and a chat widget loading simultaneously will fail LCP every time. The browser has to resolve all of those resources before it can paint the largest element. Unstable image dimensions . When an image loads without defined width and height attributes, the browser doesn't reserve space for it. It renders the surrounding text, then jumps it down when the image appears. That jump is CLS. Third-party scripts blocking the main thread . Analytics pixels, ad tags, and live chat tools run on the browser's main thread. When they stack up, every click and tap has to wait in line — driving INP scores up. A single slow third-party script can push an otherwise clean site into "needs improvement" territory. Too many web fonts . Each font family and weight is a separate network request. A page loading four font files before rendering any text will fail LCP, especially on mobile connections. Unoptimized images . JPEGs and PNGs served at full resolution, without compression or modern formats like WebP or AVIF, add unnecessary weight to every page load. How to measure them accurately There are two types of Core Web Vitals data you should be looking at for every client: Lab data comes from tools like Google PageSpeed Insights, Lighthouse, and WebPageTest. It simulates page loads in controlled conditions. Lab data is useful for diagnosing specific issues and testing fixes before you deploy them. Field data (also called Real User Monitoring, or RUM) comes from actual users visiting the site. Google collects this through the Chrome User Experience Report (CrUX) and surfaces it in Search Console and PageSpeed Insights. Field data is what Google actually uses as a ranking signal — and it often looks worse than lab data because it reflects real-world device and connection variability. If your client's site has enough traffic, you'll see field data in Search Console under Core Web Vitals. This is your baseline. Lab data helps you understand why the scores are what they are. For clients with low traffic who don't have enough field data to appear in CrUX, you'll be working primarily with lab scores. Set that expectation early so clients understand that improvements may not immediately show up in Search Console. Practical fixes that move the needle Fix LCP: get the hero image loading first The single most effective LCP improvement is adding fetchpriority="high" to the hero image tag. This tells the browser to prioritize that resource over everything else. If you're using a background CSS image for the hero, switch it to anelement — background images aren't discoverable by the browser's preload scanner. Also check whether your hosting serves images through a CDN with caching. Edge delivery dramatically reduces the time-to-first-byte, which feeds directly into LCP. Fix CLS: define dimensions for every media element Every image, video, and ad slot on the page needs explicit width and height attributes in the HTML. If you're using responsive CSS, you can still define the aspect ratio with aspect-ratio in CSS while leaving the actual size fluid. The key is giving the browser enough information to reserve space before the asset loads. Avoid inserting content above existing content after page load. This is common with cookie banners, sticky headers that change height, and dynamically loaded ad units. If you need to show these, anchor them to fixed positions so they don't push content around. Fix INP: reduce what's competing for the main thread Audit third-party scripts and defer or remove anything that isn't essential. Tools like WebPageTest's waterfall view or Chrome DevTools Performance panel show you exactly which scripts are blocking the main thread and for how long. Load chat widgets, analytics, and ad tags asynchronously and after the page's critical path has resolved. For most clients, moving non-essential scripts to load after the DOMContentLoaded event is a meaningful INP improvement with no visible impact on the user experience. For websites with heavy JavaScript — particularly those built on frameworks with large client-side bundles — consider breaking up long tasks into smaller chunks using the browser's Scheduler API or simply splitting components so the main thread isn't locked for more than 50 milliseconds at a stretch. What platforms handle automatically One of the practical advantages of building on a platform optimized for performance is that many of these fixes are applied by default. Duda, for example, automatically serves WebP images, lazy loads below-the-fold content, minifies CSS, and uses efficient cache policies for static assets. As of May 2025, 82% of sites built on Duda pass all three Core Web Vitals metrics — the highest recorded pass rate among major website platforms. That baseline matters when you're managing dozens or hundreds of client sites. It means you're starting each project close to or at a passing score, rather than diagnosing and patching a broken foundation. How much do Core Web Vitals actually affect rankings? Honestly, they're a tiebreaker — not a primary signal. Google has been clear that content quality and relevance still dominate ranking decisions. A well-optimized site with thin, irrelevant content won't outrank a content-rich competitor just because its CLS is 0.05. What Core Web Vitals do affect is the user experience that supports those rankings. Pages with poor LCP scores have measurably higher bounce rates. Sites with high CLS lose users mid-session. Those behavioral signals — time on page, return visits, conversions — are things search engines can observe and incorporate. The practical argument for fixing Core Web Vitals isn't just "because Google said so." It's that faster, more stable pages convert better. Every second of LCP improvement can reduce bounce rates by 15–20% depending on the industry and device mix. For client sites that monetize through leads or eCommerce, that's a revenue argument, not just an SEO argument. A repeatable process for agencies Audit every new site before launch. Run PageSpeed Insights and record LCP, INP, and CLS scores for both mobile and desktop. Flag anything in the "needs improvement" or "poor" range before the client sees the live site. Check Search Console monthly for existing clients. The Core Web Vitals report surfaces issues as they appear in field data. Catching a regression early — before it compounds — is significantly easier than explaining a traffic drop after the fact. Document what you've improved. Clients rarely see Core Web Vitals scores on their own. A monthly one-page performance summary showing before/after scores builds credibility and makes your technical work visible. Prioritize mobile. Google uses mobile-first indexing, and field data shows that mobile CWV scores are almost always worse than desktop. If you only have time to optimize one version, do mobile first. Core Web Vitals aren't a one-time fix. Platforms change, new scripts get added, campaigns bring in new widgets. Build the audit into your workflow and treat it like any other ongoing deliverable, and you'll stay ahead of the issues before they affect your clients' rankings. Duda's platform is built with Core Web Vitals performance in mind. Explore how it handles image optimization, script management, and site speed automatically — so your team spends less time debugging and more time building.
By Ilana Brudo March 31, 2026
Vertical SaaS must transition from tools to an AI-powered Vertical Operating System (vOS). Learn to leverage context, end tech sprawl, and maximize retention.
Show More

Latest posts