Note that large web pages being retried over an IPIP tunnel via UCSD
are bound to encounter packet loss, which will greatly impact performance.
It's not a high bandwidth path, folks. And never will be.
- Brian
On Tue, May 07, 2019 at 06:56:44PM -0500, David McAnally via 44Net wrote:
Date: Tue, 7 May 2019 18:56:44 -0500
From: David McAnally <david.mcanally(a)gmail.com>
To: AMPRNet working group <44net(a)mailman.ampr.org>
Subject: Re: [44net] Google indexing
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