Wren Beta — what that means

play-cricket.com

readable

B Good. A minor flaw or two

Loading speed is diagnostic only; it does not affect this grade or search ranking.

SubjectWeightScore
Interruption 35.71% 100
Readability 28.57% not scored
Accessibility and keyboard 21.43% 66
Stability and weight 14.29% 100

This letter rests on 71% of the grade. Readability was measured but is not scored here. We have not measured an article for this site. Homepages, listings and other non-article pages can make our typography measurements reflect navigation rather than prose. The numbers are below; the letter leaves them out until we have measured an article. How this is worked out.

play-cricket.com
Largest paint
1.4s
Paywall
none
Ad requests
0
Tracker requests
10
Page weight
621 KB
Readability
16px type · 1.2 line height · 143 characters per line · 18.8:1 contrast
Accessibility
1 automated check failed (1 serious)
Green hosting
not measured
Measured
2026-09-01

Observed interruptions

Ad and tracker counts above are network requests, not counts of visible ads or separate companies. They do not affect the interruption score.

Assessed 1 sampled page. The largest detected ad area was 0% of a sampled viewport. No qualifying obstructive prompts were detected.

This is a sample, not a promise that the whole site has no interruptions. Ad detection can miss formats and content outside the sampled view. Older scans did not check visibility or overlapping ad rectangles as thoroughly. The score uses the strongest observed deduction, so one panel is not penalized under multiple names. How interruptions are scored.

The type, and who can use it

Measured on 1 rendered page; latest measurement 2026-09-05 — no article measured yet. Every number is a mechanical fact about the page, not a judgment of its design.

WhatMeasuredThe bar
Body type size 16px, 13px at phone width 16px, the browser default
Characters per line 143 45–90
Line height 1.20 1.5 (WCAG 1.4.8)
Text contrast 18.8:1 4.5:1 (WCAG AA), 7:1 (AAA)
Text column 99% of the window at least 45%
Reflows at phone width no — scrolls sideways at 360px WCAG 1.4.10
Dark mode respects the system setting noted, not scored
Automated accessibility checks 1 automated check failed (1 serious): document-title WCAG 2.1 A and AA, via axe-core
Keyboard not measured never trapped, always visible
Structure no main landmark, 1 h1, no skipped heading levels a main landmark, one h1, no skips
Alt text 0% of 1 content images described every content image
Reader mode not measured parses (Firefox’s Readability)

Automated accessibility checks catch an estimated 30–40% of real problems, so “no automated violations detected” is a floor, not a certificate. We never say “accessible”. How these are scored.

Measurement dates

Oldest evidence 50 days old. At least one subject is due for rechecking (30 days or older). Dates refer to the evidence, never the card rebuild.

Measurement history

Newest 2 saved observations. Each describes a sampled page at that time; older, failed or held observations do not override the current reviewed card. Raw automated findings may have been superseded by later review or detector replay. No previous grade is inferred.

Read dated observations
  1. — Readability and accessibility observation; prose source p; desktop type 16px; phone overflow observed
    https://www.play-cricket.com/
    Evidence source: readability-top5000.jsonl · observation 2248b2353fc3
  2. — Access observation: pass
    https://play-cricket.com/
    Evidence source: verdicts-top5000.jsonl · observation 3710d2054de4

How we know

Pages rendered1
Site verdicterrors dropped; majority of remaining; ties to the stricter verdict; active reviewed exclusions override admission
Figures shownnumeric measurements generally use medians; interruption costs, overflow, keyboard traps and accessibility failures retain the strongest observed finding
Cited by1,438 encyclopedia articles

Think this is wrong? It may well be — the measurements cover only a handful of pages. Any reviewed admission decision and its dated evidence are shown above. Re-measurement on request is not built yet, so there is no button here that would do anything. When it exists it will be free and it will be on this page.