Skip to main content

Copy of some Draft Web Development Guidelines

Render blocking should be resolved

The ability to work around render-blocking issues is a great addition to the web. From deferring code, to lazy loading, to asynchronous loading, each has its use case and each can have the potential to reduce or give performance benefits to a website or application.

Criteria: Asynchronous code

Machine-testable

All external assets have been deferred or set to async (unless required) to avoid Flash Of Unstyled Content (FOUC).

Resources

Criteria: Priority loading

Machine-testable

If external resources are required on load, their priorities (delivery route) are set correctly.

Resources

Impact: Medium, Effort: Low

GRI Impact of Render blocking should be resolved
GRI Impact
materials Medium
energy Medium
water Medium
emissions Medium
Benefits of this guideline
  • Environment: Lazy loading videos and images ensures that they are only requested once the visitor needs them (not demanded even if they aren't viewed). This saves processing power which can help older devices or those with less battery capacity access your websites and applications barrier-free.
  • Performance: Letting text render first makes your website feel like it's loading faster (as the remainder will appear in the background or on demand).
  • Economic: Unused content will not contribute to your server's bandwidth bills.

Example

Tags: