DEV Community

Cover image for Mistakes to Avoid as a Web Developer
Joseph Mania
Joseph Mania

Posted on • Originally published at

Mistakes to Avoid as a Web Developer

Developing a site for single Screen Sizes

Remember, the US statistics showed that 68% of the traffic comes from mobile phone users. So, you might be tempted to develop a site, only viewing it on your machine, but not considering other screen sizes. If you are new to the web, just press F12 while viewing your site. It will show different screen sizes.
Make sure it fits and has a good impression on the computer, tablets, and many phone types. It’s hard to design a responsive website for every gadget, but an estimation of 9 gadgets is okay. Just make sure the site appears good on the phone.

Developing site for single Browser

While testing, you must be keen. This is a mistake that has affected almost every web developer. Each site has its rules, colors, fonts, and grids. Make sure you test it with four popular browsers, i.e Chrome, Mozilla, Firefox, and Microsoft Edge. You will find a different appearance in one of the four sites. This might be due to outdated functionality or a new package that is not unknown on the browser.

Using too many third parties

Third parties are packages or libraries that are owned and modified by the owner. Let’s say you have used a Django package to integrate with a certain payment method. After a while, the developer updates the package, which means the functionality won’t work. Also, those third parties increase the loading speed. If you can write your CSS, it’s fine, don’t use too much bootstrap. They increase the loading speed.

In short, if you can write your code do it. Let’s not pour those libraries into every place. Using libraries and packages speed up the rate of your development. But too much of something is poisonous.

Not designing a rough sketch

Designing is something that ‘Apple founder’ use to insist on while making their products. So if you just rush into development, it will be hard. That’s where software engineering principles apply. You have to sketch the platform and understand where all the items will go. You can do this on paper. It’s not a waste of time. Narrow down all the resources required before commencing the implementation process.

Less or No Optimization of the site

Let’s take an example, if you upload 10 images on the same page, what will be the loading time? What if you use jpeg over the png, will the time be the same? What if we add two videos? You have to understand the aspect of site optimization. The statistics say a customer will spend less than 10 seconds waiting for the site to load, if it doesn’t, he/she leaves it.

Know how to compress staff like the server-side HTTP. Make sure the images are smaller. Then, eliminate unused code in CSS, HTML, and JavaScript. Don’t fill your HTML with unimportant tags.

Top comments (0)