Website performance
Select Website Pages and Compare Task Results
NDC Inc. ·
Select an important page and user task. Before you change the page, record task problems, available counts, and page results. After you change the page, do the task check again. Compare results with the same instructions and the same device type. Record missing data and the pages in each report.
Select the page and task first
Users can stop before they complete a form when some information in its fields is not necessary.
Start with one important user task. For example, send information with a form. Select a page with a problem. The problem stops users before they complete the task.
Write the result you will record when users complete the task. For a form, make sure the website has the submission. A button click is not sufficient.
If you cannot get more tools or more time for website work, select one page first. Start with your available tools.
If you are not sure the selected task is important, examine available counts and user information. These do not always give a clear result.
Sources: [3]
Before you change the page, record the task
A Clarity page report shows locations on a page. Users click at these locations.
If this report is available, examine the page and its next step. Record task steps you cannot complete. If instructions are not clear, record them.
Record the page, task, date, device, and available submission counts. Keep missing data in a different field from counts for tasks with no submission.
Example data for task checks includes only data you make for these checks, without information about users or data they send with forms.
When example data is necessary for a task check, record only example data. Do not record information about a person or information users enter in forms. Record results without this information.
Sources: [2]
Get a PageSpeed Insights report
PageSpeed Insights gives page scores and recommends changes to make a page available more quickly.
The PageSpeed Insights interface is a connection for other tools to get page results.
Google has a tool to get PageSpeed Insights results without code.
Before you change the page, record the report date and device type. Select a change for the recorded task problem.
Lighthouse is the PageSpeed Insights tool for page tests with specified device and network conditions. Record these conditions with the results.
Examine the report and missing data
PageSpeed Insights gives user experience data for the 28-day collection period before the report date.
PageSpeed Insights gives page results from user experience data and Lighthouse tests.
Users do not always get good page experiences when Lighthouse results are good.
If page data is not sufficient, find the pages the report includes. Before you compare results for one page, record these pages.
For low traffic, record when data is not sufficient. Missing data does not make a result good. Compare task checks and page results in different fields.
Sources: [6]
Examine form fields and instructions
An empty form field can give instructions or example information before users enter data.
If your website shows instructions only in empty form fields, they are not compatible with all assistive technology.
A screen reader is assistive technology to help a user hear the information on a page.
Before you make the page faster, examine field names and instructions. Make sure users can find necessary instructions after they enter data.
If the page is available quickly, first correct instructions you find are not clear. If some fields are not necessary, remove them. This change can correct task problems before you make the page faster.
Do error and accessibility checks
W3C recommends forms compatible with different input formats for the same type of data.
For your website, do checks with the phone and date formats your users enter. Do these checks with example data.
Enter incorrect example data. Examine the error instructions. Then enter correct example data. Make sure the website has the submission.
Complete the task with a keyboard and a screen reader. Record fields you cannot find and instructions you find are not clear.
These accessibility checks examine task problems for users with a keyboard or screen reader. Before you change the page, do these checks with the task instructions. After you change the page, do these checks again with the same instructions. These checks do not always find all accessibility problems.
Compare results for the next step
A Lighthouse error can make it necessary to discard its result.
Before you compare results, examine report errors with the person who does your website work. If more checks are necessary, do the checks again.
After you change the page, do the task check again with the same device type. Compare available submission counts from equal periods.
Record other website changes and different conditions. These results are not sufficient to find the cause of larger submission counts.
If the task problem continues, examine its next step and instructions again. When time for website work is available, select the next important page.
Page and task check worksheet
These six rows are examples, not results from users. Record your pages and tasks in these rows. Record dates, missing data, and the pages in each report. Record only example data for task checks. After you change each page, do the same task check again.
| Page and user task | Data before you change the page | Change and next check |
|---|---|---|
| Form page: send information. | Record page scores, form problems, and available submission counts. | Correct one problem. Do the same task again. Compare counts. |
| Information page: find important information. | Record problems with information and the next step. | Change the instructions. Record remaining task problems. |
| Website page: find the form. | Record the steps necessary to find the form. | Change the next step. Do the same task again. |
| Form page: correct an error. | Record example data and error instructions. | Correct the instructions. Do the checks again with incorrect example data. Then do the checks with correct example data. |
| Form page: complete a keyboard check. | Record the task step you cannot complete. | Change the form. Do the keyboard check again. |
| Your page: complete your task. | Record the device, dates, pages in each report, and missing counts. | Record the change and next check date. |
Sources and checks
- PageSpeed Insights API | Google for Developers
Source checked 2026-10-19 - Heatmaps overview | Microsoft Learn
Source checked 2026-10-19 - Forms Tutorial | Web Accessibility Initiative (WAI) | W3C
Source checked 2026-10-19 - Method: pagespeedapi.runpagespeed | PageSpeed Insights | Google for Developers
Source checked 2026-10-19 - Form Instructions | Web Accessibility Initiative (WAI) | W3C
Source checked 2026-10-19 - About PageSpeed Insights | Google for Developers
Source checked 2026-10-19 - Validating Input | Web Accessibility Initiative (WAI) | W3C
Source checked 2026-10-19 - Get Started with the PageSpeed Insights API | Google for Developers
Source checked 2026-10-19