How to optimise performance of a web-site or mobile site

-
These are all the points which can boost up your website performance. Below are just bullet points. I'll be touching each of these point every week. Stay tuned for more info.

  1. Http2 multiplexing, header compression and other features like server push
  2. Rather than showing a loader, show a rendered page(did not mean interactive). Something like server side rendering.
  3. Adding more to point 2. Push interactive state away and try to render as early as possible.
  4. Code chunks, lazy loading.
  5. Css splitting, should be route and component based.
  6. DNS resolution ? 
  7. Omitting option call.
  8. To load only useful code, rest can be loaded later when resources are free.
  9. Minify css
  10. Dns preconnect
  11. Code splitting, js and css
  12. Preloading and prefetching
  13. Image sprite using grunt
  14. Prepond API call
  15. Reduce the number of bundle
  16. JS code which can delayed, should be delayed
  17. MJS
  18. Compression: Gzip vs Brotli
  19. CDN
  20. Critical rendering CSS
  21. Service worker: Caching, prefetching
  22. Web worker: using multiple threads
  23. DNS prefetching
  24. DNS resolution using same domain and then redirection to the actual domain
  25. Service worker prefetching

Comments

  1. Kristy3 October 2022 at 00:26

    The "this site can't be reached" issue is one of the most frequent error messages you may encounter while exploring the internet. This error, which often appears in your browser's tab, indicates that the server could not locate the website you were attempting to access. This error notice could happen for a number of reasons, but fortunately there are a few things you can do to solve it.this site can't be reached problem

    ReplyDelete

Post a Comment

Popular posts from this blog

On Boarding Post

-
Welcome on board guys, I am Shubham . I am a web developer and software engineer currently living in Delhi, India. My interests range from technology to entrepreneurship. I am also interested in running, fitness, and programming. I have more than 3 years of experience in website and mobile applications development. I will be sharing all the solutions to problems that I will face in my daily life personal as well professional. Hang a minute ... personal does not include my girlfriend's talks, just kidding guys. So I hope I will be helping my audience with my experience.  
Read more

How to publish an Node application on Ubuntu.

-
Image
Do you have a dream of seeing your nodeJS application running on a live server?   But all such dreams ended up in a nightmare because you don't know anything about how to use a remote machine? And the dream remains a dream throughout your lifetime. If so then I have my empathy for you because I had been sharing the same nightmare a few days ago ever since when a friend of mine made this simple and made me took a step ahead.  Let me make it  Prerequisites: Make sure you have a running remote machine in Ubuntu14.04, say EC2 instance. If you don't know how to set up a remote machine I promise I will help you up in my upcoming posts. You have an established connection to the remote machine. So that you can access your remote machine. You can use any client say Putty or directly the ssh command. Will surely post about this well. Here are some very simple bullets points to set up a node application: After you successfully connected to the remot...
Read more

Timing tab of chrome dev tools

-
Timing breakdown phases explained Here's more information about each of the phases you may see in the Timing tab: Queueing (no-color, transparent, white ) . The browser queues requests when: The request was postponed by the rendering engine because it's considered lower priority than critical resources (such as scripts/styles). This often happens with images. The request was put on hold to wait for an unavailable TCP socket that's about to free up. The request was put on hold because the browser only allows  six TCP connections  per origin on HTTP 1. Time spent making disk cache entries (typically very quick.) Stalled/Blocking (grey) . Time the request spent waiting before it could be sent. It can be waiting for any of the reasons described for Queueing. Additionally, this time is inclusive of any time spent in proxy negotiation. Proxy Negotiation (grey): Time spent negotiating with a  proxy server  connection. DNS Lookup (Dark green) . Time spent p...
Read more