Mike S1
Tera Contributor

As I've been looking into performance issues related to portals, I decided to run a few tests in different browsers just to do some basic comparisons. This is just to check the portal in my PDI in each of the 3 main browsers I have installed on the laptop here. I don't know that any of this matters for this test but either way, here's the summary:

  1. Chrome Version 140.0.7339.81 (Official Build) (64-bit)
  2. Firefox Version 142.0.1 (64-bit)
  3. Edge Version 140.0.3485.54 (Official build) (64-bit)

 

For all of these I ran them in Incognito or Private mode, then logged in with a test user and went to the portal. From there I ran the widget check script in the browser console (https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0744521) to see the load times for the widgets on the main page. Will there be any differences?

 

First up is Chrome:

MikeS1_0-1757519982555.png

Running 5 refreshes on the Header widget:

Call to Employee Center Header took 602.7999999523163 ms.

Call to Employee Center Header took 573.3000000715256 ms.

Call to Employee Center Header took 586.1000000238419 ms.

Call to Employee Center Header took 578.8999999761581 ms.

Call to Employee Center Header took 552.3999999761581 ms.

 

And then 5 refreshes on the Content Experience widget:

Call to Content Experience took 154.30000007152557 ms.

Call to Content Experience took 156.80000007152557 ms.

Call to Content Experience took 140.5 ms.

Call to Content Experience took 162.20000004768372 ms.

Call to Content Experience took 156.69999992847443 ms.

 

Second is Firefox:

MikeS1_1-1757520061640.png

Running 5 refreshes on the Header widget:

Call to Employee Center Header took 703 ms.

Call to Employee Center Header took 658 ms.

Call to Employee Center Header took 646 ms.

Call to Employee Center Header took 692 ms.

Call to Employee Center Header took 561 ms.

 

 

And then 5 refreshes on the Content Experience widget:

Call to Content Experience took 226 ms.

Call to Content Experience took 243 ms.

Call to Content Experience took 182 ms.

Call to Content Experience took 201 ms.

Call to Content Experience took 295 ms.

 

Third is Edge:

MikeS1_0-1757520189312.png

 

Running 5 refreshes on the Header widget

Call to Employee Center Header took 573.2999999523163 ms.

Call to Employee Center Header took 671.2000000476837 ms.

Call to Employee Center Header took 1275.6000000238419 ms.

Call to Employee Center Header took 648.3000000715256 ms.

Call to Employee Center Header took 571.6000000238419 ms.

 

 

And the Content Experience widget

Call to Content Experience took 145.40000009536743 ms.

Call to Content Experience took 156.19999992847443 ms.

Call to Content Experience took 156.70000004768372 ms.

Call to Content Experience took 147.30000007152557 ms.

Call to Content Experience took 150.5 ms.

 

So what was the outcome of this? Between testing here and then across a bunch I ran just at various times through the day was that Edge was more inconsistent. It's low values were in line with the others but it had spikes that jumped out.