Hopefully someone can help.
Pagespeed insights will only show an old 'broken' version of my website. It's been completely fixed and updated now, but it still will not change on pagespeed insights.
I have cleared every cache imaginable and even downloaded firefox - but still the same issue. Strangely enough, it's also the same problem with gtmetrix and pingdom. I even tried with my wifes laptop and still nothing.
The only way i can get the updated reading is by using an incognito firefox window on my mobile phone - after downloading the firefox application. It's been so difficult to get help, because every person i speak to tries it on their computer and it works fine. It just seams to be a problem with all my devices.
Is there some kind of pagespeed insights cache i need to clear? I'm lost for ideas now and cannot think of anything else!
Related
PageSpeed Insights (https://pagespeed.web.dev/) is no longer working on my PC. It just spins. I've tried using multiple different URL's to analyze. I've tried it in Incognito. I've cleared cache. I've reinstalled Chrome. I've even tried it with the Edge Browser.
This seems to correspond to the new Pagespeed Insights Release. I've never had a problem with this until recently. This has always worked before.
I don't know if it's a cookie issue, or the new PageSpeed Insights release, maybe a new firewall issue that cropped up. Or, does it now require a KEY or something? Or, could my IP have gotten blocked by Google for this?
Note: I can run Lighthouse from Inspect. That works. But not https://pagespeed.web.dev/
Windows - Chrome is up to date Version 96.0.4664.45 (Official Build) (64-bit)
I'm baffled. It's probably something obvious but I can't figure it out.
Any ideas out there?
Thanks,
Bob
For us, the lighthouse report in Chrome dev tools is not working behind a VPN. It was working earlier. Not sure what is the issue.
We were looking to test new page templates on the dev environment. Unfortunately, the PSI is not warming on staging on a VPN
EDIT This issue seems to only affect Chrome and Safari on my Macbook Pro. I can't replicate this issue on other computers and browsers. I thought it might have been malware or virus, so I reformatted my Macbook. Didn't fix the issue All of a sudden, I am running into this issue when developing on my local server as well with MAMP. Assets are missing everywhere and some pages fail to load all together
I've noticed recently when I refresh my Vue SPA with the cache disabled, the page tends to look messed up with missing images/resources.
When I check the console, I see a lot of ERR_CONNECTION_REFUSED for resources that are definitely there. If I refresh the page, the errors go away. It tends to happen after I clear cache and load up the webpage for the first time, or if I disable cache in the developer console.
It turns out there had recently been a DDos attack against my IP address so my hosting service forced rate limit connections to my IP address. So if you ever run into the same issues, check with your hosting company first.
Not sure why, but my the background on my site isn't loading (or, when it occasionally does, it's taking forever) on mobile browsers. I've tested it on both an iPhone 4S and an iPad 2. Any suggestions on how to fix this? The problem started happening out of nowhere.
The site is http://fanbeat.com.
Thanks.
It looks like your server is quite slow. On my cable internet connection (desktop computer mind you) it took 1.5s to download, which is crazy for a 130Kb file.
Here's a smaller version of your background image to try. It's only 40K.
I am having an SSL issue, but it only appears to be happening in Google Chrome.
I've checked with Firefox, Safari and Internet Explorer and there fine.
Does anyone know what is wrong? I've tried it on a BLANK page and Chrome still says there is an issue. Screenshot:
If anyone can help that would be much appreciated!
I think you may be referring to content that does not belong to your domain (ex. images) and that are retrieve from another location on the internet.
Since the browser has to get them via a http:// request on the other site, it warns you that all the content does not come from your website overs the SSL connection.
Did you tried the blank page after accessing another page of your site? Or just after launching chrome?
I run into this exact problem and solved it this morning. Two things:
Clear Google Chromes's browser cache data
Make sure your app doesn't have references to external resources that is none-https
Hope this helps,
Ray.
I'm developing a cross-platform NPAPI+XPCOM extension for Firefox and Google Chrome (Windows, Linux and Mac). I was wondering if anyone could enlighten me on the best practices of handling component crashes.
As I understand it, currently Mozilla's Crash Reporter submits mini-dumps and crash reports created to Mozilla Dev. I experimented with blocking SIGSEV to Firefox and creating my own core in the plugin code. Although that works just fine, I'm sure I'm not supposed to do that.
And Google Chrome doesn't even seem to create any core dumps! Any suggestions?
The firefox crash report database is publicly searchable, so you don't have to do your own handling. If you ask nicely (i.e. prove you're the plugin author) I'm sure they'll even give you the minidumps from your plugin's crashes.
This is awfully late, but yeah, don't do that. You will wind up catching a lot of things that aren't just your plugin, and you will screw up our crash stats. You should be able to find your plugin crashes in our crash report site. If you need better reporting, you can file a bug on us and we should be able to help you.