You don't have access to this class

Keep learning! Join and start boosting your career

Aprovecha el precio especial y haz tu profesi贸n a prueba de IA

Antes: $249

Currency
$209
Suscr铆bete

Termina en:

1 D铆as
21 Hrs
23 Min
57 Seg

Rendimiento frontend con Core Web Vitals

20/23
Resources

What are Frontend Performance and Core Web Vitals?

Frontend performance is a crucial aspect that determines how users experience a web application. Core Web Vitals are a widely accepted industry standard created to measure that performance. They comprise three key categories that should be analyzed together:

  • Availability: Is your application accessible?
  • Functionality: Do all features work properly?
  • Performance: Is it fast enough?

Together, these categories determine whether the user experience is satisfactory. Imagine that an application is available and works, but responds slowly: this could lead the user to abandon it without completing a transaction.

How to improve availability?

Availability is crucial, because without it, users cannot interact with your app. Here are some recommendations:

  • Monitoring with Synthetics: Set up ping monitors to anticipate drops in performance.
  • Track uptime against SLAs: Compare uptime against Service Level Agreements to ensure standards are met.

How can functionality be improved?

Prioritize fixing bugs that affect your application's functionality. JavaScript errors are especially common in user interactions. To manage this effectively:

  • JavaScript errors: Prioritize fixing these errors to improve the user experience.
  • Scripted Browser Monitor and Alerts: Configure scripted browser monitors and alerts to be aware of potential problems.

How to ensure optimal performance?

Performance focuses on how quickly your application responds, directly affecting user satisfaction. Some key actions include:

  • Frontend code optimization: Use traces to identify code improvement opportunities.
  • Load speed alerts: Configure alerts for excessive load times.
  • Apdex Threshold: Adjust the frontend to be within Apdex acceptable limits.

Why are Core Web Vitals important?

Core Web Vitals are part of an initiative that defines when a website is of quality. Google uses these indicators to evaluate the relevance of your website in search results. Here are the three main Core Web Vitals:

  1. Largest Contentful Paint (LCP): measures the time it takes to load the largest content on the page.
  2. First Input Delay (FID): Evaluates the time from the first user interaction until the browser responds.
  3. Cumulative Layout Shift (CLS): Analyzes how long it takes for the frontend to respond to user interactions.

For example, if a user tries to complete a purchase and does not receive immediate feedback, he could press the button repeatedly, generating multiple unwanted transactions. This highlights the importance of a low CLS.

How to identify Core Web Vitals in New Relic?

New Relic is a useful tool for monitoring Core Web Vitals. Through its interface:

  1. Navigate to the menu and select Browser to view the monitored applications.
  2. In the summary section, you will find information about LCP, FID and CLS.
  3. The color indicators reflect Google's criteria: green for good, red for unacceptable.

These indicators will guide you to make necessary adjustments, especially if they are in red or yellow status.

Your application needs to live up to these standards not only to be found on Google, but also to offer an exceptional experience. Keep learning and improve the quality of your projects!

Contributions 4

Questions 0

Sort by:

Want to see more contributions, questions and answers from the community?

Las Core Web Vitals conforman un sistema de m茅tricas que utiliza Google para calcular la velocidad, la estabilidad visual y la capacidad de respuesta de una p谩gina web.

  • El LCP 芦renderizado del mayor elemento con contenido禄 es el encargado de medir el tiempo de carga de un sitio; es decir, el tiempo que pasa hasta que todo el contenido de la web se encuentra accesible y visible para el usuario.

  • **El FID ** 芦latencia de la primera interacci贸n禄 es una m茅trica que da cuenta de la rapidez con la que los usuarios interact煤an con el sitio web.

  • El CLS 芦cambios de dise帽o acumulados禄 mide la estabilidad visual del dominio. Tiene que ver con elementos que alteran o que se superponen sobre otros elementos de la p谩gina y que pueden llevar al usuario, por ejemplo, a cliquear en un lugar en donde no quer铆a.

  • Largest Contentful Paint: Despliegue del contenido m谩s extenso (LCP) es una m茅trica importante centrada en el usuario para medir la velocidad de carga percibida porque marca el punto en la l铆nea de tiempo de carga de la p谩gina cuando es probable que el contenido principal de la p谩gina se haya cargado. Un LCP r谩pido ayuda a asegurar al usuario que el la p谩gina sea 煤til.

  • First Input Delay: Demora de la primera entrada (FID) es una m茅trica importante centrada en el usuario ya que mide la capacidad de respuesta de la carga porque cuantifica la experiencia que sienten los usuarios cuando intentan interactuar con p谩ginas que no responden, una FID baja ayuda a garantizar que la p谩gina sea utilizable .

  • Cumulative Layout Shift: Cambio Acumulativo del dise帽o (CLS) es una m茅trica importante centrada en el usuario para medir la estabilidad visual porque ayuda a cuantificar la frecuencia con la que los usuarios experimentan cambios de dise帽o inesperados; un CLS bajo ayuda a garantizar que la p谩gina sea agradable .