Our page titles arrive 32 nodes into the head, after ten font preloads and fourteen scripts
Nobody reads the <head> . It is assembled by a framework from a metadata object, it works, and you move on. I had never actually counted what ours contains, so I downloaded all 76 public pages of Nakodo and parsed every node between <head> and <body> . curl -s https://nakodo.app/sitemap.xml \ | grep -o '<loc>[^<]*</loc>' | sed 's/<[^>]*>//g' > urls.txt while read u ; do curl -s -H…
The structure of page titles in the Nakodo website is analyzed in detail. A total of 4,569 nodes are present in the 76 page heads, with the title being the 32nd node on 72 pages. The first 31 nodes are part of platform plumbing, followed by ten font preloads, fourteen scripts, and various meta tags. The majority of the page weight is allocated to 1,354 links, which are predominantly preloads (740 of them fonts).
The analysis reveals that the title is relatively insignificant in terms of page size, accounting for only 1.10% of the median page size. The site's metadata is largely consistent, with only minor variations in locale and social media tags. Some fields, like keywords and article:modified_time, are present but do not serve a practical purpose.
The homepage and pricing page are unique in their omission of font preloads and other optimizations, resulting in a smaller performance impact during first paint. The analysis highlights the importance of properly identifying and optimizing the head of a webpage, as it plays a crucial role in rendering and performance.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.