![WebmasterDragon.com](data:image/svg+xml;utf8,<svg xmlns="http://www.w3.org/2000/svg" width="350" height="110"><rect width="100%" height="100%"><animate attributeName="fill" values="rgba(153,153,153,0.5);rgba(153,153,153,0.1);rgba(153,153,153,0.5)" dur="2s" repeatCount="indefinite" /></rect></svg> "WebmasterDragon.com")
![normal Google Chrome icon](data:image/svg+xml;utf8,<svg xmlns="http://www.w3.org/2000/svg" width="1452" height="865"><rect width="100%" height="100%"><animate attributeName="fill" values="rgba(153,153,153,0.5);rgba(153,153,153,0.1);rgba(153,153,153,0.5)" dur="2s" repeatCount="indefinite" /></rect></svg>)
Despite Google giving web developers advance notice, I think a lot of people are going to be caught off guard by the upcoming “Not Secure” connection security label that will start showing in the Google Chrome.
As a result, your viewers and users might be confused and start asking questions. This is particularly true for content management sites (CMS) that have a login link.
![](data:image/svg+xml;utf8,<svg xmlns="http://www.w3.org/2000/svg" width="224" height="224"><rect width="100%" height="100%"><animate attributeName="fill" values="rgba(153,153,153,0.5);rgba(153,153,153,0.1);rgba(153,153,153,0.5)" dur="2s" repeatCount="indefinite" /></rect></svg>)
Like many of you, I have many roles when it comes to websites. I worry about privacy and performance. Another part of me likes to see what other sites are doing. For example, what services are other websites using? It’s not often that you find a free browser tool that covers privacy and competitive intelligence.
![Example of IE6 browser issue with image backgrounds](data:image/svg+xml;utf8,<svg xmlns="http://www.w3.org/2000/svg" width="269" height="286"><rect width="100%" height="100%"><animate attributeName="fill" values="rgba(153,153,153,0.5);rgba(153,153,153,0.1);rgba(153,153,153,0.5)" dur="2s" repeatCount="indefinite" /></rect></svg>)
This morning I was doing some last minute checks on an A/B split test. I ran the new page through different browsers to make sure my code didn’t break anything. It was then I noticed an error. I checked the original page and saw the same problem. The next question was determining how many people are impacted by this bug. To answer this, I used my web analytics program.