Search Results for 'other ads'

Hi,

The banners are looking good, when one of the banners or both are from google ads, but when they are not from google, then is showing the problem with the them. They are not in line, one is upper than the other.

About the code I put him in custom css but I don’t see any change. Everything is the same.

Thanks in advance

It worked just perfect.. Thanks Lucian. However, header ad slot doesn’t appear just below navigation. How can I put ad adsense or any other ad just below navigation on all pages?

Thanks again… 🙂

Hi,

Thx, then I need to change post by post.
I have another question, is lightbox doesn’t support Swipe Gesture yet?
It seems need to click next / prev icon to next image.

And I have another problem, it seems a bug.
The inline ads will appear on the gallery.
http://www.screencast.com/t/rnW3lh4rqVT

I was able to get this figured out so I will place what I figured out here as a reference in case others are also using double click.

First, in your header file you need to use the following code:

<script type=’text/javascript’ src=’//partner.googleadservices.com/gampad/google_service.js’>
</script>
<script type=’text/javascript’>
GS_googleAddAdSenseService(“ca-pub-your google ad sense pubid”);
GS_googleEnableAllServices();
</script>
<script type=’text/javascript’>
GA_googleAddSlot(“ca-pub-your google ad sense pubid”, “DFP inventory name spot1 here”);
GA_googleAddSlot(“ca-pub-your google ad sense pubid”, “DFP inventory name spot2 here”);
GA_googleAddSlot(“ca-pub-your google ad sense pubid”, “DFP inventory name spot3 here”);
GA_googleAddSlot(“ca-pub-your google ad sense pubid”, “rightsidebar_300x250″);

</script>
<script type=’text/javascript’>
GA_googleFetchAds();
</script>

Then in the theme file under the ads setting you place the following code in place:

<div style=”width:300px;height:250px;margin-top:10px;margin-left:auto;margin-right:auto”>
<script type=”text/javascript”>
GA_googleFillSlot(“rightsidebar_300x250”);
</script>
</div>

This works for me.

If you’re having trouble optimizing via plugin, I would likely contact your hosting provider and optimize your dbase from phpmyadmin or similar outside of wordpress (e.g., command line, or from server side).

But yes… on a 190MB dbase, WP-Optimize clears out on average about 27.5MB of crap, depending on when you do an optimization.

I think the pagespeed insights reference to browswer caching is having
1) expires headers from the server (or via htaccess on Apache, or config file on nginx), which specify a time to live, such as “cache fonts for one week, don’t reload them every time a page loads” … that is the purpose of “browser caching” — same with CSS, images like a logo, javascript, etc. — my settings are in the sticky for pagespeed.

2) remember to have gzip/deflate running on server side, you don’t need plugin for that as the server can compress everything on request

I’m not currently using W3 cache, and frankly I’d leave that off until you get everything else sorted as otherwise you end up caching incomplete pages from the other errors or overloads. Once EVERYTHING else is solid, THEN you would turn on the cache as the LAST thing in the chain.

Hope that helped a little (been there!). 🙂

• This reply was modified 12 years by simchris.

Make sure the server is running deflate/gzip properly, and you have the proper expires headers set, and server side normal caching if so provided, …. compression and expires headers are good for at least 20 points.

Just for a reference point, one of my pages on the test site, with caching plugin turned off, and the disqus, adsense stuff running (3 ad spots), Gravatar, and one YouTube video.
http://ga-ga.com/1763/book-review-anti-americans-star-sons-wichita/

is 90 desktop / 79 mobile

I need to swap out Gravatar for local author image and should shave off 708bytes from the featured image upload (has “red” in it, so didn’t compress as much).

With the gravatar fixed, and if I ignore the “errors” from Disqus and AdSense, it’s totally in a doable range for us.

I think it works out to be 93/83 without the “errors” on there.

Not bad since NOT running any caching plugin, not using CDN, and not using a minification plugin other than mod_pagespeed optimizing the pages on the fly.

• This reply was modified 12 years by simchris.

thanks Lucian

however that isn’t correct – it not custom ad 3 its ARTICLE TOP AD and using the code you gave me adds another ad 3 block above the header text with the words in the loop-single.php shown under.

thanks

Andrew

Here’s a screenshot (from another theme … sorry) that shows more or less what I’d like to see with standard posts when using Module 1 – headline, full-size featured image, excerpt, “Read more” button. If there’s way to accomplish this, that would be super!

Hi Lucian,

Thank you for your quick reply. I have made the changes, the ad appears now after the Disqus plugin but I have another question. How do I remove the article bottom ad now? If I remove the Adsense code from the article bottom probably both ads will disappear.

Please advise,

If the <p> tag has any “style” content, the inline adsense ad doesn not show at all.

Content of many posts are given justified style on my site. Here is the example:
http://www.igeeksblog.com/put-apps-on-the-notification-center-using-weespaces-cydia-tweak/

Is there any way to post Article Top ad slot after number of paragraphs instead of exactly below title?

One more thing, I experience drastic down in CTR and CPC in adsense since I have changed theme to Newspaper. Is there any tip to improve CTR?

Another important thing, Can I block specific third party scripts to load from responsive mobile site?

livingsmarttv,

Yes it is possible to not crop and only scale images. It gets a bit tricky with this theme though because it is set to crop every image(except the featured.)

In the functions.php file, you will find somewhere around line 320:

