Loading

WebsiteBy Bait · · 10 min read

Core Web Vitals, WCAG and conversion: how to prioritize improvements to a corporate website

Core Web Vitals measure page loading, responsiveness and visual stability; WCAG sets accessibility criteria. Learn how to prioritize both on your website.

Fluid architectural path in violet, with wide ramps and an unobstructed passage.

Improving a corporate website means removing obstacles so people can find information and complete tasks. Performance, accessibility and conversion are complementary views of that experience. Core Web Vitals measure how a page loads, responds and stays stable; WCAG sets criteria so content works for people with disabilities; conversion shows whether the tasks that matter get completed.

Each of the three fails in its own way. A fast page can have an incomprehensible form; a visually clear interface can fail for someone navigating by keyboard. In large organizations, the challenge is prioritizing across many requests and teams. Start with the journeys that support important relationships: evaluating a solution, requesting contact, finding customer service, consulting documentation or completing a purchase.

What Core Web Vitals are

Core Web Vitals are a set of metrics defined by Google to measure the real user experience of a page across three dimensions: loading, responsiveness to interaction and visual stability. The web.dev documentation describes the current metrics and the thresholds for a good experience.

  • LCP (Largest Contentful Paint): measures loading, as the time until the largest visible element, such as an image or a block of text, is rendered. The threshold for a good experience is 2.5 seconds or less.
  • INP (Interaction to Next Paint): measures how the page responds to clicks, taps and key presses throughout the visit. The threshold is 200 milliseconds or less; above 500 milliseconds, responsiveness is considered poor.
  • CLS (Cumulative Layout Shift): measures visual stability, as the largest burst of unexpected element shifts during the visit. The threshold is 0.1 or less.

These thresholds are assessed at the 75th percentile of page loads, with mobile and desktop measured separately. INP became a stable Core Web Vital in 2024, replacing the previous responsiveness metric. In the Google Search Central documentation, Google recommends that site owners achieve good results on these metrics and states that this, along with other aspects of page experience, aligns with what its ranking systems seek to reward.

Measure what happens in real conditions

The metrics can be observed in the field, with data from real visits, and in the lab, with controlled tests. web.dev lists the Chrome User Experience Report, PageSpeed Insights, the Search Console Core Web Vitals report and the web-vitals library as field tools, and Lighthouse and Chrome DevTools, among others, as lab tools. A lab result helps diagnose causes, but it does not replace the experience observed in the field.

Analyze by page template, device and relevant context. A sitewide average can hide problems in a high-value journey. The product page, the contact form and the customer area usually have different components, scripts and audiences, and deserve to be read separately.

What WCAG is and what AA conformance means

WCAG (Web Content Accessibility Guidelines) is the W3C's set of guidelines for making web content accessible to people with disabilities. WCAG 2.2 is a W3C Recommendation published on December 12, 2024. The guidelines are organized around four principles: content must be perceivable, operable, understandable and robust. Each guideline has testable success criteria, classified into levels A, AA and AAA.

According to the WCAG 2.2 conformance section, a page reaches level AA when it satisfies all level A and level AA success criteria, or when it provides an alternative version that meets that level. Level AA includes level A and adds criteria such as minimum text contrast, which makes it a sound target for corporate websites.

Two conformance requirements often surprise teams. Conformance applies to full pages: it cannot be claimed while excluding part of a page. And when a task spans several pages, such as a registration or a purchase, every page in the process must meet the claimed level. The W3C itself does not recommend requiring level AAA as a general policy for entire sites, because some content cannot satisfy all of its criteria.

Digital accessibility and the Brazilian Inclusion Law

In Brazil, the Lei Brasileira de Inclusão da Pessoa com Deficiência (Brazilian Law for the Inclusion of Persons with Disabilities, Law 13.146/2015) establishes in Article 63 that accessibility is mandatory on websites maintained by companies headquartered or commercially represented in the country, or by government bodies, for use by persons with disabilities, in accordance with internationally adopted accessibility best practices and guidelines. The first paragraph requires these websites to display a prominent accessibility symbol.

The law does not name a specific guideline. WCAG, as an international W3C Recommendation, is a direct technical reference for meeting this requirement. Legal interpretation in each case belongs to qualified specialists; the role of design, content and development teams is to turn the criteria into verifiable practice.

Make accessibility part of the quality bar

Turn the applicable requirements into design, development and editorial review work, not an isolated audit at the end of the project. An automated tool helps find problems, but it cannot assess the whole experience on its own.

  • Check keyboard navigation and focus visibility.
  • Review form labels, instructions and error messages.
  • Test contrast, zoom and content reflow on small screens.
  • Provide meaningful alternatives for images, videos and other content.
  • Combine technical checks with manual evaluation of the journeys, including screen readers.

