frontendchecklist.io Open in urlscan Pro
3.70.101.28  Public Scan

Form analysis
0 forms found in the DOM

Text Content

Your JavaScript seems to be desactivated. Please enable your JavaScript to use
all functionnalities of the Front-End Checklist.


THE FRONT-END CHECKLIST

🗂 The Front-End Checklist Application is perfect for modern websites and
meticulous developers!

 * 
 * 
 * 


FILTER BY TAGS

 * All
 * Best practices
 * Seo
 * Testing
 * Css
 * Javascript
 * Performance
 * Meta tag
 * HTML tag
 * CSS
 * Performance
 * Social meta
 * Html
 * Security
 * Images
 * Requests
 * Accessibility
 * Webfont


HEAD

0 % Head items are ✓
Check Check
Plus Expand Minus Collapse
Eye

 * Check Check
   Doctype: The Doctype is HTML5 and is at the top of all your HTML pages.
   
   DOCUMENTATION
   
    * Determining the character encoding - HTML5 W3C
   
    * META TAG
   
   Arrow
 * Check Check
   Charset: The charset declared (UTF-8) is declared correctly.
   
    * META TAG
   
   Arrow
 * Check Check
   Viewport: The viewport is declared correctly.
   
    * META TAG
   
   Arrow
 * Check Check
   Title: A title is used on all pages
   
   SEO: Google calculates the pixel width of the characters used in the title
   and cuts off between 472 and 482 pixels. Average character limit would be
   around 55 characters
   
   
   
   DOCUMENTATION
   
    * Title - HTML - MDN
   
   TOOLS
   
    * SERP Snippet Generator
   
    * META TAG
   
   Arrow
 * Check Check
   Description: A meta description is provided, it is unique and doesn't possess
   more than 150 characters.
   
   DOCUMENTATION
   
    * Meta Description - HTML - MDN
   
    * META TAG
   
   Arrow
 * Check Check
   Favicons: 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).
   
   
   
   DOCUMENTATION
   
    * Favicon Cheat Sheet
    * Favicons, Touch Icons, Tile Icons, etc. Which Do You Need? - CSS Tricks
    * PNG favicons - caniuse
   
   TOOLS
   
    * Favicon Generator
    * RealFaviconGenerator
   
    * META TAG
   
   Arrow
 * Check Check
   Apple Web App Meta: Apple meta-tags are present.
   
   DOCUMENTATION
   
    * Configuring Web Applications
    * Supported Meta Tags
   
    * META TAG
   
   Arrow
 * Check Check
   Windows Tiles: Windows tiles are present and linked.
   
   DOCUMENTATION
   
    * Browser configuration schema reference
   
    * META TAG
   
   Arrow
 * Check Check
   Canonical: Use rel="canonical" to avoid duplicate content.
   
   DOCUMENTATION
   
    * Use canonical URLs - Search Console Help - Google Support
    * 5 common mistakes with rel=canonical - Google Webmaster Blog
   
    * META TAG
   
   Arrow
 * Check Check
   Language attribute: The <code>lang</code> attribute of your website is
   specified and related to the language of the current page.
    * HTML TAG
   
   
 * Check Check
   Direction attribute: The direction of lecture is specified on the html tag
   (It can be used on another HTML tag).
    * HTML TAG
   
   
 * Check Check
   Alternate language: The language tag of your website is specified and related
   to the language of the current page.
    * HTML TAG
   
   
 * Check Check
   Conditional comments: Conditional comments are present for IE if needed.
   
   DOCUMENTATION
   
    * About conditional comments (Internet Explorer) - MSDN - Microsoft
   
    * HTML TAG
   
   Arrow
 * Check Check
   RSS feed: If your project is a blog or has articles, an RSS link was
   provided.
    * HTML TAG
   
   
 * Check Check
   Inline critical CSS: The inline critical CSS is correctly injected in the
   HEAD.
   
   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).
   
   TOOLS
   
    * Critical by Addy Osmani on GitHub automates this.
   
    * HTML TAG
    * CSS
    * PERFORMANCE
   
   Arrow
 * Check Check
   CSS order: All CSS files are loaded before any JavaScript files in the HEAD
    * HTML TAG
   
   
 * Check Check
   Facebook Open Graph:
   
   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, although 1200 x 630
   pixels is recommended. Using og:image:width and og:image:height will specify
   the image dimensions to the crawler so that it can render the image
   immediately without having to asynchronously download and process it.
   
   DOCUMENTATION
   
    * A Guide to Sharing for Webmasters
    * Best Practices - Sharing
   
   TOOLS
   
    * Test your page with the Facebook OG testing
   
    * SOCIAL META
    * TESTING
   
   Arrow
 * Check Check
   Twitter Card:
   
   DOCUMENTATION
   
    * Getting started with cards — Twitter Developers
   
   TOOLS
   
    * Test your page with the Twitter card validator
   
    * SOCIAL META
    * TESTING
   
   Arrow


