パーツ 3: Growing & Making Money
3.1 Performance
速いあなたのサイトを維持する - 人間と検索エンジンの両方が待機して好きではない
3.1.1 Minimise plugins
Throughout this article we’ve recommended lots of plugins. They’re all valuable and can add to your site. However, don’t go over the top. Each and every plugin that changes your site appearance adds processing and transfer overheads. Plugins that are for management use only (例えば. バックアップPLU-ギンズ) are of much less issue. Wherever possible, 機能が含まれてテーマを使用, または実装メントソリューションtions PLU-ギンズのない, 例えば, instead of using the “external links” plugin to apply style your external links, 単に少し、このスタイリングを自分で実装 CSS and an image or 2. Try to keep a sensible balance — don’t remove valuable plugins just to keep the number of plugins low, しかし、どちらかあなたが本当に必要としないものは保管しないで.
3.1.2 未使用のプラグインを削除する
This is simple — if you’re not using a plugin then don’t waste hosting space on them. Unless you think you might want to reactivate a plugin in the future don’t just deactivate, but delete. Removing unneeded plugins also keeps your wordpress management page less cluttered.
3.1.3 プラグを交換してください
いくつかのプラグインは非常に大きく、多くの機能を持っている, but you might only use one feature of such a huge plugin. Consider manually adding the code for that feature and ditching the overhead of the whole plugin (セクションを参照してください。 3.1.1) or consider finding an alternative plugin which offers just the features that you need.
3.1.4 キャッシュ & 縮小する
ワードプレスは、に基づいている PHP とMySQL, and both of these require significant processing whenever a page is accessed. Since neither users nor search engines like waiting for pages to load you should reduce load times by utilising various caching and efficiency plugins. Caching generates static HTMLの あなたのページのそれぞれのためのファイル, reducing the delay caused by your web server processing PHP and accessing the database. Minifying removes redundancy from your CSS and JavaScript. The 2 鉛INGソリューションtionsです W3は合計キャッシュ, その行いキャッシングおよび又は縮小または両方の組み合わせ WP スーパーキャッシュ そして WP Minify.
[google_adsense]
3.1.5 圧縮
Your hosting will almost certainly be running on either the Microsoft of the Apache web server. Our host uses Apache, それから送信されたデータの圧縮をサポートしています, if you choose to enable it. The Microsoft web server also supports compression which can simply be turned on or off. All modern web browsers support compression. There are 2 ApacheでCOM-圧力シオンデータのやり方, and you may only want to compress certain files. Here at DIYMH we compress all our text based files using apache’s mod_deflate. This reduces our front page load size from approx 100k to approx 20k! Depending on your web host you may only be able to enable some types of compression. BetterExplained have an COM-圧力シオンへのExcelベース貸しガイド which we recommend you read.
3.1.5 Keep scripts in files
All non content really should be in external files, ロードされていないインライン. This speeds up browser rendering significantly and also makes debugging any page errors easier. JavaScript should be in js files, STYL-INGはにする必要があります CSS files etc. Even some meta content can go in external files (例えばSEC-tionsを参照してください。 1.4.3 そして 1.4.17). WordPress is very good at keeping to this, but if you make modifications try to stick to the system. Some wordpress plugins are better than others at this, その中には、スクラッチまででない場合, CON-サイダーの検索 - INGの代替.
3.1.6 使用 CSS スプライト
CSS スプライトはの数を減らすための優れた方法である HTTP requests sent back and forth between the readers browser and your web server. Instead of having 30 individual images, すべてはrequesの - テッド9月-AR-atelyされなければならない, you can reduce the number of requests to the server by having all of images in a single file. Use CSS to insert the correct part of the image each time you want to use it. Another benefit is that 1 large image file is often smaller than several small images combined. There is more information at CSSTricks, W3Schoolsの そして スマッシュ-ING-MA-ガスINE
3.1.7 Compress images
By default lots of images can be losslessly compressed better than wordpress does by default. This will save on image transfer times. There are plugins that will do this for you, 例えば. WP Smush.it. If you’re using PNGs (などのセクションで推奨メンズDED 2.1.2) then there are several ways to improve efficiency. To maximise PNG 効率の画像はPNGGauntletで圧縮することができます, どのようにしかし、これが行われなければならない 後に upload. If the image doesn’t contain many shades or colours then save it as a 256-colour image — this will reduce the file-size significantly, しかし、再び, this efficiency should be sought after upload. The reason for not compressing or reducing the colour depth of images before upload is that the PHP resize function will not create good quality resized images if they are already compressed. So, 画像をアップロード, ワードプレスは、リサイズした画像を生成してみましょう, でそれらをダウンロード FTP プログラム, PNG-やせ-letでそれらをCOM-PRESS, and then reupload and over-write the originals. WP Smush.itはあなたを取得します 90% 道のとはるかにCON-veni-ENTです. 我々は常にPNGGauntletでローカルに私たちのPNG画像を再圧縮, but you may not want the hassle — the choice is yours.
3.1.8 Set expiration of static resources
Browsers cache all the content that they load. To avoid images and other static resources being reloaded on every page load you can specify an expiry time which instructs the browser to use its cached copy until the expiry date passes, when it will fetch a fresh copy. Anything that doesn’t change very often should have an expiry set. At DIYMH we do this via W3 Total Cache.
3.1.9 Use relative links
あなたのサイト上で何か他のものへのリンクを挿入した場合は、常に相対パスを使用する, むしろ完全なパスより. これはページサイズのほんの少しを保存します, しかし、より多くの輸入antly, それはあなたがあなたのドメイン名を変更した場合は、それらを変更する必要がないことを意味します.
3.1.10 古いリビジョンを削除する
By default wordpress retains a copy of all previous revisions of every article on your site. This is overkill in our view. The easiest way to manage this is to use a plugin, 例えば. REVI-シオンの制御, which will automatically cull older revisions based on your settings. This will keep your database size down and the speed of your site will benefit.
3.1.11 Check your page speed
Googleのページスピードながら (セクションを参照してください。 1.3.2) 開始するには良い場所です, 我々は使用して推奨つくろう ツールの広い範囲 チェックするためにあなたは完全にあなたのサイトOPTIM標準に保つました.
“Hi James I realise it has been a long while, but I just checked this on windows 11 (build 23H2)…”