Oops!
I don’t know why all of a sudden my phone picked a different address. Strange. Anyway. Sorry.
Roger VA7LBB
On May 8, 2019, at 18:07, Roger ve7wwd@rezgas.com wrote:
Hi all, Just a reminder that Google has already told me where the issue originated. It’s not with content. It’s not with speed. It’s not the time my site has been up. It’s an anomaly between google and me. They just can’t or won’t tell me what that anomaly is. But it has nothing to do with content or anything like that.
Roger.
On May 7, 2019, at 16:56, David McAnally david.mcanally@gmail.com wrote:
Roger,
May I suggest looking at your web site home page load / rendering performance? I tried loading your page in the Google Page speed Insights https://developers.google.com/speed/pagespeed/insights/ tool. It will not complete loading your URL for analysis, returning the much too common NO_FCP error message. (see their tool's references for details on FCP. I was able to load your URL in the analyze.websiteoptimization.com tool, which shows the page is almost 3MB in size, mostly images and javascript, which may be slowing the page load/rendering. While 3MB may not seem all that much in today's fast networks, home page size and load times have been known to cause crawling index systems to skip the site due their limited budget in time and resources. Poor performance scripting can be an issue too. If your network route to users, or in this case analysis tool, crosses a slower network gateway, the size of your page and content rendering performance could have even more impact. Don't know if improving page performance will make Google indexing happier, but can't hurt to try.
At one time I had access to better tools for web site analysis, but I've retired, so I no longer get to play with that stuff.
Regards, David M. WD5M
Now that I know where to look.. PMTU has caused me a lot of headache lately. I believe it could be the problem. Sending large packets to 44.135.179.28 yields no reply. tracepath does send back need to frag, but when TTL expires at amprgw.ucsd.edu. I believe amprgw.ucsd.edu should send back need-to-frag for higher TTLs as well.
root@atl:~# ip route get 44.135.179.28 44.135.179.28 via 169.254.169.254 dev ens3 src 44.38.10.1 cache root@atl:~# ping -M do -s 1462 44.135.179.28 PING 44.135.179.28 (44.135.179.28) 1462(1490) bytes of data. ^C --- 44.135.179.28 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3076ms
root@atl:~# tracepath 44.135.179.28 >/dev/null ^C root@atl:~# ping -M do -s 1462 44.135.179.28 PING 44.135.179.28 (44.135.179.28) 1462(1490) bytes of data. ping: local error: Message too long, mtu=1480 ping: local error: Message too long, mtu=1480 ^C --- 44.135.179.28 ping statistics --- 2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1028ms
I think clearing this up would promote better communication across the gateway.
Regards, Scott.
On Wed, May 8, 2019 at 10:02 PM Roger va7lbb@rezgas.com wrote:
Oops!
I don’t know why all of a sudden my phone picked a different address. Strange. Anyway. Sorry.
Roger VA7LBB
On May 8, 2019, at 18:07, Roger ve7wwd@rezgas.com wrote:
Hi all, Just a reminder that Google has already told me where the issue originated. It’s not with content. It’s not with speed. It’s not the time my site has been up. It’s an anomaly between google and me. They just can’t or won’t tell me what that anomaly is. But it has nothing to do with content or anything like that.
Roger.
On May 7, 2019, at 16:56, David McAnally david.mcanally@gmail.com wrote:
Roger,
May I suggest looking at your web site home page load / rendering performance? I tried loading your page in the Google Page speed Insights https://developers.google.com/speed/pagespeed/insights/ tool. It will not complete loading your URL for analysis, returning the much too common NO_FCP error message. (see their tool's references for details on FCP. I was able to load your URL in the analyze.websiteoptimization.com tool, which shows the page is almost 3MB in size, mostly images and javascript, which may be slowing the page load/rendering. While 3MB may not seem all that much in today's fast networks, home page size and load times have been known to cause crawling index systems to skip the site due their limited budget in time and resources. Poor performance scripting can be an issue too. If your network route to users, or in this case analysis tool, crosses a slower network gateway, the size of your page and content rendering performance could have even more impact. Don't know if improving page performance will make Google indexing happier, but can't hurt to try.
At one time I had access to better tools for web site analysis, but I've retired, so I no longer get to play with that stuff.
Regards, David M. WD5M
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
-
Roger -
Scott Nicholas