Parte 3: Growing & Making Money

3.1 Performance

Mantenha o seu site rápido - os seres humanos e os motores de busca não gostam de esperar

3.1.1 Minimise plugins

Through­out this art­icle we’ve recom­men­ded lots of plu­gins. They’re all valu­able and can add to your site. How­ever, don’t go over the top. Each and every plu­gin that changes your site appear­ance adds pro­cessing and trans­fer over­heads. Plu­gins that are for man­age­ment use only (por exemplo. de backup plu-gins) are of much less issue. Wherever pos­sible, usar um tema que inclui a funcionalidade, ou soluções de imple-mento sem plu-gins, por exemplo, instead of using the “extern­al links” plu­gin to apply style your extern­al links, simplesmente implementar esta denominar-se com um pouco de CSS and an image or 2. Try to keep a sens­ible bal­ance — don’t remove valu­able plu­gins just to keep the num­ber of plu­gins low, mas não mantenha aqueles que você realmente não precisa tanto.

3.1.2 Remover plugins não utilizados

This is simple — if you’re not using a plu­gin then don’t waste host­ing space on them. Unless you think you might want to react­iv­ate a plu­gin in the future don’t just deac­tiv­ate, but delete. Remov­ing unneeded plu­gins also keeps your word­press man­age­ment page less cluttered.

3.1.3 Substitua plugins

Alguns plugins são muito grandes e têm uma série de características, but you might only use one fea­ture of such a huge plu­gin. Con­sider manu­ally adding the code for that fea­ture and ditch­ing the over­head of the whole plu­gin (ver secção 3.1.1) or con­sider find­ing an altern­at­ive plu­gin which offers just the fea­tures that you need.

3.1.4 Esconderijo & Apoucar

Palavra-Press é baseada em PHP e MySQL, and both of these require sig­ni­fic­ant pro­cessing whenev­er a page is accessed. Since neither users nor search engines like wait­ing for pages to load you should reduce load times by util­ising vari­ous cach­ing and effi­ciency plu­gins. Cach­ing gen­er­ates stat­ic HTML arquivos para cada uma de suas páginas, redu­cing the delay caused by your web serv­er pro­cessing PHP and access­ing the data­base. Mini­fy­ing removes redund­ancy from your CSS and JavaS­cript. The 2 levar-ING soluções de são W3 Total Cache, que faz as duas coisas cache e minifying ou uma combinação de WP Super Cache e WP Mini­fy.
[google_adsense]

3.1.5 Compressão

Your host­ing will almost cer­tainly be run­ning on either the Microsoft of the Apache web serv­er. Our host uses Apache, que suporta a compressão de todos os dados que envia, if you choose to enable it. The Microsoft web serv­er also sup­ports com­pres­sion which can simply be turned on or off. All mod­ern web browsers sup­port com­pres­sion. There are 2 maneiras de dados com-pres-são com Apache, and you may only want to com­press cer­tain files. Here at DIYMH we com­press all our text based files using apache’s mod_deflate. This reduces our front page load size from approx 100k to approx 20k!  Depend­ing on your web host you may only be able to enable some types of com­pres­sion. Better­Ex­plained have an guia de exce-lente para com-pres-são which we recom­mend you read.

3.1.5 Keep scripts in files

All non con­tent really should be in extern­al files, linha não carregado. This speeds up browser ren­der­ing sig­ni­fic­antly and also makes debug­ging any page errors easi­er. JavaS­cript should be in js files, Esti-ção deve estar em CSS files etc. Even some meta con­tent can go in extern­al files (por exemplo, ver SEC-ções 1.4.3 e 1.4.17).  Word­Press is very good at keep­ing to this, but if you make modi­fic­a­tions try to stick to the sys­tem. Some word­press plu­gins are bet­ter than oth­ers at this, por isso, se alguns não são até zero, con-sider-ing encontrar uma alternativa.

3.1.6 Uso CSS Sprites

CSS sprites são uma excelente maneira de reduzir o número de HTTP requests sent back and forth between the read­ers browser and your web serv­er. Instead of hav­ing 30 indi­vidu­al images, que tudo tem que ser reques-ted setembro-ar-diatamente, you can reduce the num­ber of requests to the serv­er by hav­ing all of images in a single file. Use CSS to insert the cor­rect part of the image each time you want to use it. Anoth­er bene­fit is that 1 large image file is often smal­ler than sev­er­al small images com­bined. There is more inform­a­tion at CSSTricks, W3Schools e Smash-ing-Ma-gás-ine

3.1.7 Compress images

By default lots of images can be losslessly com­pressed bet­ter than word­press does by default. This will save on image trans­fer times. There are plu­gins that will do this for you, por exemplo. WP Smush.it.  If you’re using PNGs (como reco-men-ded na sec-ção 2.1.2) then there are sev­er­al ways to improve effi­ciency. To max­im­ise PNG imagens de eficiência pode ser compactado com PNGGauntlet, no entanto isso deve ser feito depois upload. If the image does­n’t con­tain many shades or col­ours then save it as a 256-col­our image — this will reduce the file-size sig­ni­fic­antly, mas novamente, this effi­ciency should be sought after upload. The reas­on for not com­press­ing or redu­cing the col­our depth of images before upload is that the PHP res­ize func­tion will not cre­ate good qual­ity res­ized images if they are already com­pressed. So, upload de suas imagens, deixar wordpress gerou as imagens redimensionadas, down-carregá-los com um FTP pro-grama, com-pressioná-los com PNG-Gaunt-let, and then reup­load and over-write the ori­gin­als. WP Smush.it vai chegar 90% do caminho e é muito mais con-veni-ent. Nós sempre recompactar nossos PNGs localmente com PNGGauntlet, but you may not want the hassle — the choice is yours.

3.1.8 Set expiration of static resources

Browsers cache all the con­tent that they load. To avoid images and oth­er stat­ic resources being reloaded on every page load you can spe­cify an expiry time which instructs the browser to use its cached copy until the expiry date passes, when it will fetch a fresh copy. Any­thing that does­n’t change very often should have an expiry set. At DIYMH we do this via W3 Total Cache.

3.1.9 Use relative links

Se você inserir qualquer relação com qualquer outra coisa em seu site sempre usar um caminho relativo, em vez de um percurso completo. Isso economiza um pouquinho de tamanho da página, mas mais import-antly, isso significa que você não terá que alterá-los, se você mudar o seu nome de domínio.

3.1.10 Remover revisões antigas

By default word­press retains a copy of all pre­vi­ous revi­sions of every art­icle on your site. This is overkill in our view. The easi­est way to man­age this is to use a plu­gin, por exemplo. revi-são con-trole, which will auto­mat­ic­ally cull older revi­sions based on your set­tings. This will keep your data­base size down and the speed of your site will benefit.

3.1.11 Check your page speed

Enquanto o Google Page Speed (ver secção 1.3.2) é um bom lugar para começar, nós recomendamos o uso de um ampla gama de ferramentas para verificar que você optim-zados seu site totalmente.