I'm running SharePoint 2010 with Visio Services enabled.

I created a new site with a custom list containing hardware items found in a couple of data centers (e.g. equipment type, name, location, manufacturer, model, server rack number, etc.)

I have a Visio diagram with several pages. Each page drills down from data center to room, room to rack. Each rack is a separate page/tab in the same diagram with images of data center equipment (maybe a server or network switch, or whatever) that is installed in that rack. 

I have links set up within the diagram so that I can move from one diagram page to another - starting at a page with the names of datacenters, followed by a diagram of the floor plans within the data centers, followed by equipment racks withing each room

Each piece of equipment in each rack is linked to the SP List I mentioned above and displays that information in a dialog box.

The diagram is saved out in the .vdw format and uploaded to a document library.

The default page of the site has a Visio Services Web Part, referencing the document in the doc library.

I looked at as many examples as I could find and I'm confident that it's set up correctly. It technically "works" but when you click a link or select a page from the dropdown menu in the web part heading a "Refreshing..." dialog appears with a "Cancel" button.

Occassionally, if I let it sit long enough without canceling (more than 2 minutes) it will eventually refresh with no other effort on my part. Other times it times out.

If I click a link, cancel the refresh immediately, and then click the link again, it comes up with almost no delay.

I've tried it on IE 9 and 11 and have Silverlight updated to version 5.1.40728 (latest as of today) with the same behavior.

The diagram was created/saved using Visio 2010, but also tested with Visio 2013 - same behavior.

There are about 20 pages/tabs in the diagram, but most are blank right now. I only mention it in case there is some threshold that we're going over. The file size is less than 800K.

Any ideas? 

Hi Dan- this really sounds like a browser issue. I'd make sure you're using the 32-bit version/running it in compatibility mode.