Perhaps it would even have a negative impact, given that some browsers enforce OCSP for EV certificates, which could slow things down if the server or client does not support OCSP stapling. (Not sure if that combination - enforcing OCSP for EV but not supporting stapling - exists in a browser out there.)
Then:
https://paypal.com Identified by Thawte
Compared to now: PayPal Inc [US] | https://paypal.com
I'd love to either be able to do this ourselves or for the browsers to test the effectiveness of their own UIs.That'd be pretty cool. A flag you could set (probably in head > meta) that instructs the browser to use a default padlock instead of a fancy EV name for display HTTPS info. That'd obviate the need to have two separate HTTPS endpoints for your app too. Combined with User-Agent verification you could infer what % of clients respect the flag and what % impact (if any) it has on their conversion habits.
Course I doubt browser vendors would be up for adding something like this. Would probably be a pain as the rendering code would be separate from the display of the overall chrome.
A pretty green bar with your company name is great and all but is it actually worth it? It's not just the couple hundred dollar price tag of getting the EV cert. It's the maintenance of having to manually replace it every N years v.s. automating the deployment via something like LetsEncrypt.