01 / MOBILEPerformance
—Loading, visual stability, and responsiveness in the lab test.
Free Website Growth Score · public pages
See where your website is ready to grow.
Start with real Google technical data, then add a few business facts to see a transparent Growth Score across website health, local visibility, reviews, contact experience, and advertising readiness.
No email for the instant preview · One public page · A scan may take up to a minute
WEBRESPAWNGrowth Score
YOUR GROWTH READINESS
Real data first. Business context second.
PerformanceLoading and responsiveness
AccessibilityAutomated usability basics
SEO basicsTechnical search foundations
Best practicesCommon technical checksUnknown signals stay unverified instead of becoming a fake zero.
No email to startSee the instant technical preview first.
One public pageEnter a homepage, service page, or landing page.
Transparent scoringAutomated and business-reported signals stay clearly separated.
Automated foundation
Start with what Google can actually measure.
The first score uses only returned Google data. Add the optional business context below to expand the Growth Score without turning unknown information into a penalty.
01 / MOBILE02 / ACCESSAccessibility
—Automated checks that can identify some barriers.
03 / SEARCHSEO basics
—Selected technical elements that support discovery.
04 / TECHNICALBest practices
—Common web standards checked by Lighthouse.
The page tested
What to look at first
Real-user data, when eligible
Key mobile lab metrics
Run the scan to populate LCP, CLS, FCP, Speed Index, and blocking time.
WEB RESPAWN GROWTH SCORE
—/100
A readiness score, not a revenue prediction.
Run the scan to see the automated foundation.
Unknown signals are excluded from the calculation. Google data and business-reported answers are labeled separately.What the score is based on
Best next step from the evidence we have
Optional business context · no email required
Add the signals Google cannot see from one page.
Answer what you know. Choose “Not sure” when you do not know; uncertainty is shown as unverified rather than counted as a failure.
Business-context answers are self-reported, not independently verified. Answer choices use illustrative readiness values (strong 100, mixed 70, weak 35); “Not sure” stays out of the score. Check the source and coverage before treating the combined number as a business assessment.
Want a human review?
Ask Web Respawn to review the Growth Score.
Your score and business context stay visible without an email. Share contact details only if you want a human follow-up on the clearest priorities.
What the checker measures
A technical check has a clear boundary.
The scan can flag specific technical issues on one page. It cannot decide whether your services, proof, pricing, or next step make sense to a customer.
What it checks
- PerformanceHow a simulated mobile page loads and responds.
- Accessibility basicsSome detectable issues, with manual review still needed.
- SEO basicsSelected technical search foundations, not rankings.
- Best practicesCommon security and browser checks.
What still needs a person
- Offer clarityWhether the site explains what you actually provide.
- Customer fitWhether the page addresses the right questions and concerns.
- Proof and trustWhether the supporting details are real and useful.
- Next stepWhether visitors can book, visit, buy, or inquire as appropriate.
Google data, explained
A lab snapshot and real-user data answer different questions.
Mobile Lighthouse snapshot
A test run at one point in time, under a simulated mobile environment. The four category scores and many audit details come from this result.
Chrome user experience, when eligible
Available Core Web Vitals reflect a rolling 28-day period for real Chrome users. Smaller websites may have no eligible public data; we show that as unavailable, never as zero.
Findings in business context
The next fix depends on what customers need to do.
A slow page, unclear service description, or difficult form can affect different businesses differently. Web Respawn can review the technical result alongside the page’s actual job.
BookingsCan people choose and request the right service?
VisitsAre hours, location, and important details clear?
PurchasesCan people understand the product and complete the path?
InquiriesIs it easy to send useful details and know what happens next?
From URL to next step
Run the check, then decide what deserves attention.
01
Enter a public URL
Use the page customers see. Private previews and dashboard links are not supported.
02
Run the mobile scan
The submitted URL is checked with Google PageSpeed Insights.
03
Read the instant preview
Review real category scores, priorities, and eligible field data without an email.
04
Ask for a fuller report
Share your business details only if you want a priority report and follow-up.
After the scan
Understand what a result can mean for your site.
Before you run it
Questions about the free Website Growth Score.
Is the instant check really free?
The technical check does not require an email address. When the instant scanner is unavailable here, the page links directly to Google PageSpeed Insights so you can check a public URL there.
Does this test my entire website?
No. It tests the public page you enter. It is not a full crawl or a complete SEO audit.
Why is real-user data sometimes missing?
Chrome UX Report data needs enough eligible public Chrome visits. A smaller site may have no public record. We label this unavailable rather than showing a zero.
Does a high score guarantee more customers?
No. Technical quality can remove barriers, but people also need a relevant offer, trustworthy information, and a practical next step.
Where does the URL go?
Your public URL is sent to Google PageSpeed Insights for the requested scan. Contact details are only submitted to Web Respawn if you request the fuller priority report. See our privacy policy.
Which page should I check first?
Start with a page customers use before contacting you, such as the homepage or a main service page. Use the exact public URL. A result for one page does not describe every page on the site.
Can I test a page that needs a login?
Use a public page that visitors can open without signing in. The check cannot review your private account pages. Do not enter a URL containing a password, private access token, or sensitive customer information.
Why can two checks show different scores?
A test is a snapshot. Network conditions, server response, page changes, and outside scripts can affect it. Compare the same page and test type, and look for repeated issues rather than judging the site from one score.
Does this check prove my form delivers messages?
No. A technical scan does not confirm that an inquiry reaches your inbox. The full contact path needs a separate test, including submission, the confirmation shown to the visitor, and actual message delivery.
What should I do with the results?
Look for a clear issue that affects visitors, then confirm it on the page. Useful fixes may include a heavy image or a hard-to-use layout. If the instant scanner is unavailable here, use the Google PageSpeed link shown on the page. Ask us to review a website issue.
Ready to check a page?
Start with the page your customers use.
Run the instant preview without an email, then decide whether you want a fuller review.