Conversion rate optimization (CRO) services

Conversion rate optimization (CRO) finds out why visitors who could become customers leave, and changes the website so more of them take the next step. Dardo does CRO for sites that already get steady traffic: an audit of the funnel, forms, speed, messaging and mobile experience, changes ranked by evidence, and the design and code to ship them. We run A/B tests when traffic supports them and say plainly when it does not.

Message us on WhatsAppRead in Spanish
Dardo / Editorial illustration
On this page

What CRO work includes

We shape the engagement around the actual brief. The proposal identifies which of these deliverables are included, who supplies the inputs and how each one is accepted.

  • Funnel and event audit: what is tracked, what is missing and what is wrong
  • Review of forms, speed, messaging, proof, mobile and checkout
  • Session recordings and on-page evidence for each problem
  • Hypothesis backlog ranked by evidence and effort
  • Design and implementation of the changes in your site
  • A/B tests where traffic allows; before-and-after measurement where it does not
  • Monthly report of changes shipped and what the data shows

Is your site ready for CRO?

CRO fits a site that already has steady traffic and a clear action, such as a quote request, a sign-up or a purchase, but too few people complete it. If the page itself is missing or speaks to the wrong audience, start with a landing page or a website redesign. If too few people arrive in the first place, SEO comes first, because improving a page few people see changes little.

How a CRO engagement runs

We start by checking the measurement, because a test is only as good as its data. Common problems are events that fire twice, forms counted by button clicks instead of successful submissions, and no record of which inquiries became customers. With a baseline you can trust, we review the funnel step by step using analytics, session recordings, form drop-off, speed data and the questions your sales team hears. Each finding becomes a hypothesis: what we will change, why, which metric should move and how we will know.

Then the work runs in monthly cycles. We take the top items from the backlog by evidence and effort, design and build them in your site, and measure them: as an A/B test when traffic can reach a decision, otherwise against a clean baseline with the release date marked. The monthly report lists what shipped, what the data shows, what was inconclusive and what comes next. Because the team that finds the problem also builds the site, a change does not wait in another agency's queue.

What does the CRO audit cover?

The audit follows the path to the action, not the design in isolation. Each finding comes with the evidence behind it and a proposed change:

Speed is part of conversion as well as search. Google's Search Central documentation sets good Core Web Vitals at Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint under 200 milliseconds and Cumulative Layout Shift under 0.1. We measure them on the pages that convert, from real visits where the data exists, before and after each change.

  • Funnel and events: every step from landing to inquiry or purchase, checked against real submissions and orders
  • Forms: number of fields, labels, error messages, the right mobile keyboard, and spam protection that does not block real people
  • Messaging and proof: whether the page says what you sell, to whom and why you, with evidence a buyer would believe
  • Mobile: the full journey on a phone, including tap targets, sticky elements and payment
  • Checkout where relevant: forced accounts, costs shown late, payment options and error handling
  • Accessibility barriers that also stop customers, such as unlabeled fields or dialogs that trap the keyboard
  • Session recordings and the questions sales hears, to explain what the numbers show

Which methods does your traffic support?

An A/B test needs enough comparable visitors and conversions to tell a real difference from chance. Below that level, the honest method is research-led change measured against a clean baseline, and the report says which method was used.

Before a test starts we write down the metric, the smallest change worth detecting, the sample it needs and how long it must run, and we do not stop it early because the first days look good. The useful measure is conversions per variant, not page views.

Which methods does your traffic support?
Traffic levelWhat worksWhat doesn't
A few conversions a weekResearch-led fixes from recordings, form analytics, interviews and sales questions; clear fixes shipped and compared with a clean baselineA/B tests: they cannot reach a decision in useful time, and a winner picked from a handful of conversions is noise
Steady daily conversions on one page or funnelA/B tests of large changes, such as the offer, page structure or form length, one at a time, with research-led fixes elsewhereTesting button colors or small wording changes, whose effect is too small to detect at this volume
High volume across several funnelsA continuous program of experiments, segmented by device and channel, with feature flags for gradual rolloutsOverlapping tests on the same visitors without a plan, and declaring winners without checking the traffic split and data quality

E-commerce: where checkouts lose buyers

For online stores the checkout gets its own review. Baymard Institute's average documented cart abandonment rate is 70.22%, calculated from 50 studies (last updated 22 September 2025). Part of that is people who were only browsing, so the goal is not zero; it is the share lost to problems the store can fix.

Baymard's checkout survey lists those problems: extra costs that appear late, forced account creation, long or complicated checkouts, site errors, declined cards and too few payment methods. We test the checkout on real phones with your payment provider in test mode, read its decline and error reports, and compare drop-off at each step before and after each change.

Which tools, and what about privacy?

When we set up the analytics, we use PostHog: funnels, session replays linked to each experiment variant, feature flags to release changes gradually, and experiments with Bayesian or frequentist statistics. If you already use GA4 or another tool and its data is sound, we work with it rather than adding a second tracker that slows the pages we are trying to improve.

Analytics collects personal data, so the setup follows the consent rules where you operate. In Colombia, Ley 1581 de 2012 defines authorization as the prior, express and informed consent of the data subject. PostHog masks form inputs in session replays by default, and it can keep data in page memory until a visitor consents, then switch to persistent storage. Your counsel confirms the privacy policy and consent banner.

Questions before you choose

How much traffic do I need for A/B testing?

It depends on your current conversion rate and the size of change you want to detect, so the measure that matters is conversions per variant, not visits. We estimate the sample and duration before proposing a test. If a test would take months to reach a decision, we recommend research-led changes measured against a baseline instead.

Can you guarantee more conversions?

No. Conversion also depends on traffic quality, offer, price, reputation and sales follow-up, which the website does not control. What we commit to is the method: a baseline you can trust, changes based on evidence, honest measurement and a report that shows inconclusive results as well as wins.

Which CRO tools do you use?

PostHog for product analytics, session replay, feature flags and experiments when we set up the stack. GA4, a tag manager or another tool you already use is fine if its data is accurate; we audit it before relying on it.

How long until we see results?

It depends on your traffic, how quickly changes can be approved and released, and whether a change is A/B tested or measured before and after. Clear problems found in the audit, such as a broken form or a slow page, can be fixed in the first cycle. Tests run as long as their sample requires, and before-and-after comparisons need several comparable weeks on each side to account for weekly patterns.

Do you change the design or just recommend changes?

We change it. Dardo designs and builds websites, so the team that finds a problem also designs the fix, builds it in your site and measures it. If another team owns the code, we deliver designs and specifications and review their implementation.

What about privacy and consent for analytics?

We set analytics up to follow the consent rules where you operate, mask form inputs in session recordings and collect only the events the analysis needs. In Colombia, Ley 1581 de 2012 requires prior, express and informed authorization to process personal data. Your counsel confirms the privacy policy and consent text.

What does CRO cost, and what do you need from us?

Cost depends on the number of funnels and pages in scope, the state of your analytics, whether design and development of the changes are included and how many tests run each month. We quote the audit first and the monthly work after it, once the backlog shows what is worth doing. You provide access to analytics and the site or CMS, plus data on which inquiries or orders became revenue.

Sources & further reading

Sources behind this page, with further detail from the original publishers.

Check whether your traffic supports testing

Tell us what the site should get people to do and roughly how many do it each month. We reply with what an audit would cover and which methods your traffic supports.