Keep the website working for the business

Keep the review short enough to repeat. Focus on customer outcomes before cosmetic changes.

1. Submit one labelled test enquiry and confirm receipt.
2. Review new enquiries, qualified enquiries, quotes, won jobs, and missed replies.
3. Check traffic by source and investigate unexpected drops.
4. Choose one action with an owner and a due date.

Week ending:
New enquiries / qualified enquiries:
Quotes sent / jobs won:
Missed calls or overdue replies:
Main source of qualified enquiries:
One issue to fix:
Owner / due date:
Result to check next week:

A lead is a request. A qualified lead fits the service, area, and scope. A won job has an agreed commitment.

Outdated hours or availability can waste a customer's time even when the website works correctly.

1. Check hours, service areas, prices, team details, and contact links.
2. Replace expired offers and broken external links.
3. Add useful recent work and answer a question heard repeatedly that month.
4. Check Search Console for new indexing issues and important changes in search traffic.
5. Update holiday hours on the website and Business Profile before the holiday.

• Review Search Console

Test the homepage and main service page with PageSpeed Insights. Compare real-user data with the diagnostic lab test.

Good Core Web Vitals thresholds are LCP at most 2.5 seconds, INP at most 200 milliseconds, and CLS at most 0.1.

These assess load speed, responsiveness, and layout stability at the 75th percentile. A small site may have insufficient real-user data.

1. Resize and compress large photos before upload. Keep useful image detail.
2. Remove widgets and scripts that no longer serve a business purpose.
3. Give a developer the affected URL and the specific diagnostic, rather than only the score.
4. Retest the customer journey after changes.

A perfect lab score is not the business goal. Prioritize problems that prevent customers from reading, navigating, or contacting the team.

• Open PageSpeed Insights
• Google Web Vitals definitions

The business should retain control of the domain and key accounts, even when a developer handles daily work.

1. Record the domain registrar, host, renewal dates, and responsible person in a private business record.
2. Enable multifactor authentication where available. Keep recovery methods current.
3. Use individual access for helpers and remove access when work ends.
4. Keep a backup before changes. For self-hosted sites, keep source, content, and local images together.
5. Test how to restore a previous version before a major update.

Hosted plans and code purchases have different responsibilities. Confirm which updates the agreed support scope includes.

• Self-hosted update workflow

A precise report helps the person fixing the site reproduce the issue.

1. Record the public URL, time, device, browser, and exact action that failed.
2. Check whether the issue affects one page or the whole website.
3. For form problems, record whether the request reached the inbox or lead dashboard.
4. Share the visible error and a screenshot with private customer details removed.
5. Include the last known working time and any recent changes.

Do not send passwords, API keys, or customer messages in a support screenshot.

• Contact Webrenew
• Hosting troubleshooting