Rendering of heavy graphic websites seems slower than Internet Explorer 10

UNCONFIRMED
Unassigned

Status

()

Core
General
UNCONFIRMED
3 years ago
3 years ago

People

(Reporter: Alex Vojacek (TecnoGaming), Unassigned)

Tracking

({perf, testcase})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: rendering, URL)

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.125 Safari/537.36

Steps to reproduce:

This seems more like an optimization than a Bug thing.

I had notice for quite some time now that IE10 is incredible fast and responsive on the rendering level, this  is specially true on heavy graphic websites.

I'm a website designer and I can easily show this problem if I use a lot of border-radius with text-shadow and box-shadow properties in CSS3, this combined with moving sliders will slow down the rendering quite a lot.

This same website rendered in IE10 feels smooth.  Our gaming network website is a simple example of this.

http://games.tecnogaming.com




Actual results:

Invoking the responsive design in this heavy shadow/pictures/sliders website will show quite easily what i'm talking about.  Firefox will slow down the redraw and feel slugish (chrome does it even worse) but IE10 do it incredible smooth.


Expected results:

IE10 do the rendering the right way, either by implementing Hardware Acceleration in a proper way or by using some GPU acceleration where Firefox does not.

Firefox should mimic IE10 behavior in this matter, since websites will get incresingly complex and this will only make matters worse.
(Reporter)

Updated

3 years ago
Component: Untriaged → General
Whiteboard: rendering

Comment 1

3 years ago
Can you post the graphics section of about:support here? HWA depends on your system as well as the Firefox configuration...
Component: General → General
Flags: needinfo?(tecnogaming)
Keywords: perf, testcase
Product: Firefox → Core

Updated

3 years ago
Flags: needinfo?(tecnogaming)
You need to log in before you can comment on or make changes to this bug.