Prioritize by reach, severity and task value

Rank problems by the number of people affected, the difficulty imposed and the importance of the action. An error that prevents a request from being submitted deserves different treatment from a visual detail. Also consider shared components: fixing the source can improve many pages at once.

A practical order of work helps you get out of the endless list of requests.

  • Map the critical journeys and the pages that make them up.
  • Gather Core Web Vitals field data by page template and device.
  • Run an accessibility evaluation of the same journeys, both automated and manual.
  • Cross-reference the problems with the funnel: where there are errors, drop-offs or users coming back.
  • Fix what blocks tasks first, then what makes them harder, and finally the polish.
  • Record the baseline before each change so you can compare afterward.

Connect improvements to results carefully

Track task completion, errors, abandonment and the quality of the inquiries received. A change in conversion rate may reflect shifts in audience, campaign or offer. When conditions allow, experiments help evaluate an intervention; in other cases, document the limitations of the before and after comparison.

Performance and accessibility also relate to search presence. Fast, stable pages with a clear semantic structure tend to be easier to crawl and interpret, as discussed in the article on SEO and GEO for large companies. Even so, none of these improvements guarantees ranking or business results on its own.

Prevent regressions after launch

Define publishing criteria and owners for maintenance. Performance can degrade with new tags, heavy images and integrations. Accessibility can be compromised by content changes, such as a banner without alt text or a form edited without labels. Add checks to publishing workflows and review field data periodically. In groups with several websites, a multi-brand design system with accessible components reduces rework for each brand.

Common mistakes

  • Chasing a lab tool score and ignoring field data.
  • Evaluating the site by its overall average, hiding problems in the highest-value journeys.
  • Treating accessibility as a final checklist, after design and content have already been approved.
  • Relying on automated scanners as proof of conformance.
  • Adding third-party scripts without measuring their effect on page responsiveness.
  • Attributing every change in conversion to a technical change, without considering audience and offer.

Hypothetical example: the form that loses data on mobile

Consider a hypothetical B2B services group whose website receives requests for proposals. The situation is illustrative. Field data shows INP above the threshold on form pages on mobile, and a manual evaluation reveals that, after a validation error, the form clears the completed fields and the error message is not announced by screen readers.

The priority is not replacing the page's hero image. The team trims the script that blocks interaction, keeps the data after an error, associates the messages with their fields and moves focus to the first problem. After publishing, it tracks form completion and the quality of the requests received, noting that campaign changes during the same period limit the comparison.

The same care applies to the investor relations website, where PDF reports are often the weak point for accessibility. See the article on the investor relations website.

Frequently asked questions about Core Web Vitals and WCAG

What are Core Web Vitals?

They are metrics defined by Google to measure the real user experience of a page. LCP measures the loading of the largest visible element, with a threshold of 2.5 seconds or less. INP measures responsiveness to interactions, with a threshold of 200 milliseconds or less. CLS measures visual stability, with a threshold of 0.1 or less. The thresholds are assessed at the 75th percentile of visits, with mobile and desktop measured separately.

What is WCAG?

WCAG stands for Web Content Accessibility Guidelines, the W3C guidelines for making web content accessible to people with disabilities. Version 2.2 is a W3C Recommendation from December 2024. It is organized around four principles, perceivable, operable, understandable and robust, and defines testable success criteria at three conformance levels: A, AA and AAA.

What does WCAG AA conformance mean?

It means the page satisfies all WCAG level A and level AA success criteria, or provides an alternative version that meets that level. Conformance applies to the full page and, for multi-step tasks, every page in the process must meet the level. The W3C does not recommend requiring AAA as a general policy for entire sites.

Does a high performance score guarantee more sales?

No. A lab score describes one technical dimension under controlled conditions, and even good field data does not guarantee business results. Conversion also depends on the offer, trust, audience, content and the full journey experience. Performance removes obstacles; the effect on the business needs to be measured carefully, taking into account audience and campaign changes during the same period.

Can we evaluate accessibility with a scanner alone?

No. Automated tools find some of the problems, such as insufficient contrast or images without alt text, but they do not assess whether a label makes sense, whether the reading order is logical or whether a task can be completed by keyboard and screen reader. Evaluation needs to combine automation, manual review of the journeys and, whenever possible, testing with people with disabilities.

Learn about the Website area, which treats experience, performance and accessibility as parts of the same work.