Tips to improve your website's performance
At the beginning of my career I always had trouble keeping my sites performing well, so I did some research that led me to good results that I want to share with you here. Here are some tips for improving your site's performance: 1. **Image Optimization**: Reduce the size of image files so that the site loads faster. Use optimized image formats, such as JPEG or WebP, and consider using image compression tools. 2. **Cache de Navegador**: Set up appropriate cache headers so that browsers cache static resources such as images, CSS and JavaScript. This will reduce loading times on subsequent visits to your site. 3. **CSS and JavaScript minification**: Remove whitespace, comments and other unnecessary characters from your CSS and JavaScript code to reduce its size, making it load faster. 4. **GZIP compression**: Enable GZIP compression on the server to reduce the size of files transferred between the server and the user's browser. 5. **CDN (Content Delivery Network)**: Use a CDN to distribute static content to servers around the world, ensuring fast loading times for users in different geographical regions. 6. **Minimize HTTP requests**: Reduce the number of HTTP requests needed to load a page by combining CSS and JavaScript files whenever possible and using image sprites to reduce image requests. 7. **Responsiveness**: Make sure your site is responsive and adapts to different screen sizes, ensuring a good user experience on mobile devices and desktops. 8. **Asynchronous Resource Loading**: Load non-essential resources, such as social media widgets or analysis scripts, asynchronously so that they don't impede the initial page load. 9. **Performance Monitoring**: Use performance monitoring tools such as Google PageSpeed Insights or GTmetrix to identify areas for improvement and track your site's performance over time. 10. **Quality Hosting**: Choose a reliable, high-quality hosting provider to ensure that your site has a good response speed and uptime. Please mention in the comments any other techniques you've used that haven't been mentioned for good performance.
@jair_messias_bol For Islam (Salafism), just visit your local mosque found easily enough on Google Maps. For conservative Mennonites, look for a local church on [this map](https://churchindex.org/).
@amargo85 I can't read [his fucking CSS](https://perfectmotherfuckingwebsite.com/fuckingstyle.css) because he fucking compressed it.
someone pointed out this site as a good way to see good performance 😁😁😁 [https://perfectmotherfuckingwebsite.com/](https://perfectmotherfuckingwebsite.com/)
And how can I join one of these groups?
Modern scum are members of modern culture. Since modern culture is global and ubiquitous, anyone who doesn't reject modern culture is a member of it. Some alternatives to modern culture include Salafism, conservative Mennonites, and ultra-orthodox Judaism. Joining any of these will improve your programming since you will be free of the horrible values of modern culture. I follow the [Old Testament](http://www.mikraite.org/The-Old-Testament-on-Programming-tp1923.html) myself.
I actually liked your approach to the subject, I just wanted to know who the modern scum are (members of the depraved modern culture)
This is modern thinking and mostly wrong. Modern scum (members of depraved modern culture) never test anything, they just believe in evil on faith. As Donald Knuth said "Premature optimization is the root of all evil.". <br> One needs to understand the difference between throughput and latency. On the modern internet, throughput is high, so almost all delays are due to latency. Based on this, I can respond to the points. 1. I reduce image size just as a courtesy to the user, to not abuse his cache. In general, image size has little impact on speed. 2. Yes! Caching reduces calls, so critical for speed. 3. Absolutely not. Only modern scum do this. This just makes code unreadable and has no impact on speed at all. 4. Like with #1. I don't even know if my sites do this, my sysadmin would know, but probably not. 5. I don't bother with a CDN. The less services of modern scum that I have to deal with, the better. If you limit the number of HTTP calls per page, you don't need a CDN. 6. Minimize HTTP requests of course. But the details here are all wrong. Caching is the way to do this. Don't screw up your code by combining files unnecessarily or with disgusting image hacks. For example, I use SVG files extensively while modern scum put SVG inline in the HTML. My way is better because the page is dynamic and needs to be loaded each time while the SVG files are cached. 7. Has nothing to do with performance. 8. I only do this where it is obvious. Small benefit here. 9. Monitor performance by just playing with your site. Avoid all tools made by modern scum since they are all crap. And Google is probably the world's worst company, producing the world's worst software. My sites are fast. Websites made by modern scum are usually slow.