Website SEO
Free Website SEO Audit (200 pages)
Crawl up to 200 public pages with a free verified account. Review technical, on-page and link evidence, then prioritize fixes without ranking promises.
Page Speed & Core Web Vitals Checker
Review page-speed and Core Web Vitals concepts with clear data sources. Google PageSpeed and CrUX results depend on provider configuration and data availability.
Evidence-based analysis with disclosed data sourcesVersion 1.0.0
Loading your private workspace…
How to use Page Speed & Core Web Vitals Checker
- Sign in with an email-verified free Mayexa account and review availability and daily limits.
- Choose the relevant task in this product workspace. Enter only the public website, page, business or prompt details it requests.
- Read the processing disclosure and submit only if the required integration is available. A disconnected provider cannot return live data.
- Review the evidence, source and timestamp alongside the explanation. Treat unavailable checks separately from confirmed failures.
- Verify proposed changes before applying them. Save a report only when you want it retained with your account.
A practical example
A restaurant site scores 48 on mobile; the trend shows LCP worsening over three months, and the top opportunity is 2.1 s of unoptimised images.
How it works
PageSpeed Insights API (Lighthouse performance category) for both strategies; CrUX API queryRecord (URL then origin) and queryHistoryRecord for 25 weekly periods.
Limits and assumptions
Lab results vary between runs and devices. Real-user data exists only when Google has enough Chrome users for the URL or site; otherwise we say so. Results come from Google PageSpeed Insights and the Chrome UX Report (CC BY 4.0).
Frequently asked questions
What does Page Speed & Core Web Vitals Checker help with?
A speed checker can show lab measurements from a controlled test and field measurements from actual visits when the relevant data exists. These describe different conditions. Mayexa keeps PageSpeed Insights and CrUX availability explicit rather than treating missing field data as a zero performance score.
What should I check before relying on the result?
Google integrations are optional and are not configured on the current deployment. The tool must show an unavailable state when it cannot retrieve them. A performance score is not a ranking prediction, and a page can require accessibility or content improvements even after a speed issue is fixed.
Do I need a Mayexa account?
A free email-verified Mayexa account is required. Public explanations remain accessible without signing in. Daily limits apply; unconfigured providers are shown as unavailable.
Learn the method and check the limits
Work through a practical example and understand how to interpret the result before relying on it.
Page Speed and Core Web Vitals: Distinguish Lab Tests From Field Data