theuxbites
UX, performance and AI-visibility audits

Sample report: a real audit of our own site

theuxbites.com

Audited on 17 November 2025. This page always shows the latest audit.

This is the report theuxbites produced for theuxbites.com, shown in full and unedited, findings included. Every report has these sections; yours would show what was measured on your page.

UX score

92

Performance (test run)

95

SEO

90

Accessibility

89

The UX score of 92 is theuxbites' own composite, not a measurement: a weighted average of Performance 95 (50%, from the test run), Accessibility 89 (33%) and SEO 90 (17%). This report has no UX-principle checks, so the other three share the whole weight. The findings in the action plan explain why each part is not 100; they are not subtracted again.

Performance, SEO and Accessibility are Lighthouse category scores measured in Chrome on the audit date. AI visibility is a weighted score across the checks listed below. All are out of 100.

What we measured

How this page loaded in one test run in Chrome, emulating a mid-range phone on a slow 4G connection. These are measurements, not tasks: the action plan below lists what causes them. A single run varies, and your real visitors may see different numbers.

First content visible (FCP)

1.1 s

Good

Main content visible (LCP)

2.9 s

Needs improvement

Visually complete (Speed Index)

2.0 s

Good

Time the page was blocked (TBT)

40 ms

Good

Fully interactive (TTI)

3.0 s

Good

Layout shift (CLS)

0

Good

Action plan

10 findings, most urgent first. Each one is a check that failed on this page. Times are rough estimates for a developer, not quotes, and the fix notes are suggestions.

Critical (4)

Checks that failed outright, or a delay estimated at a second or more.

Dialogs are missing accessible names

~45min

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements.

Impact on users

Accessibility issues create barriers for users with disabilities, limiting their ability to navigate and interact with your content. This audit does not assess whether a legal requirement applies to your site.

Found on this page

  • body.__variable_188709 > main > div.min-h-screen > div#mobile-nav (aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements t…

How to fix

Implement accessibility fixes to ensure all users, including those with disabilities, can access and use your content effectively.

Text doesn't have enough color contrast

~45min

Low-contrast text is difficult or impossible for many users to read.

Impact on users

Users with visual impairments cannot read text with insufficient contrast

