The following warnings occurred:
Warning [2] count(): Parameter must be an array or an object that implements Countable - Line: 802 - File: showthread.php PHP 7.2.24-0ubuntu0.18.04.1 (Linux)
File Line Function
/showthread.php 802 errorHandler->error

Current time: 12-07-2019, 01:50 PM Hello There, Guest! (LoginRegister)

Post Reply 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Prerender - Cost being added to WPT for initial page
06-14-2016, 07:59 PM
Post: #1
Prerender - Cost being added to WPT for initial page
Hi - We've just started trialling a prerender on our landing pages, to get the JS and CSS for our product availability page before the customer does a search.

In WPT the cost of the Prerender is being added to our homepage. Our JS has doubled, Start Render delayed by 2s, overall page weight has doubled. This leads to a false negative. We put this out in a rush last week, and I'm glad we did because I'd not have done so if I'd looked at WPT.

When I look at Chrome dev tools it is not, it acts according to the spec, as if being opened in another window. We use mPulse for measuring real users and have seen a real benefit from this on the availability page, in our custom first render marker and other timings, and no negative effect on the homepage.

Why would the prerender be affecting Start Render time, adding to the overall page weight when it is (supposed to be) executed after the initial page has loaded and in a separate window?

We are separately working on making these files smaller, but that is a lot more difficult.

Many thanks

Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
Prerender - Cost being added to WPT for initial page - benthompson - 06-14-2016 07:59 PM

Forum Jump:

User(s) browsing this thread: 1 Guest(s)