WRDP

14 min read

2026-09-01 WPQP practice scan — QuizWizz polish leads

This is a dossier-to-design synthesis for the QuizWizz mega-polish drive. It covers the fourteen scored WPQP products, excludes the three controls, and records what the dossiers say rather than presenting a fresh browser observation. WPQP source references below are relative to /home/loca/dev/wpqp/q5vault/; the linked dossier headings are the published reading surface. Verdicts classify whether a practice should be reused in QuizWizz, not whether a product is good in the abstract. This bench record is releaseEligible: false.

Scores order this reading pass; they are not merit claims

WPQP’s score file says to consult coverage and completionPass rather than treating the weighted total as the benchmark. It also warns that the original-ten and expansion cohorts used different scoring methods, so small cross-cohort gaps reflect method rather than merit (evidence/audit-scores.json:3-4). The descending sequence below is a review index, not a product ranking adopted by QuizWizz.

Four locked reuse calls

  • Adopt Codevery’s anonymous zero-friction start path: no account or enrolment is required, although its surface still has one literal Start button (Codevery dossier § Signature-feature walkthrough, plugins/codevery-quiz.md:101-105).
  • Adopt Academy’s add-on-gated disclosure as a settings-tier precedent, while refusing its fresh-install discoverability failure: paid cards are visibly locked, but quizzes do not appear until an operator finds and enables the add-on (Academy dossier § Live coverage, plugins/academy.md:71-73; § Catches, plugins/academy.md:114-120).
  • Avoid Qwizcards’ inline-markup soup: it has no quiz builder, list, question editor or post type, and its TinyMCE-only Qwizard did not run on the captured WordPress version (Qwizcards dossier § Catches, plugins/qwizcards.md:115-122).
  • Avoid Forminator’s broken [forminator_quiz id="undefined"] embed state. The dossier says the shortcode remained undefined and no quiz rendered; installed QuizWizz source instead defines intentional locked and unavailable cards with actionable CTAs (plugins/forminator.md:47-58,96-101; wp/wp-content/plugins/quizwizz/includes/Frontend/QuizEmbed.php:70-76,89-96).

1. Sensei LMS

Order key — 84.90. The score row records completionPass: false; it is ordering metadata, not a recommendation (evidence/audit-scores.json:371-397).

  • Settings-UX lead — Keep unavailable capability visible and explain the boundary in context. Sensei’s disabled Ordering selector says what the type does and links to the Pro upgrade, while the free editor still exposes its six available question types (Sensei dossier § Live coverage, plugins/sensei-lms.md:71-75).
  • Play-start lead — Treat enrolment as a negative precedent for public QuizWizz play. The dossier records a logged-out preview with disabled answers and no completion control; the learner must enrol or sign in before an attempt exists (Sensei dossier § Catches, plugins/sensei-lms.md:113-118).
  • Embed-presentation lead — Do not make the native permalink or an iframe the only viable presentation. Sensei registers no quiz shortcode, its quiz block renders nothing outside quiz posts, and the dossier had to iframe the native quiz URL for an inline demo (Sensei dossier § Signature feature, plugins/sensei-lms.md:92-105; § Catches, plugins/sensei-lms.md:118).
  • Verdict — noted: Reuse explicit locked-capability disclosure and consider the local reporting model, but not the course gate or iframe-only presentation (Sensei dossier § Verdict, plugins/sensei-lms.md:141-143).

2. Tutor LMS

Order key — 83.74. The score row records completionPass: false (evidence/audit-scores.json:7-32).

  • Settings-UX lead — The course → topic → quiz hierarchy is legible for an LMS, but it is too much structure for a standalone QuizWizz setting or quiz. The dossier also records that every tested Tutor admin and authoring route later returned HTTP 500, so the hierarchy is not an unqualified implementation precedent (Tutor dossier § Live coverage, plugins/tutor.md:58-66; § Catches, plugins/tutor.md:89-94).
  • Play-start lead — Avoid an enrolment CTA that does not transition to an attempt. The captured Enroll Now action did not start the quiz and no score was observed (Tutor dossier § Catches, plugins/tutor.md:89-93).
  • Embed-presentation lead — Avoid replacing an embed with a link into a course funnel. The benchmark pages linked to the native course view, and the measured course shell was the roster’s heaviest front-end load at about 361 KB across 24 requests (Tutor dossier § Runtime weight, plugins/tutor.md:66-87).
  • Verdict — avoid: None of the captured settings, start or presentation paths should be copied into QuizWizz’s public standalone flow; the dossier itself says the live funnel was blocked (Tutor dossier § Verdict, plugins/tutor.md:114-116).

