-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optimization of Prebid.js's speed #31
Comments
Same here. But as far as I can tell this is your browser parsing the Javascript. I'm not exactly a prebid.js or Javascript expert but I think it should be possible to reduce this parsing time by helping the JS engines a bit. This seems to be a useful article: |
Thanks @BartVB ! We are adding a new feature (coming up soon), that allows Prebid to inform GPT send out the impression immediately after the timeout hits, without having to wait for GPT to load. Closing the ticket for now. |
That's great and this would really help reduce latency on a page level, but it would still be really nice if it were possible to make prebid.js faster. |
…ata (#7167) * DL-1746: Remove trId and use notid instead (#31) * Remove trId and use notid instead * Update version to 0.7.3 * Set default value to empty string Co-authored-by: SublimeJeremy <jeremy@sublimeskinz.com> * DL-1780: Fix pubtimeout (#32) * Update timeout value with onTimeout data * Add test for onTimeout * Update state with timeout asap Co-authored-by: SublimeJeremy <jeremy@sublimeskinz.com>
…ata (prebid#7167) * DL-1746: Remove trId and use notid instead (prebid#31) * Remove trId and use notid instead * Update version to 0.7.3 * Set default value to empty string Co-authored-by: SublimeJeremy <jeremy@sublimeskinz.com> * DL-1780: Fix pubtimeout (prebid#32) * Update timeout value with onTimeout data * Add test for onTimeout * Update state with timeout asap Co-authored-by: SublimeJeremy <jeremy@sublimeskinz.com>
* KRKPD-1083: Refactor and expand testing (#31) * Refactor the Kargo adapter testing to be more comprehensive and include testing of invalid inputs * Fix the window size test to pull data from the browser instead of hardcoded values * Remove a duplicate test * unhook triggerPixel after tests * fixes circleci failure * Update the localStorage non-functional test In FireFox, having localStorage.getItem throw an error isn't working so the test was updated to not have a valid localStorage value to pass on FireFox. * Restore the bidderSettings following testing --------- Co-authored-by: William Klausmeyer <klawil@users.noreply.github.com> Co-authored-by: “Nick <“nick.llerandi”@kargo.com> Co-authored-by: William Klausmeyer <willyk95@gmail.com>
* KRKPD-1083: Refactor and expand testing (prebid#31) * Refactor the Kargo adapter testing to be more comprehensive and include testing of invalid inputs * Fix the window size test to pull data from the browser instead of hardcoded values * Remove a duplicate test * unhook triggerPixel after tests * fixes circleci failure * Update the localStorage non-functional test In FireFox, having localStorage.getItem throw an error isn't working so the test was updated to not have a valid localStorage value to pass on FireFox. * Restore the bidderSettings following testing --------- Co-authored-by: William Klausmeyer <klawil@users.noreply.github.com> Co-authored-by: “Nick <“nick.llerandi”@kargo.com> Co-authored-by: William Klausmeyer <willyk95@gmail.com>
* KRKPD-1083: Refactor and expand testing (prebid#31) * Refactor the Kargo adapter testing to be more comprehensive and include testing of invalid inputs * Fix the window size test to pull data from the browser instead of hardcoded values * Remove a duplicate test * unhook triggerPixel after tests * fixes circleci failure * Update the localStorage non-functional test In FireFox, having localStorage.getItem throw an error isn't working so the test was updated to not have a valid localStorage value to pass on FireFox. * Restore the bidderSettings following testing --------- Co-authored-by: William Klausmeyer <klawil@users.noreply.github.com> Co-authored-by: “Nick <“nick.llerandi”@kargo.com> Co-authored-by: William Klausmeyer <willyk95@gmail.com>
I noticed there's a 30-50ms lag between when Prebid.js finished loading and when the first pre-bid calls are initiated.
This is a Chrome capture on page: http://prebid.org/header-bidding-demo.html
The text was updated successfully, but these errors were encountered: