Skip to main content
November 25, 2025
Question

Interactive content lagging when displayed in adobe connect?

  • November 25, 2025
  • 1 reply
  • 94 views

While examining a puzzle activity on a website that provides daily letter challenges, I noticed something strange. I've been testing the behaviour of various interactive content types within adobe connect. In a browser, the animations and letter interactions load smoothly; however, within connect, they occasionally lag or become unresponsive.

Has anyone else encountered problems with adobe connect rendering lightweight web-based puzzle elements smoothly? I'm not sure if this has to do with shared-screen refresh rates, html rendering limits, or connect's handling of scripts in embedded content. If anyone else has discovered a solution for comparable circumstances, please let me know.

1 reply

Randy Hagan
Community Expert
Community Expert
November 30, 2025

You're layering latency challenges running web apps inside of Adobe Connect.

 

First, you're dependent on the delivery speed of the web app server. Then you're relying on the power of your network to deliver that content. Which is then inside of a shell provided by Adobe Connect, which is a web service delivered by Adobe and/or partners web servers. Which again relies on the power of your network to deliver that service, then provide you the web app content inside that shell. Then you're relying on one more layer of latency as you deliver your Connect presentation from your server to be received by whatever connection(s) your audience have to access your content in a Connect session.

 

Whew.

 

I've never run external web-based puzzle elements on Connect. But I have run other streaming content from the web through Connect, and have encountered similar challenges. Especially if I have other interactive elements running in other pods in the same workspace. Anything you can do to reduce the layers of latency/lag built into this process will make your life easier.

 

I'd suggest the following:

 

1) Run your web puzzle in a separate workspace, with no extraneous pods running in the same workspace.

2) If you run with "hidden" pods behind your visible content to speed up transitions between workspaces, trade off the extra latency in your puzzle-presenting workspace for minor delays as you transition from that workspace to the next one(s) you will be using in your presentations.

 

You're robbing Peter to pay Paul, but at least Peter's puzzle-providing workspace will be optimized as much bandwidth as you can get away with using your existing setup.

 

Hope this helps,

 

Randy