Closed Bug 1448864 Opened 3 years ago Closed 5 months ago

Slow page loading on some URL

Categories

(Firefox for Android Graveyard :: General, defect, P3)

All
Android
defect

Tracking

(fennec?)

RESOLVED INCOMPLETE
Tracking Status
fennec ? ---

People

(Reporter: joss.ru, Unassigned)

Details

(Keywords: perf)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.162 Safari/537.36 OPR/52.0.2871.27 (Edition beta)

Steps to reproduce:

Android 7.0 Huawei P10 Lite

1. Clean install, no any ad-blocks.
2. Open the page: https://www.strategium.ru/forum/topic/86246-europa-universalis-iv-rule-britannia?page=40
3. Return back and open the page again


Actual results:

1st try:
Firefox Nightly: 15 sec for the page loading
Chrome Dev: 12 sec

2nd try:
Firefox Nightly: 11 sec for the page loading
Chrome Dev: 5 sec





Expected results:

The speed should the same.
[triage] Performance is a known issue and we're working on it. Snorp, can you triage this bug appropriately?

Fun game, by the way. :)
tracking-fennec: --- → ?
Flags: needinfo?(snorp)
Flags: needinfo?(snorp)
Keywords: perf
Priority: -- → P3
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Unspecified → Android
Hardware: Unspecified → All
Version: Firefox 61 → Trunk
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.