HTML

0 % HTML items are ✓
Check Check
Plus Expand Minus Collapse
Eye

 * Check Check
   HTML5 Semantic Elements: HTML5 Semantic Elements are used appropriately
   (header, section, footer, main...).
   
   TOOLS
   
    * HTML Reference
   
    * HTML
    * BEST PRACTICES
   
   Arrow
 * Check Check
   Error pages: Error 404 page and 5xx exist
    * HTML
    * BEST PRACTICES
   
   
 * Check Check
   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"
   
   DOCUMENTATION
   
    * About rel=noopener
   
    * HTML
    * BEST PRACTICES
    * SECURITY
   
   Arrow
 * Check Check
   Clean up comments: Unnecessary code needs to be removed before sending the
   page to production.
    * HTML
    * BEST PRACTICES
   
   
 * Check Check
   W3C compliant: All pages need to be tested with the W3C validator to identify
   possible issues in the HTML code.
   
   TOOLS
   
    * W3C validator
   
    * HTML
    * TESTING
   
   Arrow
 * Check Check
   HTML Lint: I use tools to help me analyze any issues I could have on my HTML
   code.
   
   TOOLS
   
    * Dirty markup
    * webhint
   
    * HTML
    * TESTING
   
   Arrow
 * Check Check
   Link checker: There are no broken links in my page, verify that you don't
   have any 404 error.
   
   TOOLS
   
    * W3C Link Checker
   
    * HTML
    * TESTING
   
   Arrow
 * Check Check
   Adblockers test: Your website shows your content correctly with adblockers
   enabled
    * HTML
    * TESTING
   
   


WEBFONTS

0 % Webfonts items are ✓
Check Check
Plus Expand Minus Collapse
Eye
 * Check Check
   Webfont format: WOFF, WOFF2 and TTF are supported by all modern browsers.
   
   DOCUMENTATION
   
    * WOFF - Web Open Font Format - Caniuse
    * WOFF 2.0 - Web Open Font Format - Caniuse
    * TTF/OTF - TrueType and OpenType font support
    * Using @font-face - CSS-Tricks
   
    * WEBFONT
   
   Arrow
 * Check Check
   Webfont size: Webfont sizes don't exceed 100 KB (all variants included).
    * WEBFONT
   
   
 * Check Check
   Webfont loader: Control loading behavior with a webfont loader.
   
   DOCUMENTATION
   
    * Typekit Web Font Loader
   
    * WEBFONT
   
   Arrow


CSS

