Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve GCS Core Web Vitals for mobile pages #767

Open
kenkunz opened this issue Jun 21, 2024 · 0 comments
Open

Improve GCS Core Web Vitals for mobile pages #767

kenkunz opened this issue Jun 21, 2024 · 0 comments
Assignees
@kenkunz
Labels
priority: P1 An important issue that must be fixed before the next release, but does nto require immediate focus. size: M An ordinary task that can be completed in a few days or in a week type: tech debt Technical debt

Comments

@kenkunz
Copy link
Contributor

kenkunz commented Jun 21, 2024

Summary

The Core Web Vitals available from Google Search Console (GSC) show an increase in "URLs needing improvement" for mobile devices. This indicates potential issues with the end-user's experience on mobile devices, and can also have a negative impact on Google SEO rankings.

Details

Recent snapshot of "Good URLs" vs. "URLs needing improvement" (for mobile):

search google com_search-console_core-web-vitals_resource_id=sc-domain%3Atradingstrategy ai

Report indicating cause of "needs improvement" ranking:

search google com_search-console_core-web-vitals_resource_id=sc-domain%3Atradingstrategy ai (1)

Acceptance Criteria

  1. Interaction to Next Paint (INP) score less than 200ms for all mobile pages (75th percentile)
  2. Largest Contentful Paint (LCP) score less than 2.5s for all mobile pages (75th percentile)
  3. Other GCS Core Web Vitals scores are not adversely affected
@kenkunz kenkunz added priority: P1 An important issue that must be fixed before the next release, but does nto require immediate focus. size: M An ordinary task that can be completed in a few days or in a week type: tech debt Technical debt labels Jun 21, 2024
@kenkunz kenkunz self-assigned this Jun 21, 2024
@kenkunz kenkunz mentioned this issue Jun 28, 2024
Merged
This was referenced Jul 12, 2024
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kenkunz kenkunz

Labels
priority: P1 An important issue that must be fixed before the next release, but does nto require immediate focus. size: M An ordinary task that can be completed in a few days or in a week type: tech debt Technical debt
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kenkunz