3. Quiz Maker by AYS

Order key — 83.24. The score row records completionPass: true (evidence/audit-scores.json:35-60).

  • Settings-UX lead — Co-locate answer text, points, correctness and explanation in one question row, and mark paid boundaries where the operator meets them. The captured editor exposes those controls together; advanced question and reporting capabilities are explicitly Pro-gated (Quiz Maker dossier § Visual evidence, plugins/quiz-maker.md:140-145; § Catches, plugins/quiz-maker.md:100-106).
  • Play-start lead — Keep the published quiz directly answerable for logged-out visitors. The dossier records a complete anonymous benchmark submission rather than an enrolment or account funnel (Quiz Maker dossier § Live coverage, plugins/quiz-maker.md:69-75).
  • Embed-presentation lead — Adopt the result-review hierarchy: percentage first, then corrections and explanations. The native completion showed 62.5%, marked incorrect answers, highlighted corrections and displayed explanation blocks; the timed signature also made the quiz-wide countdown visible (Quiz Maker dossier § Live coverage, plugins/quiz-maker.md:69-75; § Signature demo, plugins/quiz-maker.md:94-98).
  • Verdict — adopt: Reuse the public standalone path, control co-location and layered result review, not the product’s exact visual skin or Pro-only limits (Quiz Maker dossier § Verdict, plugins/quiz-maker.md:127-130).

4. PressPrimer Quiz

Order key — 79.60. The score row records completionPass: true (evidence/audit-scores.json:63-88).

  • Settings-UX lead — Present player consequences together: test/tutorial mode, save and resume, backward navigation, confidence capture and pass score are configured as one formal-exam model rather than scattered toggles (PressPrimer dossier § Signature demo, plugins/pressprimer-quiz.md:79-89; § Visual evidence, plugins/pressprimer-quiz.md:134-138).
  • Play-start lead — Make continuity obvious without forcing a second decision. With save/resume enabled, the observed surface displayed a resume indicator; test mode also prevented premature correct-answer reveal (PressPrimer dossier § Signature demo, plugins/pressprimer-quiz.md:79-87).
  • Embed-presentation lead — Use a compact formal result hierarchy when consequences matter: the result showed 100%, 6 / 6, a 60% required threshold and a confidence-review block, while the measured front end remained light (PressPrimer dossier § Live coverage, plugins/pressprimer-quiz.md:64-75; § Runtime weight, plugins/pressprimer-quiz.md:77-89).
  • Verdict — adopt: This is the strongest dossier precedent for consequence-oriented controls, resumable attempts and a legible formal result surface (PressPrimer dossier § Verdict, plugins/pressprimer-quiz.md:121-125).

5. H5P

Order key — 78.78. The score row records completionPass: true (evidence/audit-scores.json:91-116).

  • Settings-UX lead — Treat library-dependent capabilities as an operator-facing dependency, not an invisible promise. H5P’s usable question types depend on installed content libraries; the Hub request did not complete and the dossier had to import an official package (H5P dossier § Live coverage, plugins/h5p.md:49-61; § Catches, plugins/h5p.md:92-96).
  • Play-start lead — Preserve direct anonymous completion even when the player is isolated. A logged-out visitor answered and submitted the Question Set inside its iframe and reached the native result view (H5P dossier § Observed completion, plugins/h5p.md:63-69).
  • Embed-presentation lead — Packaged interaction plus a self-contained iframe is a useful isolation reference, not a QuizWizz target architecture. The same library stack embeds reusable Question Set and Boardgame content, but adds a moderate iframe-and-assets footprint (H5P dossier § Signature demo, plugins/h5p.md:88-90; § Runtime weight, plugins/h5p.md:71-86).
  • Verdict — noted: Reuse the ideas of portable packages and anonymous completion; avoid importing library administration or an iframe boundary into the ordinary QuizWizz embed (H5P dossier § Verdict, plugins/h5p.md:114-116).

