What the review covers
A website audit for speed, usability and technical decisions.
The review covers what is visible and testable from the outside, plus any access you explicitly grant. It is not an intrusive security assessment, a repair commitment or a guarantee of business outcomes.
Performance and Core Web Vitals
The review looks at how important pages load, respond and stay stable. Large images, third-party scripts and delayed content can affect different journeys in different ways. Findings distinguish what is observable in a browser from questions that require server or analytics access.
Mobile and responsive behaviour
Navigation, forms, product options and calls to action need to work in the space available. The review checks for clipped text, horizontal overflow, awkward tap targets and panels that hide essential information. A desktop screenshot alone cannot establish that a mobile journey is usable.
Conversion friction and checkout flow
The focus is whether a visitor can understand the offer and complete the intended action. Unclear delivery choices, validation messages or product selections can introduce avoidable effort. Observations become questions and recommendations, not claims that a particular change will produce more sales.
SEO basics and structured data
Public checks can review page titles, descriptions, canonical URLs, heading structure, crawl rules and visible structured data. They can identify inconsistent signals or missing information. Search performance also depends on content, competition and indexing; this review does not promise rankings or a traffic increase.
Technical issues and errors
A broken link, failed request or inconsistent interaction can point toward an implementation problem. The written findings describe the affected page and the behaviour observed. Where the cause cannot be established externally, the recommendation explains what further investigation or access would be needed.
Security basics
The outside review can flag visible configuration concerns and unsafe public behaviour. It does not include intrusive testing, attempts to bypass authentication or a certification that the site is secure. Internal permissions, updates and infrastructure require an agreed scope and appropriate access before conclusions are drawn.
Tracking and analytics setup
Useful measurement starts with events that represent real actions rather than arbitrary clicks. The review considers observable event behaviour and the information you provide about your setup. Cross-domain journeys, embedded forms and third-party checkout steps may need cooperation from the service that owns them.
Accessibility basics
The review considers visible labels, keyboard access, focus states, readable contrast and the structure of important interfaces. These checks can expose barriers in navigation or enquiry flows. They are a starting point for remediation rather than a complete accessibility certification or a replacement for testing with users.
Platform and architecture fit
A new frontend or another plugin is not automatically the right answer. The review considers the publishing workflow, integration boundaries and maintenance responsibilities behind the request. Recommendations can include keeping the current platform and improving a focused part of it when that fits the operating need.
How it works
A written review, with a clear scope.
- 01
Send your details
Share the site or planned build and the concern you want investigated.
- 02
I review the context
The review considers visible journeys and the information you choose to provide.
- 03
Receive written priorities
Get a summary of findings, questions and recommended next steps.
- 04
Discuss the next move
An optional conversation can clarify the recommendations. There is no obligation to commission a build.
What you receive
Findings you can use to choose the next step.
A written summary of the findings
You receive an explanation of the observed issues and the journeys they affect. Each finding separates an observation from a suspected cause, so an unverified assumption is not presented as a diagnosis.
Priorities and practical next steps
Recommendations identify what to investigate first, what may be a focused improvement and what depends on additional information. Where a larger rebuild is being considered, the summary can outline questions to answer before choosing an approach.
A boundary for any follow-up work
The review is separate from implementation. You can use the findings to discuss work with your existing team, ask for clarification or request a scoped proposal. There is no obligation to commission development or agree to an ongoing service.
What I need from you
Context helps direct the review.
Share the page or journey that concerns you and describe what you expected to happen. A product URL, form page or short reproduction path is often more useful than a general request to make everything faster.
Tell me which platform you use, which integrations matter and whether the issue affects publishing, sales or enquiries. If you are planning a site, describe the audience, required features and existing tools instead of supplying a URL.
Do not send credentials, API keys, payment data or customer records in the form. If internal access becomes necessary, the permissions, purpose and scope should be agreed separately. Optional references should be public websites you are comfortable sharing.
Platform notes
The platform changes what needs checking.
Sample report format
Findings organised for decisions.
Example layout, placeholder data—not a completed audit or a real client’s report.
SummaryPlaceholder observation for the reviewed page or journey.
Suggested next step to be confirmed after review. Priority issuesPlaceholder observation for the reviewed page or journey.
Suggested next step to be confirmed after review. Quick winsPlaceholder observation for the reviewed page or journey.
Suggested next step to be confirmed after review. Recommended approachPlaceholder observation for the reviewed page or journey.
Suggested next step to be confirmed after review. Who the audit suits
- Live stores and sites with speed, checkout, bug or architecture concerns.
- Businesses planning a new website, rebuild or migration.
Outside this review
- Requests that only need a logo.
- Standalone content-writing work without a website review.
Questions
Before you send the request.
Is it really free?+
Yes. The offer is a written review with recommendations and no obligation to commission development. Any implementation or continuing support would be scoped separately.
What do you need from me?+
Your name, email and the type of help you need are the starting point. A public URL and a short explanation help direct the review; leave the URL blank if the site is still being planned.
Do you need admin access?+
Not for the initial outside review. If a finding needs internal access, the access and scope should be agreed separately; do not send passwords through this form.
Will you sell me something?+
You receive recommendations and can decide what to do with them. A follow-up discussion or implementation scope is optional.
How long does it take?+
I reply directly, but no fixed turnaround is promised on this page. The scope, available information and current workload determine what can be reviewed and when.
Is my site data private?+
Provide only information you are comfortable sharing for the review. A submitted request uses the configured form provider, or the email or WhatsApp service you choose; avoid passwords, API keys and private customer records.
Can you plan a new site instead?+
Yes. Choose the planning or rebuild option and describe the intended audience, features and constraints. The written recommendations can then focus on the platform and scope rather than an existing site's issues.
Which platforms do you cover?+
The existing capability set includes Shopify Liquid and Hydrogen, WooCommerce, WordPress and Next.js, with CMS and integration work. The review first checks whether that experience matches the problem you need solved.