Skip to main content

​
What this module does

Core Web Vitals audit helps you:
  • prioritize the most important pages (top pages by default)
  • separate results by device (desktop vs mobile)
  • run bulk audits instead of checking URLs one by one
  • view score categories:
    • Performance
    • Accessibility
    • Best Practices
    • SEO
  • identify opportunities and diagnostics
  • get AI suggestions to fix each issue faster

​
Why Core Web Vitals matter

  • Faster pages improve user experience and engagement
  • Performance correlates with SEO outcomes
  • For GEO, faster pages reduce failure and timeout risk for crawlers

​
Quick start

  1. Login
    https://ma.copyrocket.ai/login
  2. Open Core Web Vitals
  3. Connect GSC property
  • Select the correct property from the property selector
  1. Choose what to audit
  • Default: Top pages (recommended)
  • Optional: Custom URLs (manual list)
  1. Choose device
  • Desktop
  • Mobile
  1. Choose count / batch size
  • Start small first (example: top 5 pages)
  • Scale when settings look correct
  1. Run batch
  2. Open the report
  • Review overall scores
  • Review opportunities and diagnostics
  • Fix top issues first
  • Re-run audit to confirm improvements

​
Report sections explained

​
Score categories

  • Performance: speed and loading experience
  • Accessibility: usability and compliance signals
  • Best Practices: common web quality checks
  • SEO: crawl and index signals

​
Opportunities

Lists improvements likely to increase scores.

​
Diagnostics

Highlights technical or UX issues, often tied to specific assets or UI components.

​
How to use AI suggestions

When an issue is detected:
  • open the issue details
  • identify the offending asset or element
  • use the AI suggestion flow to get step-by-step fixes
  • apply fix, then re-run the audit
Example issues:
  • insufficient contrast ratio
  • heading hierarchy problems
  • repeated UI component causing structure issues

​
Best practices

  • Always start with top pages. Fixing them gives the biggest ROI.
  • Audit desktop and mobile separately. Mobile usually needs more attention.
  • Fix template-level issues first, they affect many pages at once.
  • Re-run the same batch after changes to verify improvements.

​
Troubleshooting

​
Results look incomplete

  • increase top pages count
  • switch to custom URLs for specific templates
  • ensure the selected property matches your main domain

​
Mobile results look much worse

  • this is normal, mobile is stricter
  • focus on template performance and UX issues first

​
FAQ

​
Should I audit every page?

Start with top pages. Then scale. For large sites, batch in phases.

​
How often should I run this?

  • after major releases
  • weekly for fast-moving sites
  • monthly for stable sites