www.wysiwygwebbuilder.com

I'm pretty sure this is not a WWB problem, but this seemed like the right place to find and explanation.
I use the following font in a logo for my site. It renders smoothly in some browsers, but jagged in others.
The font is: Arial Italic Bold Size 13
Below is a brief matrix describing my results.

Chromebase - single machine (ChromeOS):
Chrome Browser -renders smoothly
Microsoft Edge - renders smoothly
Pale Moon - renders smoothly

Windows 11 - single machine:
Chrome Browser - renders jagged
Microsoft Edge - renders jagged
Firefox - renders smoothly
Pale Moon - renders smoothly
Vivaldi - renders smoothly

Any thoughts regarding causes or solutions will be appreciated.
An example of the issue can be seen at this url: https://timespreader.com (logo at top-left of landing page)
Thanks,
DB

An interesting addendum:

On the same Windows 11 machine mentioned previously;
In a Chrome browser running in the Windows Subsystem for Linux
(instead of the native Windows version), the rendering is smooth.
This seems to indicate the problem is a combination of Browser / OS interaction.
With so many possible combinations, this seems like a hard thing to get a grip on.

Strangeness;
After a few hours, I ran the same tests again.
Somehow the rendering was correct in all the previously mentioned test cases.
It seems strange that this resolved on its own without any intervention on my part.
I had done the usual cache and data clearing in the browsers prior to all these tests.
Can a browser adapt and correct font rendering where it had previously failed without user intervention?
(i.e. nothing was changed or published to the site in the intervening hours)

The software does not have any control over the quality of font rendering. This functionality is implemented in the browser.
It may be related to graphics drivers of your computer.

Thanks Pablo,
I fully agree that this is a client-side browser rendering issue.
As best I can tell, turning on the "Clear Type" feature in the
Windows OS may have been what cleaned up the rendering for me.
Seems like Microsoft should have that enabled by default.
It's interesting that several browsers seemingly didn't require it for proper rendering.