SiteViewer Help Centre

Plan fixes and show progress in Pre-Flight

Pre-Flight's New view shows where to start and how long the fixes take, lists findings page by page, charts your progress run by run and makes a summary of what you fixed for your client.

The New view shows the same checks, results, Run and Ignore as the classic checklist, as one table, and adds the parts that help you plan the work and show a client how far their site has come. To try it, open a preview's Pre-Flight tab and choose New view at the top. It is marked Beta while we finish it. Your choice is remembered in this browser, and Classic takes you back. For what the checks themselves look at, see The Pre-Flight check.

The summary

Across the top are four counts: To fix, Suggestions, Passed and Couldn't run (which includes checks that haven't run yet). Press one to show only those checks; press it again to show everything. The guidance about the checks sits behind the small i beside the Pre-Flight title.

Start here

  • Where to start. The one or two checks that hold the most to fix, the easier one first when two hold the same, and whether they are Easy. Press a check's name to jump to it.
  • How long it takes. A rough time for everything to fix, counting about 5 minutes for an Easy fix and about 15 for a Moderate one. Suggestions are optional, so they are never counted.
  • Biggest win. The check that clears the most in one go, and how long that takes.

While checks are running, the counts are still moving, so Start here shows a placeholder and fills in when the checks finish.

By check and By page

By check lists each check with its result, its effort and its type (Quick, Page load or Read-through), and a Run button. Press anywhere on a row to open it and see its findings. Beside the By check and By page switch are filters (All, To fix, Suggestions, Couldn't run and Passed) and a search across checks and findings. Once there are two or more runs, a small line beside a check's result shows how its number to fix has moved over the last runs.

By page lists each page with what is open there, worst page first, with a rough time to fix it and Open page, which opens that page in a new tab. A page of your own preview opens without asking you for its password. Press a page to see its findings, each naming its check, with the same actions as By check. A problem found on 3 or more pages is one piece of work, so it is listed once, under Several pages, rather than on every page.

Turn a finding into a task

  1. Open a finding and choose Fix this.
  2. Choose who it's for. You are chosen to start with, and the list holds your team, not freelancers on the project.
  3. Choose Create task. The task goes on this project's Tasks with everything the finding says: the check, the page and its address, what was found, the words around it, the suggestion and how to fix it, so whoever picks it up needs nothing else.

While the page stays open, the finding says who it is assigned to, with Open Tasks. Once you leave or reload the page, the finding shows Fix this again, so look in Tasks before you make another one. Fix this is there for people who can create tasks on the project.

Your progress over time

Each time checks finish, Pre-Flight keeps the results as a run, and the chart beside the counts draws two lines: red for To fix and blue for Suggestions. Its heading says which way things are going, for example "Page by page: down from 17 to 15 to fix since 18 Nov".

  • Counted page by page. The chart counts each page a finding is on, ignored findings included, so a problem spreading to more pages, or a finding you ignored, never looks like progress. That is why its number can differ from the To fix count beside it.
  • Like for like. A run is kept only when it covers at least the checks the last kept run did, so a check that couldn't run can never read as fixed, and the quick checks that run by themselves on a new upload don't add a point until the rest have run. A check that covered only part of the site is left out of the count. Runs are compared on the checks they all had, and the chart says when a check that not every run had is left out of the line.
  • Each point. Point at a dot, or tab to it, to see the date and time, the version, the numbers to fix and suggestions, and the change from the run before. When every run on the chart was on the same day, the times show under the line too.
  • Since the last run. Under the chart, with the date and time of the run before, Fixed and New list what changed.
  • Show as a list gives every kept run in words. The chart itself shows the most recent runs that fit your screen, up to 8, and says when there are more.

While checks are running, the line waits: it shows complete runs only, and adds this one when it finishes.

A summary for your client

Once there are two runs to compare and there is less to fix than at the start, How we've improved your site appears under the chart. It opens a clean page in a new tab, in your studio's name, with your logo if you've added one, never SiteViewer's:

  • the dates it covers, and how many things there were to fix at the start and now;
  • What we fixed, check by check, with the findings fixed where we can name them;
  • What's left, check by check, and how many findings you looked at and chose to leave as they are.

Press Print or save as PDF to keep it or send it. The page is made in your browser from the results on screen, so nothing is sent anywhere. If the checks are still running, or today's results have moved on since the last full run, Pre-Flight says so instead and asks you to run all the checks first, so the summary never disagrees with itself.

Tip

Choose Run all checks once before you start fixing and again when you're done. The chart and the summary for your client then show exactly what changed in between.


Was this helpful?Thanks for the feedback.

Still stuck?

Our team replies to every message, usually within a few hours. No bots, no ticket queues.