View:

Do Better Web

We've compiled some recommendations for modernizing your web app and avoiding performance pitfalls.

Using modern offline features

  • Offline: Site is not using Application Cache
    Application Cache has been deprecated by Service Workers. Consider implementing an offline solution using the Cache Storage API.
  • Offline: Site is not using WebSQL DB.
    Web SQL Database is deprecated. Consider implementing an offline solution using IndexedDB.

Using modern protocols

  • Security: Site is on HTTPS
  • Performance: Site uses HTTP/2 for its own resources
    h2 offers many benefits over its http/1.1 predecessor: binary, multiplexing, server push, etc. See this FAQ for more information.

Using modern JavaScript features

  • JavaScript: Site does not use Date.now() in its own scripts
    Consider using performance.now(), which as better precision than Date.now() and always increases at a constant rate, independent of the system clock.
    URLs
    https://www.chromestatus.com/static/elements/features-imports.vulcanize.js (line: 3, col: 17028)
    https://www.chromestatus.com/static/elements/features-imports.vulcanize.js (line: 6, col: 28985)
  • JavaScript: Site does not use console.time() in its own scripts
    Consider using the User Timine API (performance.mark() and performance.measure()), which is a standard, uses high resolution timestamps, and has the added benefit of integrating with the DevTools timeline.

Avoiding APIs that harm the user experience

  • Performance: Site does not use document.write()
    Consider using <script async> to load scripts. document.write() is considered harmful for performance.