This is the current rebuild of my site, click to see the Old version (before you tell me I know that the url is new.letorey.co.uk that is because the ssl certificate works for this but not old).
The <head>
HTML element helps describe to the browser what is going on in a web page. Here I describe what those things are, what they do, and why they are important.
The following tags must be in the <head>
and in the correct order.
The absolute first thing in the page tells the browser what character set to use. This has to go first as the browser needs to know what to use for every proceeding element.
<meta charset="utf-8" />
The title, or name, of the page is used for:
<title>What's going on in the (HTML) head</title>
This tells the browser how wide to set the content and makes the page responsive. There are two other attributes that are also essential and without you may fail accessibility checks, they are initial-scale
and user-scalable
.
<meta
name="viewport"
content="width=device-width, initial-scale=1, user-scalable=1"
/>
The next element are not essential but really should be included to aid with search and understanding.
This <meta>
element is used to help with discoverability and says who wrote the page/content.
<meta name="author" content="Dave Letorey" />
This <meta>
element is used to help with discoverability and understandability. It is often displayed in listings, such as search results to give more context about the content.
<meta
name="description"
content="The description of the page can improve SEO and understanding of what the page is about"
/>
In order for your site to be indexed by search engines and appear in the search results you need to let them know which pages to be included. This is usually done with a robots.txt
file. You can also override this file with a robots
meta tag, which can exclude individual pages.
<meta name="robots" content="noindex, nofollow" />
noindex
- do not index this pagenofollow
- do not follow any links on this page and index themThis meta tag allows you to set a theme colour for your site this may effect the chrome of the browser and other elements, but generally this is added via manifest.json
.
<meta name="theme-color" content="#ff0000" />
Metadata can be added to your page so that when a link is shared on social platforms the link would show more details about the page. All platforms, except Twitter, use Open Graph metadata.
There are many social media fields the most important are:
website
<meta property="og:title" content="Title of post" />
<meta property="og:type" content="website" />
<meta property="og:url" content="https://letorey.co.uk/path-to-post" />
<meta property="og:image" content="https://letorey.co.uk/images/image-of-post.png" />
<meta property="og:description" content="Brief description of the content" />
Twitter has it's own rules that differ from every other social platform. The main being that is has a twitter:card
property, which has a number of setting to do with the content need to be output:
summary
- added a card with a square imagesummary_large_image
- adds a large rectangular imageapp
- for linking to an Appplayer
- for linking to rich media, such as video, audio, etc<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="Title of post" />
<meta name="twitter:description" content="Description of your content here" />
<meta name="twitter:site" content="@yourusername" />
<meta name="twitter:image" content="https://letorey.co.uk/images/image-of-post.png" />
<meta name="twitter:creator" content="@yourusername" /><!-- optional if sames as twitter:site -->
<link>
elementsThe link element is used to load in external resources that are not part of the content, such as icons and stylesheets.
This is a tiny little image that appears in the browser tab, it is a representation of you website/company usually, but can also be dynamic.
<link rel="icon" type="image/svg+xml" href="images/favicon.ico" />
Other icons can be loaded into the head using the <link>
element these are used to add icons to devices such as phones. They can also be added in the mainfest.json
file.
In this example different icons are loaded for different resolution devices.
<link rel="apple-touch-icon" sizes="144x144" href="images/icon144.png" />
<link rel="apple-touch-icon" sizes="114x114" href="images/icon114.png" />
<link rel="apple-touch-icon" sizes="72x72" href="images/icon72.png" />
<link rel="apple-touch-icon" href="images/icon57.png" />
<link rel="icon" href="images/icon32.png" />
As previously mentioned the manifest.json
file is used to load in the settings for the website or web app, such as:
<link rel="manifest" href="manifest.json" />
CSS is used to change the look and layout of a website and this can be loaded in as a resource alternative the styles can be written inline in the head.
<link rel="stylesheet" href="styles.css" />
<style>
elementsThe CSS can also be written inline in the head, this has the advantage that a separate request does not need to happen to load the styles, but it does need to be added to every page. This is often added for essential styles and means the styles are added strainght away rather than waiting for the style to be downloaded (fetched), although once fetched the styles will be stored in the browser (cache).
<script>
elementsThe <script>
element can be used in two ways, to inline some JavaScript or to load a JavaScript file.
JavaScript adds interactivity to a website, for example making things happen when a user clicks on things.
Inline JavaScript allows you to have things happen immediately instead of waiting for a script to load. In this example a class is removed from the documentElement (<html>
element on a website), this i used to style things differently for browsers that have JavaScript enable.
<script>
document.documentElement.classList.remove("no-js");
</script>
Alternatively JavaScript can be loaded as a resource. The <head>
is not the only location to load a JavaScript file this can also be done at the very bottom of the HTML file just before the closing <body>
element. This is done to make sure that the parsing of the JavaScript does not stall the painting of the rest of the page.
<script src="javascript.js"></script>
Alternatively a defer
attribute can be added to the <script>
element, this will make sure that the rest of the page is loaded/painted before the JavaScript is parsed and has the same effect as adding before the closing <body>
element.
<script defer src="javascript.js"></script>