FireFox upto 90% Faster


Recommended Posts

so,is this a real bad no no for 56k users? cause i done the tweak then read that post  :unsure:

should i go back to default?

586032663[/snapback]

go back? no, theres a huge difference in pages like devianart so it works

Link to comment
Share on other sites

Same here, even with Neowin forums.

So I'm not sure what happen to those people that saying Neowin's forum is actually much slower using this trick.

Link to comment
Share on other sites

Um, way old.

But anyway, person asking for drawback,

about nglayout.initialpaint.delay :

By default, Firefox doesn't try to render a web page for 250 milliseconds while it's waiting for data. If you add the code below to your user.js file, Firefox immediately starts to display the page, even without complete data. The drawback, especially on slower machines, is that the total time to display the page will be longer.

about pipelining :

Pipelining is an experimental feature, designed to improve page-load performance, that is unfortunately not well supported by some web servers and proxies.

Source : http://www.mozilla.org/support/firefox/tips#oth_rendering

I use the pipelining feature, but setting the max requests to anything above 8 is pointless as theres a built in limit of 8. I dont use the nglayout.initialpaint.delay tho because everythings already very fast for me and waiting half a second longer for the page to load properly doesn't bother me.

Link to comment
Share on other sites

Thanks for the tweak info. (Y)

Yeah it wasn't 90% faster but it did noticably increase in speed. And those, with broadband, who think it slowed down, have to revisit the page they were just on. The first time I went to Neowin after the tweak it too excessively longer, actually, to load up. However, the next try it went much faster than normal.

Link to comment
Share on other sites

Thanks for the tweak info. (Y)

Yeah it wasn't 90% faster but it did noticably increase in speed. And those, with broadband, who think it slowed down, have to revisit the page they were just on. The first time I went to Neowin after the tweak it too excessively longer, actually, to load up. However, the next try it went much faster than normal.

586033157[/snapback]

Um, thats probly cause the page was now Cached.

Try it with pipeling on, and without the nglayout.initialpaint.delay tweak because that one can actually make it take longer then non tweaked.

Link to comment
Share on other sites

i had those settings already... and im using Deer Park 1... but i added the last nodelay thing... no difference yet though

Link to comment
Share on other sites

wow thanks

edit: if i set a lower Network.http.pipelining.maxrequests would it be better for 56k? like instead of 30 put 20

586032616[/snapback]

8 is the maximun anyway...

still waiting for someone to point out the downside ;)

586032690[/snapback]

It breaks some older servers and proxies

Link to comment
Share on other sites

I notice a difference. Not that sites load faster, but that you can see the site faster. Which is better for me. Nice to click something and see something instantly. Even if it's not the complete site.

Link to comment
Share on other sites

1. Variations of this tweak have been posted several times before.

2. There is a hard-coded limit of eight requests to a client, thirty is non-beneficial.

3. Everyone's supposed increase in speed is an impression mostly had by disabling render delays.

4. You have absolutely no idea how taxing this is to a web server, pipelining is wasteful of bandwidth.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.