Web standards are there to unify code and that helps to create device independent apps. Sometimes the web developer makes the mistake of using inappropriate DOCTYPES which includes transitional DOCTYPES using HTML that doesn\u2019t apply anymore like canter elements not validating code or ignoring the results. It is always needed to pay attention to web standards and work around them to avoid mistakes and create a clean and error free-code and it is rightly said that old habits are difficult to get rid of.<\/p>\n
Web developers who started coding in the earlier days of HTML may still have the habit of using lots or spans and \u2018&nbps\u2019s which not only increases the line of code but also causes layout issues in updated browsers like Microsoft Edge, Google Chrome and Firefox.<\/p>\n
Ignoring <\/strong>Cross-Browser Compatibilities<\/h2>\nThose days are a distant memory when the Internet Explorer was the main program accessible to get to sites. At present, aside from the hotshots like Chrome, Firefox, Safari, there are many desktop and mobile browsers, even some device-specific browsers that are favored by users for accessing websites.<\/p>\n
![\"best](\"https:\/\/owaisnoor.info\/blog\/wp-content\/uploads\/2019\/06\/3-point.png\")
<\/a><\/p>\nUse analytic tools and target browsers on which your site is intended to run appropriately. Complete appropriate testing and see whether any usability or functional issue is happening in any such browser. Find any CSS or HTML issues that are causing breakage in a particular browser and fix the issues by supplanting them or including vendor-specific codes.<\/p>\n
Ignoring Technical SEO<\/strong><\/h2>\nWhen it comes to SEO, developers tend to work towards the quality of content, tags, keywords, meta-data, site map, etc and feel contented. However, SEO is much more than this. \u00a0It includes eliminating duplicate content, having crawlable site architecture, intelligent backlinking and a lot more. Some web developers have thoughts that SEO is something best left to the marketers or content developers. While SEO is something that must be embraced from the beginning for it to be effective. SEO is not just about content or backlinks.<\/p>\n
Authentication Without Proper Authorization<\/strong><\/h2>\nAuthentication:<\/strong> Verifying that a person is (or at least appears to be) a specific user since he\/she has correctly provided their security credentials (password, answers to security questions, fingerprint scan, etc.).<\/p>\nAuthorization:<\/strong>\u00a0Confirming that a particular user has access to a specific resource or is granted permission to perform a particular action.<\/p>\nStated another way, authentication is knowing who an entity is, while authorization is knowing what a given entity can do. You need to make sure that you verify actual requestor and content of request within your\u00a0@controller<\/strong> method\u00a0and implement proper\u00a0Authorization\u00a0<\/strong>of the request<\/p>\nAuthentication\u00a0<\/strong>and\u00a0Authorization\u00a0<\/strong>are two sides of the same coin. Never treat them separately.<\/p>\nNot Optimizing Bandwidth Usage<\/strong><\/h2>\nMost development and testing take place in a local network environment. So when you are downloading 5 background images each being 3MB or more, you might not identify an issue with 1Gbit connection speed in your development environment. But when your users start loading a 15MB home page over 3G or 4G connections on their smartphones, you should prepare yourself for a list of complaints and problems.<\/p>\n
Optimizing your bandwidth usage could give you a great performance boost, and gain this boost you probably only need a couple of tricks. There are few things that many good web developers do by default, including:<\/p>\n
\n- Minification of all JavaScript<\/strong><\/li>\n
- Minification of all CSS<\/strong><\/li>\n
- Server-side HTTP compression<\/strong><\/li>\n
- Optimization of image size and resolution<\/strong><\/li>\n<\/ol>\n
Incomplete Input Validation<\/strong><\/h2>\nValidating user input on client and server side is simply\u00a0a must do<\/strong>! We are all aware of the sage advice\u00a0\u201cdo not trust user input\u201d<\/strong> but, nevertheless, mistakes stemming from validation happen all too often. Remember that most front-end development frameworks provide out-of-the-box validation rules that are incredibly simple to use. Additionally, most major back-end development platforms use simple annotations to assure that submitted data are adhering to expected rules. Implementing validation might be time-consuming, but it should be part of your standard coding practice and never set aside.<\/p>\nDealing With Broken & Poorly Optimized Pages<\/strong><\/h2>\nThere\u2019s nothing worse than clicking a link and seeing \u201cPage Not Found,\u201d especially when it comes to a product or landing page. In other cases, the page may still exist but not display properly due to a site conflict or a broken plugin. Some websites also lose potential conversions by neglecting their product descriptions and failing to provide enough information. Any of these mistakes can have a huge impact on a business\u2019s bottom line.![\"best](\"https:\/\/owaisnoor.info\/blog\/wp-content\/uploads\/2019\/06\/2.png\")
<\/a><\/p>\n <\/p>\n
The only way to avoid these issues is to actively have eyes on your website\u2014whether it\u2019s a developer, a QA specialist, or through direct feedback from customers. There are tools that can assist in locating and solving some of these issues, but it still requires a hands-on approach with a system in place for diligent bug reporting and eliminating problems<\/p>\n
Autoplaying Videos With Sound<\/strong><\/h2>\n
<\/a><\/p>\nUse analytic tools and target browsers on which your site is intended to run appropriately. Complete appropriate testing and see whether any usability or functional issue is happening in any such browser. Find any CSS or HTML issues that are causing breakage in a particular browser and fix the issues by supplanting them or including vendor-specific codes.<\/p>\n
Ignoring Technical SEO<\/strong><\/h2>\nWhen it comes to SEO, developers tend to work towards the quality of content, tags, keywords, meta-data, site map, etc and feel contented. However, SEO is much more than this. \u00a0It includes eliminating duplicate content, having crawlable site architecture, intelligent backlinking and a lot more. Some web developers have thoughts that SEO is something best left to the marketers or content developers. While SEO is something that must be embraced from the beginning for it to be effective. SEO is not just about content or backlinks.<\/p>\n
Authentication Without Proper Authorization<\/strong><\/h2>\nAuthentication:<\/strong> Verifying that a person is (or at least appears to be) a specific user since he\/she has correctly provided their security credentials (password, answers to security questions, fingerprint scan, etc.).<\/p>\nAuthorization:<\/strong>\u00a0Confirming that a particular user has access to a specific resource or is granted permission to perform a particular action.<\/p>\nStated another way, authentication is knowing who an entity is, while authorization is knowing what a given entity can do. You need to make sure that you verify actual requestor and content of request within your\u00a0@controller<\/strong> method\u00a0and implement proper\u00a0Authorization\u00a0<\/strong>of the request<\/p>\nAuthentication\u00a0<\/strong>and\u00a0Authorization\u00a0<\/strong>are two sides of the same coin. Never treat them separately.<\/p>\nNot Optimizing Bandwidth Usage<\/strong><\/h2>\nMost development and testing take place in a local network environment. So when you are downloading 5 background images each being 3MB or more, you might not identify an issue with 1Gbit connection speed in your development environment. But when your users start loading a 15MB home page over 3G or 4G connections on their smartphones, you should prepare yourself for a list of complaints and problems.<\/p>\n
Optimizing your bandwidth usage could give you a great performance boost, and gain this boost you probably only need a couple of tricks. There are few things that many good web developers do by default, including:<\/p>\n
\n- Minification of all JavaScript<\/strong><\/li>\n
- Minification of all CSS<\/strong><\/li>\n
- Server-side HTTP compression<\/strong><\/li>\n
- Optimization of image size and resolution<\/strong><\/li>\n<\/ol>\n
Incomplete Input Validation<\/strong><\/h2>\nValidating user input on client and server side is simply\u00a0a must do<\/strong>! We are all aware of the sage advice\u00a0\u201cdo not trust user input\u201d<\/strong> but, nevertheless, mistakes stemming from validation happen all too often. Remember that most front-end development frameworks provide out-of-the-box validation rules that are incredibly simple to use. Additionally, most major back-end development platforms use simple annotations to assure that submitted data are adhering to expected rules. Implementing validation might be time-consuming, but it should be part of your standard coding practice and never set aside.<\/p>\nDealing With Broken & Poorly Optimized Pages<\/strong><\/h2>\nThere\u2019s nothing worse than clicking a link and seeing \u201cPage Not Found,\u201d especially when it comes to a product or landing page. In other cases, the page may still exist but not display properly due to a site conflict or a broken plugin. Some websites also lose potential conversions by neglecting their product descriptions and failing to provide enough information. Any of these mistakes can have a huge impact on a business\u2019s bottom line.<\/a><\/p>\n <\/p>\n
The only way to avoid these issues is to actively have eyes on your website\u2014whether it\u2019s a developer, a QA specialist, or through direct feedback from customers. There are tools that can assist in locating and solving some of these issues, but it still requires a hands-on approach with a system in place for diligent bug reporting and eliminating problems<\/p>\n
Autoplaying Videos With Sound<\/strong><\/h2>\n
Authentication:<\/strong> Verifying that a person is (or at least appears to be) a specific user since he\/she has correctly provided their security credentials (password, answers to security questions, fingerprint scan, etc.).<\/p>\n Authorization:<\/strong>\u00a0Confirming that a particular user has access to a specific resource or is granted permission to perform a particular action.<\/p>\n Stated another way, authentication is knowing who an entity is, while authorization is knowing what a given entity can do. You need to make sure that you verify actual requestor and content of request within your\u00a0@controller<\/strong> method\u00a0and implement proper\u00a0Authorization\u00a0<\/strong>of the request<\/p>\n Authentication\u00a0<\/strong>and\u00a0Authorization\u00a0<\/strong>are two sides of the same coin. Never treat them separately.<\/p>\n Most development and testing take place in a local network environment. So when you are downloading 5 background images each being 3MB or more, you might not identify an issue with 1Gbit connection speed in your development environment. But when your users start loading a 15MB home page over 3G or 4G connections on their smartphones, you should prepare yourself for a list of complaints and problems.<\/p>\n Optimizing your bandwidth usage could give you a great performance boost, and gain this boost you probably only need a couple of tricks. There are few things that many good web developers do by default, including:<\/p>\n Validating user input on client and server side is simply\u00a0a must do<\/strong>! We are all aware of the sage advice\u00a0\u201cdo not trust user input\u201d<\/strong> but, nevertheless, mistakes stemming from validation happen all too often. Remember that most front-end development frameworks provide out-of-the-box validation rules that are incredibly simple to use. Additionally, most major back-end development platforms use simple annotations to assure that submitted data are adhering to expected rules. Implementing validation might be time-consuming, but it should be part of your standard coding practice and never set aside.<\/p>\n There\u2019s nothing worse than clicking a link and seeing \u201cPage Not Found,\u201d especially when it comes to a product or landing page. In other cases, the page may still exist but not display properly due to a site conflict or a broken plugin. Some websites also lose potential conversions by neglecting their product descriptions and failing to provide enough information. Any of these mistakes can have a huge impact on a business\u2019s bottom line. <\/p>\n The only way to avoid these issues is to actively have eyes on your website\u2014whether it\u2019s a developer, a QA specialist, or through direct feedback from customers. There are tools that can assist in locating and solving some of these issues, but it still requires a hands-on approach with a system in place for diligent bug reporting and eliminating problems<\/p>\nNot Optimizing Bandwidth Usage<\/strong><\/h2>\n
\n
Incomplete Input Validation<\/strong><\/h2>\n
Dealing With Broken & Poorly Optimized Pages<\/strong><\/h2>\n
<\/a><\/p>\nAutoplaying Videos With Sound<\/strong><\/h2>\n