MyBB Internal: One or more warnings occured. Please contact your administrator for assistance.
WebPagetest Forums - Google adsense on test results

WebPagetest Forums

Full Version: Google adsense on test results
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
Okay here it is my site runs smooth and fast however the test results also show adsense, the adsense takes 12 seconds to load. How is this my fault, there is nothing i can do to effect adsense, if they decide to run .flv movies from universal studios how can i stop that Huh

So every time i run webpagetest it tells me i have a slow site because of adsense.
Umm, technically, if you have a slow site because of adsense, you have a slow site (the same could be said for any other 3rd party widget you put on your site like facebook like buttons, etc) ;-)

More seriously, for recent browsers (IE 8+), adsense should load asynchronously now so even if it is slow your page content should not be delayed because of it. You should probably verify by enabling the video capture for a test and make sure the page content loads quickly.

If you want to test the site in isolation and remove the adsense impact from the times you can use the content blocking feature in the advanced settings and block the adsense js (and you can also do a comparison video against the normal site to see the real user impact).

There is a huge load on my site because of adsense, i'm not going to take it off. So what can i do.
Here is a comparison of the site with and without adsense:

I think you were seeing some really long loads because of a video ad that played after onLoad but the impact to the actual page itself loading looks like it's only ~100ms (using IE8 which has the async support in adsense).

The only reason I recommended blocking adsense for running a test was so you could see if you had any room for optimization outside of the ads and to get a cleaner read on the page itself:

Looking at the waterfall, I'd say your best bet for optimization is to actually focus on the back-end page generation. Looks like it is taking a little over 600ms to construct the html on the server side. A quick trick would be to get early flushing working so you could flush out enough of the html to get the browser loading external resources while you work on the more expensive back-end calls.
early flushing sounds like a new concept to me i've never heard of this before anywhere good i can research this :/
Here you go:

You can also Google for "flush document early" to get more information.
thanks for the help it was really helpful now i have a little new performance tool to learn Smile

However after doing research into flushing they say the way to do it with php, is adding the code

<?php flush(); ?>

after the

in my index.php page, i'm using joomla and after putting it there expecting it to work nothing happened i'm still getting the slow initial slow response that it said it would fix no difference Sad
In php there can be some interactions with output buffering so sometimes you need to use ob_flush() but if you're running Joomla you might want to avoid that - there could be code in the templates that are counting on the buffers not having been flushed.

What version of Joomla are you running? Have you enabled the built-in page caching mechanisms? Joomla is one of the harder CMS systems to optimize because there aren't a lot of plugins that can help (though there are a few threads around here from people working on it).
Confused before i even start (not good) i'm using the latest version of Joomla 1.5 and i'm using the built in page caching along with a CDN called maxcdn which gzips everything for me in advance. Wish there were more performance plugins for joomla but all you get are "compress css plugins" for the performance section of joomla and only a handfull of useful plugins that do something different Sad

i taken the
<?php flush(); ?>

off my site cause you said it may conflict with joomla.
Quote:3Unable to post message to Recipient has origin
Unsafe JavaScript attempt to access frame with URL from frame with URL Domains, protocols and ports must match.
4Unable to post message to Recipient has origin
Unsafe JavaScript attempt to access frame with URL from frame with URL Domains, protocols and ports must match.

Use Chrome Tools and there the console.
There 9 errors like that.
Pages: 1 2
Reference URL's