141–150 of 361 posts
How does this work on devices with touch screen? (My apologies if this question has already been raised)
It prefetches on touch event while a "click" is normally triggered by a touch release.
This is really impressive! I noticed the script uses `const` and `let` which might cause javascript errors in older browsers ( https://caniuse.com/#search=let ) so I ran it through the Google Closure compiler to compile it down to ES3 and it works great. https://closure-compiler.appspot.com/home I've added it to my blog and a Django side project. Really speeds up page loads. Just need to add `data-no-instant` attribu…
This is really impressive! I noticed the script uses `const` and `let` which might cause javascript errors in older browsers ( https://caniuse.com/#search=let ) so I ran it through the Google Closure compiler to compile it down to ES3 and it works great. https://closure-compiler.appspot.com/home I've added it to my blog and a Django side project. Really speeds up page loads. Just need to add `data-no-instant` attribu…
It’s loaded as a module so older browsers won’t execute it (and thus won’t choke on the modern syntax).
That is, if you wanted to prove that "X is better than Y by 1%" you would need a sample approaching 10,000 attempted conversions to have a hope of having a good enough sample.
Many people browse the web from an employer who has rules about what types of pages may be accessed. For example, a person applying for a job with my team may include a link to a web page about their job-related background -- portfolio.html or whatever. HR tells us to be sure we don't follow links to any other page that may be more personal in nature, such as a page that reveals the applicant's marital status (which…
A "1% improvement in conversion rate" is a big claim to make for a claim that seems so small. That is, if you wanted to prove that "X is better than Y by 1%" you would need a sample approaching 10,000 attempted conversions to have a hope of having a good enough sample.
A "1% improvement in conversion rate" is a big claim to make for a claim that seems so small. That is, if you wanted to prove that "X is better than Y by 1%" you would need a sample approaching 10,000 attempted conversions to have a hope of having a good enough sample.
But there's no guarantee that it will apply for all pages.
A "1% improvement in conversion rate" is a big claim to make for a claim that seems so small. That is, if you wanted to prove that "X is better than Y by 1%" you would need a sample approaching 10,000 attempted conversions to have a hope of having a good enough sample.
dieulot, is there a small bug with the allowQueryString check?
const allowQueryString = 'instantAllowQueryString' in document.body.dataset
const allowQueryString = 'instantallowquerystring' in document.body.dataset
'instantAllowQueryString' in document.body.dataset === false
'instantallowquerystring' in document.body.dataset === true
A "1% improvement in conversion rate" is a big claim to make for a claim that seems so small. That is, if you wanted to prove that "X is better than Y by 1%" you would need a sample approaching 10,000 attempted conversions to have a hope of having a good enough sample.
See: https://developers.google.com/web/fundamentals/performance/w...