JavaScript: Difference between revisions
mention missing content and hidden content |
frameworks are not the only generator |
||
| Line 45: | Line 45: | ||
===Performance=== | ===Performance=== | ||
{{See also|Bloatware}} | {{See also|Bloatware}} | ||
If | If the DOM-tree is dynamically generated by JS (such as [[wikipedia:Web_framework|frameworks]]), the user must wait longer before the browser can display content. This is because HTML+CSS can be parsed and rendered incrementally (immediately as the bytes arrive to the client), while JS must (typically) be completely parsed and then executed. | ||
If the JS fails to load for any reason, the user is left with no content.<ref name=":0" /><ref>{{Cite web |last=Luu |first=Dan |title=How web bloat impacts users with slow connections |url=https://danluu.com/web-bloat/ |access-date=2026-04-13}}</ref> If the page relies on JS to display content from the main document, the browser will waste bandwidth and time downloading data that won't be shown to the user; this is the case of sites with "splash screens" or "spinners" that use CSS to hide content until it's "ready to be seen" and then un-hidden by JS.<ref>https://github.com/Rudxain/uBO-rules/blob/b1086023e7db98dee55d425edc20722e641dd4b8/rx.abp#L71-L75</ref> | If the JS fails to load for any reason, the user is left with no content.<ref name=":0" /><ref>{{Cite web |last=Luu |first=Dan |title=How web bloat impacts users with slow connections |url=https://danluu.com/web-bloat/ |access-date=2026-04-13}}</ref> If the page relies on JS to display content from the main document, the browser will waste bandwidth and time downloading data that won't be shown to the user; this is the case of sites with "splash screens" or "spinners" that use CSS to hide content until it's "ready to be seen" and then un-hidden by JS.<ref>https://github.com/Rudxain/uBO-rules/blob/b1086023e7db98dee55d425edc20722e641dd4b8/rx.abp#L71-L75</ref> | ||