Profile cover photo
Profile photo
Night Owl
4 followers -
I am merely the webmaster.
I am merely the webmaster.

4 followers
About
Night's posts

Post is pinned.Post has attachment
Public
I am not Edward T. Babinski. I merely manage Ed Babinski's blogs, i.e., performing HTML updates and coding of template, etc. If you wish to contact Edward T. Babinski then you can locate him at the following social media sites. I also don't agree with every thing +Edward T. Babinski writes and believe that's okay with E.T. Babinski. Only politics and religions seek to assimilate people across the world into a sheepishly mindless, undifferentiated herd.

Facebook: edbabinski
Twitter:@edwardtbabinski
Google + ID: 111830531772258533632

Post has attachment
No more tracking in social media share buttons.

Post has attachment

Post has shared content
This happened to me last night.. Google Pagespeed Insights began a new error message, "Prioritize Visible Content" above the fold. I've worked for hours to rectify a non-issue.
Google pagespeed insights tool is inaccurate with the "Prioritize visible content" error message - do not use this error message to change your site!
I have noticed a scenario where the pagespeed insights tool is giving incorrect results. Namely the prioritize visible content result.
I have been recieving many questions about this and just want to let people know that in most cases....

It is Google pagespeed insights tool, not you.

The tool will report that a page needs to "Prioritize visible content" and gives the following message...

-----------------------------------------------------------------------------------------------------

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 3% of the final above-the-fold content could be rendered with the full HTML response see screenshot.

---------------------------------------------------------------------------------------------------------

There are many times when that error comes up and it is simply incorrect. From the amount of emails I have been getting about this, many people are wondering about it and getting frustrted by it.

To put your mind at ease, we can simply use a url where there is nothing but an html page, and I have lots of those at feedthebot. 
Here is a page I will use --

"https://www.feedthebot.com/pagespeed/wicked-fast.html"

This page calls no css, no js, no images, it loads completely and entirely with just the html.

If we put that in the Google pagespeed insights tool, there should be no way that we can receive that error, but we still receive it...

-----------------------------------------------------------------------------------------

"The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 3% of the final above-the-fold content could be rendered with the full HTML response see screenshot."

-------------------------------------------------------------------

Clearly this error as it is written is not possible, but let's break it down...

error message: "The entire HTML response was not sufficient to render the above-the-fold content. " 
me: "Yes it is. There are no other resources except the html and the page is rendering, therefore tool is wrong."

error message: "Only about 3% of the final above-the-fold content could be rendered with the full HTML response see screenshot." 
me: "100% of the above the fold content can be rendered, in fact 100% of the entire page can be rendered. There are no other resources except the html and the page is rendering, therefore tool is wrong."

So in any case, if this is causing you issues, do not depend on the tool for this matter. It is not providing accurate results for this.


 +Paul Irish +Ilya Grigorik 

Ed's blogs reached 100% Pagespeed, 100% Yslow... but we can't afford to pay the exorbitant cost of a pro-online CDN (Content Delivery Network). Cloudflare, which we currently use injects cookies. So I've added a "Donate" button. If we can raise at least a couple $100 or more, we can probably then afford to pay Godaddy the cost of a Sitelock install, which will provide an on-site CDN. Till then, the score for YSlow remains at 99% :-(

https://gtmetrix.com/reports/edward-t-babinski.blogspot.com/XtPOSpeV

Post has attachment

Got the pagespeed score down to (sometimes sporadic) half second. Other times goes as high as 1.5 second. Would like a quick server response at all times.

Post has attachment

Post has attachment

Post has attachment
Wait while more posts are being loaded