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

    Fixit - Redirect On Load

  • This test determines if your page experiences any redirects on initial load. Redirects require the browser to resend page requests and significantly increases initial page load time.
  • Best Practices - Posted by mark.anderson - 09 Jan 2014
  • Thumbnail of Section Feature Image

    Fixit - Cookie Size

  • This test determines if your page is generating excessively large cookie data. Cookie data must be transmit by the browser with each HTTP request, so excessive cookie data will directly affect transfer speed and result in slower page load times.
  • Best Practices - Posted by mark.anderson - 09 Jan 2014
  • Thumbnail of Section Feature Image

    Fixit - CSS Import Directive

  • This test determines if your page CSS makes use of the @import directive. The import directive allows one CSS file to include others but results in slower loading time as the downloads cannot be made in parallel. CSS files should be directly referenced in the HTML markup, or condensed into a single file to increase data transfer time.
  • Best Practices - Posted by mark.anderson - 09 Jan 2014
  • Thumbnail of Section Feature Image

    Fixit - Image Crunch

  • This test determines if your page make use of images which are larger than necessary. Image files often contain metadeta and other information which is never displayed and can be stripped out to reduce the image filesize. Smaller files will transfer faster and result in a quicker page load time.
  • Best Practices - Posted by mark.anderson - 08 Jan 2014
  • Thumbnail of Section Feature Image

    Fixit - Image Sprites

  • This test determines if your page make use of image sprites. Grouping multiple images into one image sprite drastically speeds up delivery and load time. When many images are used independently many network requests are required to download them all, an image sprite combines the images into a single file which can then be cut-up using CSS.
  • Best Practices - Posted by mark.anderson - 08 Jan 2014
  • Thumbnail of Section Feature Image

    Fixit - Favicon

  • This test determines if your page has a Favicon which is a suitable size and is delivered with a far-future expiry header. All browsers will request a Favicon on page load and so it is recommended to have one, but also one which is small enough to transfer quickly and which can be cached properly.