Search Results for 'other ads'

Hey!
I’ll post updated version once I finish the tweak of doom! Have been messing with the new TD Composer beta, so got sidetracked, as I wanted to leave VC behind entirely from “now” onward.

I will actually update and add the #comments on what couple of the things actually do. And I’ll include my AMP footer injection code, too!

Actually the trick with the stupid render blocking thing is three step

a) generate ‘critical CSS’ for your post page; insert this into the header.php right before </head>

b) in functions.php – “de-enqueue” the main style.css from being generated and placed in the head.

c) put link to the main style.css file in the footer.php file.

d) if you don’t want to use functions.php to move the other .js stuff; use the “Scripts to Footer” WP plugin.

THAT is the super secret way we do it for my SEO service here (not a sales pitch). What this does is load the important CSS “above the fold” inline, then page loads on mobile (and I have 98 MPS score to prove it; the last gotcha is the CSS for stupid ‘tap targets’ — ugh) without waiting for anything, then main CSS loaded at end.

This simply works. If you have weirdo plugins injecting css and js in the head, you’ll have to de-enqueue them and move to footer.php manually. But the speed rating improvement is insane as there is literally *no* “render blocking” of any kind for Google on mobile or desktop. Period.

I was writing an ebook on all of this but personal life intruded so that didn’t happen.

• This reply was modified 9 years by simchris.

You guys have the best customer service. Thank you for everything!

Are there other threads or information on how to turn certain things back to Newspaper 4?

Sorry.
We ‘hacked’ the plugin a couple of years back (4 years?) when it was very simple and there was no pro version, as at the time it didn’t work well with https or couple of other things, so we “modified” the code. Since it still works with latest WP, and PHP, we’ve just left it as is. Might have to revisit when we start mucking with PHP7, but have not gotten to that YET.

Initially very simple plugin to create ad groups, a “weight” for each ad, and then rotate those ads, randomly in a widget. That was it. Still, we’ve been recommending it on these forums for 3 years now (has it been THAT long since TagDiv launched? Yikes!).

I think I used “hacked” in the wrong sense here. Should have said “modified.”

We license everything up the wazoo over here as a legal business/company in California, USA.

No “warez” here !

((I don’t work here; we just run “most” of our sites on TagDiv themes.))

• This reply was modified 9 years by simchris.

To anyone considering this plugin; it works very well and we’ve been using it for years, although in a slightly hacked version. 50,000 installs and counting on the repo.

The trick is to use to rotate ads randomly on view which is default behavior and NOT try to set funky schedules to have ads rotate every xx minutes, which is wrong and will overload system and violate most ad networks.

if you READ THE FRIENDLY MANUAL for the plugin; it’s designed to ROTATE ads; meaning each time a page is loaded, a different ad is served. This violates no ad terms; so you can serve an AdSense ad one time, then house ad the next time, in same ad spot, very simply.

Put another way, knowing the terms of use for any ad service like AdSense is important if using that, whereas loading your own ads off your own site you can do whatever you want.

AdRotate does NOT work like an animated GIF ad server.

Traditionally it has been used to “randomly” load ads from a set ad group which you can define, and you can put any ad group into any widget or ad spot you wish.

Only you can be responsible for knowing the “rules” for any ad network to which you participate and act accordingly. An ad server plugin is only a tool, it’s not making choice for you.

And reading the instructions properly, helps too.

Share and enjoy 🙂

@Cat:

I updated my site’s FTP to the new Newspaper theme and, once again, I have an error and NO FRONT/HOME PAGE on my site. (VERY BAD!!) http://www.theautoreporter.com

Theme config
Theme name i Newspaper
Theme version i 7.3
Theme database version i 7.3
Theme aurora version i 1.1
Theme Mobile Newspaper mobile version
php.ini configuration
Server software i Apache
PHP Version i 5.6.24
post_max_size i 65M – You cannot upload images, themes and plugins that have a size bigger than this value. To see how you can change this please check our guide here.
max_execution_time 30 – the execution time should be bigger than 60 if you plan to use the demos. To see how you can change this please check our guide here.
max_input_vars 1000 – the max_input_vars should be bigger than 2000, otherwise it can cause incomplete saves in the menu panel in WordPress. To see how you can change this please check our guide here.
SUHOSIN installed false
WordPress and plugins
WP Home URL i http://www.theautoreporter.com
WP Site URL i http://www.theautoreporter.com
WP version i 4.6
WP multisite enabled i No
WP Language i en_US
WP Memory Limit 40 MB/request – We recommend setting memory to at least 64MB. The theme is well tested with a 40MB/request limit, but if you are using multiple plugins that may not be enough. See: Increasing memory allocated to PHP. You can also check our guide here.
WP_DEBUG False
Caching plugin WP super cache – for best performance please check the plugin configuration guide here.

