1. UTILIZING TABLES INSTEAD OF DIV CONTAINERS

Tables were the accepted method for HTML component situation years back. They nearly appear to be simpler to work with than utilizing div holders and CSS when you’re beginning a front-end configuration vocation.
Be that as it may, tables can be quite muddled and can cause configuration blemishes and removals in various programs.
Table plans have been supplanted increasingly more by CSS and div compartments as a progressively ideal approach to put components and make a design. Tables are as yet helpful when showing outlines of data, yet they’re infrequently used to make designs. Attempt to settle on “table-less” formats when structuring your front-end HTML code.

2. CODING WITH OLD HTML ELEMENTS

HTML5 is the most current type of the HTML coding language, and it’s given a lot of changes to the standard page plan. HTML5 replaces components, for example, Adobe Flash with the “canvas” tag.
The new benchmarks additionally belittled a few labels, for example, and “center”for CSS plan.
It’s generally best to abstain from coding with more seasoned HTML models. Front-end configuration depends intensely on program support.
More seasoned HTML backing isn’t constantly accessible in certain programs, and it’s a terrible practice that can place your site off guard over the long haul. (Also, HTML5 has numerous magnificent favorable circumstances that will make a site increasingly current and secure.)
The code can be more diligently to help and sometimes, it can leave your site progressively defenseless against security assaults.

3. NEGLECTING TO TEST FOR EACH MAJOR BROWSER

Front-end configuration depends intensely on JavaScript and customer side scripting. This is the reason the prescribed procedures are to test your code in all the real programs.
At the very least, a great many people expect you will test your code in Chrome, Firefox and Internet Explorer (presently Edge). You can figure out what programs you’d like to help by taking a gander at your site’s perusing investigation information or utilizing an outer source to decide regular programs.
You ought to likewise decide the most established program variant you’ll bolster. Numerous clients stay with indistinguishable more seasoned programs from their PC ages, so you ought to gauge the upsides and downsides of conceivably distancing these clients with the exertion it takes to keep up code for both more established and more current programs.
Choose the most seasoned program variant you’ll support and after that test on these more established renditions.

4. OVERLOOKING RESPONSIVE MOBILE DESIGN

Portable is the new age web design services. Tablets and cell phones are the most prevalent ways for perusing the web, progressively supplanting work area perusing.
Your front-end configuration ought to consistently be responsive and bolster cell phones, or you’ll hazard punishments in indexed lists. You can likewise make a different site for a portable (additionally called “m sites”) on a subdomain, however responsive structure ought to be the default in present-day front-end coding.
After you make your plan responsive, you’ll need to test it also—with all programs and program variants. Keep in mind that cell phones have a few distinctive screen sizes, so guarantee that your code bolsters all conceivable breakpoints.
You can utilize emulators that help you test with the goal that you don’t need a few gadgets close by to test.

5. NOT PRIORITIZING SITE SPEED

Servers and transfer speed are significant for site speed, yet it’s conceivable that your front-end can be too enlarged notwithstanding for the quickest server. Picture size is a central point, as is enlarged JavaScript code that could be excessively moderate.
Continuously lessen picture size and utilize a configuration that can be resized without losing much quality, for example, PNG.
A few site speed analyzers are accessible to enable you to recognize what components of your site configuration are hindering your application. “Spaghetti” JavaScript code can hinder the customer side, and huge pictures can slow page load execution.
Likewise, with responsive structure, web crawlers even contemplate site speed for positioning, on the grounds that moderate sites baffle clients. A best practice is to consistently test your site and guarantee its exhibition is tweaked.

6. UTILIZING OUTDATED OR ABANDONED JAVASCRIPT LIBRARIES

Master tip: Stick to JavaScript libraries that have dynamic help, documentation, and reliable updates by their designers. You don’t need to just stay with worldwide renowned libraries, however, you ought to guarantee that the one you do pick will be kept up down the line.
On the off chance that the library isn’t upheld or kept up years after the fact, you may end up in a tight spot with a reliance that is never again utilitarian if a designer relinquishes their task.
It’s hard to anticipate what an engineer will do with a venture a very long time from now; however, you can see its fame by looking through the number of help networks on the web. For example, you can’t turn out badly with AngularJS or KnockoutJs libraries—they’re well known and upheld by huge brands.
These mix-ups are normal, however simple to maintain a strategic distance from. As a front-end designer, your objective ought to be to make applications that are anything but difficult to use for your watchers and bolster site usefulness and speed.
JavaScript is likely the most troublesome front-end innovation to streamline, yet by utilizing great libraries and upheld code, you can plan a front end that doesn’t back your site off and is exceptionally receptive to cell phones.