How does eValid compare with products that are based on use of the HTTP protocol?
Because eValid is a true browser, when it downloads a page it downloads all parts of the page in addition to the base URL — everything that’s needed to completely render the page. This means that timings you make with eValid always reflect the total client-side time it takes to download a page, all of its referenced components, and to completely render the page. Other systems that use HTTP protocol require you to list every page element separately to obtain this kind of detail, and even then do not include the page rendering time.