QA report: external/jpegworld.io at hosted
The landing page renders and links correctly, but header navigation links for the Stack and FAQ sections point to missing anchor targets.
Testing covered 10 scenarios across the landing page, verifying initial page loads, external app launcher links, social links, 404 route handling, and in-page anchor navigation.
Two navigation issues were confirmed during testing. Both the 'Stack' link and the 'FAQ' link append their respective hash targets (#stack and #faq) to the URL, but the page does not scroll because the target elements do not exist in the document.
While general landing page features and other section links such as Infrastructure and Overview operate without issue, these missing anchors leave user navigation incomplete.
Run summary
| Metric | Count |
|---|
| Scenarios executed | 10 |
| Passed | 8 |
| Failed | 2 |
| Blocked | 0 |
| Findings raised | 2 |
| Issues after the audit | 2 |
| Withdrawn by the audit | 0 |
| Critical / high / medium / low | 0 / 0 / 2 / 0 |
Target: https://jpegworld.io/ · Testing level: deep_feature · Stack: unknown
Issues
Medium severity
F1 · Navigation link 'Stack' (#stack) does not scroll viewport to any Stack section
Severity: medium · Type: functional · Verdict: confirmed · Scenario: S4
The observations clearly show that the anchor link '#stack' does not match any element on the page, leaving it non-functional.
Expected: The page should contain a Stack section and scroll the viewport to display the Stack section upon clicking the 'Stack' navigation link.
Actual: The URL hash updates to #stack, but no element or section with id 'stack' exists on the page and the viewport does not scroll.
Steps to reproduce:
- Navigate to https://jpegworld.io/
- Click the 'Stack' anchor link in the header navigation
- Observe the viewport position and content
Evidence: screenshots/S4-1.png, screenshots/S4-3.png
F2 · Header FAQ anchor link points to a non-existent section
Severity: medium · Type: functional · Verdict: confirmed · Scenario: S7
The observations clearly show that the anchor link '#faq' points to a section that does not exist in the DOM, failing to scroll the page.
Expected: The page should scroll down to display an FAQ section corresponding to the #faq anchor.
Actual: The URL updates to https://jpegworld.io/#faq but no scroll occurs and no FAQ section exists on the page.
Steps to reproduce:
- Navigate to https://jpegworld.io/
- Click the 'FAQ' anchor link in the header navigation
- Observe viewport position and page content
Evidence: screenshots/S7-1.png, screenshots/S7-3.png
Scenario results
| Scenario | Priority | Result | Issues |
|---|
| S1 Verify landing page load and title | high | pass | none |
| S2 Verify Mainnet App launch link | high | pass | none |
| S3 Verify Testnet App launch link | high | pass | none |
| S4 Test Stack anchor link navigation | medium | fail | F1 |
| S5 Test Infrastructure anchor link navigation | medium | pass | none |
| S6 Test Overview anchor link navigation | medium | pass | none |
| S7 Test FAQ anchor link navigation | medium | fail | F2 |
| S8 Test Explore anchor button | medium | pass | none |
| S9 Verify 404 handling on unknown paths | low | pass | none |
| S10 Verify Follow on X link | low | pass | none |
The audit
The Critic reviewed 2 findings and re-verified 0 of them live in the browser, replaying the reported steps on a fresh page.
- The 404 console error observed in S9 is a deliberate outcome of testing the handling of unknown paths.
What to fix first
- Add the missing 'stack' element ID to the landing page or update the 'Stack' header link destination (F1).
- Add the missing 'faq' element ID or remove the 'FAQ' navigation link if the content is unavailable (F2).
Coverage and caveats
In scope: Landing page initial load; External DApp launch links; Internal anchor link navigation; 404 error page handling.
Not covered: Web3 wallet interactions (the intake mentioned wallet capabilities, but the landing page AppMap reveals no wallet connection flow on this origin); DEX, NFT marketplace, and other app functionality (hosted on separate subdomains according to the AppMap).
- Testnet and Mainnet app links point to external subdomains, and the tester can verify navigation by observing the new URL.
- The 404 console error on load is a minor static asset failure that does not block core page rendering.
By the numbers
| Metric | Value |
|---|
| Scenarios | 8 passed, 2 failed, 0 blocked of 10 (28 planned steps) |
| Browser actions | 50 (10 clicks, 0 inputs, 14 navigations, 26 snapshots) |
| Screenshots | 19 (1 explore, 18 scenario, 0 critic), 18 captioned |
| Coverage | 2 pages, 0 forms, 2 flows, 1 console errors |
| Audit | 2 findings, 0 re-verified live, 2 confirmed, 0 promoted, 0 withdrawn |
| Model calls | 67 |
| Tokens | 256,294 input, 4,942 output, 7,327 thinking |
| Time | 5 min |
| Wallet | 0 transactions, 0 signatures, 0 refusals on chain 5042002 |
| Stage | Calls | Input | Output | Thinking | Seconds |
|---|
| explore | 7 | 30,341 | 835 | 1,081 | 43 |
| plan | 1 | 2,665 | 1,507 | 1,405 | 23 |
| test | 57 | 218,323 | 2,177 | 3,845 | 215 |
| critique | 1 | 3,552 | 189 | 481 | 7 |
| report | 1 | 1,413 | 234 | 515 | 8 |