Tag Archives: Best Practices
Fixit – File minification
January 14, 2014, by mark.anderson
This test determines if your page makes use of excessive whitespace. Whitespace in markup, CSS and JavaScript files tend to make them more readable. However the extra data adds significantly to transfer and processing times. Minification is the process of reducing whitespace in files to an absolute minimum. In many cases filesizes can drop by over 30% through minifcation, thus speeding up content delivery and processing... Read More
Fixit – Applets
January 14, 2014, by mark.anderson
This test determines if your page make use of applet tags. Applets, by and large, require specific pplugins to be installed at the browser level. While this may be possible in some instances, and for some device browsers, the majority of plugins are not mobile friendly and their use is strongly discouraged... Read More
Fixit – Inline JavaScript
January 14, 2014, by mark.anderson
This test determines if your page make use of inline JavaScript code. Requiring the browser to pass markup for JavaScript code slows processing and makes web applications increasingly brittle. Moving all JavaScript code to dedicated JavaScript include files provides a clean seperation of markup, style and code... Read More
Fixit – Styled Markup
January 14, 2014, by mark.anderson
This test determines if your page has styled markup such as basefont, center, font or u. These style markup tags are considered dated and require additional processing time to render. Best practice dictates that all style related information should be contained in CSS files and not be included in amongst markup... Read More
Fixit – Inline Styles
January 14, 2014, by mark.anderson
This test determines if your page has any inline style directives. Inline styles are both harder to maintain and require additional processing time so are not optimal. All style directives should be in dedicated CSS files instead... Read More
