This is a sample report. The site, people, numbers and visits are made up, and the screenshots are drawings. Everything else is exactly what a client receives: the same layout, sections and evidence, made by the same code. Back to SourceCode QA

SourceCode QA

Developer report: Example Shop / Production, 1 Sep 2026 to 30 Sep 2026

1 Sept 2026 to 30 Sept 2026, compared with the same length of time before. Generated 30 Sept 2026.

Summary

Open issues

1 critical, 2 high

New issues

previous period: 41

Fixed

previous period: 27

Came back

previous period: 2

Critical flows passing

93%

56 of 60 runs

Main content appears

2.1 s

was 2.5 s

Accessibility problems open

0 new this period, previous period: 1

Security weaknesses open

0 new this period, previous period: 0

Open by severity: 1 Critical · 2 High · 3 Medium · 0 Low

Business-critical areas with critical or high issues: Checkout (1), Account (1)

What to fix first

Ranked by how serious each is, how sure we are it is the site's fault, how many pages it is on, and whether it touches checkout, accounts or another page the business depends on. Problems seen from one location only are listed separately below, and ones that only follow from a page failing to load are left out.

Critical QA-214: JavaScript exception: Cannot read properties of undefined (reading 'postcode')
Confirmed (real visitors met it), on 1 page, including checkout.
High QA-198: Server error on /account/orders
Confirmed (failed again when asked a second time), on 3 pages, including account.
Medium QA-205: Page scrolls sideways
Confirmed (seen in every one of 4 tests of its pages), on 37 pages, including product.
Medium QA-187: Accessibility: form field has no label
Confirmed (seen in every one of 4 tests of its pages), on 9 pages, including newsletter sign-up.

Failing from one location only

Each of these failed from our scanner's location, again on its recheck, and loaded from another location. That can mean visitors in that region are being turned away (a firewall, a country rule, a regional outage), or only that our scanner was. Check from that region before deciding.

High QA-176: Page fails from some locations only
https://shop.example/stores/berlin

Key findings

Needs attention: Checkout breaks on iPhone-sized Safari: the test-card payment flow failed on 29 Sep, and 3 real visits met the same JavaScript error.
Needs attention: QA-214 came back after being verified as fixed on 21 Sep.
Good: 32 issues were fixed and verified this month, 5 more than in August.
Note: One page failed only from our scanner in Germany and loaded from the United States. It is listed separately rather than as a fault.

Every check

Every kind of check this site can have, how often it ran in this period and what it found. Results below are each site's latest run in the period.

Check	In this period	Result
Availability	8640 page checks	99% of 8,640 checks answered; 12 did not.
Crawl	30 runs	1,284 addresses found; 4 still failing after a recheck; 1 failed only for our scanner.
Browser test	4 runs	800 page results: 794 passed, 6 failed.
Accessibility	4 runs	1 problem found on 200 pages.
Performance	4 runs	40 page measurements; main content appears in 2.1 s (middle of them).
Visual comparison	0 runs	Never run on this site.
Passive security	4 runs	Nothing found.
Active security scan	0 runs	Never run: an active scan attacks the site, so it needs a written sign-off first.
Flows	60 runs	56 of 60 runs passed.
Payment tests	30 test payments	28 of 30 test payments went through.
Real users	18420 visits	18,420 visits; 1% met an error.

Results by check

Availability

Example Shop / Production (latest run: finished, 30 Sept 2026)

Pages watched: 3
Answered: 8,628 of 8,640
Last failure: /checkout answered 502

Crawl

Example Shop / Production (latest run: finished, 30 Sept 2026)

Pages: 1,284
Failed at first: 61, mostly under the crawl's own load
Still failing after a recheck: 4
Failed only for our scanner: 1 (loaded normally from a second location)

Still failing after a recheck
Address	Answered	Linked from
/account/orders?page=2	500	1
/account/orders?page=3	500	1
/discontinued/wool-scarf	404	6
/blog/summer-sale-2024	404	2

Browser test

Example Shop / Production (latest run: finished, 29 Sept 2026)

Browsers: Chromium desktop, Chromium phone, WebKit phone, Firefox desktop
Pages per test: 50

Trends

Issues found and fixed FoundFixed

Flow runs RanPassed

Main content appears (LCP) PhoneDesktop

Top open issues

Issue	Site	Occurrences	Pages
Critical JavaScript exception: Cannot read properties of undefined (reading 'postcode') QA-214	Production	18	1
High Server error on /account/orders QA-198	Production	6	3
Medium Page scrolls sideways QA-205	Production	41	37
Medium Accessibility: form field has no label QA-187	Production	9	9
High Page fails from some locations only QA-176	Production	3	1