0 % CSS items are ✓
Check Check
Plus Expand Minus Collapse
Eye
 * Check Check
   Responsive Web Design: The website is using responsive web design.
    * CSS
   
   
 * Check Check
   CSS Print: A print stylesheet is provided and is correct on each page.
    * CSS
   
   
 * Check Check
   Unique ID: If IDs are used, they are unique to a page.
    * CSS
   
   
 * Check Check
   Reset CSS: 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.)
   
   DOCUMENTATION
   
    * Reset.css
    * Normalize.css
    * Reboot
   
    * CSS
   
   Arrow
 * Check Check
   JS prefix: All classes (or id- used in JavaScript files) begin with js- and
   are not styled into the CSS files.
    * JAVASCRIPT
    * BEST PRACTICES
   
   
 * Check Check
   Embedded or inline CSS: Avoid at all cost embeding CSS in <style> tags or
   using inline CSS
    * CSS
   
   
 * Check Check
   Vendor prefixes: CSS vendor prefixes are used and are generated accordingly
   with your browser support compatibility.
   
   TOOLS
   
    * Autoprefixer CSS online
   
    * CSS
   
   Arrow
 * Check Check
   Concatenation: CSS files are concatenated in a single file (Not for HTTP/2).
    * CSS
    * PERFORMANCE
   
   
 * Check Check
   Minification: All CSS files are minified.
    * CSS
    * PERFORMANCE
   
   
 * Check Check
   Non-blocking: CSS files need to be non-blocking to prevent the DOM from
   taking time to load.
   
   DOCUMENTATION
   
    * loadCSS by filament group
    * Example of preload CSS using loadCSS
   
    * CSS
    * PERFORMANCE
   
   Arrow
 * Check Check
   Stylelint: All CSS or SCSS files are without any errors.
   
   DOCUMENTATION
   
    * Sass guidelines
   
   TOOLS
   
    * stylelint, a CSS linter
   
    * CSS
    * TESTING
   
   Arrow
 * Check Check
   Responsive web design: All pages were tested with the correct breakpoints.
    * CSS
    * TESTING
   
   
 * Check Check
   CSS Validator: The CSS was tested and pertinent errors were corrected.
   
   TOOLS
   
    * CSS Validator
   
    * CSS
    * TESTING
   
   Arrow
 * Check Check
   Desktop Browsers: All pages were tested on all current desktop browsers
   (Safari, Firefox, Chrome, Internet Explorer, EDGE...)
    * CSS
    * TESTING
   
   
 * Check Check
   Mobile Browsers: All pages were tested on all current mobile browsers (Native
   browser, Chrome, Safari...)
    * CSS
    * TESTING
   
   
 * Check Check
   OS: All pages were tested on all current OS (Windows, Android, iOS, Mac...)
    * CSS
    * TESTING
   
   
 * Check Check
   Reading direction: All pages need to be tested for LTR and RTL languages if
   they need to be supported.
   
   DOCUMENTATION
   
    * Building RTL-Aware Web Apps & Websites: Part 1 - Mozilla Hacks
    * Building RTL-Aware Web Apps & Websites: Part 2 - Mozilla Hacks
   
    * CSS
    * TESTING
   
   Arrow


JAVASCRIPT

0 % JavaScript items are ✓
Check Check
Plus Expand Minus Collapse
Eye
 * Check Check
   JavaScript Inline: You don't have any JavaScript code inline (mixed with your
   HTML code).
    * JAVASCRIPT
   
   
 * Check Check
   Concatenation: JavaScript files are concatenated.
    * JAVASCRIPT
   
   
 * Check Check
   Minification: JavaScript files are minified (you can add the .min suffix).
   
   DOCUMENTATION
   
    * Minify Resources (HTML, CSS, and JavaScript)
   
    * JAVASCRIPT
   
   Arrow
 * Check Check
   JavaScript security:
   
   DOCUMENTATION
   
    * Guidelines for Developing Secure Applications Utilizing JavaScript
   
    * JAVASCRIPT
    * SECURITY
   
   Arrow
 * Check Check
   noscript tag: Use `<noscript>` tag in the HTML body if a script type on the
   page is unsupported or if scripting is currently turned off in the browser.
   This will be helpful in client-side rendering heavy apps such as React.js.
   
   DOCUMENTATION
   
    * Quick Tip: Don’t Forget the “noscript” Element
   
    * JAVASCRIPT
   
   Arrow
 * Check Check
   Non-blocking: JavaScript files are loaded asynchronously using async or
   deferred using defer attribute.
   
   DOCUMENTATION
   
    * Remove Render-Blocking JavaScript
   
    * JAVASCRIPT
    * PERFORMANCE
   
   Arrow
 * Check Check
   Modernizr: If you need to target some specific features you can use a custom
   Modernizr to add classes in your <html> tag.
   
   DOCUMENTATION
   
    * Customize your Modernizr
   
    * JAVASCRIPT
   
   Arrow
 * Check Check
   ESLint: No errors are flagged by ESLint (based on your configuration or
   standards rules).
   
   DOCUMENTATION
   
    * ESLint - The pluggable linting utility for JavaScript and JSX
   
    * JAVASCRIPT
    * TESTING
   
   Arrow


IMAGES