Mobile devices need smaller footprint page loads for better user experience and SEO, etc.

Complex page => desktop

Simpler page, less bandwidth, smaller footprint => mobile

This is why Google and others have come with alternate solutions like AMP, etc.

Mobile speed *is* now a ranking factor for mobile with majority of web traffic NOW on mobile devices.

So, the idea is NOT ridiculous, but clever way of serving two version of site when “responsive” alone is not enough for some people. And surprise, you can turn it off if you RTFM.

Welcome to webdev, always a learning experience.

System information:
Theme config
Theme name i Newspaper
Theme version i 6.2
Theme database version i 6.2
php.ini configuration
Server software i Apache
PHP Version i 5.6.24
post_max_size i 65M – You cannot upload images, themes and plugins that have a size bigger than this value.
max_execution_time 30 – the execution time should be bigger than 60 if you plan to use the demos
max_input_vars 1000 – the max_input_vars should be bigger than 2000, otherwise it can cause incomplete saves in the menu panel in WordPress
SUHOSIN Installed False
WordPress and plugins
WP Home URL i http://www.theautoreporter.com
WP Site URL i http://www.theautoreporter.com
WP version i 4.6
WP multisite enabled i No
WP Language i en_US
WP Memory Limit 40 MB/request – We recommend setting memory to at least 64MB. The theme is well tested with a 40MB/request limit, but if you are using multiple plugins that may not be enough. See: Increasing memory allocated to PHP
WP_DEBUG False
Caching plugin WP super cache

the reply I posted was from Adsense, they don’t like the code your adsense friendly web theme produces. I bought the theme as it was easy, now I have to learn and ad plug ins. Seems that is miss selling.
I am trying to flag a potential problem. Adsense want to see their variable auto sizing codes, your adsense theme apparently destroys them, and apparently could have been coded differently.

Is there another solution.

Adsense are taking a special look at my adverts now, manually as their auto system throws it out.

Just saying…… just trying to make stuff work. So you can tell me not to put fixed sizes in when they have told me to do that. So, does this theme hate fixed sizes, is that another problem…..

Hi, sorry if my reply sounded mean 🙂

Critical CSS is the “needed CSS” to render the above the fold content. Which might only be 20% of the CSS loaded for entire page, but when loaded inline with every page the page itself is a little bigger, but the browser doesn’t need to wait for ANY of the css and js files. This is the only way I’ve found to fully eliminate the “render blocking” message from Pagespeed Insights.

While the SpeedBooster plugin does pretty good job of moving stuff to footer (and I presume you know how to look at your page source to see if that actually happened, and WHAT is being loaded in the header), as I stated in many cases with WP, you cannot just move everything to the footer as then nothing actually loads until you get there.

TagDiv are doing a “sort of” version of this by front loading some of the CSS, and then moving the stuff to footer; but if you still get the message then it means this “scheme” didn’t quite work, and not really their fault — it will NOT work for everyone; even if they can do it with some (ahem, not all) of their demos.

Go test their demo post for example, see what happens 😉

So, the trick is to use a custom css “critical css generator” that scans your post and then figure out WHAT needs to load first “critical” in the sense it’s needed to load the page BEFORE all the css/js crap in the footer.

For this example “critical” would be defined as :

critical
· adj.
having a decisive importance in the success or failure of something.

So … TagDiv might want to — and will — weigh in as part of their lovely support effort, but you should concentrate on ALL OTHER pagespeed elements, and leave that one thing for last. Or it will drive you insane until you just learn how to get the “critical CSS’ added to the header.php file right above the body tag. Seriously. Been there. 🙂