B86%
Quality Score
7
Pages
70
Issues
7.8
Avg Confidence
7.5
Avg Priority
21 Critical31 High17 Medium1 Low
>_ Testers.AI
AI Analysis
Github was tested and 70 issues were detected across the site. The most critical finding was: Excessive number of network requests on page load. Issues span Performance, A11y, Other, UX categories. Persona feedback rated Visual highest (7/10) and Accessibility lowest (5/10).
Qualitative Quality
Github
Category Avg
Best in Category
Pages Tested · 7 screenshots
Homepage
github.com.bytedance.deer
github.com.bytedance.deer
github.com.bytedance.deer
github.com.bytedance.deer
github.com.bytedance.deer
github.com.bytedance.deer
Detected Issues · 70 total
1
Excessive number of network requests on page load
CRIT P9
Prompt to Fix
Consolidate assets into fewer bundles: e.g., create a single vendor.js and app.js; move fonts to self-hosted or use font-display: swap; remove unused icons; enable lazy-loading for off-screen images; reduce dependencies; enable HTTP/2 and consider CDN tiering.
Why it's a bug
Page shows total network requests: 418. This high request count increases overhead, latency, and can hurt TTFB/LCP, especially on slower connections.
Why it might not be a bug
Some pages deliberately load many assets (icons, fonts, analytics); however, 418 is unusually high and likely improvable.
Suggested Fix
Audit assets; bundle CSS/JS into fewer files; enable code-splitting and lazy-load non-critical resources; remove unused assets; enable HTTP/2 server push/bundling if appropriate; host assets on a fast CDN; enable preconnect to critical hosts.
Why Fix
Reduces connection overhead, improves TTI and LCP, and lowers data usage on mobile users.
Route To
Frontend Engineer / Build Engineer
Page
Tester
Tariq · Performance Specialist
Technical Evidence
Console:
No console logs availableNetwork:
Total network requests: 4182
UI data contains placeholder/empty button labels and IDs
CRIT P9
Prompt to Fix
Review the AI-generated UI data structure and fill in all placeholder fields. For every button object, ensure text is non-empty (provide a clear label or localized key), assign a unique non-empty id, and keep className consistent. If a button is purely decorative, mark it as aria-hidden or remove it from the navigational structure. Add aria-labels where text is missing. Provide a patch or updated data structure with valid, production-ready values.
Why it's a bug
The Page Content JSON shows multiple button entries where the text and id fields are empty (e.g., text: "" and id: ""), indicating incomplete or placeholder data. This will lead to inaccessible UI, rendering issues, and a confusing user experience if used in production.
Why it might not be a bug
If this is a debug/mock excerpt from a generator output, it may not reflect the final production data. However, as AI-generated UI data, placeholders should be avoided or validated before deployment.
Suggested Fix
Populate all button entries with meaningful, non-empty labels and unique IDs. Add aria-labels for accessibility and ensure localization keys exist. Implement a validation step in the AI/code generator to reject or auto-fill empty text/id fields. Remove or replace placeholder entries with real, production-ready data.
Why Fix
Fixing this ensures accessible, reliable rendering and preserves a trustworthy user experience, preventing empty-button rendering and navigation confusion.
Route To
Frontend Engineer / Accessibility Engineer
Page
Tester
Jason · GenAI Code Analyzer
Technical Evidence
Console:
Page Content:
{"buttons":[{"text":"Toggle navigation","tagName":"BUTTON","type":"button","id":"","className":"HeaderMktg-backdrop d-lg-none border-0 position-fixed top-0 left-0 width-full height-full js-details-target"},{"text":"","tagName":"BUTTON","type":"button","id":"","className":"js-details-target js-nav-padding-recalculate js-header-menu-toggle Button--link Button--medium Button d-lg-none color-fg-inherit p-1"},{"text":"","tagName":"BUTTON","type":"button","id":"icon-button-35e8b6b7-7d44-4e8a-981e-f864d6ebfac2","className":"Button Button--iconOnly Button--invisible Button--medium AppHeader-button HeaderMenu-link border"},{"text":"Platform","tagName":"BUTTON","type":"button","id":"","className":"NavDropdown-module__button__PEHWX js-details-target"},{"text":"Solutions","tagName":"BUTTON","type":"button","id":"","className":"NavDropdown-module__button__PEHWX js-details-target"},{"text":"Resources","tagName":"BUTTON","type":"button","id":"","className":"NavDropdown-module__button__PEHWX js-details-target"},{"text":"Open Source","tagName":"BUTTON","type":"button","id":"","className":"NavDropdown-module__button__PEHWX js-details-target"},{"text":"Enterprise","tagName":"BUTTON","type":"button","id":"","className":"NavDropdown-module__button__PEHWX js-details-target"},{"text":"Search or jump to...","tagName":"BUTTON","type":"button","id":"","className":"header-search-button placeholder input-button form-control d-flex flex-1 flex-self-stretch flex-items-center no-wrap width-full py-0 pl-2 p"}]}Network:
GET https://github.com/bytedance/deer-flow/ - Status: 2003
UI Button with Empty Text (placeholder) in Page Content
CRIT P9
Prompt to Fix
In the AI-generated UI code, detect components where Button text is empty. Replace with a meaningful label or attach an accessible aria-label. Ensure all buttons have either visible text or aria-label. Update tests to verify button accessibility and ensure no empty string texts remain.
Why it's a bug
An element representing a button has an empty text value in the Page Content JSON, which would render as an unlabeled button. This is a clear artifact of AI-generated code that didn't finalize the label. It degrades accessibility and usability.
Why it might not be a bug
If the button is intended to be an icon button with an aria-label, this could be intentional; however the current data shows text as empty, which suggests incomplete generation. Without context, we can't assume it is an icon-only control; safer to require label or aria-label.
Suggested Fix
Provide a visible label or use an accessible icon with aria-label. Example: replace { text: '' } with { text: 'Menu' } or add aria-label='Menu' and ensure visual label is present if appropriate. Ensure all buttons have meaningful text or aria-labels.
Why Fix
Ensures accessibility, improves UX, prevents broken rendering and confusion for users and assistive tech.
Route To
Frontend Developer / Accessibility Engineer
Page
Tester
Jason · GenAI Code Analyzer
Technical Evidence
Console:
No console logs available