Speed in The Web
In the old days, speed was a top issue on the creations of web pages. Nowadays, you probably heard someone saying, speed is not an issue anymore. The reason is because computers are more powerful and most people have access to high speed Internet.
But the reality is that speed is still a major issue on delivering your web pages. Application are also bigger, multimedia is the new standard, and bandwidth is limited. Besides, many web applications make use of frameworks, libraries, and APIs which makes the whole process slower. Most applications nowadays make use of cashing and use client programming. Client programing means that a great deal of the execution of the program are going to be executed from the client or the user. In this case, the user computer is the one processing the programs. Sure, not all the programming is client side, but rather a combination of both client and server.
The maximum size for a web image used to be 14k, and the highest width for pixel was 400px. Now, you could see images of even 10 megabytes as web headers and plenty of videos and sounds.
For a better user experience and better use of resources, we should consider at all times to save the resources. In the long run, this will bring great savings to our company and a better web experience to our users.
The best ways to save bandwidth are:
Small size images ( I mean good use of colors, backgrounds and layers, this is not necessarily the graphical size).
Small size coding (Less code, faster programs). This is achieved by removing unnecessary libraries, using frameworks only when necessary and writing efficient code.
Use of cash. This means to make use of programs that save or control the saving of your application in the user computer rather than in the server. This way, the user won't be doing a new server request every time he needs the same data.