I am working with an ASP.Net WebForms project that is using an UpdatePanel and in IE it is extremely slow to load the page, however in Chrome and FireFox this is not an issue at all.
I have seen and tried the answer here ASP.NET website very slow Internet Explorer 10
I have also tried the suggested answer here too https://www.devexpress.com/Support/Center/Question/Details/T268620
I also have the update condition set to conditional too as suggested here Update Panel working very slow
I should also note that I have a repeater on the page too.
When looking at what is sent and recevied using Fiddler I am getting this result
Bytes Sent: 1,888 (headers:1,331; body:557)
Bytes Received: 5,280 (headers:148; body:5,132)
When navigating to the page, the data is loaded and appears immediately, but the page is not responsive which is the actual issue.
I would apprecaite all help in order to resolve this issue and speed up the performance in IE to mach (as close as possible) that of Chrome and FF.
Edit -
Although this question has been asked, its been asked for different versions of VS.
I have resolved this now and have displayed the answer below
I found the answer, and did consider deleting the question, however the problem has now almost gone give or take its still a 2 second load, rather than a 15.62 on average.
In Visual Studio the system has a function that needs turning off and whoever stumbles across this question with the same issue this will hopefully fix it for you too.
http://www.poconosystems.com/software-development/how-to-disable-browser-link-in-visual-studio-2013/
Its a combination of the DevExpress link and the turning off the option in Visual Studio.
Related
We built a Joomla website for one of our clients which can be located at:
http://mayslakeministries.org/
Although everything was looking fine from our end, the client was seeing the website as if no CSS was being rendered. Unfortunately, I do not have a screenshot at the moment. I will try and get one up here in the next hour or so if we don't come up with a resolution. (If anyone is able to see the mess that I'm describing, if you could post a screenshot that would be appreciated as well. We have limited testing equipment available and it's hard for us to reproduce.)
But here is what we've concluded: the website works fine in Chrome and Firefox on all systems. It works fine with IE10 on all systems as well. However, as soon you switch to IE9, things get strange.
IE9 will work fine if you are on Windows 8, but if you are viewing in IE9 from Windows 7 or Vista, things look as if the CSS isn't being loaded.
Any help would be appreciated. If you view the site and find that the information I've provided contradicts what you are seeing, then let me know. We have limited equipment to test with, so it was difficult for us to be able to see the problem.
This is the first time I've encountered a problem that only occurs on a certain OS.
Oh! One more thing I think is worth mentioning. The Joomla template we are using works fine even on Windows 7 IE9. So we believe it's something that we have done to the website that changed it's behavior.
Here is the Joomla template demo:
http://www.astemplates.com/itempreview/186
Alright, it took is a few days, but we finally figured out the problem.
IE apparently has a limit to the number of resources that can be linked to the page at one time. Our Joomla site has around 200 JS/CSS files being linked through the source, and this caused IE to bug out and not load our CSS properly.
This is one of the strangest problems I've had to deal with, so I'm very glad it's fixed.
I've been having an issue with a client's site that I haven't been able to replicate. A few users have reported an issue with the website (http://beyondbbd.com) where the pages don't display a majority of the styling and render as below:
In trying to troubleshoot, I am having difficulty replicating the issue on my browser checking system (Browserstack), or finding an underlying cause.
Users reporting the issue are using Windows 7 and Internet explorer (though I don't know their version of IE at this time), and are encountering the issue on these pages, among others:
http://beyondbbd.com/motivational-speakers-for-business/
http://beyondbbd.com/leadership-workshops/
http://beyondbbd.com/internal-coach-training-program/
I haven't been able to replicate on any version of Windows or IE using Browserstack, but this issue has been reported by more than one user so I don't think it's an isolated case.
Anyone have any ideas as to what the cause could be, or how I could replicate the bug?
Thanks in advance!
-Nick
I couldn't replicate, but you have two opening 'head' tags as well as lots of other validation errors (stray closing tags). It is possible that this is chocking some instances of IE.
In our company, we have bought a web application that we are testing in the intranet zone. We are using IE 8.
Basically, on a particular page, there are a few buttons, and one of them populates a fairly big gridview.
Then as soon as I click on another button that causes a postback, I immediately get a 'web page navigation cancelled (DNS Error).
At first I thought it could be a problem with the URL being too long, but it's not the case.
Then, the vendor performed the same actions on his computer, and it worked correctly. Clearly, this is not a problem with the website itself, but probably a configuration with IE8.
Unfortunately, we cannot use or test with Firefox or IE9. We are stucked with IE8.
Any ideas?
Thank you!
Take a look at the answers on this thread, specifically the one by SpritX. Many reasons this could be happening and there are a few solutions in that discussion you can try.
I was working on some ASP.NET 2.0 pages when I noticed that some of the pages' back buttons were unavailable - greyed out. And clicking the drop down menu next to them showed clear results, as if I had come to this page fresh. I looked through the code trying to find something to specifically disable the back buttons (redirects, clever javascript), but found nothing. So I started picking apart the page and noticed that when two particularly large drop down lists (One had 38 thousand items!) were commented out that the back button would again be available. By 'Commented out' I mean I did not databind them in the code behind.
It seems that these pages used to work before I inherited this project. One of the things we did was upgrade the server from .NET 2.0 to .NET 3.5, although the code still targets the 2.0 framework. I doubt this is the culprit though.
This problem occurs in both IE 6 and IE 8 with all the latest updates. It occurs on Server 2003 RC2 with all the updates I could find and on Windows XP machines that the client has selectively updated but are all running IE 6.
My question is, has anyone ever heard of this, and if so, what causes it? Is it just an Internet Explorer bug?
Well, 38k options # 28 characters^1 gives one a page size of 1,064,000 characters for the options alone, nevermind the accompanying viewstate. Which, when I think about it is probably what is killing IE as your POST size has to be in the megabytes range.
Personally, rather than beat on the issue which you probably can't fix, I'd go for hitting it from the easier side of re-factoring the interface so users get a managable number of options. I really don't know how one could pick the correct one in 38k in the first place anyhow . . .
^1: <option value="x">y</option> is about as short an option as ASP.NET will generate and that is 28 characters. I'd bet we are looking at far more data than that. I pray this is an intranet app . . .
I've noticed a strange behavior in two different sites when using IE8.
The first site is in the site that I maintain xebra.com.
The second site is google analytics.
The behavior is that when an address is typed directly into the address bar of IE8, both sites display correctly,
But when one of the sites has already been loaded, and you press the refresh button or F5 key, the layout gets all screwed up:
See screenshots here: here
Something is causing IE8 to render in 'quirks mode' which causes the breakage.
You can duplicate this by browsing to your site in IE8 and selecting Tools > Developer Tools > Document Mode > Quirks Mode.
Make sure your document is always being served in standards mode.
EDIT My original answer had 'compatability mode' where it should have read 'quirks mode' - the two are different.
JS.Companion was what was causing this odd bug, and not IE8. Phew!
http://www.my-debugbar.com/wiki/CompanionJS/HomePage
I spent the whole morning trying to figure out what was going on, I removed companion.js and bingo my site is perfect! thanks for this.
That's really strange. I don't have the problem on my computer with Companion.JS installed and http://www.xebra.com/ web page (under Vista SP1).
I would be happyto correct the Companion.JS bug that generates this problem if you can provide more information about the problem.