当サイト、Codex 日本語版は今後積極的な更新は行わない予定です。後継となる新ユーザーマニュアルは、https://ja.wordpress.org/support/ にあります。
万が一、当サイトで重大な問題を発見した際などは、フォーラムWordSlack #docs チャンネルでお知らせください。</p>

WordPress の最適化

提供: WordPress Codex 日本語版
2015年7月25日 (土) 17:02時点におけるNukaga (トーク | 投稿記録)による版 (ソフトウェアパフォーマンス)

移動先: 案内検索

トラフィックの多い WordPress インストールを運営している場合は、WordPress とサーバーが出来る限り効率よく動くよう最適化したいと思うことでしょう。この記事ではその際に検討すべき全般的な概要を説明しています。各分野の細かい技術的な解説ではありません。


WordPress 最適化へのイントロとしては、チートシートが良いでしょう。最適化関連のすべての記事は、WordPress の最適化カテゴリーで読めます。

高トラフィック WordPress サイト向けのヒントも参照してください。





バーチャルホスト (VPS) / 専用サーバー

このホスティング環境では、自分のサーバーをコントロールすることができます。サーバーは専用のハードウェアの時もありますし、物理的にはひとつのハードウェアを共有しているバーチャルサーバーの場合もあります。キーとなるのは、サーバー設定を変更できるということです。上記 (キャッシングWordPress パフォーマンス) に加え、以下のテクニックが参考になるでしょう。




WordPress データベースは簡単に別サーバーへ移動でき、設定ファイルに少し変更を加えるだけで済みます。同様に、画像などの静的ファイルも代替サーバーに移動できます (オフロードを参照)。

複数のデータベースを採用する場合は、HyperDB クラスを標準の WPDB class にそのまま入れ替えることができ、レプリケーションおよびパーティション構造のどちらでも複数のデータベースサーバーに対応できます。


Your hardware capability will have a huge impact on your site performance. The number of processors, the processor speed, the amount of available memory and disk space as well as the disk storage medium. Hosting providers generally offer higher performance for a higher price.

One innovation in hosting is the use of Solid State Drives or SSDs which are faster than traditional magnetic media. Digital Ocean offers affordable SSD hosting and Amazon has recently added SSD hosting to its cloud offerings.


Your theme will have a huge impact on the performance of your site. A fast, lightweight theme will perform much more efficiently than a heavy graphic-laden inefficient one.

The number of plugins and their performance will also have a huge impact on your site's performance. Deactivating and deleting unnecessary plugins is very important way to improve performance.


最新のソフトウェアを使用しているかどうかを確認することも重要です。ソフトウェアのアップグレードは、多くの場合、バグを修正し、パフォーマンスを向上させるようになっています。Linux(または Windows )が、Apache、MySQLサーバと PHP の最新バージョンを実行していることを確認することは非常に重要です。



The amount of traffic on your server and how its configured to handle the load will have a huge impact as well. For example, if you don't use a caching solution, performance will slow to a halt as additional page requests come in and stack up, often crashing your web or database server. If configured properly, most hosting solutions can handle very high traffic. Offloading traffic to other servers can also reduce server load.

Abusive traffic such as login attacks, image leaking (other sites linking to your image files from high traffic pages) or DoS attacks can also increase server load. Identifying and blocking these attacks is very important.


Making sure the images in your posts are optimized for the web can save time, bandwidth and increase your search engine ranking.


The distance between your server and your website visitors also has an impact on perceived performance. A Content Delivery Network or CDN can mirror static files and images across various geographic regions so that all of your site visitors have optimal performance.

画像・静的ファイルへの CDN 利用

画像、JavaScritp、CSS、テーマファイルなどの検索・配信を CDN にオフローディングすることで、高速化のみでなく WordPress サーバーのアプリスタック自体への不可を軽減できます。CDN は WordPress キャッシングプラグインと一緒に使うと最も効果的です。詳しくは キャッシングのページをご覧ください。


  • Google PageSpeed is an excellent way to measure your WordPress site's performance and receive clear, specific feedback on how to make improvements.
  • New Relic also provides a free library for measuring server performance in PHP and MySQL
  • Linux Top provides a dashboard for your server's real time performance.
  • If using Varnish Cache, VarnishStat helps assess the performance aspects of your caching tools.
  • Zend Server Z-Ray provides X-Ray vision and deep insight into your WordPress PHP application