6. Academy LMS

Order key — 77.14. The score row records completionPass: false (evidence/audit-scores.json:287-312).

  • Settings-UX lead — Adopt the add-on-gated disclosure as a settings-tier precedent: a named switch reveals Quizzes, paid cards stay visible behind lock treatment, and unavailable question types are disabled rather than silently omitted. Preserve the tension: quizzes are invisible until the operator discovers Add-ons, so the disclosure is good but the entry-point discoverability is not (Academy dossier § Live coverage, plugins/academy.md:71-75; § Catches, plugins/academy.md:114-120).
  • Play-start lead — Avoid coupling start to enrolment and account state. Public access is Pro-locked, the anonymous CTA opens login, and the free tier withdrew Start Quiz after one attempt (Academy dossier § Live coverage, plugins/academy.md:77-79).
  • Embed-presentation lead — Avoid a course-card-only substitute for an embed. Academy registers no quiz shortcode, ordinary pages can only advertise the course, and the tested enrol-form shortcode failed with HTTP 400 (Academy dossier § Runtime measurements, plugins/academy.md:98; § Signature walkthrough, plugins/academy.md:108; § Catches, plugins/academy.md:116-121).
  • Verdict — adopt: The adoption is deliberately narrow: use its explicit add-on and locked-card disclosure to inform QuizWizz settings tiers; reject its hidden fresh-install entry point, enrolment gate and course-only presentation (Academy dossier § Verdict, plugins/academy.md:143-145).

7. Quiz and Survey Master

Order key — 75.62. The score row records completionPass: true (evidence/audit-scores.json:119-144).

  • Settings-UX lead — Segment authoring by task. The free wizard and Questions tab handle quiz construction, while the Contact tab owns local Name and Email capture; keep that separation, but do not force essentials into separately priced add-ons (QSM dossier § Live coverage, plugins/quiz-master-next.md:55-70; § Signature walkthrough, plugins/quiz-master-next.md:91-96; § Catches, plugins/quiz-master-next.md:102-108).
  • Play-start lead — Retain a direct shortcode-to-attempt path. The Core Six rendered through [qsm quiz="1"], and the logged-out browser run completed and returned a result (QSM dossier § Runtime measurements, plugins/quiz-master-next.md:74-87; § Signature walkthrough, plugins/quiz-master-next.md:91-96).
  • Embed-presentation lead — The inline shortcode is reusable, but its generic default completion message is not a presentation model; richer result pages and conditional feedback sit behind add-ons (QSM dossier § Signature walkthrough, plugins/quiz-master-next.md:91-96; § Catches, plugins/quiz-master-next.md:102-106).
  • Verdict — noted: Reuse the task-tab separation and direct inline attempt; do not copy the generic result or modular paid fragmentation (QSM dossier § Verdict, plugins/quiz-master-next.md:126-128).

8. HD Quiz

Order key — 75.14. The score row records completionPass: true (evidence/audit-scores.json:147-172).

  • Settings-UX lead — Group timer, answer marking, correct-answer reveal, pass/fail copy and explanation fields around the outcome they change. The native settings exposed that compact consequence set without an add-on (HD Quiz dossier § Signature walkthrough, plugins/hd-quiz.md:90-96).
  • Play-start lead — Use an explicit start gate only when it protects a real consequence. The captured ten-second timer became visible after QUIZ START; the dossier does not establish that gate as useful for an untimed quiz (HD Quiz dossier § Signature walkthrough, plugins/hd-quiz.md:90-98).
  • Embed-presentation lead — Adopt the runtime restraint and clear terminal state. The anonymous native wrapper completed at 10 / 10 — 100%, while the Core-Six page used ten requests, about 87.7 KB and no jQuery (HD Quiz dossier § Live benchmark, plugins/hd-quiz.md:54-70; § Runtime measurements, plugins/hd-quiz.md:72-88).
  • Verdict — adopt: Reuse the lean client, compact outcome settings and timer-specific start semantics; do not infer a universal Start gate or ordering support (HD Quiz dossier § Audit score and verdict, plugins/hd-quiz.md:107-120).

