Prefetching Puns

Anyone know if prefetching affects lighthouse scores? I can't see how it wouldn't as if you are prefetching, doesn't it "add the next pages load" to the current frame, so to speak?

I'm just switching from CRA to Nextjs, I would be happy to be corrected if I'm wrong and thanks in advance for reading !

from https://nextjs.org/learn/basics/navigate-between-pages/client-side :

> Next.js does code splitting automatically, so each page only loads what’s necessary for that page. That means when the homepage is rendered, the code for other pages is not served initially. This ensures that the homepage loads quickly even if you have hundreds of pages.

Let's imagine I have two pages, /home and /admin, that'd mean I could import two big libraries like Moment and MaterialUI in /admin and still not have /home first load time ( or maybe time to become interactive to be more precise ) affected by these 2 libraries as long as I don't directly import them in /home ?

from the same link : > Furthermore, in a production build of Next.js, whenever Link components appear in the browser’s viewport, Next.js automatically prefetches the code for the linked page in the background

So if I put a Link that points to /admin at the top of my /home page are these operations followed in this order when going to /home ? :

• Server send the HTML and it's rendered by the browser
• the browser download the needed JS for /home and execute React, /home is now interactive
• Since Link pointing to /admin is in the browser's viewport It'll download the js for /admin, If I then clikc this Link it'll be Client side rendered and not server side rendered ?

I have a project where use react-router v3 only for one reason. The reason is the need of server side rendering with data prefetching and the most convenient way to do this is to keep centralized route config in an object or array and loop over the matching elements to fetch the data from the API on the server side. The data later is going to be passed to the client with the response HTML and stored in variable of JSON format string.

Also application uses code splitting, however with the use of babel-plugin-transform-ensure-ignore on sever side I can directly fetch the components instead of lazy loading and the native import method will be used only on client side.

Nevertheless, above-mentioned structure isn't working with react-router v5, as it's little bit difficult, since I can't use @loadable/components, as react-router official documentation suggests. Per my observation @loadable/components just generates the HTML on the server side instead of giving me the components in which I implement the fetch method responsible for server side logic.

Therefore, I would like to ask you the good structure for webpack + react-router v5 + ssr + data prefetch + redux + code splitting

I see it's quite complicated and no universal solution, however I may be wrong.

Any direction or suggestion is appreciated.

It really doesn't help with my slow/average connection, in fact it makes loading things I want to see slower because it's trying to download another video that I'm not interested in watching

Any way to prefetch a model property? I got a model structure as follows for history/versioning reasons and have super long SQL runtimes when trying to query like 200 instances of my main model (License). Is there any way to prefetch a property? Or any other good way for me to do this? I already tried prefetching just all Counters for every License, but doesn't really improve performance (aside from SQLite eventually saying there's too many arguments).

class License(models.Model):
    name = models.CharField(max_length=16)

    @property
    def counter(self):
        self.counters.filter(primary=True).get()


class Counter(models.Model):
    license = models.ForeignKey(License, on_delete=models.CASCADE)
    primary = models.BooleanField(default=False)
    
    class Meta:
        constraints = [
			UniqueConstraint(fields=['license'], condition=Q(primary=True), name='unique_primary_counter')
		]

I tried to do a write-up on how assembly works and what prefetching is in the README. The code is pretty short and beginner friendly (or so I think).

The project is available on Github: https://github.com/alin1popa/prefetch-cpu-simulator

Should be Python2/Python3 compatible. Drop me suggestions (or pull requests) if any 🙃

Hey, I'm new to svelte and I'm trying to get prefetching on hover working. I want to avoid using sapper so I'm playing around with routify and I kind of have it working. I have the following:

<header><a on:mouseover={() => prefetch('/home')} href="/home">home</a></header>

But the issue is that on hover it pulls everything (root.js, home.js, css, etc.) and on click it pulls home.js again. Is there some way to get routify to only pull the home.svelte page on hover and just mount it on click? Or is there a way to do it with a different router?

https://extensa.tech/blog/prefetching/

Continuation of previous post:

https://www.reddit.com/r/cpp/comments/e6fuu0/blogposts_about_various_methods_of_packing/

Is it possible to configure the app so that the prefetching happens in a specific order?

In both the uBlock origin GUI and the wiki, we're told that leaving prefetching enabled somehow gives the browser the ability to bypass the filters and visit blocked domains. (That's unintuitive and sounds like a bug to me.)

To test this I disabled the setting in uBlock and made sure that all available prefetch settings were enabled in about:config. I then browsed around while watching all the connects made with Wireshark. During that time, I didn't see any connections to blocked domains. That's on Linux with Firefox 55.0.3.

Is it still necessary to disable link prefetching?

I need to import massive amount of catalog products from csv_files into a database. Knowing that :

• those products have many relations to other schema (tags, categories, ...)
• The incoming data quality is very poor
• Most of the relations of a product already exist (tags, categories)

How would you process one line into your database ?

What I did for now :

I considered going with one big Ecto.Changeset with many put_assoc/4 calls. BUT as most of the relations already exist I would have had a lot of invalid changesets. Pre-fetching all this data didn't look like a good idea at that time (I was worried about performances).

Instead I went full Ecto.Multi, handling multiple changesets individually with the on_conflict: :nothing, return: true properties to return existing data. A final step of the transaction (the product changeset) creates and links the product with all the inserted-or-fetched relations.

It resulted in a working code but with a bit too much overhead to my taste. Should I have prefetched everything before-hand ? How you guys would have done it ?

I get why someone would want to disable this for privacy concerns, but won't it slow down browsing?

How come I have to manually select HD for every picture I look at (especially a pain with albums) if I don't want to download the HD version of every image on my front-page regardless of whether I want open it or not? I don't have a ton of space on my phone, so I want to download what I want to look at, not everything indiscriminately.

I'm sorry if this comes off kind of rudely, but I couldn't figure out to describe the problem in another way.

Please allow me to look at albums without pressing hd for every single image. Thank you.

I have a project where use react-router v3 only for one reason. The reason is the need of server side rendering with data prefetching and the most convenient way to do this is to keep centralized route config in an object or array and loop over the matching elements to fetch the data from the API on the server side. The data later is going to be passed to the client with the response HTML and stored in variable of JSON format string.

Also application uses code splitting, however with the use of babel-plugin-transform-ensure-ignore on sever side I can directly fetch the components instead of lazy loading and the native import method will be used only on client side.

Nevertheless, above-mentioned structure isn't working with react-router v5, as it's little bit difficult, since I can't use @loadable/components, as react-router official documentation suggests. Per my observation @loadable/components just generates the HTML on the server side instead of giving me the components in which I implement the fetch method responsible for server side logic.

Therefore, I would like to ask you the good structure for webpack + react-router v5 + ssr + data prefetch + redux + code splitting

I see it's quite complicated and no universal solution, however I may be wrong.

Any direction or suggestion is appreciated.