Roll20 Lag - Console Log

I'm a player in a campaign and seem to be the only one having lag issues. Any advice is appreciated. I've done steps 1-3. Here is the console log: JQMIGRATE: Logging is active jquery.migrate.js :20:10 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). 3 jquery-1.9.1.js :1444:6 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). 3 jquery-1.9.1.js :1450:5 Some cookies are misusing the recommended “SameSite“ attribute 31 Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> editor Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> editor Cookie “gdpr_accepts_cookies” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> editor :305:2 Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> startjs Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 3 startjs Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 3 false Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> false Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> fetchroot Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 3 fetchroot Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> marketplace_purchases_index Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 3 marketplace_purchases_index Cookie “_ga” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> analytics.js :34:486 Cookie “_gid” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> analytics.js :34:486 Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 2 sheetsandbox.bundle.js Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 150 Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 150 Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 1 Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 3 1 Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 2 Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 3 2 Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 30 Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 30 Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 30 Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 30 Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 30 Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 30 Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 30 Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 30 Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 30 Cookie “rack.session” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> 30 Cookie “_gat” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read <a href="https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite" rel="nofollow">https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite</a> analytics.js :34:486 Cookie “rack.session” has been rejected because it is already expired. editor This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. editor Loading failed for the &lt;script&gt; with source “ <a href="https://static.ads-twitter.com/uwt.js" rel="nofollow">https://static.ads-twitter.com/uwt.js</a> ”. editor :1:1 Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content. jquery-1.9.1.js :9392:13 Content Security Policy: The page’s settings blocked the loading of a resource at <a href="https://static.ads-twitter.com/uwt.js" rel="nofollow">https://static.ads-twitter.com/uwt.js</a> (“script-src”). gtm.js :76:463 Ignoring unsupported entryTypes: longtask, largest-contentful-paint, layout-shift. datadog-rum.js :1:27594 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). gtm.js :513:413 Cookie “rack.session” has been rejected because it is already expired. startjs CAMPAIGN ID: 11291539 startjs :23:9 WebRTC: RTCIceServer.url is deprecated! Use urls instead. 3 vtt.bundle.js :24015 70 vtt.bundle.js :26461:126319 TOUCH SUPPORTED: false vtt.bundle.js :26492:85804 USING WEBGL ACCELERATION... vtt.bundle.js :26492:86342 WEBGL STARTUP SUCCESS vtt.bundle.js :26492:86781 Loading Custom character sheet. vtt.bundle.js :26568:57256 tuts loaded tutorial_tips.js :7:10 Source map error: Error: request failed with status 404 Resource URL: <a href="https://app.roll20.net/assets/base.css?1668723864" rel="nofollow">https://app.roll20.net/assets/base.css?1668723864</a> Source Map URL: bootstrap.css.map ​

Hi&nbsp;GM Jeremy! It's mostly community support here on the forum. If you want to file that info in a&nbsp; Help Center Request , it will generate a ticket and get it in front of the eyes of the team. What's the kind of lag you are seeing? I.e. what operations seem to lag the most?

Thanks! The lag is with moving tokens (both with mouse and arrow keys) and dragging the mapview.

Have you tried toggling hardware acceleration on your browser? This is the most common culprit. Here is the help center page most closely associated with the symptoms you describe. Also, if you use the extension Grammarly, try toggling it off while playing.

I did. I didn't notice any change after restarting my browser though. I don't have any extensions installed. I'm wondering if maybe the game map is maybe too big. Do you think that could cause this type of problem?

GM Jeremy said: I did. I didn't notice any change after restarting my browser though. I don't have any extensions installed. I'm wondering if maybe the game map is maybe too big. Do you think that could cause this type of problem? Large maps and using Explorer mode (Updated Dynamic Lighting) are both primary culprits for significant lag. You can also try swapping browsers - some users have better luck with Firefox, some with Chrome.&nbsp; In my case, on my laptop, I use Chrome in Incognito mode.&nbsp; If I try to use regular Chrome or Firefox (no extensions,) there is significant lag.&nbsp; On my desktop, Firefox (no extensions) works without any issue.&nbsp; There doesn't seem to be any fool-proof way of making sure that the device and browser you use will work optimally other than trial and error. Best of luck. -Adam

Also, it might be worth trying unsupported browsers. I have one use who has lag on anything but Edge. It might be unsupported, but if it works, it works.