dotMobimobiThinkingmobiForgemobiReadyDeviceAtlasgoMobi
background image
  • Best Practices - Posted by mark.anderson - 14 Jan 2014
  • Thumbnail of Section Feature Image

    Fixit - Inline Styles

  • 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.
  • Best Practices - Posted by mark.anderson - 14 Jan 2014
  • Thumbnail of Section Feature Image

    Fixit - Empty Image

  • 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.
  • Best Practices - Posted by mark.anderson - 14 Jan 2014
  • Thumbnail of Section Feature Image

    Fixit - GZip Encoding

  • 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.
  • Best Practices - Posted by mark.anderson - 14 Jan 2014
  • Thumbnail of Section Feature Image

    Fixit - Stylesheet Placement

  • This test determines if your page has Stylesheet includes in inappropriate places. Grouping Stylesheet includes together in the head of the page markup is optimal for page load. Due to the HTTP specification putting Stylesheet includes elsewhere in the page, at the bottom for instance, will result in the design loading blocking while the Stylesheets are downloaded.
  • Best Practices - Posted by mark.anderson - 09 Jan 2014
  • Thumbnail of Section Feature Image

    Fixit - Javascript Placement

  • This test determines if your page has Javascript includes in inappropriate places. Grouping Javascript includes together at the end of the page markup is optimal for page load. Due to the HTTP specification putting Javascript includes elsewhere in the page, at the top for instance, will result in loading blocking while the Javascript files are downloaded.
  • Best Practices - Posted by mark.anderson - 09 Jan 2014
  • Thumbnail of Section Feature Image

    Fixit - CSS Expression

  • This test determines if your page makes use of the CSS expression directive. The expession directive encapsulates Javascript code into CSS rules, effectively mixing styling data with functional logic. This is considered bad practice as they will affect page load time. But these Javascript expressions will also be re-evaluated when the user scrolls or interacts with the page.
  • Best Practices - Posted by mark.anderson - 09 Jan 2014
  • Thumbnail of Section Feature Image

    Fixit - DNS Lookups

  • This test determines if your page uses more domain names than best practice recommends. Each unique domain name referenced by a webpage requires an additional DNS lookup, a timely network process that will ultimately slow the page loading. Grouping content on a small number of domains ensures the browser can quickly iterate through DNS lookups and proceed with page loading.
  • Best Practices - Posted by mark.anderson - 09 Jan 2014
  • Thumbnail of Section Feature Image

    Fixit - Duplicate Resources

  • This test determines if your page makes use of duplicated resources. Including the same Javascript file or CSS file for instance will likely result in double the transfer time and will impact page load time. Duplication of page resources is typically the result of human error and should be avoided whenever possible.
  • Best Practices - Posted by mark.anderson - 09 Jan 2014
  • Thumbnail of Section Feature Image

    Fixit - Etag Support

  • This test determines if your page resources are delivered using valid Etag caching support. Etags allow the browser to better understand which content can be cached and which should be re-validated on each page load.
  • Best Practices - Posted by mark.anderson - 09 Jan 2014
  • Thumbnail of Section Feature Image

    Fixit - DOM Size

  • This test determines if your page DOM (Document Object Model) is excessively large. Larger page DOMs require more memory and their extra complexity require additional data transfer time. Reducing the DOM complexity and size drastically affects page load time.