2/16/2007 ↓

Speed Up WordPress

If you like this post, please subscribe to our RSS feed to read our new posts every day.

4+1 Ways To Speed Up WordPress With Caching lists five things to do to speed up your WordPress blog. Good to follow if you have a high traffic blog.

1 Star2 Stars3 Stars4 Stars5 Stars (1 votes, average: 5 out of 5)
Loading ... Loading ...

Friends

Translate

Translate to German Translate to Spanish Translate to French Translate to Italian Translate to Portuguese Translate to Japanese Translate to Korean Translate to Russian Translate to Chinese

Latest Videos

8 Comments | Leave a comment | Comments RSS

  1. Not just useful for high-traffic blogs, but any WP site; you never know when your low-traffic site might be dugg, et cetera. An ounce of prevention, and all that.

    [Reply]

    Nemo (5 comments.) — 02/16/2007 @ 2:25 pm
  2. Your post 4+1 Ways To Speed Up WordPress With Caching
    is a very wonderful piece of advice . Since we use WordPress
    we think you are doing a great service .
    Please keep posting .
    THANKS ,
    http://blogs.mindbodynsoul.com

    [Reply]

    RAKESH (1 comments.) — 02/16/2007 @ 2:47 pm
  3. I am getting an internal server error when get near 10,000 unique visitors (IPs in a day?) and I use wp-cache. I don’t understand the problem

    [Reply]

    Carlos Aquino (1 comments.) — 02/16/2007 @ 3:50 pm
  4. 10,000 uniques per day? Wow…

    Thanks for the link. I’ve done most of these already, but had never played with WP-Cache. I doubt my site will ever generate enough traffic to warrant its use, but it’s good to know I won’t have to code something from scratch :)

    [Reply]

    Jason (57 comments.) — 02/16/2007 @ 8:47 pm
  5. Nice article but you missed a major method to speed up wordpress.. Caching with Apache!

    There is a detailed article about setting up your images, javascript, css, etc., to be cached by your visitors (and stop 304 If-Modified-Since requests) at Speed Up Sites with htaccess Caching

    If a browser receives an image with the cache control headers that say the image can be considered fresh for 2 weeks, then for 2 weeks the image can be pulled directly from the browser’s (or proxy’s) cache on subsequent requests.This is noticeably faster than even a conditional GET and a 304 response from the server since there is no round trip. After two weeks, a conditional GET would be sent to the server to check the Last-Modified date, then again, no requests would be made for the duration of the specified freshness period.

    [Reply]

    Jeremy Stewart (1 comments.) — 02/18/2007 @ 11:53 pm
  6. There has been some issues with using WP-Cache recently. Hope they sort that out with the latest WordPress version 2.1

    [Reply]

    Keith (6 comments.) — 02/19/2007 @ 2:37 pm
  7. I’m running wp-cache on both my blogs. What kind of problems are you facing?

    [Reply]

    Ajay (140 comments.) — 02/19/2007 @ 2:45 pm
  8. Awesome! I hope this post gets spread around the net, we would all benefit by implementing faster blogs and websites. Thanks!

    Missing 1 little piece though, you should encourage people to also implement a server-side caching scheme to send out the correct caching headers with static content such as images, javascript, css, pdfs, favicon.ico, etc..

    Read about it: htaccess Caching

    You will also like reading about the 14 Top Methods for faster, speedier sites

    [Reply]

    Apache Master (1 comments.) — 05/29/2007 @ 7:07 pm

Leave a comment

Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

(required)

(required, will not be published)


S2