How Long Does an Audit Take?
Several factors contribute to the time it takes for an audit to complete, including the following:
- Page load time. The ObservePoint engine loads each page of the audit in a browser. The faster a page loads, the faster the audit completes.
- Network silence. After each page loads, the audit waits for a network silence of three seconds before proceeding to the next page. If the three seconds of silence are not reached, the wait will timeout after fifteen seconds. Noisy tags that fire repeatedly are ignored for purposes of network silence, though they are captured and reported on (see Ignored Tags for a list of specific tags that are ignored).
- Simultaneous connections. As many as 10 connections, or servers, are used at once to run an audit, potentially generating dozens of page loads per minute. Best practice is to whitelist ObservePoint's IP addresses. Alternatively, you can throttle audits to a single connection (Reduce Server Load option), but this dramatically reduces the audit's speed. Auditor by Adobe always uses a single connection.
- Page retries. If a page cannot load, such as with a 404 error, or an expected tag is not found, the audit will return to that URL later in the audit. The audit will visit a page up to three times to make sure that the error was not caused by a transient issue.
- Post-processing. After an audit has run, all the data it has collected is processed and filtered through the rules. This processing time is significant, though it doesn't take as much time as the scan itself.
- Concurrent audit limit. Each ObservePoint account can have from two to eight audits running at the same time, depending on the contract. If an account is using all their allotted concurrent slots, any subsequent audits queue up in line to wait for one to finish. Auditor by Adobe always runs one at a time.