JavaScript for Line of Business Applications

Want to maximize the performance of your modern websites and apps with JavaScript and HTML5?

A step by step guide on how we made our main Dashboard app 10x faster.

Since node.js is perfectly suited to running multiple asynchronous functions in parallel, and since a lot of these internal API requests didn’t depend on each other, it made sense to parallelize them — fire off all the requests at once and then continue once they’ve all completed. We achieved this with the aid of the (incredibly useful) async module

Tracking down memory leaks with node.js has always been a challenge. The following discusses how to track memory leaks from within a node application itself with the help of two awesome node modules – memwatch and heapdump.

Nines is a tool that helps developers pinpoint critical performance issues using performance statistics from the Navigation Timing API, Resource Timing API, median page load speeds for all users that have visited the page, and an assesment of the page using WebPageTest.org.

There are five sections of the performance bar, located and fixed at the bottom of the screen. Current refers to your performance statistics and Page Median refers to the median page load speed of the statistics gathered in the database. Click on Page Median to see median results from individual countries. Each of those columns as three numbers seperated by /'s. The first number refers to the backend load time, the second number refers to the frontend load time, and the third number is the total load time for that page.

In this post, I’ll outline some recent observations and approaches to delivering sites for speed and broader access, and link out to various tools we are using to facilitate our approach. All of the tips mentioned in this post are implemented on this very site, and we’ve tested them heavily to ensure that they’re working as well as they can.

I’ll start with some high-level observations, then later I’ll dive into the more technical how-to. First, some general notes about page loading performance and what we aim to accomplish.

Our research on “slow DOM problem” took theses listed above as an input. After two years of experiments we got HTML GL – library which allows to render HTML/CSS content in WebGL. It is easy to use, framework agnostic and does not require developer to study new concepts or technologies keeping him in common HTML/CSS/JS world.

Users notice if sites and apps don't run well, so optimizing rendering performance is crucia!

To write performant sites and apps you need to understand how HTML, JavaScript and CSS is handled by the browser, and ensure that the code you write (and the other 3rd party code you include) runs as efficiently as possible.

Single-page applications are notorious for a large, upfront loading hit. Angular is no exception. But it doesn’t stop there at the initial loading. API calls for data, sometimes massive amounts, are likely to be requested on route changes in the application. Leading to more, you guessed it, waiting. Just don’t make your users hold their breathe. Keep them engaged and improve your Angular single-page application loading experience.

Response times in any application need to be snappy, especially in an era of instant gratification and proliferation of distractions. Keeping a user’s attention is critical. Continuous feedback on the response state of the application should be provided to the user.

Dealing with memory leaks in JavaScript applications can be a complex process. In this article I'm going to show you how to identify whether you have memory leaks, analyse them and ultimately resolve them.

I'm using an AngularJS application to demonstrate the concepts and approaches, but much of this material applies to any JavaScript application.

Contents:

• Understanding Memory Leaks What is a Memory Leak? Why is a Memory Leak Bad?
• Identifying Memory Leaks Method 1: The Wrong Way Method 2: The Timeline Method 3: Recording Heap Allocations Method 4: Heap Snapshots
• Analysing Memory Leaks Analysing the leak in Scenario 2 More on Graphs
• Fixing Memory Leaks Three golden rules Anti-patterns to avoid
• The Future Weak Maps AngularJS 2 Even Better Browsers
• Appendices Thanks Mysteries Futher Reading