代码拉取完成，页面将自动刷新
The Front-End Checklist is an exhaustive list of all elements you need to have / to test before launching your site / page HTML to production.
It is based on Front-End developers' years of experience, with the addition from some other open-source checklists.
All items in the Front-End Checklist are required for the majority of the projects, but some elements can be omitted or are not essential (in the case of an administration web app, you may not need RSS feed for example). We choose to use 3 levels of flexibility:
means that the item is recommended but can be omitted in some particular situations.
means that the item is highly recommended and can eventually be omitted in some really particular cases. Some elements, if omitted, can have bad repercussions in terms of performance or SEO.
means that the item can't be omitted by any reason. You may cause a dysfunction in your page or have accessibility or SEO issues. The testing priority needs to be on these elements first.Some resources possess an emoticon to help you understand which type of content / help you may find on the checklist:
Notes: You can find a list of everything that could be found in the
<head>of an HTML document.
The Doctype is HTML5 and is at the top of all your HTML pages.
<!-- Doctype HTML5 -->
<!doctype html>
The next 3 meta tags (Charset, X-UA Compatible and Viewport) need to come first in the head.
The charset declared (UTF-8) is declared correctly.<!-- Set character encoding for the document -->
<meta charset="utf-8">
The X-UA-Compatible meta tag is present.<!-- Instruct Internet Explorer to use its latest rendering engine -->
<meta http-equiv="x-ua-compatible" content="ie=edge">
The viewport is declared correctly<!-- Viewport for responsive web design -->
<meta name="viewport" content="width=device-width, initial-scale=1">
A title is used on all pages (SEO: No more than 65 characters, website title included)<!-- Document Title -->
<title>Page Title less than 65 characters</title>
A meta description is provided, it is unique and doesn't possess more than 150 characters.<!-- Meta Description -->
<meta name="description" content="Description of the page less than 150 characters">
Each favicon has been created and displays correctly. If you have only a favicon.ico, put it at the root of your site. Normally you won't need to use any markup. However, it's still good practice to link to it using the example below. Today, PNG format is recommended over .ico format (dimensions: 32x32px)<!-- Standard favicon -->
<link rel="icon" type="image/x-icon" href="https://example.com/favicon.ico">
<!-- Recommended favicon format -->
<link rel="icon" type="image/png" href="https://example.com/favicon.png">
Apple touch favicon apple-mobile-web-app-capable are present. (Create your Apple Icon file with at least 200x200px dimension to support all dimensions that you may need)
<!-- Apple Touch Icon -->
<link rel="apple-touch-icon" href="/custom-icon.png">
Use rel="canonical" to avoid duplicate content.<!-- Helps prevent duplicate content issues -->
<link rel="canonical" href="http://example.com/2017/09/a-new-article-to-red.html">
The language tag of your website is specified and related to the language of the current page.<html lang="en">
The direction of lecture is specified on the body tag (It can be used on another HTML tag).<html dir="rtl">
The language tag of your website is specified and related to the language of the current page.<link rel="alternate" href="https://es.example.com/" hreflang="es">
Conditional comments are present for IE if needed.📖 About conditional comments (Internet Explorer) - MSDN - Microsoft
RSS feed: If your project is a blog or has articles, an RSS link was provided.
CSS Critical: The CSS critical (or "above the fold") collects all the CSS used to render the visible portion of the page. It is embedded before your principal CSS call and between <style></style> in a single line (minified).
All CSS files are loaded before any JavaScript files in the <head>. (Except the case where sometimes JS files are loaded asynchronously on top of your page).Facebook OG and Twitter Cards are, for any website, highly recommended. The other social media tags can be considered if you target a particular presence on those and want to ensure the display.
All Facebook Open Graph (OG) are tested and no one is missing or with a false information. Images need to be at least 600 x 315 pixels, 1200 x 630 pixels recommended.<meta property="og:type" content="website">
<meta property="og:url" content="https://example.com/page.html">
<meta property="og:title" content="Content Title">
<meta property="og:image" content="https://example.com/image.jpg">
<meta property="og:description" content="Description Here">
<meta property="og:site_name" content="Site Name">
<meta property="og:locale" content="en_US">
- 📖 A Guide to Sharing for Webmasters
- 🛠 Test your page with the Facebook OG testing
<meta name="twitter:card" content="summary">
<meta name="twitter:site" content="@site_account">
<meta name="twitter:creator" content="@individual_account">
<meta name="twitter:url" content="https://example.com/page.html">
<meta name="twitter:title" content="Content Title">
<meta name="twitter:description" content="Content description less than 200 characters">
<meta name="twitter:image" content="https://example.com/image.jpg">
- 📖 Getting started with cards — Twitter Developers
- 🛠 Test your page with the Twitter card validator
HTML5 Semantic Elements are used appropriately (header, section, footer, main...) Error pages: Error 404 page and 5xx exist. Remember that the 5xx error page needs to have his CSS integrated (no external call on the current server).
Noopener: In case you are using external links with target="_blank", your link should have a rel="noopener" attribute to prevent tab nabbing. If you need to support older versions of Firefox, use rel="noopener noreferrer".
Unnecessary code needs to be removed before sending the page to production. All pages need to be tested with the W3C validator to identify possible issues in the HTML code. I use tools to help me analyze any issues I could have on my HTML code. Desktop Browsers: All pages were tested on all current desktop browsers (Safari, Firefox, Chrome, Internet Explorer, EDGE...).
Mobile Browsers: All pages were tested on all current mobile browsers (Native browser, Chrome, Safari...).
Link checker: There are no broken links in my page, verify that you don't have any 404 error.
Your website shows your content correctly with adblockers enabled (You can provide a message encouraging people to disable their adblocker) Pages are close to pixel perfect. Depending on the quality of the creatives, you may not be 100% accurate, but your page needs to be close to your template. WOFF, WOFF2 and TTF are supported by all modern browsers. Webfont sizes don't exceed 2 MB (all variants included)Notes: Take a look at CSS guidelines and Sass Guidelines followed by most Front-End developers. If you have a doubt about CSS properties, you can visit CSS Reference.
The website is using responsive web design. A print stylesheet is provided and is correct on each page. Your page is using a CSS preprocessor (Sass is preferred). If IDs are used, they are unique to a page A CSS reset (reset, normalize or reboot) is used and up to date. (If you are using a CSS Framework like Bootstrap or Foundation, a Normalize is already included into it.)
- 📖 Reset.css
- 📖 Normalize.css
- 📖 Reboot
All classes (or id- used in JavaScript files) begin with js- and are not styled into the CSS files.<div id="js-slider" class="my-slider">
<!-- Or -->
<div id="id-used-by-cms" class="js-slider my-slider">
Avoid at all cost the use of CSS embed or inline: only used for valid reasons (ex: background-image for slider, CSS critical). CSS vendor prefixes are used and are generated accordingly with your browser support compatibility. CSS files are concatenated in a single file (Not for HTTP/2)
All CSS files are minified. CSS files need to be non-blocking to prevent the DOM from taking time to load. Remove unused CSS
- 🛠 UnCSS Online 🛠
- 🛠 PurifyCSS
All CSS or SCSS files are without any errors. Responsive web design: All pages were tested at the following breakpoints: 320px, 768px, 1024px (can be more / different according to your analytics).
CSS Validator: The CSS was tested and pertinent errors were corrected.
All pages need to be tested for LTR and RTL languages if they need to be supported.Notes: For a complete understanding of image optimization, check the free ebook Essential Image Optimization from Addy Osmani.
All images are optimized to be rendered in the browser. WebP format could be used for critical pages (like Homepage).
- 🛠 Imagemin
- 🛠 Use ImageOptim to optimise your images for free.
You provide layout images x2 or 3x, support retina display. Small images are in a sprite file (in the case of icons, they can be in an SVG sprite image). All <img> have height and width set (Don't specify px or %).Note: Lots of developers assume that width and height are not compatible with responsive web design. It's absolutely not the case.
All <img> have an alternative text which describe the image visually. Images are lazyloaded (A noscript fallback is always provided). You don't have any JavaScript code inline (mixed with your HTML code). JavaScript files are concatenated. JavaScript files are minified (you can add the .min suffix).Guidelines for Developing Secure Applications Utilizing JavaScript*
JavaScript files are loaded asynchronously using async or deferred using defer attribute. If you need to target some specific features you can use a custom Modernizr to add classes in your <html> tag. No errors are flagged by ESLint (based on your configuration or standards rules) HTTPS is used on every pages and for all external content (plugins, images...). The HTTP header is set to 'Strict-Transport-Security'. Your are ensure that requests made to your server-side are legitimate and originate from your website / app to prevent CSRF attacks.📖 Cross-Site Request Forgery (CSRF) Prevention Cheat Sheet - OWASP
Your page or website is free from XSS possible issues. The weight of each page is between 0kb and 500kb Your HTML is minified Lazy loading: Images, scripts and CSS need to be lazy loaded to improve the response time of the current page (See details in their respective sections).
Cookie size: If you are using cookies be sure each cookie doesn't exceed 4096 bytes and your domaine name don't have more than 20 cookies.
All your pages were tested (not only the homepage) and have min 90/100.Notes: You can watch the playlist A11ycasts with Rob Dodson 📹
Major functionality like main navigation and search should work without JavaScript enabled. Color contrast should at least pass WCAG AA (AAA for mobile) All pages have an H1 which is not the title of the website. Headings should be used properly in the right order (H1 to H6)📹 Why headings and landmarks are so important -- A11ycasts #18
<header> has role="banner"
<nav> has role="navigation"
<main> has role="main"
A label is associated with each input form element. In case a label can't be displayed, use aria-label instead. Use the WAVE tool to test if your page respects the accessibility standards. Test your website using only your keyboard in a previsible order. All interactive elements are reachable and usable. All pages were tested in a screen-reader (VoiceOver, ChromeVox, NVDA or Lynx). If the focus is disabled, it is replaced by visible state in CSS. Google Analytics is installed and correctly configured. Heading text helps to understand the content in the current page. A sitemap.xml exists and was submitted to Google Search Console (ex: Google Webmaster Tools) The robots.txt is not blocking webpages
- 🛠 Test your robots.txt with Google Robots Testing Tool
Pages using structured data are tested and are without errors. Structured data helps crawlers understand the content in the current page.
- 📖 Introduction to Structured Data | Search | Google Developers
- 🛠 Test your page with the Structured Data Testing Tool
An HTML sitemap is provided and is accessible via a link in the footer of your website.Open an issue or a pull request to suggest changes or additions.
The Front-End Checklist repository consists of two branches:
master
This branch consists of the README.md file that is automatically reflected on the Front-End Checklist website.
develop
This branch will be used to make some significant changes to the structure, content if needed. It is preferable to use the master branch to fix small errors or add a new item.
Check out all the super awesome contributors.
David Dias, Geoffrey Signorato, Sandeep Ramgolam and Cédric Poilly.
此处可能存在不合适展示的内容，页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容，可点击提交进行申诉，我们将尽快为您处理。