Jump to a section +
Website checks become confusing when every tool invents a different health score. A better starting point is narrower: choose the page that matters, collect a real technical snapshot, and compare it with what customers are supposed to accomplish there. Web Respawn’s free Website Checkup does that with a mobile Lighthouse result from Google PageSpeed Insights plus three short business-context questions. You can see the instant preview without entering an email address.
How to run the checkup in about two minutes
The complete quick check
Choose the page customers actually use
Copy the exact public URL for the home page, main service page, booking page, or campaign landing page you want to understand. Do not submit a private dashboard, password-protected page, or tokenized preview link.
Run the mobile technical check
Paste the address into the Website Checkup and start the scan. The public URL is sent to Google PageSpeed Insights for a mobile Lighthouse test. The scan itself often takes about 15–30 seconds, although outside services and network conditions can occasionally take longer.
Read the instant preview
Review the four category scores, the returned loading metrics, and the top two automated priorities. Treat them as clues about this page under this test condition, not as a grade for the entire business.
Add the business context
Answer what a visitor should do first, what feels weakest now, and what happens after an inquiry. Your selections immediately create a three-part action plan for the customer path, current concern, and lead handling.
Decide whether to go deeper
If you want the complete automated priority list, enter your name, business, and email; a phone number is optional. The full result appears on the page, and Web Respawn receives the findings and answers for the requested follow-up. Submitting the report request does not subscribe you to marketing.
Choose a page that represents a real decision
| Page to test | Choose it when | What another test may still need |
|---|---|---|
| Home page | Visitors commonly enter through the brand name, referrals, listings, or direct traffic | Individual service, location, and campaign pages can use different templates and assets |
| Main service page | Calls or quote requests begin after someone researches one specific service | The home page and form-confirmation path may behave differently |
| Advertising landing page | Paid visitors should see one focused offer and action | A separate scheduler, checkout, or third-party form needs its own review |
| Location page | Local search visitors use a market-specific page to confirm coverage and fit | The scan cannot judge whether the local copy is original, accurate, or competitive |
| Booking or contact page | The form or appointment step is the main lead path | The check cannot confirm that a submitted inquiry reaches the correct person |
Testing the home page is better than guessing, but it is not a substitute for testing every important template. A lightweight home page can score well while a service page carries a large gallery, a location page uses a map embed, and a booking page loads a third-party scheduler. Run a separate check for another URL when it plays a different role or uses meaningfully different code.
Read the four scores as clues, not promises
| Category | Useful signal | Important limit |
|---|---|---|
| Performance | How the page loads, becomes visible, and responds under a simulated mobile lab test | It is a point-in-time test, not every real visitor’s experience or a promised conversion result |
| Accessibility basics | Selected automated checks for detectable problems such as missing programmatic information or insufficient contrast | Automation cannot prove that a page or website meets accessibility standards |
| SEO foundations | Selected technical basics that help search engines access and understand the tested page | It does not measure rankings, backlinks, local competition, content usefulness, or whether Google indexed the page |
| Best practices | Selected browser and code-health checks included in Lighthouse | It is not a vulnerability scan, malware review, security audit, or penetration test |
Google explains that PageSpeed Insights uses Lighthouse to produce lab data under simulated conditions. That makes the result useful for reproducing and diagnosing problems, but it also explains why two runs can differ. The page, external scripts, server response, test environment, and Lighthouse version can all change. Save the date and tested URL when comparing a result after a fix, and use the Core Web Vitals guide when you need to understand the larger performance picture.
Use the performance details to find customer friction
The performance number becomes more useful when you connect it to what a person sees. The checkup can display Largest Contentful Paint, Cumulative Layout Shift, First Contentful Paint, Speed Index, and Total Blocking Time when Google returns them. In plain English, those details help show whether the main content appears late, the layout moves, the first content takes too long to arrive, the visible page fills in slowly, or browser work delays interaction.
- Open the tested page on your own phone and confirm that the main offer becomes understandable quickly
- Watch whether a call, quote, booking, or menu control moves after you try to tap it
- Check whether a cookie banner, chat widget, video, map, or scheduler blocks the main action
- Look for an oversized opening image, unnecessary animation, too many font files, or several third-party scripts
- Complete the real customer task instead of stopping after the first screen appears
Follow automated accessibility findings with a human check
Automated accessibility checks are valuable because they can find certain repeatable problems quickly. They are not a compliance certificate. The W3C Web Accessibility Initiative states that tools cannot check every accessibility aspect automatically and that human judgment is required. A page can receive a strong automated score and still have a confusing focus order, unclear link purpose, inaccessible custom control, inaccurate alternative text, or instructions that rely only on color or sight.
- Use the page with a keyboard and make sure every interactive control is reachable, visible when focused, and operable
- Zoom the page and increase text size without losing content or controls
- Read headings and link labels without the surrounding design and ask whether their purpose remains clear
- Check form labels, instructions, required fields, error messages, and confirmation behavior
- Review meaningful images for useful alternative text and decorative images for appropriate handling
- Include people with relevant disabilities and qualified accessibility reviewers when the risk or scope requires it
If you are unsure which URL to use, test the home page. If most leads begin on a service page, location page, or advertising landing page, test that exact public URL instead. The result applies to the tested page—not automatically to the whole website.
Separate SEO foundations from search performance
A Lighthouse SEO score covers a limited set of checks on the tested page. It can flag some basic technical conditions, but it cannot tell you whether the page deserves to rank for a query. It does not crawl the full website, compare competitors, validate local relevance, review backlinks, judge first-hand expertise, or forecast traffic. Google Search Console’s URL Inspection tool is the proper place for an owner to see information about Google’s indexed version of a specific page and test whether the live URL might be indexable. Even that live test does not guarantee indexing or placement. The SEO, GEO and AI search guide library covers the broader visibility questions the scan cannot answer.
| Comparison point | The quick check helps answer | A deeper SEO review must answer |
|---|---|---|
| Technical basics | Does this public page pass selected Lighthouse SEO audits? | Can search engines consistently discover, crawl, render, canonicalize, and index the important URL set? |
| Content | Is some basic page information detectable? | Does the page satisfy a real search need with accurate, original, useful information? |
| Visibility | No ranking prediction is produced | Which queries and pages receive impressions, clicks, and qualified outcomes in Search Console and analytics? |
| Site scope | One submitted public page | Templates, internal links, sitemaps, redirects, duplicates, location pages, and other important URLs |
The three questions make the result useful to the business
Connect the scan to what happens before and after the click
What should a visitor do first?
Choose whether the main job is calling or requesting a quote, booking, buying or paying online, or learning before contacting later. A technical issue matters more when it blocks that primary action.
What feels weakest right now?
Choose the concern you already notice: an outdated or unclear site, weak search visibility, traffic without enough leads, a difficult mobile experience, hard updates, or uncertainty. This keeps the automated result from pretending every business has the same problem.
What happens after an inquiry?
Identify whether a system routes the lead, someone follows up the same day, follow-up takes longer, or inquiries are not tracked consistently. A fast website cannot recover a lead that disappears after submission.
These answers do not change the Google scores. They create a separate action plan that explains how technical findings relate to the customer action and lead process you selected. That distinction matters: Google can test parts of a page, but it does not know whether your sales team received the form, whether the offer is understandable, or whether the visitor was a good fit.
Know exactly what the checkup does not prove
- It does not crawl every page or create a full technical SEO inventory
- It does not determine whether Google indexed the page or where it ranks
- It does not evaluate keyword demand, backlinks, citations, local-pack visibility, or competitors
- It does not prove WCAG conformance or that every person can use the page
- It does not test for malware, exposed credentials, application vulnerabilities, or network security
- It does not confirm that forms, calls, bookings, payments, notifications, or CRM handoffs work end to end
- It does not judge messaging, visual credibility, proof quality, pricing clarity, customer fit, or actual conversion performance
- It does not represent every device, network, visitor, or future version of the page
Turn the result into the next sensible action
| Finding | Check next | Likely response |
|---|---|---|
| The main action is broken or hidden | Complete the call, form, booking, or payment path on a phone | Repair the task and notification path before cosmetic work |
| The page is slow or unstable | Identify the image, font, script, embed, or layout element behind the finding | Fix the specific customer interruption and retest the same URL |
| An accessibility audit fails | Reproduce the issue and review the whole interaction manually | Repair the underlying markup, content, styling, or behavior; do not rely on a badge |
| SEO foundations look strong but traffic is weak | Review Search Console, index status, query intent, content, competition, and links | Build the deeper search diagnosis around evidence rather than changing random metadata |
| Scores look strong but leads are weak | Review offer clarity, proof, calls to action, form friction, tracking, and follow-up | Use human review and conversion data instead of chasing another technical point |
Keep a copy of the tested URL, date, scores, and main finding. Make one connected improvement, verify the real customer task, and run the same page again under similar conditions. If the technical result and the business problem do not line up, request a human review rather than forcing the automated answer to explain something it cannot see.
Five useful checks after the two-minute scan
- Search the business name and main service naturally, then use Search Console—not a personalized manual result—to evaluate real query and page data
- Open the page on a phone and ask someone unfamiliar with the company what it offers, who it serves, and what to do next
- Submit a marked test inquiry and confirm the correct person receives every field once
- Check that current hours, service area, prices or starting points, policies, credentials, and contact information are accurate
- Test another high-value page if it uses a different template, form, gallery, map, scheduler, or checkout
The quick scan is most valuable as a starting point. Run the Website Checkup, connect the result to the customer path, and then spend effort where the evidence and the business goal agree.
How long does the free Website Checkup take?
The Google PageSpeed scan often takes about 15–30 seconds, and most people can review the preview and answer the three business questions in about two minutes. Outside service, traffic, or network conditions can occasionally make a run take longer.
Do I need to enter an email address to see a result?
No email is required for the instant preview, which includes the four category scores, returned metrics, and top two automated priorities. Name, business, and email are required only when you request the complete priority list and follow-up; phone is optional.
Does the Website Checkup scan the entire website?
No. It tests the one public URL submitted. Test representative pages separately when the home page, service pages, articles, location pages, forms, and landing pages use different layouts or integrations.
Will the SEO score tell me why my website is not ranking?
No. Lighthouse checks selected SEO basics on the page. Rankings and visibility require additional evidence about indexing, search intent, content, competition, links, location, and actual Search Console performance.
Does a strong accessibility score mean the website is compliant?
No. Automated tools can detect only some accessibility problems. Human evaluation, and sometimes testing with people with disabilities, is needed to assess accessibility more completely.
Is the Best Practices score a security check?
No. It covers selected Lighthouse best-practice audits. It is not a security assessment, vulnerability scan, malware review, or penetration test.
Should I redesign the website if one score is low?
Not automatically. Reproduce the finding, connect it to a real customer task, and determine whether a focused content, design, code, hosting, or integration fix is enough. A redesign makes sense only when the wider website no longer supports the business and customer journey.
Evidence behind the guide
Sources and further reading
- About PageSpeed InsightsGoogle for Developers
- Introduction to LighthouseChrome for Developers
- URL Inspection toolGoogle Search Console Help
- Selecting Web Accessibility Evaluation ToolsW3C Web Accessibility Initiative
- Easy Checks: a first review of web accessibilityW3C Web Accessibility Initiative
Continue on Web Respawn
Pages that actually connect to this decision.
These links are selected for the subject of this guide. They are not a generic service dump.
Run a real mobile Google PageSpeed and Lighthouse check, then connect the findings to the business in about two minutes.
Open page ↗RELEVANT PAGEWebsite Design FAQsGet concise answers about scope, timelines, ownership, SEO and care.
Open page ↗RELEVANT PAGEWebsite Design & RedesignExplore the strategy, content, design, build and launch foundation.
Open page ↗