9. Chained Quiz

Order key — 72.14. The score row records completionPass: true, notwithstanding the result anomaly below (evidence/audit-scores.json:175-200).

  • Settings-UX lead — Colocate branch destinations with the answers and points that drive them. The captured editor shows answer rows, points and answer-destination selectors together (Chained Quiz dossier § Visual evidence, plugins/chained-quiz.md:100-113).
  • Play-start lead — The useful progression precedent is answer-dependent goto: Core Six choices move to the next question, while the signature’s first answer chooses a Physics or Chemistry branch before reconverging (Chained Quiz dossier § Live benchmark coverage, plugins/chained-quiz.md:45-51; § Documented capabilities, plugins/chained-quiz.md:74-83).
  • Embed-presentation lead — Result arithmetic must be invariant-proved before presentation polish is trusted. The native completion displayed the impossible Score: 10 / 9 (100%) (Chained Quiz dossier § Observed result anomaly, plugins/chained-quiz.md:53-59; § Visual evidence, plugins/chained-quiz.md:100-106).
  • Verdict — noted: The branch editor and deterministic goto flow are worth studying, but the observed score breach blocks adoption of its progression/result implementation as a unit (plugins/chained-quiz.md:45-59,100-113).

10. Watu Quiz

Order key — 71.52. The score row records completionPass: true (evidence/audit-scores.json:203-228).

  • Settings-UX lead — Adopt configurable grade-band consequences, not the less-visual split authoring model. Watu assembles exams from a global question bank and lets the operator define immediate score bands in the free plugin (Watu dossier § Signature demo, plugins/watu.md:91-93; § Catches, plugins/watu.md:95-101).
  • Play-start lead — Keep an anonymous shortcode path with no account funnel. The dossier’s logged-out Chromium run answered [watu], submitted and returned a score (Watu dossier § Live coverage, plugins/watu.md:49-74).
  • Embed-presentation lead — Pair immediate score with a named consequence band on a small client footprint. The result showed score plus Needs review/Passed/Excellent bands; the Core-Six page used eight requests, about 113 KB and no jQuery (Watu dossier § Observed completion, plugins/watu.md:68-74; § Runtime weight, plugins/watu.md:76-89).
  • Verdict — adopt: Reuse the compact grade-band communication, anonymous inline path and runtime restraint; leave the dated bank/exam split behind (Watu dossier § Verdict, plugins/watu.md:103-105).

11. Forminator

Order key — 69.28. The score row records completionPass: false (evidence/audit-scores.json:231-256).

  • Settings-UX lead — A polished mode chooser is not evidence that its save path works. The admin offered Knowledge Quiz, Personality Quiz, Collect Leads and integrations, but Publish returned Something went wrong while saving your quiz, left the module unsaved and created no quiz post (Forminator dossier § Funnel versus live proof, plugins/forminator.md:47-58; § Visual evidence, plugins/forminator.md:134-147).
  • Play-start lead — There is no reusable start practice in the captured state: nothing persisted, no front-end attempt existed, and all Standard Ten rows remained unsupported on that bench (Forminator dossier § Standard Ten coverage, plugins/forminator.md:58-77).
  • Embed-presentation lead — Avoid the broken [forminator_quiz id="undefined"] render state. The dossier precisely says the shortcode stayed undefined and no native quiz rendered; by contrast, installed QuizWizz source returns a locked Password required card with an Open CTA or an unavailable card with a Browse CTA (plugins/forminator.md:56-58,96-101; wp/wp-content/plugins/quizwizz/includes/Frontend/QuizEmbed.php:70-76,89-96).
  • Verdict — avoid: Do not borrow the mode-card polish, lead funnel or embed contract until the underlying save-to-render path can be proven; the dossier stops at documented intent (Forminator dossier § Verdict, plugins/forminator.md:128-132).

12. Qwizcards

