.png)
.png)
.png)
Especially with blogs, many queries are made to the database over and over again, e.g. e.g. "give me all categories". Here it helps to activate the query cache to hold the results in memory instead of running a new selection each time. It is sufficient to give the variable "query_cache" a value > 0. Depending on the memory size, you can start experimenting with 64 MB. For tuning databases, we recommend the mysqltuner.pl and tuningprimer.sh scripts, which read the server's runtime information and give you good tips. Reduce transmission time In order to shorten the transmission time, everything that has to go through the wire should be as small as possible. This primarily affects the images, the code and the header data.
Optimally compress images and minimize header data Here you have to manage the balancing act between size and appearance. Under no circumstances make the images smaller in the HTML code or with CSS. Each additional byte burns a few milliseconds of precious loading time. As soon as your page is ready, go through all Israel phone number list the images and optimize them for size and appearance. Bet that the bottom line is that there will be a number of KB? Also keep in mind that with every request to the web server, some header data is transmitted in addition to the content. With many small graphics, this can create significant overhead.
So it almost always makes sense to combine several small graphics into one large graphic and only display a section using CSS (keyword: “ image sprites ”). small JavaScript files into one large file. Compress in real time A classic is to have your content compressed by the server via GZip before it is transmitted and to send the compressed result to the browser. It is recommended everywhere and this often saves a number of kilobytes. You have to consider that the server packs the content for each visitor in real time, ie the CPU load will increase (keyword: "hosting"). Likewise, the client must first unpack the data again before it can process.