The interesting one for me was measuring error rates (if your JS heavy web page calls the server 100 times, if two users try to load and one gets 500 that should be 50% error rate but it looks like <1%
So it feels like a piece of JS that says I have seen everything that should load load ok, then reports home with the page seems a good idea.
Probably quite doable - can JS see the network load like web developer tools ?
JS errors, page size, HTML errors, bad web design, CSS problems, SSL and broken layout has nothing to do with organic results or SEO and it is not proved that it affects your organic result position.
Even if it does, in-page problems doesn't affect your result not even by 1%. 99% is backlinks and their quality (or course).
Example: check techcrunch.com and debug/inspect their homepage. 15 JS errors, 6mb in size, no Description/Keywords, awful <title>, bad HTML elements. Can you even remotely beat them in the keyword "startup news"? No way. No matter how hard you will try to "SEO" your website.
I will tell it again. "SEO" was always a gimmick marketing thing. It's crazy that even now ppl don't understand that the only thing that matters are quality backlinks, as a result of quality content.
Exactly! And I think the problem with an SEO guide to engineers in particular, is that it ends up being a list of technical things. Things that are easy to quantify and that are black or white. Those are marginal. Yet an engineer can increase the score in some tool from X to 1.257X so they’re happy.
It’s much harder to write a guide on how to engage and delight your audience, and how to get the attention of other sites and the authority and trust to get linked to.
There can’t be a generic solution to “am I done loading everything” (see the halting problem). And tightly coupling every request to a list feels awfully fragile. I think the real problem is making 100 api calls to load a page...
So it feels like a piece of JS that says I have seen everything that should load load ok, then reports home with the page seems a good idea.
Probably quite doable - can JS see the network load like web developer tools ?