CRO starts with a measurement model: what success means, where users enter, where they hesitate and which actions actually matter to the business.
Conversion-rate optimization can become superficial when the review begins with buttons, colors and page layouts. We prefer to begin with the measurement model because it tells us which journeys deserve attention and whether the tracking is reliable enough to support a recommendation.
Define the business event before the conversion rate.
A website can have several actions, but they are not equally valuable. A newsletter signup, brochure download and qualified consultation request should not automatically sit in the same bucket. Before reviewing conversion rate, define the events that represent meaningful progress and the ones that represent the final business outcome.
In GA4, key events can be used to identify important interactions. The important part is not the label itself; it is agreeing internally on which actions should guide prioritization.
Read conversion together with traffic source and landing page.
A site-wide conversion rate hides too much. Paid search traffic arriving on a tightly matched landing page behaves differently from branded organic traffic landing on the homepage. Segmenting by source, campaign, landing page and device often reveals that the problem is concentrated in one journey rather than across the entire website.
This is also why a drop in conversion rate is not automatically a website failure. If a new campaign adds more top-of-funnel traffic, total sessions can grow faster than qualified actions.
Use engagement as context, not as the goal.
Engagement rate, page views and time can help explain whether people are interacting with the site, but they should support—not replace—business outcomes. Google Analytics counts an engaged session based on time, multiple views or a key event, which makes it useful context but not a direct proxy for revenue or lead quality.
For a service page, we might compare engagement with CTA interaction, form starts and completions. For content, we may compare engagement with internal clicks into commercial pages.
Include search visibility when organic traffic matters.
Search Console adds a different layer: impressions, clicks, CTR and average position. Those metrics help distinguish a conversion problem from an acquisition problem. A page cannot convert search demand it is not receiving, and more impressions are not automatically valuable if the queries do not match the offer.
We usually review query and page-level trends rather than relying only on site-wide totals.
Do not ignore technical experience.
Slow loading, delayed interaction and layout movement can create friction before users even process the message. Core Web Vitals give a field-data framework for loading, responsiveness and visual stability. They do not tell you what copy to write, but they can expose experience problems that make every other optimization harder.
Technical issues should be treated alongside content and UX—not as a separate score-chasing exercise.
- Primary and secondary key events
- Conversion by source, landing page and device
- Form starts, completions and errors
- Engagement rate used as supporting context
- Search Console clicks, impressions, CTR and query intent
- Core Web Vitals and obvious performance blockers