Order key — 64.60. The score row records completionPass: true (evidence/audit-scores.json:343-368).

  • Settings-UX lead — Avoid authoring by undocumented structure. Qwizcards has no builder, quiz list, question editor or post type; its only admin page documents bracket vocabulary, and its TinyMCE-only Qwizard did not run in the captured block editor (Qwizcards dossier § Live coverage, plugins/qwizcards.md:73-79; § Catches, plugins/qwizcards.md:115-122).
  • Play-start lead — The positive counter-evidence is a complete anonymous attempt with immediate per-choice feedback and free-form grading. Keep that low-friction learner behavior separate from the authoring verdict (Qwizcards dossier § Live coverage, plugins/qwizcards.md:75-81).
  • Embed-presentation lead — Avoid the inline-markup soup and duplicated client render. The whole quiz lives in [qwiz] page content; the server ships hidden raw source plus a fallback, and 42 JavaScript files build a six-question widget measuring about 506 KB and 741 DOM nodes (Qwizcards dossier § Live coverage, plugins/qwizcards.md:73-79; § Runtime measurements, plugins/qwizcards.md:85-100).
  • Verdict — avoid: Free breadth, flashcards and anonymous completion do not offset the broken authoring path, inline-markup soup, missing local result store and heavy client assembly for QuizWizz’s reuse goals (Qwizcards dossier § Verdict, plugins/qwizcards.md:143-147).

13. Quiz Cat

Order key — 61.92. The score row records completionPass: true (evidence/audit-scores.json:259-284).

  • Settings-UX lead — A simple answer/correctness editor with an adjacent Premium rail makes the boundary visible, but the free model stops at single-answer multiple choice and gates personality, lead and analytics features (Quiz Cat dossier § Pricing, plugins/quiz-cat.md:39-43; § Visual evidence, plugins/quiz-cat.md:119-134).
  • Play-start lead — Keep the drop-in anonymous route for a deliberately small quiz. The free Core Six published through [quiz-cat id="5"], and a logged-out run completed to a native score/result label (Quiz Cat dossier § Standard Ten coverage, plugins/quiz-cat.md:45-68; § Runtime measurements, plugins/quiz-cat.md:70-85).
  • Embed-presentation lead — A compact score plus memorable named outcome (Grumpy Cat) can make a lightweight engagement feel finished; the measured page used eight requests, about 117 KB and no jQuery, but the presentation cannot compensate for missing question types (Quiz Cat dossier § Live benchmark result, plugins/quiz-cat.md:64-68; § Runtime measurements, plugins/quiz-cat.md:70-85).
  • Verdict — noted: Keep the low-friction, low-weight MCQ pattern in view; it is too narrow to serve as the general QuizWizz settings or result model (Quiz Cat dossier § Verdict, plugins/quiz-cat.md:115-117).

14. Codevery Quiz

Order key — 56.60. The score row records completionPass: true (evidence/audit-scores.json:315-340).

  • Settings-UX lead — Reuse the compact bank-and-tabs organization: questions are reusable posts, quizzes select them through Questions / Settings / Coupon, and the disabled coupon path names its WooCommerce dependency. Do not copy the TinyMCE rebuild trap that can silently discard raw-textarea edits (Codevery dossier § Pricing, plugins/codevery-quiz.md:53-55; § Live coverage, plugins/codevery-quiz.md:74-76; § Catches, plugins/codevery-quiz.md:113-121).
  • Play-start lead — Adopt the anonymous zero-friction start path. A logged-out visitor used the inline Start control, completed without an account and received a server-scored result through the unauthenticated submission hook. The literal Start button matters: “zero-friction” here means no login or enrolment, not zero clicks (Codevery dossier § Signature walkthrough, plugins/codevery-quiz.md:101-105).
  • Embed-presentation lead — Keep block and shortcode output on one render path, then reveal feedback where the answer was chosen. Codevery’s dynamic block delegates to its shortcode, and instant grading expands the wrong choice, the correct choice and their explanations in place before Next becomes available (Codevery dossier § Signature walkthrough, plugins/codevery-quiz.md:101-107).
  • Verdict — adopt: Adopt the anonymous no-account path, shared block/shortcode renderer and per-card feedback contract. The verdict does not import its narrow two-radio type model, generic namespace or unproven maintenance profile (Codevery dossier § Verdict, plugins/codevery-quiz.md:141-145).