If you need a quick fix now, go straight to the Caching section, you'll get the biggest benefit for the smallest hassle there.

WordPress 設定の最適化


The first and easiest way to improve WordPress performance is plugins. Deactivate and delete any unnecessary plugins. Try selectively disabling plugins to measure server performance. Is one of your plugins significantly affecting your site's performance?

Then you can look at optimizing plugins. Are plugins coded inefficiently? Do they repeat unnecessary database queries? WordPress has its own caching system, so generally speaking, using functions like get_option(), update_option() and so on will be faster than writing SQL.


After plugins come theme optimization.

  • 画像ファイル
    • Are there any unnecessary images? (e.g. Can you replace some of the images with text?)
    • Make sure all image files are optimized. Choose the correct format (JPG/PNG/GIF) for the type of image.
    • Smush.it and WP Smush.it plugin can also help.
  • 合計のファイル数/サイズ
    • Can you reduce the number of files needed to display the average page on your site?
    • Combine multiple CSS files into a single, optimized file.
    • Minify CSS and JavaScript files.
    • If necessary, look into plugins to help this process (e.g. Head Cleaner and WP Minify).
  • Query Reduction/Optimization
    • Can static values be hardcoded into your themes? This will mean you have to edit code every time you make changes, but for generally static areas, this can be a good trade off.
      • For example, your site charset, site title, and so on.
      • Can you hardcode menus that rarely change? Avoiding functions like wp_list_pages() for example.

We have seen themes which put 3x extra load to the server. Turned out it caused 3x more database queries - which is bad in itself. Then we found out that some of the queries are unoptimized. Not good.

You can also use offloading to optimize your theme.

Let Someone Else Do It

Using a Managed Hosting solution such as WordPress.com, Page.ly or WPEngine takes advantage of the hard work and expertise of service providers to do the heavy lifting of optimization for you.


Paying more for higher service levels at your hosting provider can be very effective. Increasing memory (RAM) or switching to a host with Solid State Drives (SSD) e.g. Digital Ocean can make a big difference. Increased number of processors and processor speed will also help.


Make sure you are running the latest operating system version e.g. Linux, Windows and the latest web server e.g. Apache, database e.g. MySQL server and PHP.

DNS: Don't run a DNS on your WordPress server. Use a commercial service for DNS such as Amazon's Route 53 or your domain registrar's free offering. Using a service such as Amazon can also make switching between backup servers during maintenance or emergencies much easier. It also provides a degree of fault tolerance. If you host your DNS on external servers this will reduce the load on your primary web server. It's a simple change, but it will offload some traffic and cpu load.

Web Server: Your web server can be configured to increase performance. There are a range of techniques from web server caching to setting cache headers to reduce load per visitor. Search for your specific web server optimizations (for example, search for "apache optimization" for more info). Some web servers have higher speed versions you can pay for such as Apache Litespeed. There are also a number of ways to tune Apache for higher performance based on your particular hosting and site configuration, e.g. Memcache.

PHP: There are various PHP accelerators available which can dramatically improve performance of your PHP files. This will apply to all PHP files, not just your WordPress installation. Search for PHP optimization for more information, f.e. APC. The W3 Total Cache plugin, described below, offers integrated support for Memcache, APC and other Opcode caching.

MySQL: MySQL optimization is a black art in itself. A few simple changes to the query cache settings can have a dramatic effect on WordPress performance because WordPress repeats a lot of queries on every request. Search for mysql optimization for more.

A great example of how WordPress has been optimized was presented by Iliya Polihronov at WordCamp San Francisco 2012. Iliya, among other things, does server optimization for WordPress.com.

Don't run a mail server on your WordPress server. For your contact form, use something like Contact Form 7 with free Mailgun.



Plugins like W3 Total Cache or WP Super Cache can be easily installed and will cache your WordPress posts and pages as static files. These static files are then served to users, reducing the processing load on the server. This can improve performance several hundred times over for fairly static pages.