0 % Images items are ✓
Check Check
Plus Expand Minus Collapse
Eye
 * Check Check
   Optimization: All images are optimized to be rendered in the browser. WebP
   format could be used for critical pages (like Homepage)
   
   TOOLS
   
    * Imagemin
    * Use ImageOptim to optimise your images for free.
    * Use Kraken.io awesome alternative for both png and jpg optimization. Up to
      1mb per files on free plan.
   
    * IMAGES
    * BEST PRACTICES
   
   Arrow
 * Check Check
   Picture/Srcset: You use picture/srcset to provide the most appropriate image
   for the current viewport of the user.
   
   DOCUMENTATION
   
    * How to Build Responsive Images with srcset
   
    * IMAGES
   
   Arrow
 * Check Check
   Retina: You provide layout images 2x or 3x, support retina display.
    * IMAGES
   
   
 * Check Check
   Sprite: Small images are in a sprite file (in the case of icons, they can be
   in an SVG sprite image).
    * IMAGES
   
   
 * Check Check
   Width and Height: Set width and height attributes on <img> if the final
   rendered image size is known (can be omitted for CSS sizing).
    * IMAGES
   
   
 * Check Check
   Alternative text: All <img> have an alternative text which describe the image
   visually.
   
   DOCUMENTATION
   
    * Alt-texts: The Ultimate Guide
   
    * IMAGES
   
   Arrow
 * Check Check
   Lazy loading: Images are lazyloaded (A noscript fallback is always provided).
    * IMAGES
    * PERFORMANCE
   
   


ACCESSIBILITY

0 % Accessibility items are ✓
Check Check
Plus Expand Minus Collapse
Eye
 * Check Check
   Progressive enhancement: Major functionality like main navigation and search
   should work without JavaScript enabled.
   
   DOCUMENTATION
   
    * Enable / Disable JavaScript in Chrome Developer Tools
   
    * BEST PRACTICES
   
   Arrow
 * Check Check
   Color contrast: Color contrast should at least pass WCAG AA (AAA for mobile).
   
   TOOLS
   
    * Contrast Ratio
   
    * BEST PRACTICES
   
   Arrow
 * Check Check
   H1: All pages have an H1 which is not the title of the website.
    * BEST PRACTICES
    * SEO
   
   
 * Check Check
   Headings: Headings should be used properly and in the right order (H1 to H6).
   
   VIDEOS
   
    * Why headings and landmarks are so important -- A11ycasts #18
   
    * BEST PRACTICES
   
   Arrow
 * Check Check
   Specific HTML5 input types are used: This is especially important for mobile
   devices that show customized keypads and widgets for different types.
   
   DOCUMENTATION
   
    * Mobile Input Types
   
   
   Arrow
 * Check Check
   Label: A label is associated with each input form element. In case a label
   can't be displayed, use aria-label instead.
   
   DOCUMENTATION
   
    * Using the aria-label attribute - MDN
   
   
   Arrow
 * Check Check
   Accessibility standards testing: Use the WAVE tool to test if your page
   respects the accessibility standards.
   
   TOOLS
   
    * Wave testing
   
    * TESTING
   
   Arrow
 * Check Check
   Keyboard navigation: Test your website using only your keyboard in a
   previsible order. All interactive elements are reachable and usable.
    * TESTING
   
   
 * Check Check
   Screen reader: All pages were tested in two or more screen readers (such as
   JAWS, VoiceOver, and NVDA).
   
   DOCUMENTATION
   
    * Screen Reader User Survey #7 Results - Primary Screen Reader
   
    * TESTING
   
   Arrow
 * Check Check
   Focus style: If the focus is disabled, it is replaced by visible state in
   CSS.
   
   VIDEOS
   
    * Managing Focus - A11ycasts #22
   
    * TESTING
   
   Arrow


PERFORMANCE

