1875307 - The "View in map" image place holder loads slower compared to Chrome at expedia.com

Status: NEW

(Core :: Performance, defect, P3)

Description

[Raul Bucata]

Attachment: 20240118_173810.mp4

Environment:
Operating System: Windows 10 PRO x64
Firefox version: Firefox Nightly 123.0a1 (2024-01-18)

Preconditions:
Clean profile

Steps to reproduce:

1. Navigate to : https://www.expedia.com/Hotel-Search?adults=2&d1=2024-01-21&d2=2024-01-25&destination=Paris%20%28and%20vicinity%29%2C%20France&endDate=2024-01-25&flexibility=0_DAY&latLong=48.853564%2C2.348095&regionId=179898&rooms=1&semdtl=&sort=PRICE_HIGH_TO_LOW&startDate=2024-01-21&theme=&useRewards=false&userIntent=
2. Observe the "View in map" image placeholder.

Expected Behavior:
The map image preview loads as expected

Actual Behavior:
The map image preview loads slower compared to Chrome

Notes:

• Reproducible regardless of the status of ETP
• Reproducible on the latest build of Firefox Nightly and Release
• Works as expected using Chrome
• Screenshot is attached
• Issue found during WebCompat team [Top100] websites testing
• "Static map" image text is shown before the image loads

Comment 1

[Calin Tanase (OOO until 22nd of Nov)]

Verified this issue and it's still reproducible on Firefox versions 123 and 125.

Environment:
Operating system: Windows 10
Browsers: Firefox Nightly 125.0a1 (2024-02-26) / Firefox Release 123 / Chrome 122.0.6261.70

Note: Not reproducible on Chrome

Comment 2

[Bas Schouten (:bas.schouten)]

Here's a profile: https://share.firefox.dev/3yPXs1y

Note that we seem to be spending most of our time waiting for the socket thread in getting the image. Do you have ideas here Andrew?

Comment 3

[Bas Schouten (:bas.schouten)]

The Performance Impact Calculator has determined this bug's performance impact to be medium. If you'd like to request re-triage, you can reset the Performance Impact flag to "?" or needinfo the triage sheriff.

Platforms: Windows
Page load impact: Some
[x] Able to reproduce locally

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

This bug was moved into the Performance component.

:rbucata, could you make sure the following information is on this bug?

• For slowness or high CPU usage, capture a profile with http://profiler.firefox.com/, upload it and share the link here.
• For memory usage issues, capture a memory dump from about:memory and attach it to this bug.
• Troubleshooting information: Go to about:support, click "Copy raw data to clipboard", paste it into a file, save it, and attach the file here.

If the requested information is already in the bug, please confirm it is recent.

Thank you.

Comment 5

[Raul Bucata]

Attachment: memory-report.json.gz expedia

Comment 6

[Raul Bucata]

Attachment: memory report expedia.txt

Comment 7

[Raul Bucata]

• Performance profile: https://share.firefox.dev/4cbrRpB
• Memory dump: see attachment
• Troubleshooting information: see attachment

Comment 8

[Andrew Creskey [:acreskey]]

(In reply to Bas Schouten (:bas.schouten) from comment #2)

Here's a profile: https://share.firefox.dev/3yPXs1y

Note that we seem to be spending most of our time waiting for the socket thread in getting the image. Do you have ideas here Andrew?

I've landed a few new markers that report from the socket thread; they may help here.
Can you capture a new profile with the socket thread included? The Network setting includes it.