Noticed something strange by chance when running a Google Insights speed test on my site. For some reason, it slows down my site almost to a halt and maxes out my server resources. Talking to the host, they noticed that the test generates loads of 404s that are all images. This is very strange since the images are clearly there. They only appear as 404s when running the speed test.
I have done some testing, deactivating every plugin on all of my three sites and it happens on all of them. The only thing they have in common really is that they use the same theme and, of course, that they are running on the same server. The host says it's not on their side though.
I have reached out to the support for the theme, but still want to check with you guys too if this is something you have ever come across and if someone has any experience with this?
I suspect there is something in the code causing this to happen, but I really have no clue. It only seems to happen with Google Insights too, not when I run a test with GTMetrix for example.
Related
Google Optimize keeps saying it can't verify my GA or Optimize tag. I've set up hundreds of Optimize scripts through GTM and never have this issue. I know the usual troubleshooting techniques. Any idea why this would be happening? site is missionbayresort.com
We have a React app. Lately we are experiencing an issue which only appears in "developer" mode. Two of the modules causes the app to become unresponsive for several seconds. The cpu works hard and memory usage spikes. If I change the settings in Webpack to "production" it works smoothly.
I have tried doing performance recordings in devtools, but I am unable to interpret anything useful from it.
I have tried making the Webpack configuration as simple as possible without any signs of improvement.
I am not posting any code since I don't really know where the issue(s) might be. But maybe someone can give some ideas about where to look or how we can pinpoint the issue.
Thanks to #noitse for pinpointing the problem. I removed "redux-immutable-state-invariant" and that fixed the problem.
Does anyone know what this error even means? It is non-descript does not really lend itself to a debugging path. This occurs when testing page speed in google Lighthouse.
Facing the same issue and raised to the lighthouse Github repo.
Refer: https://github.com/GoogleChrome/lighthouse/issues/11173
They are able to reproduce it and will be fixing this soon as part of this ticket: https://github.com/GoogleChrome/lighthouse/issues/11154
Could be a variety of factors. Post the URL along with the question - easier to debug.
Speed index - has a blocker, if anything takes more than 10secs, LightHouse will time-out.
If you are using CDN - I have experience sporadic errors on LightSpeed due to cache consistency issues.
Make sure there are no blockers on your site, and you run this on a new/private window. No browser extensions should be enabled.
LightHouse uses the same underlying API. Try using PSI - https://developers.google.com/speed/pagespeed/insights/. Also, try the web version of lightspeed: https://web.dev/measure/. If you get same results - something on your end. If you get different results, something with your browser/ test.
Try running LightHouse on Mobile and Desktop.
I was running two different versions of my app with the same api_version number, and I started receiving Database locked exception. I've closed both apps, removed both from the app engine launcher, and then reloaded the one i'm currently working on; and I'm still getting the same error.
I've been googling it for 30 minutes, and it doesn't seem like there is a lot of information on this topic specifically related to GAE.
I would like to know how to go about fixing the issue, but more than that, I'd like to know what's causing it in the first place.
I gave to 2 api versions different version numbers but the same api number with the hope that I'd be able to run them concurrently and have them share a datastore instance, but if its displaying this behavior locally, I'm sure its not going to work when deployed. I suppose I have less of an understanding of the versioning than I thought. If anyone has a brief explanation of that process, what causes locking and how to fix that would be great. Thanks!
EDIT:
'api_version' refers to google's api for app engine; nothing to do with one's personal application. still trying to figure out how to deal with 'version' and #endpoints.api. What's the diff?
My current default browser is Chrome (dev). I'm using VS2010 and Silverlight4, with ASP.NET MVC3. I don't seem to have the problems with debugging that I've seen others have. My main complaint is that I regularly have to clear my browser cache to get the latest version of my app to show up. Sometimes I have to clear it two or three times. I've taken to changing the background color of certain elements just to be sure whether I've got the actual latest changes.
Are Firefox or IE better in this regard? Is there are trick to make my latest version always appear?
Too lazy to do fiddler.
Seems I hadn't googled very well before, this article seems to be precisely what I wanted
http://codeblog.larsholm.net/2010/02/avoid-incorrect-caching-of-silverlight-xap-file
via this discussion which has other options and some useful discussion https://betaforums.silverlight.net/forums/p/11995/449355.aspx
Unfortunately, that part of my project has been on hold for a bit, so I haven't tried it out yet.
Like you, I use Chrome for my main browser, and I don't use IE for any regular browsing. But I do use IE for Silverlight development, for this reason and others. I rarely if ever have trouble with the IE cache holding onto outdated versions of my XAP file, but this happens pretty regularly with FireFox and Chrome. In addition, depending on how I closed my previous debug session, when I start up a new one, FireFox and Chrome frequently open up my previous tab(s) in addition to the one that I'm actually trying to debug. Consequently, IE is (for me) the cleanest browser to actually debug with.
This isn't really an answer -- just an observation. Sorry :-).
Have you tried investigating why this is happening using Fiddler or a similar HTTP debugging tool? Personally I've never been able to debug Silverlight in Chrome so I usually have to force IE when debugging. But I never have the problem of a stale application. I'd check Fiddler to see if you can isolate the issue. It's probably not directly related to Silverlight.
Your probleme looks like a lot like a cache configuration issue. The web server is often configurated rather aggressively concerning caching of static files, as the XAP.
So the response header are probably set in a way that maximize browser caching.
You could change the webserver configuration to prevent client side caching of the XAP file.
Don't forget to remove these setting in production, however.