When combined with a system level page cache such as Varnish, this can be quite powerful. If your posts/pages have a lot of dynamic content configuring caching can be more complex.

W3 Total Cache

W3 Total Cache (W3TC) is the latest generation in WordPress performance plugins, combining the research of web development authorities to provide an optimal user experience for WordPress sites. These detailed guides walk you through

W3TC is unique in its ability to optimize server side and client side performance, adding functionality otherwise unavailable natively:

  • Page Caching: W3TC helps to decrease response time by creating static HTML versions of pages, allowing web servers to serve them without invoking PHP. It automatically updates the cache when comments are made or pages are edited.
  • Minification: Removes unnecessary characters from HTML, CSS and JavaScript files, then respectively combines them before applying HTTP compression on the cached files.
  • Database Caching: Database queries (objects) are also cached, allowing many sites to reduce the time needed to generate new pages. This is especially useful for sites that receive a lot of comments.
  • Headers: W3TC manages the headers (entity tag, cache-control, expires) which control the caching of files in web browsers, reducing server load and improving the user's perceived performance.
  • Content Delivery Network (CDN): Using a CDN allows you to Offloading resources from your hosting account. W3TC moves the requests for images, CSS, JavaScript and other static files to a network of high performance servers. The server closest to the visitor is automatically used to download the files, providing the fastest downloads possible.

W3TC can be used to optimize WordPress in both single- and multi-server environments through either shared or dedicated hosting.

WP Super Cache

WP Super Cache is a static page caching plugin for WordPress. It generates HTML files that are served directly by Apache without processing comparatively heavy PHP scripts, helping you to make significant speed gains on your WordPress blog.

WP Super Cache is a fork of WP Cache by Ricardo Galli Granada. WP Cache also caches your WordPress blog pages and delivers them without accessing the database. However, its use is no longer recommended, as WP Cache still needs the PHP engine to be loaded in order to serve the cached files.

However, WP Super Cache gets around this problem, allowing HTML files to be generated and served without ever invoking a single line of PHP. Using WP Super Cache allows your server to serve cached HTML pages at the same speed it serves regular graphic files. Consider WP Super Cache if your site is struggling to cope with its daily number of visitors, or if it appears on Digg.com, Slashdot.org or any other popular site.


Web server caching' is more complex but is used in very high traffic sites. A wide range of options are available, beyond the scope of this article. The simplest solutions start with the server caching locally while more complex and involved systems may use multiple caching servers (also known as reverse proxy servers) "in front" of web servers where the WordPress application is actually running. Adding an opcode cache like Alternative PHP Cache (APC) to your server will improve PHP's performance by many times.

Varnish Cache works in concert with W3 Total Cache to store pre-built pages in memory and serve them quickly without requiring execution of the Apache, PHP, WordPress stack.

As described within, using a plugin for comments such as Disqus instead of native WordPress comments can assist Varnish by not requiring your readers to login to WordPress and increasing the number of page views that Varnish can serve out of the cache.


Browser caching can help to reduce server load by reducing the number of requests per page. For example, by setting the correct file headers on files that don't change (static files like images, CSS, JavaScript etc) browsers will then cache these files on the user's computer. This technique allows the browser to check to see if files have changed, instead of simply requesting them. The result is your web server can answer many more 304 responses, confirming that a file is unchanged, instead of 200 responses, which require the file to be sent.

Look into HTTP Cache-Control (specifically max-age) and Expires headers, as well as Entity Tags for more information.

W3 Total Cache integrates support for browser caching and ETags.



CDN(content Delivery Network)の使用

Using a CDN can greatly reduce the load on your website. Offloading the searching and delivery of images, javascript, css and theme files to a CDN is not only faster but takes great load off your WordPress server's own app stack. A CDN is most effective if used in conjunction with a WordPress caching plugin such as W3TC, described above.

Amazon Cloudfront uses the Amazon S3 service to provide Content Delivery Network (CDN) functionality for your static files. A CDN is a service which caches your static files on numerous web servers around the world. Providing faster download performance for your users no matter where they are. It's recommended that you use Cloudfront in tandem with S3 and not only S3 alone; the costs are not significantly different. MaxCDN is a pay-per-usage Content Delivery Network (CDN) similar to Amazon Cloudfront. Among the differences are support for Video-on-demand as well as "mirroring" (no uploading required) of files, although you can upload them if you prefer.

