Website best practice
Every check our website scan runs, in its groups, the most serious first. Each says what good looks like, why it matters and the published guidance it comes from. Build to these and the scan finds nothing to fix.
Security
- The certificate has more than 21 days left. When it runs out every visitor sees a full-page warning. Serious. Source: Let's Encrypt: renew 30 days before expiry.
- The connection uses current encryption. Older versions have known weaknesses. Serious. Source: IETF RFC 8996: TLS 1.0 and 1.1 retired; NCSC: using TLS to protect data.
- No form sends over plain http. Anything typed into them can be read on the way. Serious. Source: W3C: Mixed Content; Chromium blog: Chrome warns on forms that send over http (2020).
- Server software still gets security fixes. Flaws found after support ends are never fixed, and the version on show tells attackers which to try. Serious. Source: OWASP Top 10: vulnerable and outdated components; endoflife.date: support dates.
- No private-looking keys in your own scripts. Anyone can read a site's scripts; a private key there can be used by anyone. Serious. Source: OWASP: secrets management cheat sheet; CWE-798: credentials written into code.
- No script library with known flaws. Attackers look for these versions because the way in is already written up. Serious. Source: OWASP Top 10: vulnerable and outdated components; Retire.js: the list of library flaws.
- Email cannot be faked: SPF. Without it anyone can send email that claims to come from your address. Serious. Source: IETF RFC 7208: SPF; NCSC: email security and anti-spoofing.
- Email cannot be faked: DMARC set to act. DMARC tells mail services to reject email that fakes your address. Serious. Source: IETF RFC 7489: DMARC; Google: email sender guidelines.
- The plain http address sends visitors on to https. A visitor who types the address without https should never stay on an unprotected page. Important. Source: OWASP: transport layer security cheat sheet; IETF RFC 6797 §7.2: send http on to https.
- The "always use https" header is sent. Without it, the first visit can be pushed onto an unprotected connection on public wifi. Important. Source: IETF RFC 6797: HTTP Strict Transport Security; OWASP: HTTP security headers cheat sheet.
- The "always use https" header lasts at least six months. Browsers forget the rule when it runs out, so a short time gives little protection. Important. Source: Mozilla: web security guidelines (six months at least); hstspreload.org: Google's preload list rules (a year).
- A content security policy is sent. This is the main protection if someone manages to slip a harmful script into a page. Important. Source: W3C: Content Security Policy Level 3; OWASP: content security policy cheat sheet.
- Other sites cannot show your pages inside theirs. A hostile site can lay your page under its own buttons and trick visitors into clicking. Important. Source: IETF RFC 7034: X-Frame-Options; OWASP: clickjacking defence cheat sheet.
- No insecure file is loaded by a secure page. Browsers block or warn about these, and they can be changed on the way. Important. Source: W3C: Mixed Content.
- Nothing is loaded from a test server. A test server is usually less protected, and it shows where your unfinished work lives. Important. Source: OWASP Top 10: security misconfiguration.
- Cookies carry their three safety marks. Secure, HttpOnly and SameSite stop a cookie being read by scripts or sent from other sites. Important. Source: IETF RFC 6265: cookies and their marks; MDN Observatory: tests and scoring.
- The content security policy does not allow everything. A policy that allows everything gives the feeling of protection without the protection. Minor. Source: W3C: Content Security Policy Level 3; Google research: CSP is dead, long live CSP (2016).
- File-type guessing is switched off. Without it a browser may treat an uploaded file as a script. Minor. Source: WHATWG Fetch standard: X-Content-Type-Options; OWASP: HTTP security headers cheat sheet.
- A referrer policy is set. Full addresses, which can hold search words or account details, may be passed to every outside site. Minor. Source: W3C: Referrer Policy; OWASP: HTTP security headers cheat sheet.
- A permissions policy is set. It stops an outside script from asking visitors for their camera or location. Minor. Source: W3C: Permissions Policy; OWASP: HTTP security headers cheat sheet.
- No protection header is sent twice. Two copies that disagree can make a browser ignore both. Minor. Source: IETF RFC 9110 §5.3: a header sent more than once; IETF RFC 6797 §8.1: only the first HSTS header counts.
- No link points at a plain http address. Visitors who follow them leave the secure connection, if only for a moment. Minor. Source: OWASP: transport layer security cheat sheet.
- Scripts from other companies carry an integrity check. If the other company's server is broken into, your visitors run whatever it serves. Minor. Source: W3C: Subresource Integrity.
- Server and software versions are not shown. A version number tells attackers which known flaws to try. Minor. Source: OWASP testing guide: fingerprint the web server; OWASP: HTTP security headers cheat sheet.
- Your own source maps are not published. Source maps hand out your original code, comments included. Minor. Source: OWASP testing guide: review page content for leaks.
- A security contact file exists. It tells someone who finds a flaw how to reach you, instead of telling the world. Minor. Source: IETF RFC 9116: security.txt.
Privacy
- A cookie choice is offered. UK and EU law needs a visitor's consent before tracking cookies are set. Serious. Source: UK law: PECR regulation 6, consent for cookies; ICO: guidance on cookies.
- No tracking cookies before a choice is made. Consent has to come before the tracking, not after. Serious. Source: UK law: PECR regulation 6, consent for cookies; ICO: guidance on cookies.
- No tracking cookies after "reject". Tracking a visitor who said no is what regulators fine for. Serious. Source: UK law: PECR regulation 6, consent for cookies; ICO: guidance on cookies.
- No advertising companies contacted when a visitor says no. Each request tells the advertising company that this visitor was on your page. Serious. Source: UK law: PECR regulation 6, consent for cookies; ICO: guidance on cookies.
- No session-recording tool when a visitor says no. These tools record mouse moves, clicks and sometimes what is typed. Serious. Source: ICO: guidance on cookies; Princeton: session-replay scripts take personal data (2017).
- A privacy policy is linked. The law needs one wherever personal data is collected. Serious. Source: UK GDPR article 13: what people must be told; ICO: the right to be informed.
- "Reject" is on the first screen of the cookie choice. The UK regulator expects rejecting to be as easy as accepting. Important. Source: ICO: guidance on cookies; EDPB: cookie banner taskforce report, 2023.
- Videos use the player's privacy mode. The normal player tracks a visitor before they press play. Important. Source: YouTube Help: privacy-enhanced mode.
- Your pages talk to a modest number of outside companies. Each one learns your visitor's address and which page they are on, and each is one more company to trust. Minor. Source: HTTP Archive Web Almanac: third parties.
- Fonts are not fetched from Google's servers. A German court fined a site for this in 2022. Serving the same font yourself costs nothing. Minor. Source: Munich Regional Court, 20 January 2022, 3 O 17493/20.
Speed
- Main content shows within 2.5 seconds. Google counts this in search ranking; visitors leave slow pages. Serious. Source: web.dev: Largest Contentful Paint; Google Search Central: page experience.
- The page does not jump while loading. A jumping page makes people tap the wrong thing. Google counts it in search ranking. Important. Source: web.dev: Cumulative Layout Shift; Google Search Central: page experience.
- The server starts answering within 0.8 seconds. Nothing can show until the server answers. Important. Source: web.dev: Time to First Byte.
- The homepage finishes loading within 3 seconds. Half of phone visitors leave a page that takes over 3 seconds. Important. Source: Think with Google (2016, archived copy): 53% of mobile visits leave after 3 seconds.
- The homepage weighs under 5 MB. Every megabyte is time and data on a phone. Important. Source: Lighthouse: avoid enormous network payloads.
- Scripts on the homepage weigh under 1 MB. Scripts are the slowest thing a phone handles: each must be read and run. Important. Source: V8: the cost of JavaScript.
- No menu page weighs over 5 MB. A visitor who opens it on a phone waits for all of it. Important. Source: Lighthouse: avoid enormous network payloads.
- No menu page takes over 3 seconds. Visitors judge the site by its slowest page. Important. Source: Think with Google (2016, archived copy): 53% of mobile visits leave after 3 seconds.
- Real visitors' speed, from Google. What your actual visitors experienced over the last 28 days, not one test visit. Important. Source: Chrome: the Chrome UX Report.
- The homepage loads no more than 100 files. Each file is another request before the page is complete. Minor. Source: HTTP Archive Web Almanac: page weight.
Efficiency
- Text files are sent compressed. Compression makes text files about four times smaller. Important. Source: Lighthouse: enable text compression; IETF RFC 7932: Brotli.
- Unchanging files are kept by browsers for a long time. A returning visitor should not download your logo and scripts again. Important. Source: Lighthouse: an efficient cache policy; web.dev: prevent unnecessary network requests with the HTTP cache.
- No script holds up the first view. Each one delays the first view by its download time. Important. Source: Lighthouse: eliminate render-blocking resources; WHATWG HTML: the defer and async attributes.
- Few style files hold up the first view. Each one is a wait before the first view. WordPress widgets often add one each. Important. Source: Lighthouse: eliminate render-blocking resources.
- Pictures use modern formats. WebP and AVIF are a quarter to a half smaller than JPEG and PNG at the same quality. Important. Source: Lighthouse: serve images in modern formats; Google: WebP compression study.
- No single file over 1 MB. One oversized file can be most of a page's weight. Important. Source: Lighthouse: avoid enormous network payloads.
- No heavy video starts on its own. Visitors download it whether they watch or not. Important. Source: web.dev: lazy-loading video; Lighthouse: avoid enormous network payloads.
- The newest connection type (HTTP/3) is offered. HTTP/3 copes better with phone connections that drop and resume. Minor. Source: IETF RFC 9114: HTTP/3; IETF RFC 9000 §9: connections that move networks.
- The homepage itself is not kept for days. Visitors may see an old homepage, with old prices or news, long after you change it. Minor. Source: web.dev: prevent unnecessary network requests with the HTTP cache.
- Pictures come in phone sizes. A phone downloads the full desktop picture otherwise. Minor. Source: Lighthouse: properly size images; WHATWG HTML: images and srcset.
- Pictures further down load only when needed. Pictures nobody scrolls to are downloaded anyway. Minor. Source: web.dev: browser-level lazy loading.
- Pictures state their width and height. Without a size the page jumps when each picture arrives. Minor. Source: web.dev: optimise Cumulative Layout Shift.
- Text shows while fonts load. Otherwise text stays invisible until the font arrives. Minor. Source: W3C CSS Fonts 4: font-display; Lighthouse: text stays visible while fonts load.
- No more than 8 font files. Each weight and style is a separate download. Minor. Source: web.dev: best practices for fonts.
- No more than one icon set. Each set is a whole font of icons, most never used. Minor. Source: web.dev: best practices for fonts.
- Early-connection hints for the outside hosts that matter. A hint lets the browser start connecting before it needs the file. Minor. Source: HTML Standard: preconnect (W3C Resource Hints moved here); Lighthouse: preconnect to required origins.
- Little style code goes unused. Unused style code is downloaded and read for nothing. Minor. Source: Lighthouse: reduce unused CSS.
- Scripts are minified. Minifying removes spaces and comments, often a third of the size. Minor. Source: Lighthouse: minify JavaScript.
- No file or library loaded twice. The second copy is pure waste. Minor. Source: Lighthouse: duplicate modules in JavaScript.
- No long redirect chains. Each redirect is a full round trip before the page starts. Minor. Source: Lighthouse: avoid multiple page redirects.
- Most of the script is your own. Their scripts slow your page, and you cannot control when they change. Minor. Source: web.dev: loading third-party JavaScript; HTTP Archive Web Almanac: third parties.
Code quality and upkeep
- No menu page answers "not found" or an error. Visitors who click the menu meet a dead end. Serious. Source: Google Search Central: HTTP status codes and soft 404s.
- The page language is declared. Screen readers use it to pick the voice; translators use it to offer translation. Important. Source: WCAG 2.2: 3.1.1 language of page.
- No script errors while loading. A script error can stop a menu, a basket or a form from working. Important. Source: Lighthouse: errors logged to the console.
- Script libraries still get fixes. Flaws found after support ends are never fixed, and newer parts of your site may not work with them. Important. Source: OWASP Top 10: vulnerable and outdated components; endoflife.date: support dates.
- Document type and character set declared. Without them browsers guess, and text can come out garbled. Minor. Source: WHATWG HTML: the DOCTYPE; WHATWG HTML: declaring the character set.
- Under 1,400 elements on the homepage. A large page is slower to draw and to change on every tap. Minor. Source: Lighthouse: avoid an excessive DOM size.
- Elements nested no more than 32 deep. Deep nesting slows every style calculation. Minor. Source: Lighthouse: avoid an excessive DOM size.
- No duplicate ids. Labels and links that point at an id may land on the wrong element. Minor. Source: WHATWG HTML: an id must be unique.
- Few styles written onto elements. Styles scattered on elements are hard to change and cannot be cached. Minor. Source: W3C CSP Level 3: inline styles need 'unsafe-inline'.
- Little script written into the page. Script inside the page is downloaded again on every visit. Minor. Source: web.dev: prevent unnecessary network requests with the HTTP cache.
- Few forced style overrides. Forced rules are a sign of styles fighting each other; every later change gets harder. Minor. Source: W3C CSS Cascade 4: important declarations.
- No retired tags or document.write. Browsers may drop them; document.write is blocked on slow phone connections. Minor. Source: WHATWG HTML: obsolete features; Chrome: document.write blocked on slow connections.
- The copyright year is current. An old year makes visitors wonder whether anyone looks after the site. Minor. Source: UK Intellectual Property Office: copyright notices.
Accessibility
- Zoom is not blocked. People with poor sight cannot read the page. Serious. Source: WCAG 2.2: 1.4.4 resize text.
- Pictures have a description, or are marked as decoration. A screen reader reads out the file name, or nothing. Search engines use descriptions too. Important. Source: WCAG 2.2: 1.1.1 non-text content; Google Search Central: image best practices.
- Text has enough contrast. Pale text is hard to read for one adult in twelve. Important. Source: WCAG 2.2: 1.4.3 contrast; axe-core: the accessibility rules it checks.
- Form fields have labels. A screen reader user cannot tell what to type. Important. Source: WCAG 2.2: 3.3.2 labels or instructions.
- Links have names. A screen reader says only "link". Important. Source: WCAG 2.2: 2.4.4 link purpose.
- Buttons have names. A screen reader says only "button". Important. Source: WCAG 2.2: 4.1.2 name, role, value.
- The homepage has one main heading. Screen reader users jump to the main heading to learn what the page is. Important. Source: W3C WAI tutorial: headings; WebAIM screen reader survey 10 (2024).
- Screen-reader markers are used correctly. A wrong marker is worse than none: it tells the reader something false. Important. Source: W3C: Using ARIA (its first rule); WebAIM Million: pages with ARIA have more errors.
- Every menu page has one main heading. Same reason, on every page. Minor. Source: W3C WAI tutorial: headings; WebAIM screen reader survey 10 (2024).
- Headings go in order. Screen reader users move through a page by its headings; gaps make it look as if parts are missing. Minor. Source: W3C WAI tutorial: headings; WCAG 2.2: 1.3.1 info and relationships.
- Page regions are marked. Screen reader users skip straight to the menu or the content with these. Minor. Source: WCAG 2.2: 2.4.1 bypass blocks; W3C WAI tutorial: page regions.
- Embedded frames have titles. A screen reader cannot say what the frame holds. Minor. Source: WCAG 2.2: 4.1.2 name, role, value; W3C technique H64: titles on frames.
- Lists and tables are built correctly. Screen readers announce how many items a list or table holds. Minor. Source: WCAG 2.2: 1.3.1 info and relationships; axe-core: the accessibility rules it checks.
- Keyboard order is not forced. Keyboard users jump around the page in an order that does not match what they see. Minor. Source: WCAG 2.2: 2.4.3 focus order.
Search
- robots.txt exists and does not block the site. It is the first file a search engine reads. Serious. Source: IETF RFC 9309: the robots exclusion protocol; Google Search Central: robots.txt.
- No page is hidden from search by accident. A page marked noindex drops out of Google. It is often left on by mistake after a site is built. Serious. Source: Google Search Central: block indexing with noindex.
- The phone-screen setting is present. Google ranks pages by how they work on a phone. Serious. Source: Google Search Central: mobile-first indexing.
- Every page has a title of sensible length. Google shows the title as the link in its results; too long is cut off, too short says little. Important. Source: Google Search Central: title links.
- Titles are not repeated. Google cannot tell which page to show. Important. Source: Google Search Central: title links.
- Titles are words, not addresses. It looks unfinished in search results. Important. Source: Google Search Central: title links.
- A sitemap exists and is named in robots.txt. The sitemap tells search engines every page you want found. Important. Source: sitemaps.org: the sitemap protocol; Google Search Central: build a sitemap.
- Structured data is present. Structured data is how Google shows stars, prices and opening hours in results. Important. Source: Google Search Central: structured data; schema.org.
- Structured data can be read. A block with a mistake is ignored completely. Important. Source: Google Search Central: structured data guidelines; Google: Rich Results Test.
- www and non-www end at one address. Two addresses for one site split its ranking. Important. Source: Google Search Central: consolidate duplicate URLs; Google Search Central: permanent redirects.
- Every page has a description. Without one Google picks a sentence for you, often a poor one. Minor. Source: Google Search Central: snippets and meta descriptions.
- Descriptions are not repeated. Repeated descriptions make pages look the same in results. Minor. Source: Google Search Central: snippets and meta descriptions.
- Each page names its preferred address. When one page has several addresses, Google may split its ranking between them. Minor. Source: Google Search Central: consolidate duplicate URLs; IETF RFC 6596: the canonical link.
- Sharing preview has a title, description and picture. This is what shows when someone shares your link on social media or in a message. Minor. Source: The Open Graph protocol.
- Links say where they go. Search engines and screen readers learn nothing from them. Minor. Source: Google Search Central: link text; WCAG 2.2: 2.4.4 link purpose.
- A made-up address answers "not found". If every address answers "fine", search engines list junk pages. Minor. Source: Google Search Central: HTTP status codes and soft 404s.
- Site icon present. Google shows it beside your result; browsers show it in the tab. Minor. Source: Google Search Central: favicon in search results.
- Menu addresses are readable. Readable addresses are trusted more in results. Minor. Source: Google Search Central: URL structure.
Ready for AI agents
- AI answer engines are not blocked. These fetch pages to answer someone's question right now; blocking them hides you from AI answers. Important. Source: OpenAI: its crawlers; Perplexity: its crawlers.
- The main words are in the page before scripts run. Most AI crawlers run no scripts: they see only the first figure. Important. Source: Vercel: the rise of the AI crawler (2024 study); Google Search Central: JavaScript SEO basics.
- The menu is in the page before scripts run. A crawler that runs no scripts cannot find your other pages. Important. Source: Vercel: the rise of the AI crawler (2024 study); Google Search Central: make links crawlable.
- The business is described in structured data. AI tools and Google read this to answer "who runs this site, and where are they?". Important. Source: schema.org: Organization; Google Search Central: organization structured data.
- A plain request is not turned away. Some security services block every visitor that is not a normal browser, AI tools included. Important. Source: Cloudflare: AI crawlers blocked by default (2025).
- Your robots.txt says what AI crawlers may do. Naming them is how you choose whether your pages train AI models. Minor. Source: IETF RFC 9309: the robots exclusion protocol; OpenAI: its crawlers; Google: Google-Extended and its other crawlers.
- An llms.txt file exists. A short plain-text guide to your site for AI tools. Minor. Source: llmstxt.org: the llms.txt proposal.
- At least 3% of the page is words rather than code. Tools that read pages within a size limit may stop before reaching your words. Minor. Source: Google Search Central: Googlebot reads the first 15 MB.
- The sitemap carries dates. Crawlers use the dates to decide what to read again. Minor. Source: sitemaps.org: the sitemap protocol; Google Search Central: build a sitemap.
- A feed is offered for the news or blog. Feeds let readers and tools follow new posts. Minor. Source: IETF RFC 4287: the Atom feed format; RSS 2.0 specification.
- Headings give an outline a machine can follow. Tools that summarise a page lean on its headings. Minor. Source: WHATWG HTML: headings and outlines.
Readable for people
- Contact details can be found. Visitors trust a business they can reach. Serious. Source: UK law: E-Commerce Regulations 2002, regulation 6.
- Enough words to say what the business does. Visitors and search engines need to know what you do. Important. Source: Google Search Central: creating helpful content.
- Nothing covers the page on arrival. A pop-up on arrival hides the page; Google marks pages down for it on phones. Important. Source: Google Search Central: intrusive pop-ups.
- Who runs the business is stated. UK law requires a company's website to show its registered name, number and address. Important. Source: UK law: Trading Disclosures Regulations 2015, regulation 25.
- Terms and privacy pages can be found. Visitors look for these before they buy or sign up. Important. Source: UK GDPR article 13: what people must be told; UK law: Consumer Contracts Regulations 2013, schedule 2.
- The page fits a phone screen. Sideways scrolling on a phone loses visitors. Important. Source: WCAG 2.2: 1.4.10 reflow.
- The homepage is easy to read. Long sentences and long words lose readers, on a phone above all. Minor. Source: Flesch, a new readability yardstick (1948); GOV.UK: writing for GOV.UK.
- Body text is at least 16 pixels. Small text is hard to read on a phone. Minor. Source: Lighthouse: legible font sizes.
- Menu links have words, not only icons. Not everyone knows what an icon means. Minor. Source: Nielsen Norman Group: icon usability.
- Buttons and links are big enough to tap. Small targets mean wrong taps. Minor. Source: WCAG 2.2: 2.5.8 target size.
WordPress pack
Checked only on sites these apply to.
- The WordPress version has no known holes. Its holes are published, and attackers try them on every WordPress site they find. Serious. Source: WordPress.org: which versions are still secure; OWASP Top 10: vulnerable and outdated components.
- No plugin with a known flaw. Out-of-date plugins are the usual way WordPress sites are broken into. Serious. Source: Patchstack: state of WordPress security 2024; OWASP Top 10: vulnerable and outdated components.
- The WordPress version is not shown. It tells attackers which known flaws to try. Important. Source: WordPress: hardening WordPress; OWASP testing guide: fingerprint the web server.
- User names are not listed publicly. A public list of user names is half of a login. Important. Source: OWASP testing guide: account enumeration.
- The old remote-control file is closed. xmlrpc.php lets attackers try many passwords in one request. Important. Source: Sucuri: password guessing through xmlrpc.php (2015).
- Plugins we could see. Each plugin is code someone else wrote, running on your site. Minor. Source: Patchstack: state of WordPress security 2024.
Shopify pack
Checked only on sites these apply to.
- Apps we could see, and the script each adds. Each app adds scripts to every page, and removed apps often leave code behind. Minor. Source: Shopify: app performance.
Drupal pack
Checked only on sites these apply to.
- The Drupal version still gets security fixes. Flaws found after support ends are never fixed. Serious. Source: Drupal: core release schedule; endoflife.date: support dates.
Own code pack
Checked only on sites these apply to.
- No folders or files exposed. Backups, settings files and logs left on the server. Serious. Source: OWASP testing guide: old, backup and unreferenced files.
- The programming language is not given away. It narrows what an attacker tries. Minor. Source: OWASP: session management cheat sheet.
Selling online pack
Checked only on sites these apply to.
- Product pages carry product data. Google and shopping tools show price and stock in results only with it. Important. Source: Google Search Central: product structured data; schema.org: Product.
- Product data includes the price. A result without a price is passed over. Important. Source: Google Search Central: product structured data; schema.org: Offer.
- Returns and delivery pages can be found. Buyers check these before paying; UK and EU law requires the returns terms. Important. Source: UK law: Consumer Contracts Regulations 2013, schedule 2; UK law: Consumer Contracts Regulations 2013, regulation 13.
Login pack
Checked only on sites these apply to.
- The login page has no library with known flaws. The login page is where a flaw does most harm: it handles passwords. Serious. Source: OWASP Top 10: vulnerable and outdated components; Retire.js: the list of library flaws.
- The password form sends over https. Passwords can be read on the way. Serious. Source: OWASP: authentication cheat sheet; OWASP: transport layer security cheat sheet.
Video pack
Checked only on sites these apply to.
- Videos with sound have captions. Deaf visitors, and anyone with the sound off, miss what is said. Important. Source: WCAG 2.2: 1.2.2 captions.
Many languages pack
Checked only on sites these apply to.
- Language declared on every page. On a site in many languages, search engines and translators rely on it. Important. Source: WCAG 2.2: 3.1.1 language of page; Google Search Central: sites in many languages.