As we approach the end of 2014, many businesses are taking stock of their performance over the past year, and planning initiatives for 2015. For any business with a digital presence, this will likely include four major elements: Customer Centricity, Cloud Delivery, Responsible Analytics and Contextual Relevance.
Google is hustling the Internet toward better online security practices, in this case by proactively sunsetting support for the SHA-1 cryptographic algorithm, and with Chrome 39 in November, warning users that sites with certificates that expire past January 1, 2017 are not fully trustworthy. To ensure the best end user experience for our clients' customers Yottaa is proactively addressing certificates with an expiry date past 1/1/17 and working with customers to migrate them to SHA-2 certificates.
It seems the frequency of website security exploits across the Internet has exploded in recent months. The most recent exploit is known as Padding Oracle On Downgraded Legacy Encryption, or P.O.O.D.L.E.
Cute name aside (it doesn't sound nearlyas sinister as Heartbleed or Bashpocalypse, does it?), this is a serious vulnerability in the design of SSL version 3.0 that allows the plain text of secure connections to be calculated by a network attacker.
For extensive background information, see this excellent blog post from Symantec. Yottaa has performed a comprehensive assessment of our global infrastructure and implemented a remediation plan to eliminate the exploit.
The Yottaa team is happy to announce the addition of Domain Sharding to the stable of front-end optimization techniques available on Yottaa Site Optimizer. Domain Sharding is a technique that overcomes a specific problem found in many older browser versions: a low limit on the number of simultaneous open connections with the server.
We’re happy to announce that we’ve released two new options for safely changing the status of Yottaa Optimizer: Transparent Proxy mode and Bypass mode. These options offer more flexibility for users to manage site protection risks while working on their sites.
The default status for a site running on Yottaa Site Optimizer is “Live.” This means the site is running through Yottaa DNS, through Yottaa's CDN infrastructure, through security features like IP shielding and load balancing, and through Yottaa's Site Optimizer technology.
Sometimes, for purposes of testing, experimentation, or troubleshooting, Yottaa users may wish to experience their site apart from Yottaa's services. Our new modes can accommodate these needs by immediately rerouting the site's delivery away from some or all of Yottaa's services, in a single click. When finished, "Live" mode can be resumed in the same manner.
We’re excited to announce the launch of Yottaa Benchmark as a feature in our Yottaa Monitor service!
Yottaa Benchmark is the simplest way to compare the performance of your website or web application against competitors. Yottaa Benchmark includes data visualization that enables performance pros and neophytes alike to trace performance data from high-level trending down to milliseconds.
Currently in beta, Yottaa eComet integrates Yottaa Site Optimizer into your chosen platform’s admin panel, for an easy way to speed up your page load times, lower cart abandonment and create higher conversion rates and user engagement.
We're offering Yottaa users exclusive first access to the plugin beta, plus the next two months of your Yottaa Site Optimizer free for signing up.
In Yottaa Monitor, “Issue Definitions” offer users control over which web performance events (like a 404 error or a long page load) are categorized as an “issue.” For each issue that's raised, an alert is sent to a log in the Yottaa Dashboard, as well as in emails or texts per the user's configuration.
In the most recent version of Yottaa Monitor, users can choose between raising one or multiple issues on a more granular level. This way, users have greater flexibility in what issues end up in their inbox. For each issue definition, choose to raise a single issue if the event occurs in multiple locations, or to raise separate issues for each time the event is captured. Now your issues log won’t be jammed with events you care less about, and full of ones you do!