Google Developers PageSpeed is Not Good

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   We
were at over 3 thousand pages crawled daily down to 515 with the roll-out of
V5.
Chrome add-on PageSpeed from Google Development team and their Audit
states that if a page cannot have the above the fold content delivered to user
within a second then the page is less likely to be crawled and indexed. 
Makes sense why are results are now low.  Before you state that I should
optimize my images from home page, note that has been done, however every page
from product cart still results in these bottlenecks from including resources
in the head tag.  Regardless of the content on the page, without any
images the errors still exist.  This ultimately brings the user a bad
experience which is Google's new term for getting to the top requirement.

One
of their issues is with the 302 redirect to the service.asp page, giving the empty cart message comment from the msg.asp page.  This event now creates
a new bottle-neck/stall from the angular JavaScript.  They recommend a
301, if any, especially on the first page their bot crawls.

Hopefully
this is something that will be looked into since Google is the driving
force for getting our customers, if not from our two 150 page catalogs we send
out every year.  If you inspect element anywhere within Chrome click on the Network tab and refresh.  Comment on your DOM time and Render time below.  Run the audit to see where you stand as well.  If you see results like these then maybe something has to be done.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
THORDUDE Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 03-May-2014 Location: Minnesota Status: Offline Points: 2	Post Options Post Reply Quote THORDUDE Report Post Thanks(0) Quote Reply Topic: Google Developers PageSpeed is Not Good Posted: 04-March-2015 at 1:52pm
	We were at over 3 thousand pages crawled daily down to 515 with the roll-out of V5. Chrome add-on PageSpeed from Google Development team and their Audit states that if a page cannot have the above the fold content delivered to user within a second then the page is less likely to be crawled and indexed. Makes sense why are results are now low. Before you state that I should optimize my images from home page, note that has been done, however every page from product cart still results in these bottlenecks from including resources in the head tag. Regardless of the content on the page, without any images the errors still exist. This ultimately brings the user a bad experience which is Google's new term for getting to the top requirement. One of their issues is with the 302 redirect to the service.asp page, giving the empty cart message comment from the msg.asp page. This event now creates a new bottle-neck/stall from the angular JavaScript. They recommend a 301, if any, especially on the first page their bot crawls. Hopefully this is something that will be looked into since Google is the driving force for getting our customers, if not from our two 150 page catalogs we send out every year. If you inspect element anywhere within Chrome click on the Network tab and refresh. Comment on your DOM time and Render time below. Run the audit to see where you stand as well. If you see results like these then maybe something has to be done.

Brett Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 22-April-2008 Location: Phoenix, AZ Status: Offline Points: 89	Post Options Post Reply Quote Brett Report Post Thanks(0) Quote Reply Posted: 13-April-2015 at 4:08am
	Regarding the inclusion of resources in the page head, I've found the most suitable solution to (sadly) be modifying the core files to move these resources to the end of the body. I'm currently in the process of working on upgrading our site to v5, and am building a new theme for our site in the process. I've found that while most things can be accomplished within the theme alone, some issues require modifications to "core" files (those outside the theme directory). Hopefully this is something the development team has on their agenda, as it would certainly be good practice to load resources in the proper location on the page. In the meantime, I'd suggest you address the issues on a case by case basis. My approach has been to use Sublime Text's project-wide search functionality to find the location within the code where each of these resources is being included, and then to make the necessary adjustments to move them to the correct location. Regarding the 301/302 redirects, I'm not sure I understand exactly what you mean. When are you encountering this 302 redirect?