Add public PerformWP site scan workflow for growth and education
Open
Nobody has claimed this yet.
area: frontend
area: integrations
area: performance
enhancement
priority: medium
status: needs-spec
- Dominant language
- PHP
- Stars
- 5
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Summary
Add a public PerformWP site scan workflow for lead generation and performance education.
This belongs to the website/growth surface rather than the core plugin runtime, but it should align with the Perform product roadmap.
Proposed scope
- Add a public scan form on performwp.com.
- Collect only the target URL and optional email after showing results.
- Show safe, high-level checks:
- TTFB
- compression
- page size
- mobile lab score or external test link if integrated later
- caching/header hints where available
- Route recommendations to Perform docs, feature pages, and the draft content strategy.
- Do not make unverifiable field Core Web Vitals claims from a single scan.
Acceptance criteria
- A visitor can run a scan without logging in.
- Results are clear, limited, and privacy-conscious.
- Email capture is optional and consent-based.
- Recommendations map to Perform features or content.
- Any external API usage is documented before implementation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the proposed public scan form on performwp.com and the acceptance criteria. Define the URL input, optional consent-based email flow, safe result checks, recommendation links, and external API documentation boundary. Done means an unauthenticated visitor receives limited, privacy-conscious results without unverifiable Core Web Vitals claims.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- performance, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100