Another alternative CDN provider is KeyCDN. They provide step-by-step WordPress integration guides on their support page.

KeyCDN and MaxCDN are among the most affordable CDN options available, they're able to beat the pricing of competitors like Amazon because they are a division of a much larger CDN Providers.


Any static files can be offloaded to another server. For example, any static images, JavaScript or CSS files can be moved to a different server. This is a common technique in very high performance systems (Google, Flickr, YouTube, etc) but can also be helpful for smaller sites where a single server is struggling. Also, moving this content onto different hostnames can lay the groundwork for multiple servers in the future.

Some web servers are optimized to serve static files and can do so far more efficiently than more complex web servers like Apache, for example publicfile or lighttpd.

Amazon Simple Storage Service (S3) is a dedicated static file hosting service on a pay-per-usage basis. With no minimum costs, it might be practical for lower traffic sites which are reaching the peak that a shared or single server can handle.


There can also be user improvements by splitting static files between multiple hostnames. Most browser will only make 2 simultaneous requests to a server, so if you page requires 16 files they will be requested 2 at a time. If you spread that between 4 host names they will be requested 8 at a time. This can reduce page loading times for the user, but it can increase server load by creating more simultaneous requests. Also, known is "pipelining" can often saturate the visitor's internet connection if overused.

Offloading images is the easiest and simplest place to start. All images files could be evenly split between three hostnames (assets1.yoursite.com, assets2.yoursite.com, assets3.yoursite.com for example). As traffic grows, these hostnames could be moved to your own server. Note: Avoid picking a hostname at random as this will affect browser caching and result in more traffic and may also create excessive DNS lookups which do carry a performance penalty.

Likewise any static JavaScript and CSS files can be offloaded to separate hostnames or servers.


Your feeds can quite easily be offloaded to an external service. Feed tracking services like Google FeedBurner will do this automatically, the Feedburner servers will handle all the feed traffic and only update the feed from your site every few minutes. This can be a big traffic saver.

Likewise you could offload your own feeds to a separate server (feeds.yoursite.com for example) and then handle your own feed stats / advertising.


It may be possible to host some of your files on external servers for free. For example, popular image hosting web sites like Flickr provide image hosting at no cost. Even offloading your most popular images to a free service could significantly reduce the impact on your main server.

However, there is a very important issue to consider when using a free service to offload your images. Since most of the popular services are actually photo sharing sites, copyright becomes a concern. Be sure to read the service disclaimer and decide if it suits you. Moreover, you may not want your images exposed to the users of the photo sharing site.

Consider that free image hosting services are recently becoming a less viable choice since traffic from them is often blocked by corporate networks.



There are a number of ways to compress files and data on your server so that your pages are delivered more quickly to readers' browsers. W3 Total Cache described above integrates support for most of the common approaches to compression.

W3 Total Cache supports Minify and Tidy to compress and combine your style sheets and javascript files. It also supports output compression such as zlib, see also Output Compression.

It's also important to compress your media files - namely images. The WP Smushit plugin can help with this.



The WP Optimize plugin can help you reduce extra clutter in your database.

You can also instruct WordPress to minimize the number of revisions that it saves of your posts and pages.


While it requires additional expertise, adding servers can be a powerful way to increase performance. I highly recommend reading Architecting a Highly Scalable WordPress Site in AWS A guide for building a more expensive, highly scalable AWS implementation using Amazon's Relational Data Store (RDS).

You can use Amazon's Elastic Load Balancer to spread traffic across multiple web servers and you can use HyperDB or Amazon's RDS to run more scalable or multiple database servers.

MySQL チューニングの参考文献

WordPress 向けの MySQL チューニングおよびサーバー設定については以下などを参考にしてください。



WordCamp 講演

このページ「WordPress の最適化」は未翻訳です。和訳や日本語情報を加筆してくださる協力者を求めています

最新英語版: WordPress Codex » WordPress_Optimization最新版との差分