Why PageSpeed Insights reduce my calification when adding google advertisement in my website? - adsense

Why PageSpeed Insights reduce my calification when adding google advertisement in my website ?
https://developers.google.com/speed/pagespeed/insights/?hl=es&url=https%3A%2F%2Ftaptapking.com%2F
Is there any way to optimize the code load? try asynchronously and loading ad units from js.
Please help

Your PageSpeed score will always be lowered when you have AdSense or other ad networks actively running on your site.
All AdSense is already loading asynchronously. You can only have a marginal affect on the ad loading speed by deciding at what point during the page loading process you want to trigger the loading of your AdSense code.
Even extremely well optimized websites will generally not get a PageSpeed score of 100/100 if their pages have AdSense code on it.
Google Page Speed only gives you basic insight into what could be improved. Try checking your site on webpagetest.org instead to better test your site's Loading Speed.

Related

Adsense ruins mobile's Pagespeed score, mobile 50, desktop 98

When I remove adsense code, both scores 100. Can somebody help me to speedup adsense code on mobile? or i just have to live with it?
Adsense is a third-party network that loads third party codes, you have no control over their resources. Adsense ad scripts, images and css files are poorly optimized.
What you can do is to consider lazy loading ads. Or Live with it.

How can I test Google ads on my site

I am developing a website where I want to show Google ads. How can I test ads on my site? Additionally:
Does Google allow me to test ads?
Does it think my tests are fake impressions?
Can I get blocked by Adsense?
here is site link http://www.geeksweblogs.com/
Google may not like it, but in its TOS it says you are allowed to test your ads, although I would recommend you not to refresh the site thousands of times. Instead, I would first remove the AdSense tags and use some divs with fixed width & height and a background color (or a background image which looks like a Google ad) to test it excessively. If you have tested your layouts, remove the test divs and re-add your Google AdSense code. Now you can test it an additional few times to be 100% sure that all works. You can surely reload the page 10-20 times. Remember to just view the ads for testing but never ever click on your own ads – Google doesn't like that.

GPT implementation for Instant Articles

From what I understand, Facebook only supports an iframe adtag for DFP ads. Google states there are limitations with using this functionality, seen here: https://support.google.com/dfp_sb/answer/90777?hl=en
We're hesitant to implement the iframe tag across our whole website just to satisfy Facebook's requirements as this would then impact direct website traffic.
My questions are:
Does anyone have a sample of what FB's desired implementation would look like with the use of the iframe GPT tags?
Is anyone currently doing this, and if so, have you implemented this site-wide (limiting website functionality), or are you using a REGEX to cut the original ad out and replace within your feed export - seems messy.
After reading the link you shared and the FB policy it seems there aren't any real concerns with using an iframe. FB doesn't allow expandables or 3rd party ads. You can always have house ads targeting the ad unit as a fallback so i don't think the blank situation should come into play either. Here's the Facebook policy for reference: https://developers.facebook.com/docs/instant-articles/policy

Sync vs Async in DFP

I haven't signed up for DFP Premium yet, but I had a question about it.
If I choose to use asynchronous DFP tags on my site, what happens if my site loads a line item for an advertiser that only has synchronous tags? Will the DFP placement still load asynchronously? Will DFP try to 'convert' a sync tag to an async one? (I have heard of other adservers doing this...). Also, what happens if the advertiser tag contains document.write().... will it still work to put that advertiser in an asynchronous DFP setup?
You can use sync ad tags in an async DFP setup. DFP loads the ad tags in an iframe and the tags can run document.write() all they want.
There are some drawbacks though. The iframes have a fixed size. If the sync tag renders a smaller creative, or no creative at all, then the ad unit still takes up the full size. You can work around this but that's kind of a nuisance, especially because the collapseEmptyDivs() method doesn't know if a third party tag has delivered a creative or not.
Besides that you'll have problems with out of page creatives if they don't check if they are being rendered in an iframe. The DFP iframes are 'friendly iframes' by default, so it's extremely easy to escape them for a creative, but the creative does need some small modifications for this to work.
But you can test all of this by trying the Small Business version of DFP. It's the exact same product with some advanced features (mostly related to targeting) disabled. Ad delivery is exactly the same when it comes to sync vs async.

Facebook Scrapes Beso.com so hard as to heavily impact site performance; how do we get FB to throttle its crawl?

Our site, Beso.com, which has 3MM UV a month, has started being hit by Facebook's crawler/scraper multiple times a day, to the point where it is causing a severe performance degradation on our site. We have recently implemented the Open Graph, and are encouraging a fair amount of sharing and liking on our site, along with Facebook Connect.
I understand that FB needs access to our site to scrape info, but we desperately need them to throttle down the rate of crawling, or we will be forced to block it entirely. This isn't a solution we wish to go with.
Would there be anyone from FB on this site who could connect us with an appropriate team member, or anyone from an established site who has battled this issue before?
Thanks.
Facebook scrapes open graph objects once per day. I can think of two possible reasons a site would be over-scraped...
1) You have an app that implements open graph actions. The programmer who created that app accidentally set the scrape optional parameter permanentaly to true. See here:
https://developers.facebook.com/docs/opengraph/actions/
2) A single page--what should be one open graph object--has multiple URL's such that Facebook is re-scraping the same material over and over.