GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This is not Slackware specific, not even a Linux specific. I've been thinking about a plugin which limits page loading time. The plugin does not exist, I am just considering the idea. Let's say it stops loading 5 or 10 seconds after completing a HTTP response. What is loaded should be displayed, the rest is gone. Similar to manually hitting "work offline" button on browsers which support it. However,
browser might become so busy loading the page that user has to wait until "work offline" kicks in.
Obviously, sites that load a lot of crap (advertisements) first will appear to be meaningless. However, user might have reasons to avoid such sites. Sites on slow links would be affected, but some may want to avoid them either.
Finally, plugin should have whitelisting capability.Basically, it is new form of ad blocking software.
If such a plugin existed, I would certainly not use it, as there are too many reasons for a page not to be loaded in a given amount of time.
If I really feel the need to access a page and it takes a too long time to load, Id' rather wait and if possible act to make it load faster (recently I changed the DNS in /etc/resolv.conf to use public ones, but that's just an example).
If there's nothing I can do but wait and I don't want to, I'd just interrupt the process clicking on the x next to the address bar, or close the tab or the web browser and try later.
Last edited by Didier Spaier; 01-25-2018 at 07:58 AM.
Note that stop button does not interrupt the page loading. More often than not. I sometimes wonder what is it for, anyway. Some pages are so full of crap that browser becomes non responsive, so I have to kill it with xkill.
Have you looked at what the page is loading? Most of the load time issues are requests to 3rd party sites for ads, scripts, etc. I would limit what your browser is loading first.
Browser plugins activate only after the page has fully loaded.
????
So you're telling me that I use NoScript, AdBlock and HTTPS Everywhere for no reason? If browser plugins activate only after a page is fully loaded these plugins would be completely useless.
If the page is loading too much 3rd party crap, perhaps I should stop visiting it.
I thin the effect might be achieved by using locally installed Squid cache engine, too. Once I was full time employed Squid admin, but it was long ago. I bet there are a lot of new features.
Note that stop button does not interrupt the page loading. More often than not.
strange, it works for me on all mozilla based browsers.
<Escape> does the same.
maybe what you experience is not the loading itself, but a javascript that is already loaded eating your resources?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.