0 % Performance items are ✓
Check Check
Plus Expand Minus Collapse
Eye
 * Check Check
   Page weight: The weight of each page is between 0 and 500 KB.
   
   DOCUMENTATION
   
    * Size Limit: Make the Web lighter
   
   TOOLS
   
    * Website Page Analysis
   
    * PERFORMANCE
   
   Arrow
 * Check Check
   Minified HTML: Your HTML is minified.
    * HTML
    * PERFORMANCE
   
   
 * Check Check
   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)
    * BEST PRACTICES
   
   
 * Check Check
   Cookie size: If you are using cookies be sure each cookie doesn't exceed 4096
   bytes and your domain name doesn't have more than 20 cookies.
   
   DOCUMENTATION
   
    * Cookie specification: RFC 6265
    * Cookies
   
   TOOLS
   
    * Browser Cookie Limits
   
    * BEST PRACTICES
   
   Arrow
 * Check Check
   Third party components:
   
   Third party iframes or components relying on external JS (like sharing
   buttons) are replaced by static components when possible, thus limiting calls
   to external APIs and keeping your users activity private.
   
   TOOLS
   
    * Simple sharing buttons generator
   
    * BEST PRACTICES
   
   Arrow
 * Check Check
   DNS resolution: DNS of third-party services that may be needed are resolved
   in advance during idle time using dns-prefetch.
   
    * REQUESTS
   
   Arrow
 * Check Check
   Preconnection: DNS lookup, TCP handshake and TLS negotiation with services
   that will be needed soon is done in advance during idle time using
   preconnect.
   
    * REQUESTS
   
   Arrow
 * Check Check
   Prefetching: Resources that will be needed soon (e.g. lazy loaded images) are
   requested in advance during idle time using prefetch.
   
    * REQUESTS
   
   Arrow
 * Check Check
   Preloading: Resources needed in the current page (e.g. scripts placed at the
   end of <body>) in advance using preload.
   
   TOOLS
   
    * Difference between prefetch and preload
   
    * REQUESTS
   
   Arrow
 * Check Check
   Google PageSpeed: All your pages were tested (not only the homepage) and have
   a score of at least 90/100.
   
   TOOLS
   
    * Google PageSpeed
    * Test your mobile speed with Google
    * WebPagetest - Website Performance and Optimization Test
    * GTmetrix - Website speed and performance optimization
   
    * TESTING
   
   Arrow


SEO

0 % SEO items are ✓
Check Check
Plus Expand Minus Collapse
Eye
 * Check Check
   Google Analytics: Google Analytics is installed and correctly configured.
   
   TOOLS
   
    * Google Analytics
    * GA Checker (and others)
   
    * SEO
   
   Arrow
 * Check Check
   Headings logic: Heading text helps to understand the content in the current
   page.
   
   TOOLS
   
    * Tota11y, tab Headings
   
    * SEO
    * ACCESSIBILITY
    * HTML
   
   Arrow
 * Check Check
   sitemap.xml: A sitemap.xml exists and was submitted to Google Search Console.
   
   (previously Google Webmaster Tools)
   
   TOOLS
   
    * Sitemap generator
   
    * SEO
   
   Arrow
 * Check Check
   robots.txt: The robots.txt is not blocking webpages.
   
   DOCUMENTATION
   
    * The robots.txt file
   
   TOOLS
   
    * Test your robots.txt with Google Robots Testing Tool
   
    * SEO
    * TESTING
   
   Arrow
 * Check Check
   Structured Data: Pages using structured data are tested and are without
   errors. Structured data helps crawlers understand the content in the current
   page.
   
   DOCUMENTATION
   
    * Introduction to Structured Data - Search - Google Developers
    * RDFa - Linked Data in HTML
    * JSON-LD
    * Microdata
    * Test your page with the Structured Data Testing Tool
    * Complete list of vocabularies that can be used as structured data.
      Schema.org Full Heirarchy
   
   TOOLS
   
    * Test your page with the Structured Data Testing Tool
    * Complete list of vocabularies that can be used as structured data on
      Schema.org Full Hierarchy
   
    * SEO
    * TESTING
   
   Arrow
 * Check Check
   Sitemap HTML: An HTML sitemap is provided and is accessible via a link in the
   footer of your website.
   
   DOCUMENTATION
   
    * Sitemap guidelines - Google Support
   
    * SEO
    * HTML
   
   Arrow
 * Check Check
   Pagination link tags: Provide rel="prev" and rel="next" to indicate paginated
   content.
   
   DOCUMENTATION
   
    * Pagination guidelines - Google Support
   
   TOOLS
   
    * Pagination (rel="prev/next") Testing Tool
   
    * SEO
    * HTML
   
   Arrow


A newer version of the Front-End Checklist is currently in the works, feel free
to discuss any feature you would like to see in the next version. Thank you for
your support!


REPORT AND NAVIGATION

Project Name
Page title or URL
Developer's name or team
Two arrows turn around Start new checklist
 * head
 * html
 * webfonts
 * css
 * javascript
 * images
 * accessibility
 * performance
 * seo

 * 0/47 ✓ high priority
 * 0/25 ✓ medium priority
 * 0/16 ✓ low priority

F
Printer Generate report

Accelerated by KeyCDN

Icons made by Freepik from www.flaticon.com is licensed by CC 3.0 BY

Made with ❤️ by David Dias ("The") for the Open-Source Community.