Black Mamba
Black Mamba

Reputation: 15595

Why is node in chrome audit with lighthouse this slow?

I just created a single page js as below:

// Load HTTP module
var http = require("http");

// Create HTTP server and listen on port 8000 for requests
http.createServer(function(request, response) {

   // Set the response HTTP header with HTTP status and Content type
   response.writeHead(200, {'Content-Type': 'text/plain'});

   // Send the response body "Hello World"
   response.end('Hello World\n');
}).listen(57777);

// Print URL for accessing server
console.log('Server running at http://127.0.0.1:57777/');

So it hosts on localhost:57777. And here are the audit result for it.

Image showing audit

I started learning express so as to improve my Angular SSR performance but here I see that a blank project with text response is so bad at performance then how can I expect my angular app to be better. Can I fix the performance lagging ?

Or should I shift to laravel or other PHP framework for performance as I've spent a lot of time angular and still the app isn't that great.

Here is the report of my Angular Universal project which makes it impossible to keep it deployed.

Angular stats

Is there a way to improve the above I'm following this Universal Starter's configuration

I've followed these blogs as well but to no help:

  1. A medium blog
  2. Almost completely implemented this checklist

Upvotes: 1

Views: 1947

Answers (1)

Black Mamba
Black Mamba

Reputation: 15595

Based on Henry's comment I was forced to dig deeper and I found the devil behind this low performance. The devil

When I was running the audit and I found that all the extensions that I have installed on my browser are also taken into account.

So the solution is to: Run audit in an incognito window. Now I'll move ahead to optimize my angular.

Upvotes: 2

Related Questions