Check Accessibility, HTML, CSS, Broken Links & Spelling

FAQ > Faster running

There could be several reasons why Total Validator may appear to operate slowly when testing each page. It could be that your system has reached the limit of its own performance in terms of CPU power and/or the amount of available memory. However, there are several things you can try to improve matters as listed below:

• The broken links option waits for a response from the web server. If you do have any broken links then this will naturally slow down testing. With the Pro version you can reduce the timeout from the default of 20 seconds and raise the concurrency (or set it to 0 or leave it blank for unlimited). Alternatively turn off the broken link check altogether.
• The spell check has a double impact on performance. Loading the dictionaries uses a lot of memory, and it can take time to spell check each word. So only use spell checking when absolutely necessary.
• Try limiting the number of other applications that are running concurrently
• When testing remote pages, close any other applications that may be using the network