asigno

I've just received confirmation from an Apple Webkit engineer it's coming to Safari too.

@h2ojunkie It'll actually be about 85% of web traffic come Jan.
https://gs.statcounter.com/browser-market-share/desktop/worldwide

Does anyone know if this is being used with 4.5?

I've brought this up internally for further consideration in a future release now that support is starting to gain more traction. 🙂

@bfarber No it's live now if you've downloaded the latest v76.
 
The BBC have just done a quick case study on it as below:
 

Chrome's native lazy loading is now live on Chrome 76
https://web.dev/native-lazy-loading
 
Please can we have this enabled as default with a fall back for other browsers.
 

Chrome and FF both support it.  MS edge chromium engine will release on Jan 15th'ish. So about 60% of all web traffic is covered with loading=lazy right there (until safari adapts it). 
In addition, loading=lazy works intelligently in combination with traditional lazy loading scripts (they built it into the browser engine).  You actually get even better performance when using BOTH.   There's zero downside to including that attribute on all images and iframes in addition to the javascript version. You get the best of both worlds. 

PM Sent

I use the mediation app in Ezoic which allows me to still run my own adsense through the Ezoic bid system. However I've only make a few dollars though adsense as it is nearly always outbid by the premium ads through Google's display network through Ezoic.
You can manually place the Ezoic placeholders so you have full control over their positioning.
You make considerably more revenue through Ezoic, however it considerably slows your site down too. If you have a static site (non IPB) you can use their caching and site speed functionality where it wouldn't be an issue. 

I use the mediation app in Ezoic which allows me to still run my own adsense through the Ezoic bid system. However I've only make a few dollars though adsense as it is nearly always outbid by the premium ads through Google's display network through Ezoic.
You can manually place the Ezoic placeholders so you have full control over their positioning.
You make considerably more revenue through Ezoic, however it considerably slows your site down too. If you have a static site (non IPB) you can use their caching and site speed functionality where it wouldn't be an issue. 

Chrome's native lazy loading is now live on Chrome 76
https://web.dev/native-lazy-loading
 
Please can we have this enabled as default with a fall back for other browsers.
 

Chrome's native lazy loading is now live on Chrome 76
https://web.dev/native-lazy-loading
 
Please can we have this enabled as default with a fall back for other browsers.
 

Another reason for an IPB app 😎

Another reason for an IPB app 😎

Another reason for an IPB app 😎

Another reason for an IPB app 😎

Another reason for an IPB app 😎

Another reason for an IPB app 😎

Will lazy load be available for Supergrid templates?

Hahaha sorry, didn't even see the date there. 🤣

Hahaha sorry, didn't even see the date there. 🤣

I have written a lot about this subject, incl. and i have a design to use the critical CSS to remove the Render-blocking CSS. Yes, it works, but it takes a lot of time to analyze and develop a good critical CSS.
For a few days I've been exploring another idea that came to my mind.
Code in IncludeCSS works perfectly and this code tells the browser - download all those CSS and use them to represent the site. But this code does not tell the browser when and how to use them.
The idea I'm using right now is - I created a new template that I put before closing the tag head. In my experiment, this template looks like this:
{template="preload_css" app="core" location="global" group="analysis" params=""} In this template I placed this code
{{foreach array_unique( \IPS\Output::i()->cssFiles, SORT_STRING ) as $file}} <link rel='preload' href='{expression="\IPS\Http\Url::external( $file )->setQueryString( 'v', \IPS\CACHEBUST_KEY )"}' as="style"> {{endforeach}} {{$customCss = \IPS\Theme::i()->css( 'custom.css', 'core', 'front' );}} {{foreach $customCss as $css}} <link rel='preload' href='{expression="\IPS\Http\Url::external( $css )->setQueryString( 'v', \IPS\CACHEBUST_KEY )"}' as="style"> {{endforeach}} Now, besides a browser command to download all CSS, I send the browser a command - use these CSS as a matter of priority.
And the result of over 100 my tests - no render-blocking CSS ...
There are no side effects or any other bad impact.
I've installed it on my live site and it works perfectly.
If a development team wishes, let him test it and apply it in later releases. This will speed up all sites using this really good platform.

I used Sendgrid based on the recommendation of the IPS staff and because support is built into IPS. Unfortunately the price of Sendgrid is 10x that of Amazon's SES simple email service. 
I just switched over to Amazon SES and am stuck using the SMTP route rather than via the API because there isn't native support via IPS like there is for Sendgrid. 
I'd like to ask for or vote for IPS adding support for Amazon SES, just like it supports Sendgrid.

Hi @Duken I'd recommend posting on the Google forum https://productforums.google.com/forum/#!topic/adsense/eftgSJTTBg0;context-place=topicsearchin/adsense/auto%2420ads%2420appearing%2420over%2420content
The last response was as below:
 

I'm having the same issue, have posted on the Adsense forum hoping to get someone from Google to comment. 
Would be great if you could comment there too: https://productforums.google.com/forum/#!topic/adsense/eftgSJTTBg0;context-place=topicsearchin/adsense/auto$20ads$20appearing$20over$20content