HSTS: Improving Security Without Losing Performance

This document provides recommendations for migrating a website from HTTP to HTTPS. It recommends testing the SSL certificate, setting up Google Search Console access for HTTPS, running HTTP and HTTPS simultaneously, tracking in Google Analytics using Google Tag Manager, checking all templates and mobile versions render correctly, monitoring for mixed content exceptions, setting up a site audit in SEMRush, redirecting canonical tags and sitemaps after testing, implementing 301 redirects, enabling HTTP Strict Transport Security (HSTS), and addressing potential issues like images or embeds loaded insecurely. It emphasizes a gradual, step-by-step approach to ensure minimal risk in migrating to HTTPS.

HTTP is dead. Here’s why, and what you need to know to migrate to HTTPS. Delivered to the BigWP Meetup NYC on September 15, 2015. Detailed guide: https://docs.google.com/document/d/1EJKAoa4Hxc4AyH0znuA_AAplcNeNejEhATFptFX-OME/edit

This presentation is going to focus on HTTPS, the challenges people are facing when migrating and why you should be planning your migration.

Securing your web application and protecting your users are 2 of the most important things to a developer nowadays. We all know about the dangers of cross site scripting and sql injection, but did you know that you can also make the browser do its share? In this presentation we'll dive into the world of the HTTP security headers, which will make the browser help protect your users.

Google is pushing websites to adopt HTTPS to secure connections and provide encryption. The document discusses reasons for this, including privacy benefits and how some new browser features only work for secure HTTPS sites. It outlines challenges with migrating to HTTPS, including speed impacts and ensuring all site assets use HTTPS. HTTP/2 is presented as the next evolution, allowing more efficient use of network resources. Browser support for HTTP/2 is discussed, along with how it generally requires HTTPS for implementation.

This document summarizes best practices for architecting and optimizing Ajax applications. It discusses how application architectures have evolved from traditional MVC to a more dynamic model with code running in both the server and browser. It provides guidance on improving performance through proper markup, understanding browser specifics, optimizing network usage, caching strategies, and reducing DOM manipulation. The document emphasizes that performance must be a primary consideration in Ajax application design.