Web & mobile · Website audit
A website audit in one week: from analytics to a prioritized backlog
An audit that ends as a 90-page PDF changes nothing. A useful one takes a week, checks five things in a fixed order — analytics, funnel, UX, technical health, content — and ends with a short, ranked list of tasks your team can start on Monday.

Day 1: make sure the numbers are true
Every later finding rests on analytics, so check it first. A funnel built on broken tracking points the team at the wrong problem.
- Reconcile with the backend. Compare orders or leads in analytics with the store or CRM for the last 30 days. Some gap is normal; ad blockers alone cause one. A big gap means something is missing: a tag on the confirmation page, a payment provider that sends shoppers to its own page and breaks the session, a form that submits without firing an event.
- Check that key events fire once. Place a test order or submit a form and watch it arrive in the real-time report. Page views counted twice, once by the theme and once by the tag manager, are common.
- Filter internal and bot traffic. Your own team and a crawler hitting the site at 3 a.m. are not customers.
- Clean up campaign tags. “facebook,” “Facebook” and “fb” as UTM sources are three channels in the reports and one in reality.
The output of day 1 is a short list of tracking fixes and a note on which numbers can be trusted this week.
Day 2: find where people drop off
Define the funnel for the main goal: landing page, product or service page, cart or form, each checkout step, purchase or submitted lead. Then split it, because averages hide the problem:
- by device: desktop can convert fine while mobile loses half its shoppers at the shipping step;
- by traffic source: paid social visitors behave differently from search visitors;
- by new against returning visitors.
Look for the biggest absolute loss, not the worst percentage. A step that loses 70% of 200 people matters less than one that loses 30% of 8,000.
Then add the qualitative layer. Watch 20 to 30 session recordings of visitors who dropped at the worst step. Pull the internal site search terms that return no results. List the landing pages with high traffic and the highest exit rates.
Day 3: walk the site like a customer
Pick three to five key tasks — find and buy a product, request a quote, find return or delivery terms — and do each one on a phone and on a desktop. Two people should do it separately and merge notes afterward; one reviewer misses things.
A short set of heuristics keeps the review from turning into a debate about taste. Jakob Nielsen’s ten usability heuristics are the standard reference, and on a commercial site most of what they catch comes down to five questions:
- Does the site show what happened? Did the cart update, did the form go through?
- Does it use the customer’s words, not internal ones?
- Does it prevent errors, and when they happen, explain them and keep what the person typed?
- Is the same thing done the same way everywhere?
- Can people see their options instead of having to remember them?
Rate each finding by severity, from cosmetic to blocking, and attach a screenshot and the exact page. Then add the top questions from support tickets and chat logs: every question customers keep asking is a page or a line of copy the site is missing.
Day 4: technical health and content gaps
Technical health. Six checks cover most of it:
- Core Web Vitals field data for the main templates, in PageSpeed Insights or Search Console.
- A crawl with a tool like Screaming Frog: broken links, redirect chains, duplicate titles, pages blocked from search by mistake.
- Search Console: indexing errors and important pages left out of the index.
- Forms and transactional emails: does the contact form deliver, does the order confirmation arrive and stay out of spam?
- Safari on an iPhone and Chrome on an Android phone, not just the team’s own browser.
- CMS, theme and plugins up to date, HTTPS everywhere.
Content gaps. Compare what people look for with what the site has. The sources are search queries in Search Console, site search terms, and the questions sales and support hear. Typical gaps: product pages without sizing, specs or delivery times at the point of decision; comparison questions nobody answers; outdated pages with old prices or a promotion from two years ago.
Day 5: turn findings into a backlog
By Friday you may have 60 to 100 findings. A list that long gets ignored, so turn it into tasks.
1. Write each finding as a task. Problem, evidence, proposed fix, the metric it should move, owner.
2. Merge by root cause. Five findings about mobile checkout may all come from one slow address field.
3. Score. Rate impact (how many visitors or how much revenue pass through that step), confidence (how sure you are the fix will work) and effort, each from 1 to 5. Sort by impact times confidence, divided by effort.
4. Sort into three buckets. Fix now: broken tracking, broken forms, errors, with no debate. Quick wins: a high score and low effort. Projects: bigger changes that need design and testing.
5. Commit to the top ten. Present them in one hour to the people who will do the work, agree on owners and dates, and schedule a re-measure in 30 days. The rest stays in the backlog for the next round.
The one-week checklist
- Orders or leads in analytics match the backend within a known gap.
- Key events fire once, and internal traffic is filtered out.
- The funnel is split by device and source, and the biggest absolute loss has a name.
- At least 20 recordings watched at that step.
- Key tasks walked on a phone and a desktop, with findings rated by severity.
- Crawl, Search Console and forms checked.
- Content gaps listed from search and support questions.
- A scored backlog, with the top ten assigned to owners.
Boson Group designs, builds and markets websites and online stores. If you want this audit done on your site, with a backlog your team or ours can work from, write to team@boson.group.




