Accessibility First DevRel. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
It is interesting as I have been working on a similar approach but from a different angle.
I am working on “self optimising websites”, where you deploy a page and a small JS script works out what is “above the fold” at a given screen size and communicates that back to the server so we can build variations of the page CSS and precache images that are the right size for a given screen (an over simplification but you hopefully get the idea)
The only difference in principle is I always have a “baseline” experience pre-cached. Then the first visitor at a screen size gets served something quickly and I can process the improved page in the background for the next visitor.
I am not sure if you can take that principle and apply it to this concept but just an idea. It depends how long that rendering process takes I suppose as to whether it matters.
Also thinking of core web vitals, could this potentially damage your score? I need to give that more thought though, just an initial half-baked idea that popped into my head.
P.s. - maybe a different acronym, “DPR” is “Display Port Resolution” to me and widely written about, your idea could get “lost in the noise” because of that (especially as DPR is talked about a lot in performance with regards to image resizing).
Anyway it sounds like I am being negative to what seems like a great concept for larger sites, I look forward to seeing where you take this idea! ❤️🦄
It is interesting as I have been working on a similar approach but from a different angle.
I am working on “self optimising websites”, where you deploy a page and a small JS script works out what is “above the fold” at a given screen size and communicates that back to the server so we can build variations of the page CSS and precache images that are the right size for a given screen (an over simplification but you hopefully get the idea)
The only difference in principle is I always have a “baseline” experience pre-cached. Then the first visitor at a screen size gets served something quickly and I can process the improved page in the background for the next visitor.
I am not sure if you can take that principle and apply it to this concept but just an idea. It depends how long that rendering process takes I suppose as to whether it matters.
Also thinking of core web vitals, could this potentially damage your score? I need to give that more thought though, just an initial half-baked idea that popped into my head.
P.s. - maybe a different acronym, “DPR” is “Display Port Resolution” to me and widely written about, your idea could get “lost in the noise” because of that (especially as DPR is talked about a lot in performance with regards to image resizing).
Anyway it sounds like I am being negative to what seems like a great concept for larger sites, I look forward to seeing where you take this idea! ❤️🦄
yeah i hope they find a less wordy name as well