When I chose to venture back to the WordPress default theme, one of my worries was about my Google PageSpeed score. I had to take a serious hit, right? Spoiler, there is a surprise ending!
When I first started to develop WordPress sites, I came across an issue. I had never used WordPress like my customers did. Developers and users usually don’t see things the same way. Besides, most of them had their experiences from one of the default themes. I quickly understood that I needed to experience what they had experienced, and needed to understand their go-to solutions and their pains. At the time, twenty ten was the default one. It taught me a great deal, and helped me empathise with clients in a new way.
One of the great things about owning a Tesla is the fact that it in essence is a computer on wheels. With an API in place, this means that I can pull information from the car, just like the app does on your smartphone. It took me less than a day after taking delivery of my car before I had made my first scripts using the API, and now my OS X app project is starting to take shape.
Recently the WP-admin has gotten more attention from core developers. The Media section recently got a grid design, and the plugins area also got a visual improvement. A thought that followed; why not do the same for the User section? This idea first came around for me while working on an internal project – as well as being inspired by Noel Tock’s presentation on Designing Web Applications.
A high traffic site I host for a client needed to be available on both HTTP and HTTPS. This particular site, though, needed different caches depending on what scheme was used.
Note: Since Varnish doesn’t support HTTPS, it is in this case placed behind Nginx. Nginx then indicates any HTTPS requests passed onto by setting the
With Varnish handling caching, this is what needed to be added to the configuration:
This is a question I have heard (too) many time. How does one reset the root MySQL password on Ubuntu. In order to make this as simple as possible I created a shell script (you can see it below) that does just that.
tl;dr… Using Google Webfonts will hurt your score pretty bad, however, PageSpeed forgives you if you do it “right”.
Recently I started making some changes to my WordPress theme again, giving it a slightly more minimalistic look. Unfortunately this meant that a lot of Google PageSpeed work had to be done all over. While I was at it, I wanted to use google webfonts on my site again… not good. So how does this affect you?
I updated my site to utilize html5 history and ajax recently. One of the challenges I faced was how to handle Gist embeds. Since they only consist of a single script tag it initially seemed like there wasn’t a lot to go on. Not to mention that it would trigger a
document.write() … and that would naturally ruin my site if it were triggered dynamically.