Flows

Flow	Runs	Passed	Last run
Buy a product with a test card Critical Production	30	93%	failed
Sign in and see past orders Critical Production	30	93%	passed

Slowest pages

Page	As a	Main content
/products	Phone	3.9 s
/	Phone	2.8 s

Developer appendix

The most serious open issues first, with the evidence from each one's latest occurrence.

Critical QA-214: JavaScript exception: Cannot read properties of undefined (reading 'postcode')

Status: Regression
Where: https://shop.example/checkout
Browser: webkit, Phone (390 x 844)
Timing: first byte 182 ms, loaded 1.9 s
Confidence: Confirmed: Real visitors met it
Found by: Browser test, Real users
Areas: Checkout
Seen: 18 times on 1 page, 4 Sept 2026 to 29 Sept 2026
Fingerprint: sample-214-js_exception
Real visits: 3 with the same error: visit 7f3e, visit 91ac, visit c02d

TypeError: Cannot read properties of undefined (reading 'postcode')

TypeError: Cannot read properties of undefined (reading 'postcode')
    at validateAddress (https://shop.example/assets/checkout.4f2a1c.js:1:18234)
    at HTMLFormElement.onInput (https://shop.example/assets/checkout.4f2a1c.js:1:19102)

To see it

Open https://shop.example/checkout in webkit, Phone (390 x 844).
Open the browser's console: TypeError: Cannot read properties of undefined (reading 'postcode') appears as the page loads.

Screenshot of https://shop.example/checkout when QA-214 was found

High QA-198: Server error on /account/orders

Status: Open
Where: https://shop.example/account/orders?page=2
Request: GET https://shop.example/account/orders?page=2
Response: 500
Timing: first byte 4.2 s
Confidence: Confirmed: Failed again when asked a second time
Found by: Crawler, Browser test
Areas: Account
Seen: 6 times on 3 pages, 12 Sept 2026 to 29 Sept 2026
Fingerprint: sample-198-http_server_error

To see it

Open https://shop.example/account/orders?page=2.
Watch the network panel: GET https://shop.example/account/orders?page=2 answers 500.

Medium QA-205: Page scrolls sideways

Status: Open
Where: https://shop.example/products/linen-shirt
Browser: chromium, Phone (390 x 844)
Selector: table.size-guide
Confidence: Confirmed: Seen in every one of 4 tests of its pages
Found by: Browser test
Areas: Product
Seen: 41 times on 37 pages, 3 Sept 2026 to 29 Sept 2026
Fingerprint: sample-205-horizontal_overflow

The page is 412 px wide on a 390 px screen.

To see it

Open https://shop.example/products/linen-shirt in chromium, Phone (390 x 844).
Find table.size-guide on the page: that element is where the problem above is.

Screenshot of https://shop.example/products/linen-shirt when QA-205 was found

Medium QA-187: Accessibility: form field has no label

Status: Open
Where: https://shop.example/newsletter
Browser: chromium, Desktop (1440 x 900)
Selector: input#nl-email
Confidence: Confirmed: Seen in every one of 4 tests of its pages
Found by: Accessibility
Areas: Newsletter sign-up
Seen: 9 times on 9 pages, 1 Sept 2026 to 29 Sept 2026
Fingerprint: sample-187-a11y_violation

Form elements must have labels (WCAG 2.1 A, 1.3.1 and 4.1.2).

To see it

Open https://shop.example/newsletter in chromium, Desktop (1440 x 900).
Find input#nl-email on the page: that element is where the problem above is.

High QA-176: Page fails from some locations only

Status: Open
Where: https://shop.example/stores/berlin
Request: GET https://shop.example/stores/berlin
Response: 403
Confidence: One location only: Failed from our scanner's location and loaded normally from another. It may affect real visitors near our scanner, or only our scanner
Found by: Crawler
Seen: 3 times on 1 page, 22 Sept 2026 to 29 Sept 2026
Fingerprint: sample-176-region_specific_error

Refused (403) from Falkenstein, Germany on two attempts an hour apart; loaded normally (200) from Ashburn, United States.

To see it

Open https://shop.example/stores/berlin.
Watch the network panel: GET https://shop.example/stores/berlin answers 403.

Seen only on pages that failed to load

Each of these was only ever seen on a page that answered with an error, so it describes the error page rather than the site. Fix the failing pages above first; these should go with them.

Issue	Page answered	Pages
QA-209: Image does not load	404	1