Have you seen WordPress version number as a query string after every CSS and JS file? You are not alone. It is easy to remove that string, even though there is little documentation available in the codex. Please note that it is different from what WP-Minify plugin adds in the minified version of the CSS and JS file. Having the query doesn’t allow certain browsers to cache the CSS and JS files. Once removed, it offers performance benefits on those browsers. Moreover, who would want to expose the version of WordPress at the end of these files? Continue reading “Remove Query String on CSS & JS Files”
There is no doubt that W3 Total Cache has so many options to optimize any WordPress site than any other caching plugin. Even if you use all the features it offers there are other ways to achieve the same, manually, with better efficiency and better results.
Additionally, if you have used W3 Total Cache plugin for at least a year, especially on a multisite, you’d know that it is not a perfect plugin. As with any other plugin out there, it has its own bugs, does some nasty things, some unsatisfied users, had some security flaws on some hosts and a lot more.
What’s more, it is not actively developed as of now. The latest development log shows that it’s been 5 months since the last commit with the number of unanswered questions growing by every day in the WordPress support forums.
- Jan 25, 2013 – W3 Total Cache is back in active development. Check out the screenshots of the beta version of the next major revision in W3TC!
- Jan 25, 2013 – mod_pagespeed added to the list of alternatives.
I come across this question on benchmarking WordPress in almost every optimization project I work with. So, here is a quick post to make the answer available to everyone (who might ask this question in the future).
Benchmarking can be done in two areas. Firstly the server benchmarking. It is the ability of the server to manage N number of concurrent visitors to the site. The other is application (WordPress) benchmarking. It depends on how quickly it can generate a complete webpage for the server to serve the visitor.
Whether you are an advanced user or a newbie, you may always have questions about WordPress. There are places where you can get one-to-one free help. In other places, your questions might be answered by more than 10! Anyway, there are two methods to get your questions answered.
This is a continuation of administering your WordPress blog over SSL to increase your blog security.
Nginx rewrite rules are tricky, but are easier to learn once you understand them. I’m sure they are lot easier to understand, learn and write than
.htaccess rules for Apache HTTP server. Here I solve an important issue when you use WordPress over HTTPS, otherwise called the secure protocol. Continue reading “Nginx Rewrite Rules for WP Admin over SSL”
This site is proudly powered by the following technologies…
Blogging Platform: WordPress
Web Server: Nginx – Nginx is a free, open-source, high-performance HTTP server and reverse proxy, as well as an IMAP/POP3 proxy server. Nginx is known for its high performance, stability, rich feature set, simple configuration, and low resource consumption. Here in this VPS, it listens on port 443 and has http2 enabled.
For someone like Matteo Di Capua, a WordPress upgrade may be an easy process. But, for many, it goes weird. Either the upgrade process stalls or the site starts behaving differently after the upgrade. So, what can you do to avoid any frustration during the process? Continue reading “How to Upgrade WordPress Without Trouble?”
If you are concerned about the security of your WordPress powered blog, you can start using SSL, at least for the administration of your site, irrespective of where you host (on a shared hosting or on your own VPS or dedicated). It’d make sure that the password is sent over secure channel and the WordPress backend operations are done securely. Continue reading “Administration Over SSL”