Developer Recommendation
Blogs

Developer Recommendation

For fast operation of the pages to be developed

Last updated June 14, 2023 | 2 min read
Developer Recommendation
  • Serve images in next-gen formats.
    Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
  • Efficiently encode images.
    Optimised images load faster and consume less mobile data.
  • Reduce initial server response time.
    Keep the server response time for the main document short because all other requests depend on it.
  • Reduce unused JavaScript.
    Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
  • Properly size images.
    Serve images that are appropriately-sized to save mobile data and improve load time.
  • Avoid enormous network payloads.
    Large network payloads cost users real money and are highly correlated with long load times.
  • Serve static assets with an efficient cache policy
    A long cache lifetime can speed up repeat visits to your page.
  • Ensure text remains visible during webfont load
    Leverage the font-display CSS feature to ensure that text is user-visible while webfonts are loading.
  • Reduce the impact of third-party code
    Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading.
  • Does not use passive listeners to improve scrolling performance.
    Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance.
  • Minimise main-thread work.
    Reduce JavaScript execution time.
    Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
  • Avoid an excessive DOM size
    A large DOM will increase memory usage, cause longer style calculations and produce costly layout reflows.
  • Avoid chaining critical requests
    Consider reducing the length of chains, reducing the download size of resources or deferring the download of unnecessary resources to improve page load.