What we've learned from 323,995 audit findings
323,995
total findings
500
unique issue patterns
3
tech stacks tracked
Missing og:image
Add OpenGraph images (1200x630) to all page metadata. Use a default OG image as fallback.
Missing skip navigation link
Title too long (76 chars)
Title too long (74 chars)
Title too long (75 chars)
Title too long (73 chars)
Title too long (71 chars)
Title too long (72 chars)
No inline CTA in content body. Inline text CTAs achieve 121% higher CTR than sidebar.
No CTA in bottom section. Users who read to the bottom are highly engaged.
Missing og:image
Add OpenGraph images (1200x630) to all page metadata. Use a default OG image as fallback.
Missing skip navigation link
Title too long (76 chars)
Title too long (74 chars)
Title too long (75 chars)
Title too long (73 chars)
Title too long (71 chars)
Title too long (72 chars)
No inline CTA in content body. Inline text CTAs achieve 121% higher CTR than sidebar.
No CTA in bottom section. Users who read to the bottom are highly engaged.
No JSON-LD structured data
Add JSON-LD structured data (Organization, WebSite, BreadcrumbList) to key pages.
Missing canonical URL
Add canonical URLs via metadata API. For Next.js: export metadata = { alternates: { canonical: url } }
Potential mixed HTTP/HTTPS content
25 non-framework scripts loaded (25 total) — likely hurting Core Web Vitals
25 non-framework scripts on page (25 total, 0 framework)
Use dynamic imports for non-critical components. Defer third-party scripts. Bundle related scripts.
Title too short (13 chars)
Missing meta description
1 of 1 images missing alt text
16 non-framework scripts loaded (28 total) — likely hurting Core Web Vitals
Missing og:image
Incomplete OG tags: missing og:description
No H1 tag found
Every QA audit run on NexusBro feeds into our knowledge graph, a self-learning database that tracks which issues appear most frequently, which tech stacks are most affected, and which fixes actually resolve problems in production. The data on this page is aggregated from all public audits and updated daily.
Issue patterns are categorized by severity (critical, high, medium, low) based on their impact on user experience and search engine rankings. The occurrence count reflects how many times the issue has been detected across all audited pages, while the sites affected count shows how many unique domains exhibit the pattern.
Tech stack breakdowns reveal which frameworks and platforms are most prone to specific issues. For example, WordPress sites commonly have different issue profiles than Next.js or React applications. Use these insights to prioritize fixes that will have the greatest impact on your site's quality score.
Recommendations shown alongside each issue are generated from our fix effectiveness data, showing what has actually worked for other sites with the same problem. Run a free audit on your own site to see which of these common issues affect you and get a personalized fix prompt.
Run a free QA audit and see where you stand against thousands of sites.
Run a Free AuditOpenPublicHub gives you the company intel behind the websites you audit — funding rounds, team composition, tech stack, and competitive benchmarks. Free on 8,265+ companies. Try it free →