Your problem is a horrific endless loop caused by:
FinishAction=[!SetVariable Test (#Test#+1)][!Update]
You have a large Update value, ok, bad idea (see below) but I can live with that.
However, you are having WebParser go out and get the site data and as soon as it is done, you force an update of the entire skin again. Since UpdateRate is "1", WebParser will go right back out and get data and again fire the FinishAction. You are in an endless loop where you are telling WebParser to basically hammer that site as fast as it possibly can. Not once every 30 minutes, not once a second even, but as fast as it can go. You will hit that site dozens, maybe hundreds of time per minute.
As a general practice, you want to be skeptical about using !Update in bangs. It has its place, but it is very "brute force" and can easily get you into an endless loop if you are not a bit careful. I tend to stay away from it and lean toward more targeted updates of specific things with !UpdateMeasure and !UpdateMeter.
In any case, you don't want to drive this with Update. Leave that at once a second, or Update=1000
Pretty much never set Update in [Rainmeter] more than 1000. It can be less, for animations or other things that required a more often update and redraw of the skin, or it can be Update=-1 to only update one time, if your skin is entirely driven by mouse actions and should be "on demand". But a value greater than 1000 is almost never the right solution. If you need or want things "slower", that's fine, still just set Update=1000, and use UpdateDivider
and / or DefaultUpdateDivider
on measures and meters to control things.
To have the WebParser measure then be set to go out to the web and get data once every 30 minutes, you would use UpdateRate=1800. Don't set, in fact pretty much never set, UpdateDivider on a WebParser measure.
You don't need or want any "lag" from the time that the WebParser measure actually finishes getting the current data, and when the skin uses it. Having the plugin say "Ok skin, I've got new data" and having the skin use that data in measures and meters one second or less later is what you want. You don't want "Ok skin, I've got new data", and the skin say "I'll get back to you on that in 30 minutes...".