- Our Blog
It’s obvious to say that all websites need upkeep, but often times they are left as “good enough.” Collecting dust, attracting hackers, slipping in the rankings. We’ve already gone into painstaking detail about why page speed matters and various levels of guidance for site speed optimization overhaul from novice to advanced.
One of my goals this year was to get portent.com set-up utilizing HTTP/2 and optimizing that configuration. Late last week I was able to accomplish that, and the results are impressive. Like, 500 milliseconds impressive. We used to top out around 1.2 seconds after going to HTTPS, so I didn’t think the results would be that dramatic. What’s more, this was a relatively easy win.
Most of my time is dedicated to dev projects that make the lives of marketers easier. Web sites, apps, tools, scripts, etc. Today however, I’m writing for web devs in an attempt to make their lives easier. And their solutions smarter. On top of that, I need to correct the approach I wrote about a couple of years ago for a GitHub auto-deploy solution.
Search Engine Optimization (SEO) is a bit of a mystery for most developers. So, I’ve put together this checklist of SEO essentials that will make your SEO team and your client very happy. Inspect the HTML source code Get picky about HTML source code: Is your HTML structure valid? Valid HTML structure makes the page easier for search engines to parse. You can validate it here.
At this point, anyone who browses, manages, and/or creates websites on the regular, should know that page speed matters. So.. everyone. It’s no surprise that we demand our information fast, like right meow. If this is a new concept, you are lagging far behind. I believe the majority of users understand this but are still figuring out how to accomplish it.
Preface: Let’s make a ruckus Chapter 1: How to use this “book” Chapter 2: Why Site Speed Matters Chapter 3: What Impacts Site Speed? Chapter 4: Novice Chapter 5: Intermediate Chapter 6: Advanced Chapter 7: Tools Chapter 8: Glossary Hidden Track: WordPress Optimization ← You are here Special section: Optimizing for WordPress We show unabashed favoritism and profess our love for a piece.
This is a question I get asked a lot as senior developer at Portent. A client, new or existing, has an established site running on some platform, and wants to add on a blog, a microsite, or the ability to easily control top-of-funnel marketing content. Technically, “in parallel” means WordPress (WP) is set up to run alongside your existing site, hosted from the same server.
In an effort to streamline development updates to a code base in a staging or production environment, we have created an auto-deploy setup guide for any GitHub (github.com) repository. What you will need: A server to host your site. Our example is a Ubuntu (Linux) server running either Apache or Nginx and PHP SSH access to your server with sudo/root privileges A GitHub.
It was 4:05 AM PST on November 18th when I got the email from Paul: “Andy – NBC broke the embargo early, please push the site live now.” I had just awoken an hour and a half earlier after a 3 hour nap. Preceding that, 17 hours straight of environment tweaking, nginx/php5-fpm/varnish configurations, and meticulous testing.