1773543 - www.aa.com.tr/tr loads more slowly than Chrome

Status: NEW

(Core :: Performance, defect)

Description

[Asif Youssuff]

​​### Basic information

From https://www.reddit.com/r/firefox/comments/t2o3s6/is_firefox_slow_for_android/hyt1li1/

Steps to Reproduce:

1. Load https://www.aa.com.tr/tr
2. compare to Chrome

Expected Results:

Faster in Firefox, or at least the same as Chrome.

Actual Results:

~18 seconds before the progress bar goes away in Firefox (and the page seems to be loading up until the last second or so) vs. ~5 seconds in Chrome. No other open tabs in either browser.

---

Performance recording (profile)

Profile URL: https://share.firefox.dev/3xDiEVE

System configuration:

OS version: Android 11
GPU model: PowerVR GE8320
Number of cores: Octa-core (4x2.0 GHz Cortex-A53 & 4x1.5 GHz Cortex-A53)
Amount of memory (RAM): 3GB RAM

More information

Please consider attaching the following information after filing this bug, if relevant:

• Screenshot / screen recording
• Anonymized about:memory dump, for issues with memory usage
• Troubleshooting information: Go to about:support, click "Copy text to clipboard", paste it to a file, save it, and attach the file here.

---

Thanks so much for your help.

Comment 1

[Asif Youssuff]

Attachment: about:support

Comment 2

[Olli Pettay [:smaug][[e-mail]]]

The Performance Priority Calculator has determined this bug's performance priority to be P2.

Platforms: Android
Page load impact: Severe
[x] Able to reproduce locally

Not sure about the component yet. I think this is more a scheduling issue, so Core: Performance might be reasonable.

Comment 3

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

We've previously seen issues on aa.com.tr in fenix: see bug 1734490 where fonts take a long time to load.

Comment 4

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

In the provided profile, the network calls take a long time. A next step could be to capture a performance profile from Chrome to see if it also experiences long network calls. In either case, there may be difference in how we schedule which determines how the content appears.

I think I was able to see a difference in loading performance on my desktop machine but from what :smaug said, it seems like the difference isn't as extreme. I also see long network calls on Firefox desktop: https://share.firefox.dev/3NewPVx