Design & Development
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
Fixit – Empty Image
January 14, 2014, by mark.anderson
This test determines if your page has any empty image tags (image tags with no 'src' attribute or an empty 'src' attribute). Leaving image tags empty require processing that is ultimately wasted. When image tags need to be dynamically created this should happen with JavaScript programming... Read More
Fixit – GZip Encoding
January 14, 2014, by mark.anderson
This test determines if your page is transferred using GZip encoding. GZip encoding, or compression, reduces the data being sent and this speeds up the transfer time considerably. Where possible all web assets should use GZip encoding for transmission... Read More
