----Main criticisms ----
Final HTML (DOM) size is significantly larger than initially delivered HTML (1.11kb larger, or 0.5% of total HTML).
Typically this is due to over-reliance on JavaScript for generating content, but increases can also happen as a result of browsers normalizing HTML structure as well. Common issues such as JavaScript errors and third-party network delays and outages can present potential single points of failure.
--------------------------
Make the following changes to improve accessibility:
SERIOUS Elements Must Have Sufficient Color Contrast More Info
Fix any of the following: Element has insufficient color contrast of 4.17 (foreground color: #1474b8, background color: #ebebeb, font size: 8.3pt (11px), font weight: bold). Expected contrast ratio of 4.5:1<span itemprop="name">Other XenForo discussions and feedback</span>
----------------------------
The main thread was blocked for 359 ms
When files block the main thread, users are unable to interact with the page content. Typically, parsing and executing large JavaScript files, as well as running long JavaScript tasks can block the main thread and should be avoided. These files had high thread blocking times:
67 ms:
https://xenforo.com/community/js/xf/preamble.min.js?_v=99f58bb3
377 ms:
https://xenforo.com/community/js/xf/core-compiled.js?_v=99f58bb3
----------------------------
28 static files have inadequate cache settings.
Cache settings can instruct browsers and intermediaries to store recent versions of a site's static files (JavaScript, CSS, Images, fonts...) for reuse, reducing page weight and latency.
--------------------
Images within the initial viewport are being lazy-loaded.
When images are lazy-loaded using loading="lazy", they will be requested after the layout is established, which is too late for images in the critical window.
/community/data/avatars/m/0/521.jpg?1701362629
----------------------
9 externally-referenced CSS files are blocking page rendering.
By default, references to external CSS files will block the page from rendering while they are fetched and executed. Sometimes these files
should block rendering, but can be inlined to avoid additional round-trips while the page is waiting to render. Sometimes, such as with stylesheets that are only used for loading custom fonts, inline or async CSS can greatly improve perceived performance.
---------------------
1 JavaScript file is blocking page rendering.
By default, references to external JavaScript files will block the page from rendering while they are fetched and executed. Often, these files can be loaded in a different manner, freeing up the page to visually render sooner.
/community/js/xf/preamble.min.js?_v=99f58bb3
Q: are any of these "suggestions" valid ?
It's minorly interesting I had to adjust my contrast on my monitor today to see the slightly darker blue background and webpagetest complained about the colo(u)r differentiation.
