no, they're not and cannot be equivalent in speed. JavaScript requires additional CPU cycles, which by definition take resources and more time. The actual latency will vary based on JS in question, site, etc.
-
-
Replying to @igrigorik @adamheatonuk and
Here is a good example to guess how fast it is. This website http://bugs.chromium.org migrated very recently to a new UI and now is using the shadowRoot to store all the text contents. Only Googlebot evergreen can index it. Currently, there are ~20/30 pages indexed per day....
1 reply 0 retweets 0 likes -
Replying to @check_ca @igrigorik and
Why is this so hard to talk about this issue? Let's face it, some people are using web components massively in production and this *performance* issue cannot be denied. SSR won't really help to fix this since HTML doesn't offer any solution to serialize these contents /cc
@JohnMu1 reply 0 retweets 0 likes -
Replying to @check_ca @adamheatonuk and
sorry, missed this.. How are you measuring 20/30 pages per day?
1 reply 0 retweets 0 likes -
Replying to @igrigorik @adamheatonuk and
I was measuring this by looking at the search results of the "past week" during 4-5 consecutive days. I cannot measure this more precisely on my end.
1 reply 0 retweets 0 likes -
Replying to @check_ca @igrigorik and
One of the problems with that site is that's barely crawlable. For example, https://bugs.chromium.org/p/chromium/issues/list … (linked from the homepage) is blocked from crawling. We have to find the URLs linked from elsewhere on the web, it's quite inefficient & independent of the framework used.
1 reply 0 retweets 0 likes -
Replying to @JohnMu @igrigorik and
Well, this does not explain the fact that almost all pages have as title "chromium Monorail". This clearly shows there is an issue with the framework used...
1 reply 0 retweets 0 likes -
Replying to @check_ca @igrigorik and
Not necessarily. Google generates titles automatically, they're not always exactly what the page specifies (often they're also rewritten to match a query). I really think with that particular site, it's primarily a problem with normal crawling rather than anything else.
1 reply 0 retweets 0 likes -
Replying to @JohnMu @igrigorik and
(╯°□°)╯︵ɐɔ‾ʞɔǝɥɔ Retweeted (╯°□°)╯︵ɐɔ‾ʞɔǝɥɔ
But the descriptions were not better... cf this tweet I sent you some weeks agohttps://twitter.com/check_ca/status/1121561114276433920 …
(╯°□°)╯︵ɐɔ‾ʞɔǝɥɔ added,
1 reply 0 retweets 0 likes -
Replying to @check_ca @igrigorik and
If there's no description meta tag, then the site:-operator results can be a bit weird, since it's not a normal query. There are certainly things the site could do much better, but as far as I can tell, the framework isn't the problem.
2 replies 0 retweets 1 like
Contact lost... You're welcome BTW!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.