A real GradeMyBiz report for grademybiz.app, shown exactly as it was generated. Grade your site
Website Audit Report
grademybiz.app
Here's what we found.
And exactly what to do about it.
A
90.1 / 100
Executive Summary
GradeMyBiz.app is a well-built SaaS landing page that excels in technical fundamentals. It achieves a perfect 100/100 SEO Foundations score with all critical signals — title tag, meta description, canonical tag, sitemap, robots.txt, Open Graph tags, and heading hierarchy — properly configured. Security is equally impressive at 95/100: HTTPS with HSTS, a strict Content-Security-Policy, and a full complement of security headers place it in the top tier. Lighthouse lab tests measured a perfect 100/100 desktop performance score and 99/100 on mobile, with all Core Web Vitals well within good thresholds.
The site's primary improvement opportunities are in accessibility and visual design. axe-core detected 3 serious violations and 3 color contrast failures — straightforward fixes that would push the accessibility score higher and bring the site closer to full WCAG 2.1 AA compliance. On the design side, the page is clean and well-structured but relies entirely on text with no images in the page content. Adding a hero visual (such as a sample report screenshot) and richer illustrations in the 'How It Works' section would strengthen the first impression for a SaaS product page.
Content quality is solid at 82/100, with 586 words of professional-level copy organized across 9 well-nested headings. The main opportunities are adding structured content elements (lists, tables, comparison grids) and slightly simplifying the readability of technical sections. Overall, this is a strong foundation — the highest-impact next steps are fixing the accessibility violations and adding visual assets to match the site's excellent technical posture.
Top Priorities
Focus here first. These changes have the biggest impact on your grade.
Fix 3 serious axe-core accessibility violations
Run axe-core locally to identify and remediate the 3 serious violations. These represent the 1 failing WCAG 2.1 AA rule and are the highest-priority accessibility gap.
See details in AccessibilityResolve 3 color contrast failures
Increase the contrast ratio on the 3 elements flagged by axe-core. Audit the teal accent color against light backgrounds, particularly the step labels in the 'How It Works' section.
See details in AccessibilityAdd visual assets to the landing page
Include a hero illustration or annotated screenshot of a sample grade report above the fold, and enhance the 'How It Works' section with richer visuals to increase engagement.
See details in Design & User ExperienceDesign & User Experience
Strong
Design & UX
Strengths
- The viewport meta tag with width=device-width is correctly configured, ensuring proper responsive rendering across devices.
- A favicon link tag is present, reinforcing brand identity in browser tabs and bookmarks.
- The above-the-fold layout is clean and focused: a bold headline, a concise value proposition, and a single URL-input CTA create a strong visual hierarchy with generous whitespace. The teal accent color on the 'Grade It' button and 'at a glance' text draws the eye to the primary action.
Areas for Improvement
- The page contains no images in its content. For a SaaS landing page, the absence of visual assets (screenshots, illustrations, or icons beyond the small step icons) limits visual engagement and social proof above the fold.
- The 'How It Works' section uses a three-column layout with small circular icons that are visually understated. The step labels ('STEP 01', 'STEP 02', 'STEP 03') and descriptions are compact, leaving the section feeling sparse rather than informative.
Recommendations
- Add a hero illustration or annotated screenshot showing a sample grade report to give visitors an immediate preview of the product's output and increase visual engagement above the fold.
- Strengthen the 'How It Works' section with larger, more detailed illustrations or animated transitions to make the three-step flow more visually compelling and reinforce the simplicity of the process.
Content Quality
Strong
Content Quality
Strengths
- The page contains 586 words of body text with a Flesch Reading Ease score of 59.1 and an average sentence length of 13 words — professional-level writing that is clear and readable.
- Content is well-organized with 9 headings across 3 levels of depth with proper nesting, and 53 paragraphs averaging 9 words each, creating scannable, digestible sections.
- The page has a healthy internal linking structure with 17 internal links and 3 external links, including authoritative outbound references to Google PageSpeed Insights and WCAG guidelines.
Areas for Improvement
- Only 1 structured content element (a definition list) is present on the page. No ordered or unordered lists, tables, or comparison grids are used, which limits content richness for a SaaS product page.
- The Flesch Reading Ease score of 59.1 sits at the lower end of accessible readability. For a general-audience SaaS landing page, some sections use denser phrasing than necessary.
Recommendations
- Add structured content elements — such as a feature comparison table, a bulleted list of key benefits, or a pricing breakdown — to increase scannability and content richness beyond the single definition list currently present.
- Simplify phrasing in the methodology and FAQ sections to push the Flesch Reading Ease score above 60, making the content more accessible to a broader audience. Shorter sentences and simpler vocabulary in technical explanations will help.
SEO Foundations
Excellent
SEO Foundations
Strengths
- Title tag is 35 characters and meta description is 148 characters — both within their ideal ranges (30–60 and 120–160 respectively). All 3 Open Graph tags (title, description, image) are present for strong social sharing.
- Full crawlability infrastructure is in place: canonical tag pointing to https://grademybiz.app, robots.txt allowing crawling, XML sitemap found, and no noindex directives detected.
- JSON-LD structured data is present and the heading hierarchy is proper with a single H1 and H2 subheadings.
Areas for Improvement
- The JSON-LD structured data type is classified as 'unknown,' which reduces the chance of earning rich snippets in search results. A recognized schema type (e.g., SoftwareApplication, WebApplication, or FAQPage) would be more effective.
Recommendations
- Update the JSON-LD structured data to use a recognized Schema.org type such as 'SoftwareApplication' or 'WebApplication' to improve rich snippet eligibility. Additionally, add FAQPage schema to the FAQ section, which already has the correct content structure for it.
- While all SEO fundamentals are passing, consider adding Twitter Card meta tags (twitter:card, twitter:title, twitter:description) alongside the existing Open Graph tags for broader social platform coverage.
Performance Signals
Excellent
Performance
Based on Lab estimate
Strengths
- Lighthouse's synthetic desktop test measured a perfect 100/100 performance score, with Largest Contentful Paint at 0.6s and First Contentful Paint at 0.2s — both well within good thresholds.
- In lab conditions, Cumulative Layout Shift is 0 (perfect visual stability), Total Blocking Time is 50ms (well under the 200ms good threshold), and Speed Index is 0.6s.
Areas for Improvement
- Real-user field data (CrUX) is not available for this domain, so the perfect lab score cannot be validated against actual visitor experiences. The lab measurement is a synthetic benchmark, not a guarantee of real-world performance.
Recommendations
- Monitor real-user performance via the Web Vitals JavaScript library or a RUM (Real User Monitoring) tool to validate that the excellent lab scores translate to actual visitor experiences once traffic grows enough to generate CrUX data.
Mobile Friendliness
Excellent
Mobile
Based on Lab estimate
Strengths
- Lighthouse's throttled mobile test measured 99/100 with only a 1-point gap from the desktop score of 100, indicating near-parity across device types.
- In simulated mobile conditions, LCP is 2.1s, CLS is 0, and FCP is 0.9s — all within good thresholds.
Areas for Improvement
- Mobile LCP at 2.1s is within the good threshold but is 3.5× slower than the desktop LCP of 0.6s, indicating room for mobile-specific optimization of the largest content element.
Recommendations
- Investigate the largest content element rendered on mobile (the hero heading text block) and ensure font files are preloaded and critical CSS is inlined to narrow the 1.5s LCP gap between mobile and desktop lab measurements.
Security & Trust
Excellent
Security & Trust
Strengths
- HTTPS is enforced with HTTP-to-HTTPS redirect and an HSTS header with a 2-year max-age (63,072,000 seconds), ensuring browsers always connect securely.
- A Content-Security-Policy header with strict script-src is present, CSP frame-ancestors provides clickjacking protection (equivalent to X-Frame-Options), and X-Content-Type-Options is set to nosniff.
- Referrer-Policy (strict-origin-when-cross-origin) and Permissions-Policy headers are both set. No cookies are exposed in the response, and no cross-origin scripts are loaded, eliminating the need for Subresource Integrity.
Areas for Improvement
- No weaknesses are identified in the security header configuration. All major security headers are present and properly configured.
Recommendations
- Consider submitting the domain to the HSTS preload list (hstspreload.org) to ensure HTTPS enforcement even on the very first visit before the HSTS header is received. The current max-age of 63,072,000 seconds already meets the preload minimum requirement.
- Add visible trust signals to the page content — such as a privacy badge, a link to the refund policy from the hero section, or a brief data-handling statement near the URL input — to complement the strong technical security posture with user-facing trust cues.
Accessibility
Strong
Accessibility
Strengths
- axe-core detected zero critical violations, 96% of WCAG 2.1 AA rules passed (26 of 27), and 100% of form inputs have associated labels.
- A skip navigation link is present, the HTML lang attribute is set, and 4 landmark region types (main, nav, header, etc.) are defined — providing strong structural accessibility for screen reader users.
- Heading hierarchy is proper with a single H1 and H2 subheadings, and 2 navigation regions with 8 links are present.
Areas for Improvement
- axe-core detected 3 serious accessibility violations that require remediation to meet WCAG 2.1 AA compliance.
- 3 elements have insufficient color contrast, failing WCAG contrast ratio requirements. The teal 'STEP 01/02/03' labels visible in the 'How It Works' section are a candidate source of these failures.
Recommendations
- Run axe-core locally and remediate the 3 serious violations. These are distinct from the color contrast issues and represent the 1 failing WCAG 2.1 AA rule (26 of 27 passed).
- Fix the 3 elements with insufficient color contrast by increasing the contrast ratio to at least 4.5:1 for normal text and 3:1 for large text. Audit the teal accent color used for step labels and link text against the light gray background.
- After fixing the serious violations and contrast issues, re-test with axe-core to confirm 100% WCAG 2.1 AA pass rate and push the Lighthouse accessibility score above the current 91/100.
Your Action Plan
Fix 3 serious axe-core accessibility violations
Run axe-core locally to identify and remediate the 3 serious violations. These represent the 1 failing WCAG 2.1 AA rule and are the highest-priority accessibility gap.
high impact/LOW EFFORT
Resolve 3 color contrast failures
Increase the contrast ratio on the 3 elements flagged by axe-core. Audit the teal accent color against light backgrounds, particularly the step labels in the 'How It Works' section.
high impact/LOW EFFORT
Upgrade JSON-LD to a recognized Schema.org type
Replace the unknown JSON-LD type with SoftwareApplication or WebApplication, and add FAQPage schema to the FAQ section to improve rich snippet eligibility.
medium impact/LOW EFFORT
Add visual assets to the landing page
Include a hero illustration or annotated screenshot of a sample grade report above the fold, and enhance the 'How It Works' section with richer visuals to increase engagement.
high impact/MEDIUM EFFORT
Add structured content elements (lists, tables)
Introduce bulleted benefit lists, a feature comparison table, or a pricing grid to improve content scannability beyond the single definition list currently present.
medium impact/LOW EFFORT
Simplify readability in technical sections
Revise the methodology and FAQ copy to use shorter sentences and simpler vocabulary, pushing the Flesch Reading Ease score above 60 for broader audience accessibility.
medium impact/LOW EFFORT
Submit domain to HSTS preload list
The HSTS header already meets preload requirements (max-age ≥ 63,072,000). Submitting to hstspreload.org ensures HTTPS enforcement from the very first visit.
low impact/LOW EFFORT