This question could be asked about any browser, but I'm using the latest
KM-Goanna builds.

I'm trying to preview many pages of images stored on different servers.
Some of the images load slowly, and I'm wasting a lot of time.

I know that clearing browser caches (cookies, history, etc.) and disabling
extensions can increase browser speed. I tried that and it didn't seem to
increase the speed of those slow loading images.

Changing browser settings or adding an extension created for images might
be the solution. If the servers are the problem, then tinkering with KM-Goanna
won't help.

The problem is at the server performance. You can't do anything tweaking any browser.

If the server is busy, is busy.

Might also be your ISP peering, but, again, is something that you can't control through a web browser.

Patience is the only solution

You're correct, of course. I asked because all of you that create each new
KM-Goanna build are amazing experts.

The problem is with one particular server. Many of the images I need to preview
are on that slow server.

Does disabling js help?

Quote
Mello
Does disabling js help?

If it is a generic question to the topic, and not a question for clutterless, the answer is no.

Disabling JavaScript would help to lower the CPU load, but nothing else. Yes, for huge images (thousand pixels wide) would help, but not if the server is busy.

Can be just a slow server, or perhaps anything tricky, but without an example page it's hard to tell.
And of course blocking JS helps against lots of probs in general

Reminds me for example of the once popular postimg.org hoster, which took the evil way and since then transformed all seemingly harmless direct jpg-links to full iframe pages, one for every single pic. And the worst: even if javascript and all other stuff was blocked!
The solution to prevent such evil tricks was this setting, but IMO that's default long since anyway:
network.http.accept.default = */*

Another thought, considering there are meanwhile tons of different ways to include images in webpages:
It can very well depend on the useragent if the server sends tiny pics or huge ones. Nowadays it has become normal to prepare in the source code a variety of different sizes for several different client setups. Have recently given up trying to keep overview...
A look inside the source code of the page may be revealing.
Experimenting with useragents (IE7?) could matter (or not), with a smaller window size (or not), with blocking ALL stylesheets or subdocuments etc., for example
permissions.default.stylesheet = 2
Whatever, things can get better, or worse, it depends mostly on the website author.
And of course - if really the server is just slow, there's zero solution.

Or perhaps the page has prefetch/preload stuff in the meta-tags in the header? Or the browser is set to try preloading anything globally? Have no experience how much such prefs really matter (or not), for this specific case, if working in K-Meleon at all or which version, and if Mozilla prefs are affecting the Goanna engine too, or if yes if KM/Goanna may have different default values etc.
Over time have just read somewhere and collected those prefs, just in case for future browser versions, since I have a slow network:

network.prefetch-next = false
network.dns.disablePrefetch = true
network.dns.disablePrefetchFromHTTPS = true
network.predictor.enabled=false: tracking+preload in FF32+ (KM76?), netpredictions.sqlite, very SLOW
network.seer.enabled = same as above, just older pref name in FF21-31 (KM74-75?)
network.stricttransportsecurity.preloadlist = false

But again, things can get faster, but also slower with such preload/prefetch settings. Depending on network speed and on hardware power (if those prefs are working at all). Just thinking that a little test in case of probs can't harm.

Quote
JohnHell

Quote
Mello
Does disabling js help?

If it is a generic question to the topic, and not a question for clutterless, the answer is no.

Disabling JavaScript would help to lower the CPU load, but nothing else. Yes, for huge images (thousand pixels wide) would help, but not if the server is busy.

Thanks - it was addressed to clutterless.

Quote
siria
(...) Over time have just read somewhere and collected those prefs, just in case for future browser versions, since I have a slow network:
network.prefetch-next = false
network.dns.disablePrefetch = true
network.dns.disablePrefetchFromHTTPS = true
network.predictor.enabled=false: tracking+preload in FF32+ (KM76?), netpredictions.sqlite, very SLOW
network.seer.enabled = same as above, just older pref name in FF21-31 (KM74-75?)
network.stricttransportsecurity.preloadlist = false (...)

I hope someday all useful prefs will be collected. Above ones work fine.

Quote
clutterless
I'm trying to preview many pages of images stored on different servers.

siria had another partial expanation, "if the server sends tiny pics or huge ones." A lot of loading speed is the size of the image(s). Example: A 100 terabyte image size will take an aweful long time to show.

Might be able to use Google Images of the domain if it's publicly searched by Google.

Since you guys dig up again that older topic, here's yet another possible image-size factor:
window width!
If speed matters most and you don't mind getting SMALLER pics, try if it helps to pull your window smaller before loading the page. This probably works on many websites, but not all.
CATCH:
when it's finished loading and you want to pull the page WIDER now, it probably adjusts instantly and now starts loading the BIG images again...
(but injecting a little userscript to modify the sourcecode probably prevents this)

Odd as this sounds, but nowadays many sites send different image sizes depending on the user's current window width, to optimize looks for small mobile and large desktop browsers. There are different methods for this, some require javascript, but the most simple method works by CSS alone.

DESCRIPTION:
https://developer.mozilla.org/en-US/docs/Learn/HTML/Multimedia_and_embedding/Responsive_images

example:
<img srcset="pic-320w.jpg, pic-480w.jpg 1.5x, pic-640w.jpg 2x" src="pic-640w.jpg">
or
<img srcset="pic-480w.jpg 480w, pic-800w.jpg 800w" sizes="(max-width: 600px) 480p, 800px" src="pic-800w.jpg">

"srcset" works as pure CSS since KM76/FF38/PM27.
The "src" pic was intended as fallback for older browsers.
But when the page just finished loading the html code, before CSS is read too, browsers still start loading "src", so today this is often just a 1px placeholder to speed up loading in modern browsers. Catch: older browsers get no image at all (but luckily a workaround with userscripts often helps, partly at least)

Another method: <source srcset...>
https://www.html5rocks.com/en/tutorials/responsive/picture-element/



Edited 2 time(s). Last edit at 06/30/2020 02:12AM by siria.