WPScans.com VS The Acid3 Test

During insurance renewals with cyber cover but you could always provide the underwriters with a report from something as simple as https://wpsec.com/ which should reduce it. My concern with your model is that that you must keep in mind the state of the insurance market and always attempt to reduce your clients' overall cost for selecting your service. If your service is going to quote higher than insurance without... Source: about 1 year ago

I would suggest contacting GoDadd for help, but from what you've described sounds like WordPress itself maybe the issue. Could be installation issue like an insecure SQL connection or a vulnerability in a plugin / theme. Sounds like you've taken a good first action in cycling out passwords and logins, another step to take would be scan the site with a vulnerability scanner like https://wpsec.com/ and look into a... Source: over 2 years ago

Try running a scan on https://wpsec.com/ to see where you are on security. The report may give you some ammo when you talk to the boss. Source: over 2 years ago

Https://shadow.goose.icu/?http://acid3.acidtests.org/. - Source: Hacker News / 7 months ago

During the browser wars, web developers created “Acid Tests” to see how well a browser supported various style sheet and markup conventions. When the acid tests became popular, there were accusations that browser engineers were manipulating their rendering engines to pass those tests. For instance, some cascading style sheet attribute would pass the test, but fail to work as expected under normal use on a web page. Source: about 1 year ago

I am sure that both firefox and chromium-based browsers will pass most of something like ACID3 test. But at this stage standards have nothing to do with reality. Standards define perhaps 10% of the code you are writing and interpretation of the rest 90% of the code is up to the browsers. Source: almost 2 years ago

The old version (http://acid3.acidtests.org/) will reach 97/100 on modern compliant browsers. There is a newer version (https://wpt.live/acid/acid3/test.html) which incorporates the changes made to the specs in the meantime, so modern browsers will reach 100/100 on this one again. The test was carried out against this version, as you can see in the address bar in the screenshot. - Source: Hacker News / about 2 years ago

Different PRESENTATION of content on mobile is good. Different content on mobile is the definition of r/assholedesign. It does not matter if the http user agent is a "good" one or not, it should just work. There is a specification, numerous accessibility guidelines, plenty of tests and benchmarks. This isn't 1999 anymore... 🤷‍♂️. Source: over 2 years ago