After successfully optimizing your website for speed, it’s essential to maintain and build upon those improvements. This guide will help you understand the best practices (Dos) and common pitfalls to avoid (Don’ts) to ensure your website remains fast, responsive, and user-friendly.
Securing your WordPress folders is crucial to safeguarding your website from unauthorized access and potential attacks. In this guide, we’ll walk you through essential steps to enhance the security of your WordPress directories using .htaccess rules and other methods.
Recently in Ubuntu which I use for my hosting operating system of choice I needed to bulk change permissions on a bunch of folders and files. I needed to set permissions on folders within a WordPress installation to 755 and all files in theme, plugin and asset directories to 644.
We are all trying to increase our sites speed and give our users a better experience and one often overlooked method is to leverage browser caching.
For anyone who doesn’t know exactly what we are trying to do here, I’ll try and explain. Browser caching stores elements of internet sites for an amount of your time so as to form them load quicker. For instance, if you look at 10 pages on a website and it has the same background image, logo, social media icons and so on, we can store these in the browser in order that they don’t keep being downloaded.
If you have ever changed a URL on your website, or your permalink structure without adding redirects you could have a serious problem on your hands.
But why is this a problem?
Changing URL’s without adding redirects causes problems with search engines like Google, it stops them from indexing your content and can impact your rankings.
It’s also a huge problem for users – if they find a broken link then that’s a lost opportunity for you and it’s frustrating for them, they may never return.
Here’s how to host multiple sites on your EC2 instance running the Amazon Linux AMI. You might want to host different websites on a single instance, or perhaps just different subdomains, i.e., “subdomain.yoursite.com” (this is what I wanted to do).
Today, we will be using rsync to make daily, weekly, incremental backups and then a full compressed/archived backup once a month. We will then use cron to automate the process. Lets face it us humans get lazy sometimes and most backup systems loose complete effectiveness if they are not completely automated.
