Image lazy loading and width/height checker
Image lazy loading checker: paste HTML to test every img tag for width and height, lazy loading on the likely LCP image. Free, runs in your browser.
humans.txt generator: build a humans.txt file with TEAM, THANKS and SITE sections from the humanstxt.org template. Free, runs in your browser.
Runs entirely in your browser. Nothing you enter is uploaded, logged or stored.
Save it as humans.txt (lower case, UTF-8) in your site root. Optional, in the page head:<link rel="author" href="/humans.txt">
A humans.txt file is a short text file that says who made a website. This humans.txt generator writes one in the layout of the humanstxt.org quick start template, from a form, in your browser. Nothing you type is sent anywhere.
A plain text file with up to three sections, each opened by a comment-style heading, which is how the standard’s own template separates them:
Developer: Jane Doe. Contact goes on a Site: line, the handle on Twitter: and the city on
Location:, matching the template’s labels. A blank line separates people.Name: line for each name or URL you list.Last update: in YYYY/MM/DD form, then Language:, Standards:,
Components: and Software: for whatever you fill in.Lines inside a section are indented with a tab. Empty fields and empty sections are left out, so the file only states what you entered. Line breaks typed inside a field are collapsed to spaces, because each fact in the file sits on its own line.
The generator raises three notes, all advisory:
A last update value that is not a date is reported and left out of the file.
The form opens with one person, Developer Jane Doe in Lisbon, Portugal, a thanks line for “The Open Source community”, English as the language and “HTML5, CSS3” as the standards. With the date set to 26 September 2026 it writes:
/* TEAM */
Developer: Jane Doe
Location: Lisbon, Portugal
/* THANKS */
Name: The Open Source community
/* SITE */
Last update: 2026/09/26
Language: English
Standards: HTML5, CSS3
No notes appear. Type jane@example.com into the contact field and a Site: line is added under
her name, along with the spam note.
humans.txt, in lower case, as the standard requires.<link rel="author" href="/humans.txt"> to the page head. The standard’s
example uses a relative humans.txt; a leading slash makes the link resolve to the root file
from any page, not just the home page.The standard also offers humansTXT buttons to link the file from your footer.
Humans.txt or humans.TXT is not the file the standard describes, which
is always lower case.A plain text file at the root of a site that credits the people behind it. The humanstxt.org standard describes it as a place to list each person involved, with their role, name and contact details, plus optional information about the site itself, such as its last update, language and the software used to build it.
In the root of your site, next to robots.txt, so it loads at yourdomain.com/humans.txt. The standard says to name it humans.txt, always in lower case, and to save it UTF-8 encoded so names with accents or other scripts display correctly.
No. The standard lists it as something you can also do. It shows the reference as a link element with rel set to author in the page head. This generator suggests an href of /humans.txt, which points at the root file from any page on the site.
None of the sources behind this tool describe any search ranking effect from humans.txt, and the standard itself does not claim one. It is a credit file for people. Treat it as a courtesy to your team, not a search tactic.
Only if you accept the risk. The standard warns that you may have to deal with spam if you include email addresses. A link to a contact form works as the contact value instead, and the generator flags any email address it finds.
Image lazy loading checker: paste HTML to test every img tag for width and height, lazy loading on the likely LCP image. Free, runs in your browser.
Noindex, canonical and sitemap conflict checker: see where one page's three signals contradict Google's own guidance. Free, runs in your browser.
Open Graph tag checker: tests pasted og meta tags for the four required properties, relative URLs, duplicates and og:type. Free, runs in your browser.
Meta viewport tag validator: checks the content string for unknown keys, width=device-width and zoom blocking under WCAG 1.4.4. Free, runs in your browser.