Found on this page

  • section.pt-28 > div.mx-auto > div.mx-auto > p.mx-auto (Element has insufficient color contrast of 3.65 (foreground color: #83827d, background color: #faf9f5, font size: 13.5pt (18px), font weight: normal). Expected cont…
  • div.mx-auto > div.rounded-3xl > div.flex > span.text-sm (Element has insufficient color contrast of 3.35 (foreground color: #83827d, background color: #f2efe7, font size: 10.5pt (14px), font weight: normal). Expected co…
  • div.mx-auto > div.band > div.band-head > p.mt-2 (Element has insufficient color contrast of 3.17 (foreground color: #83827d, background color: #ede9de, font size: 12.0pt (16px), font weight: normal). Expected contrast r…
  • div.band > div.grid > div.px-6 > div.eyebrow (Element has insufficient color contrast of 3.17 (foreground color: #83827d, background color: #ede9de, font size: 10.5pt (14px), font weight: normal). Expected contrast rati…
  • div.band > div.grid > div.px-6 > p.text-muted-foreground (Element has insufficient color contrast of 3.17 (foreground color: #83827d, background color: #ede9de, font size: 12.0pt (16px), font weight: normal). Expected c…

How to fix

Ensure text has sufficient color contrast against background colors

  1. Check current contrast ratios using tools like WebAIM
  2. Aim for at least 4.5:1 for normal text, 3:1 for large text
  3. Adjust colors to meet contrast requirements
  4. Test with color blindness simulators
  5. Verify changes across different devices

Links rely on color to be distinguishable.

~45min

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision.

Impact on users

Accessibility issues create barriers for users with disabilities, limiting their ability to navigate and interact with your content. This audit does not assess whether a legal requirement applies to your site.

Found on this page

  • div.border-t > div.flex > p.text-muted-foreground > a.text-primary (The link has insufficient color contrast of 1.01:1 with the surrounding text. (Minimum contrast is 3:1, link text: #c96442, surrounding text: #83827d) …

How to fix

Implement accessibility fixes to ensure all users, including those with disabilities, can access and use your content effectively.

Links have vague text

~30min

Descriptive link text helps search engines understand your content.

Impact on users

Users and search engines cannot understand link destinations without descriptive text, reducing click-through rates and SEO value

How to fix

Replace generic link text with descriptive, contextual text that clearly indicates the destination

  1. Identify links with generic text like "click here", "read more", "link"
  2. Replace with descriptive text that explains the destination
  3. Keep link text concise but informative
  4. Test with screen readers to ensure accessibility
  5. Verify that link text works standalone when removed from context

Quick wins (3)

Findings estimated as small to fix.

The largest element on screen loads slowly

~90min

This is the largest contentful element painted within the viewport.

Impact on users

Performance issues delay when content appears and when the page responds. This audit measures the delay, not its effect on your visitors or your sales.

How to fix

Optimize performance to improve page load times, interactivity, and user experience, especially on mobile devices and slower connections.

Unused JavaScript slows page load

~90min

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.

Impact on users

Users wait longer for pages to load due to unnecessary JavaScript execution

Found on this page

Est savings of 57 KiB

  • https://theuxbites.com/_next/static/chunks/3587-e4f62fb32ab0539e.js (could save 34 KB)
  • https://theuxbites.com/_next/static/chunks/1164-df6b5b534a7389ce.js (could save 22 KB)

How to fix

Eliminate unused JavaScript code to reduce bundle size and improve performance

  1. Use bundle analyzers to identify unused code
  2. Remove dead code and unused imports
  3. Implement code splitting for large applications
  4. Use tree shaking to eliminate unused exports
  5. Monitor bundle size after changes

Requests wait on one another before the page can show

~90min

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Impact on users

Performance issues delay when content appears and when the page responds. This audit measures the delay, not its effect on your visitors or your sales.

How to fix

Optimize performance to improve page load times, interactivity, and user experience, especially on mobile devices and slower connections.

Planned (3)

Worth scheduling after the items above.

Static assets aren't cached efficiently

~30min

A long cache lifetime can speed up repeat visits to your page.

Impact on users

Users experience slower repeat visits when caching is not optimized

Found on this page

1 resource found

  • https://theuxbites.com/_vercel/insights/script.js (1 KB)

How to fix

Configure appropriate cache headers for static resources

  1. Set Cache-Control headers for static assets
  2. Use versioned filenames for cache busting
  3. Set long TTL (e.g., 1 year) for immutable resources
  4. Configure CDN caching if applicable
  5. Test cache behavior with browser dev tools

Render-blocking resources slow page display

~75min

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.

Impact on users

Users see blank pages longer due to resources blocking initial render

Found on this page

Est savings of 0 ms

  • https://theuxbites.com/_next/static/css/0f57112e72e75929.css (22 KB; 150 ms)

How to fix

Optimize critical rendering path by removing or deferring blocking resources

  1. Identify render-blocking CSS and JavaScript
  2. Inline critical CSS in the document head
  3. Defer non-critical JavaScript loading
  4. Use async or defer attributes for scripts
  5. Optimize font loading with font-display

Old-style JavaScript is sent to modern browsers

~90min

Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpiling

Impact on users

Performance issues delay when content appears and when the page responds. This audit measures the delay, not its effect on your visitors or your sales.

Found on this page

Est savings of 11 KiB

  • https://theuxbites.com/_next/static/chunks/1255-15f04a30ae2c7791.js (could save 11 KB)

How to fix

Optimize performance to improve page load times, interactivity, and user experience, especially on mobile devices and slower connections.

This report was produced by theuxbites (theuxbites.com) for its own site. It reflects the page as it was measured on the date above.

Audit your own site free