Can someone please shed some light or point me in a different direction.
We are using adobe flash that launches an app inside of a JSP. Up until yesterday everything was running fine without any issues. Today when the Flash Object launches you can see the initialize bar where before you hardly seen it.
While working within the app as well all the operations are very slow (not much but a 2 second delay on most of the things is visible).
I have 3 browsers installed on my PC
IE 11 running Flash version 23.0.0.207
Chrome 55.0.2883.87 running Flash version 24.0.0.194
Waterfox 32.0 also running the same Flash version as IE 23.0.0.207
Running the app from all 3 these browsers is slow apart from Waterfox.
I deleted all the caches from the flash settings in control panel and for chrome I used the web interface (http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager07.html).
I cleared all browser caches. We are running McCafee which I disabled.
I had a look at any windows updates that was done recently which I uninstalled.
What could be different between these? What else can be checked to see what is making this app slow in IE and Chrome?
The slowness could be caused by the files not being cached by the browser like they used to be. I would start there. If you reload the page and you're not seeing a 304 "Not Modified" for the swf(s) you're loading them from the server each time where they used to be loaded from the browsers cache.
Here's some more info on the subject: https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/http-caching
Both Chrome and IE have developer tools you can load to see the http calls and check the headers and response codes.
https://msdn.microsoft.com/en-us/library/dd565628(v=vs.85).aspx
https://developer.chrome.com/devtools
When i load my website on IE10/9/8 some images wont load.
and if i reload the page, the previous images loads perfectly, but some other images wont load.
And if i remove the browser cache, and refresh the page, same thing. some images load and other w'ont load. you can also see that problem in the portfolio page
thanks
Have you tried loading the webpage in alternative browsers? I'm loading it in Google Chrome and all the images load perfectly fine. Internet Explorer utilities your graphics card as well as your processor to load images to make it faster, which might be totally irrelevant for this question but perhaps your graphics card/processor is causing you issues?
If it's working in other browsers, then use them as opposed to Internet Explorer. It will be a bug with their browser and it's compatibility with whatever system you're using. It's the worst browser to use in all honesty.
There has been very little changed to this page since it just recently stopped loading properly on Chrome.
If you click the link three times things usually load up fine. I've looked through the developer tools and can see that it's hanging up on the js the first load. The second load has pending on most/all of the .jpgs, and then finally another click/load works.
I know it's a heavy site, but the other pages are fine, in terms of actually loading and not just going idle, and this loads well enough in Firefox. I don't think this site is even the largest of the pages in terms of images and video.
I've gone through others solutions to this problem by changing the "https" and renaming files incase an adblocker was causing it, but nothing seems to work.
Any idea of what in the page is causing the issue?
I have a website which displays fine in IE, Chrome, FF and even on Chrome on Mac but it doesn't work on Safari on Mac.
Here's what happens.
When I open the home page, most of the page loads but not full. It keeps loading. So if I refresh the page, it opens instantly
No background image is being displayed
If I go to new page, it sometimes load very quickly but sometimes it doesn't load like point 1 above and I had to refresh it (sometimes even refreshing doesn't work so it is all random)
Safari version is 7.0.1 and OS is Max OS 10.9.1
This is one of the shitiest browser I have seen.
In my case, i solved this issue adding google dns 8.8.8.8 in the System Preferences > Network > Advanced > DNS.
I also tried empty the Safari cache, but it's not help.
I'm using WP Mobile Detector with W3 Total Cache and a responsive layout (media queries), and I have a few issues:
When I view the site locally (localhost) on a Blackberry, it looks good; the zoom/viewport is correct, media queries have trigger correctly etc. However, when I view the live site on the Blackberry, the viewport has zoomed out. In the context of a responsive layout, locally I see two columns, but on live I see all six columns (i.e. the Blackberry thinks it is a full browser - quite annoying!).
I thought I would deactivate W3 Total Cache to see if that was having any effect: yes, it was. When the cache is off, the viewport/zoom is good and all is well. Problem solved? Not quite...
With the cache off, I navigate to the live site and while the sub-pages of the site - e.g. www.SITE.com/about, www.SITE.com/contact - are responding with the mobile theme, when I click a link back to home (or type it into the address bar) - i.e. www.SITE.com/ - I'm no longer delivered the mobile theme, just the normal 'desktop' theme. If I go back to a sub-page I see the mobile theme again. What's going on there then.
When viewed on the Blackberry (for example), if I click the 'View Full Site' link (which triggers a Javascript function to modify the cookie) it doesn't show the full site (i.e. normal theme), it just refreshes and shows the mobile theme. However, when viewed in Firefox on the desktop (via a User Agent Switcher) the link DOES modify the cookie and switches back to the normal desktop theme.
Thoughts/Questions
W3TC does work with WPMD (mobile theme delivers minified JS/CSS), but maybe I haven't configured something correctly. The following two links were very useful and I have implemented the changes suggested:
--- http://snipplr.com/view/47970/wp-mobile-detector--w3-total-cache-integration/
--- http://journal.code4lib.org/articles/6223
Is this a known [Blackberry HotSpot/Internet Browser] issue? I have added the requisite meta tags in the document head to indicate viewport data, and the HandheldFriendly meta data which I understand is mainly for Blackberry purposes. As I said, it looks ok with the cache switched off, excepting the home page issue.
I should say it works nicely in Firefox with the User Agent Switcher extension set to iPhone 3, and I have none of the Blackberry issues.
WPMD works by setting a cookie. This appears to be working, else I wouldn't have seen the mobile theme at all.
Does the Blackberry have a problem with the Javscript function? Not easy to tell from the phone itself - might need to drop in a JS error monitor (I was looking at one the other day).
Who'd have thought mobile dev would be so tricky!
UPDATE 1
It's a few weeks since first posting, and I will soon be following Joshua and Frederick's advice to uninstall and then reinstall the [latest version of] W3TC and I'll post my results.
I found that different browsers (both desktop and mobile) treat javascript redirect statements differently. For example:
setTimeout(function(){window.location.reload();},10)
window.location.reload();
location.reload();
The three lines above effectively perform the same action (slightly different implementations, depending on your needs), but I had varying success across browsers using each one - Chrome worked with one, Firefox another, etc.. Unfortunately, I still could not get the Blackberry browser to perform a proper automatic refresh via Javascript.
What else...so, switching between desktop and mobile using a desktop PC/browser has proven interesting. Let's say we're on the desktop version, and we switch to the mobile version of the page. We're OK so far, but then we switch back to the desktop version of the page. Still OK, but if we quickly click a link on the desktop page to go to another [desktop] page then we may find ourselves looking at the mobile version instead of the desktop version.
So, what happened there? As the page was still loading when we clicked another link, did we interrupt something? Presumably not, as the cookie would have been set and sent in the previous request from the mobile version of the page to say, e.g., "show-desktop-version = true". If we do hit F5 or the browser's 'Refresh' button (or, in fact, a link to any other page) then we do see the correct mobile or desktop version (respectively).
Another interesting thing: say we're on our mobile version (using desktop browser), and we're looking at site.com/mypage, and on the page is a link to 'View Full Site' (VFS). We click VFS once and it refreshes but we're still seeing the mobile version. So we click again - same result. So we click again, and again, and again, and again, and - oh, OK this time it switched to the full site. This cycle/process seems to occur once, and then not for a while, and then happens again.
UPDATE 2
Regarding the mobile-desktop theme switching problems, please disregard my notes in 'Update 1'. One of my switcher links (from desktop theme to mobile), e.g....
View Mobile Site
...was using the query parameter (as you can see). I had used this technique to test whether a mobile browser was preventing a proper refresh as the link pointed to the same/current URL. The switcher link should have actually looked like this,
View Mobile Site
...with just a hash to allow the link to be clickable, while allowing the Javascript function to do its magic (update cookie, reload page).
Problem resolved.
(W3TC + WPMD compatibility still an issue for me - will post updates).
I am the developer of the WP Mobile Detector.
The issues you describe are exactly what happens when the W3 Total Cache is installed. For whatever reason, sometimes it is necessary to deactivate and delete the W3 Total Cache.
Two customers that I can remember reported issues even when the W3 Total Cache was disabled. Once it was removed, it fixed the problem. They then re-uploaded W3 Total Cache, made the changes at the link you posted, and seemed to be fine.
For whatever reason these issues seem to be more prevelant with newer versions of the W3 Total Cache. I need to get with Frederick (the creator of W3 Total Cache) and make sure the plugins play nice together.
Make sure to clear your cache on the BlackBerry device as well.
Without evaluating the plugin there are some things to consider here. First W3TC attempts by default to set a cookie to properly determine which page cache to use for user agent groups for smartphones and less-smart phones; it keeps unique caches for each because of the popularity of mobile theme plugins prior to popularity of responsive web design and progressive enhancement.
The user agent groups can be disabled or used to redirect visitors to another page or theme. The next release also removes the need for the cookie when user agent groups are set. A future release will also allow cookies to be used to unique cache user requests as well.