Priority work
- Complete the questions to see recommended actions.
Tools: audit and estimator
Answer a few questions, then run the audit if the site allows it.
The estimator works fully on a static GitHub Pages site. The scanner uses public PageSpeed checks where possible, then falls back to the guided estimate when a website blocks public audit tools.
Question-led estimator
Build a detailed estimate before asking for a quote.
GitHub Pages cannot run backend audit code. That makes the question-led estimate the dependable part of this tool, while the automatic scan is a useful bonus when the target website allows public testing.
Results
Audit findings and detailed quote.
Complete the questions to generate scores, detected platform signals, priority fixes and a recommended Octopye package.
Instant estimateComplete the questions
The estimate updates after a scan or when you choose manual options.
Detected setup
No scan yet. Manual platform choice will be used if scanning is blocked.
--
Mobile performance
--
Desktop performance
--
SEO
--
Accessibility
Recommended route
- Complete the questions to get a package recommendation.
Send this audit to Octopye
The audit summary is copied into the booking link so the enquiry starts with context.
GitHub Pages limits
What the static auditor can and cannot do.
HTML sites
Can be checked when PageSpeed can publicly fetch the page and return rendered results.
WordPress
Can show speed and SEO signals when the site allows public testing; blocked hosts fall back to the estimate.
React and SPAs
Can be assessed through rendered PageSpeed results where public crawling is allowed.
Optional upgrade
For fewer blocked scans, deploy audit-worker.js separately on Cloudflare Workers or similar and set window.OCTOPYE_AUDIT_ENDPOINT.