//featured image
$td_crop_features_image = td_util::get_option('tds_' . 'crop_features_image');
if ($td_crop_features_image == '') {
    add_image_size('featured-image', 700, 0, true);
} else {
    add_image_size('featured-image', 700, 357, true);
}
//the small thumbnails
set_post_thumbnail_size(          100, 65, true );
add_image_size('art-thumb',       100, 65, true);
//small height, 1 col wide
add_image_size('art-wide',        326, 159, true);
//medium height 1 col wide
add_image_size('art-big-1col',    326, 235, true);
//the slides
add_image_size('art-slide-small', 326, 406, true);
add_image_size('art-slide-med',   700, 357, true);
add_image_size('art-slide-big',  1074, 483, true);
//big slider - big image
add_image_size('art-slidebig-main',  745, 483, true);
//the gallery
add_image_size('art-gal',         210, 210, true);

Notice that TagDiv has built in the ability to turn cropping on or off on the featured image based on a setting in the theme panel, but you are asking for all of them.

add_image_size('featured-image', 700, 0, true);

In the line above, it is the ‘0’ argument that tells wordpress to adjust the height based on the aspect ratio of the image after it is scaled. To analyze the code a little more, what is happening with the ‘featured-image’ image size is that if them theme is not set to crop option then the ‘featured-image’ will be scaled to 700px wide and left to be however tall the image is. If you select the crop option, it will be scaled to 700px wide and then cropped to 357px tall.

You would need to look at which block(s) you are using and then determine which module the block is using to tell what image size it is. For example, let’s say your block uses td_module_2.php.

In that file, line 13 reads: <?php echo $this->get_image('art-big-1col'); ?>

If we look above at the functions.php entry, we see: add_image_size('art-big-1col', 326, 235, true); This means that if you upload a 1280×720 image, this will resize it’s width and crop it’s height to 235 pixels. If the scaled down image height is less than 235px tall, then it will scale the height to 235px and crop the width to 326px. This is not what you want. Rather, perhaps something like this: add_image_size('art-big-1col', 326, 0, false); This will take the image and scale to 326px wide and let the height be what it will be.

If you want make these changes so that updates to the theme will not break it, then you need to copy the image size declarations out of the theme’s functions.php file and put them in your child theme’s functions.php file and change the options. You might try something like this:

//featured image
$td_crop_features_image = td_util::get_option('tds_' . 'crop_features_image');
if ($td_crop_features_image == '') {
    add_image_size('featured-image', 700, 0, false);
} else {
    add_image_size('featured-image', 700, 357, false
}
//the small thumbnails
set_post_thumbnail_size(          100, 0, false );
add_image_size('art-thumb',       100, 0, false);
//small height, 1 col wide
add_image_size('art-wide',        326, 0, false);
//medium height 1 col wide
add_image_size('art-big-1col',    326, 0, false);
//the slides
add_image_size('art-slide-small', 326, 0, false);
add_image_size('art-slide-med',   700, 0, false);
add_image_size('art-slide-big',  1074, 0, false);
//big slider - big image
add_image_size('art-slidebig-main',  745, 0, false);
//the gallery
add_image_size('art-gal',         210, 0, false);

By setting all the height arguments to 0, we tell WordPress to always use the full height of an image relative to the horizontal scaling and by changing ‘true’ to ‘false’ we enable ‘soft crop mode’ vs ‘hard crop mode.’ Soft crop mode ensures your images will maintain their aspect and not have any cropping. Note, the 0 setting will make it so that any image uploaded that is not 16×9 aspect will be scaled and output at it’s own aspect ratio. This can break styling, but if you only upload 16×9 images it will be fine.

You would need to either re-build your current thumbnails or upload some new images to see if this fixes your problem(or creates others)

There are lots of gotchas here, and I certainly didn’t give you a definitive answer, but perhaps what I did say will help you figure out what combination of options will solve your problem.

Good luck!

h2 tag is optional not required for SEO, only suggested as it’s a second level headline for use on pages/posts … you can use h2 tags anywhere in your pages or posts…

I often use them as subheads below the image in posts, or at top of page.

I generally use h3 tags for section heads in posts, or chapter starts, etc. h3 is also the common level used for sidebars, and various other headline elements in the theme.

Thanks for the reply, Lucian.

Am I right in thinking that that is only for Google Adsense ads?

If I had a custom code from another network, it would load and only be hidden by display:none in the CSS under the correct @media attribute?

Speed Booster Pack

This plugin is a all in one that will give you that 95% score on Google PageSpeed, YSlow, Pingdom and GTmetrix.

The plugin comes with some great features like:

1. Moves scripts to the footer to improve page loading speed.

2. Loads javascript files from Google Libraries rather than serving them from your WordPress install directly, to reduce latency, increase parallelism and improve caching.

3. Defers parsing of javascript files to reduce the initial load time of your page.

4.Removes query strings from static resources to improve your speed scores.

5. Removes extra Font Awesome stylesheets added to your theme by certain plugins, if Font Awesome is already used in your theme.

6. Removes junk header tags to clean up your WordPress Header.

I’m using this plugin as well and it really help removed the rest of those files in render-blocking CSS and JS files.

With this plugin you will not need the other plugin ““Query Strings Remover”…

The plugin name is “Speed Booster Pack” by the author tiguan

You can download this plugin via the wordpress website @ this url

http://wordpress.org/plugins/speed-booster-pack/

Speed Booster Pack – Documentation

http://tiguandesign.com/docs/speed-booster/

@Lukao350
Hi, it’s almost impossible to fully remove all render blocking — most websites need to have some CSS load before the page … otherwise you get a flash of unstyled text – where page starts to load but is messed up, then the CSS loads and corrects – ugly.

So, with full optimization, you typically you will end up with one main CSS file, and one main JS file, as well as the other render blocking stuff will be external files (e.g., fonts from Google) that don’t load in “async” mode. The TagDiv Speed Booster plugin helps a bit – have you tried that yet ?