Primary resources for better website decisions
Standards and search guidance change. For accessibility, search requirements and browser technology, use primary documentation where possible rather than relying only on summaries.
Google Search Central
Google's documentation explains Search Essentials, people-first content, crawling, indexing and structured data. It is a better source for what Google says than second-hand claims about secret ranking formulas.
Google Search Central →W3C Web Accessibility Initiative
W3C publishes WCAG and supporting accessibility guidance. WCAG 2.2 is the current W3C Recommendation and adds criteria covering areas such as focus visibility, target size and accessible authentication.
W3C WCAG overview →MDN Web Docs
MDN is a practical reference for HTML, CSS, JavaScript and browser APIs. It is useful when checking how a web feature is intended to work and what browser support considerations apply.
MDN Web Docs →Commercial examples and service research
When comparing web-design providers, use their sites as starting points rather than proof of quality. Read the scope, open live work, ask who owns the finished website and compare the process described in the proposal. Our website examples page includes WebForLess.ca, WebsiteForLess.net and several service-business sites as educational examples.
Use resources to verify, not to avoid judgment
A checklist cannot decide whether a particular website is right for a business. Standards can establish accessibility requirements and search documentation can clarify technical guidance, but choices about content, brand, workflow and conversion still depend on the audience and business model.
Performance testing resources
Lighthouse and PageSpeed Insights can help identify slow resources, layout instability and implementation problems. Treat scores as diagnostic evidence rather than a contest for perfection. Test representative templates and consider whether a flagged resource provides enough user value to justify its cost.
Keep a small source library for the project
Save standards, platform documentation and business references that influenced important decisions. Future maintainers then have context for accessibility, SEO and performance choices instead of unknowingly reversing them.