The 12Axes test
The 12Axes test turns political statements into twelve separate readings rather than one left-versus-right score. This guide explains what happens before, during, and after a run.
12Axes Not Working? Diagnose It
Most loading problems are local, but you should not have to guess. This page gives a decision tree for isolating browser, network, device and site-side symptoms.
Short answer: Reload the page, test another browser or network, and compare results from another device. If the problem persists, email support with the URL, browser, device, time, error text and a screenshot.
Start with this decision tree
- Check your connection, then reload the page. If other websites also fail, resolve the network issue first.
- Open /test in a private window or another browser. If it works there, a browser extension or cached file is the likely difference.
- Try mobile data or another Wi-Fi network. A change points to the original network, DNS filter or proxy.
- Use another device on a different connection. If only one device fails, clear that browser’s site data or update it.
- Ask whether another person can open the same URL. A single report is not enough to establish a site-wide incident.
- If the problem continues across browsers, devices and networks, send a bug report with the details below.
What “Failed to fetch” can mean
“Failed to fetch” is a browser message, not a precise 12Axes diagnosis. It can appear when a request is blocked, interrupted, redirected unsafely, sent to an unreachable address, or prevented by browser security rules.
- The device has no working internet connection.
- A browser extension, content blocker or privacy setting interrupted the request.
- A corporate, school or mobile network filters the destination.
- DNS, a proxy or a VPN cannot reach the host correctly.
- A required page asset failed during loading.
The scoring calculation itself does not require a 12Axes test API: it runs in the browser from the loaded application. A fetch error therefore does not by itself prove that the scoring service is down.
Protect your unfinished answers first
Progress is stored in the browser. Before clearing site data, try another browser first. If you must clear data on the affected browser, an unfinished run stored there may be removed; a finished result link will still contain the encoded scores.
If a page is stuck, avoid repeatedly starting new runs until you know whether the saved progress can still be resumed. Open the test page and look for the unfinished-run notice before resetting.
How to report a reproducible problem
Email support@12axes.io after the cross-browser and cross-network checks. Include enough information for someone to reproduce the issue:
- The full URL and whether the failure occurs on the homepage, /test or /results.
- Date, time and timezone.
- Device, operating system, browser and version.
- Network type and country, plus whether a VPN or proxy was in use.
- The exact error text and a screenshot or console snippet.
- Whether another browser, device or network succeeds.
Do not include payment details in an email. If the problem concerns an order, use the purchase email and order reference rather than card information.
What this page cannot establish
This page does not claim a current incident, a resolved outage, or a specific third-party API failure. A live status cannot be inferred from one local error. Reports that reproduce across independent networks are the evidence needed before making any site-wide statement.
Put the guide into practice
The explanation above is easier to judge against your own answers than against an abstract example. Choose a run length and see which political values move for you.
Frequently asked questions
Why does 12Axes show “Failed to fetch”?＋
That message means the browser could not complete a request. It can be caused by connectivity, an extension, DNS, a filtered network, a browser security rule or a failed page asset. It is not enough on its own to identify one cause.
How can I tell whether 12Axes is down?＋
Check the same URL from another browser, device and network, and see whether another person can open it. Only a reproducible failure across independent users and networks suggests a possible site-wide issue.
Will clearing my browser data delete my unfinished test?＋
It can, because unfinished progress is stored locally. Try another browser first, and clear site data only after deciding that the saved run is no longer needed.
What should I include in a 12Axes bug report?＋
Include the URL, date and timezone, device, OS, browser version, network/VPN details, exact error text, screenshot or console output, and whether another browser or network succeeds. Never include card details.
Where do I get help with a paid report?＋
Use the purchase email and order reference when contacting support. For the free test, the URL and browser details are usually more useful than an order number.
Read a related guide
Reading your results
A 12Axes result contains twelve positions, ranked comparisons and a shareable link. This guide explains how to read those pieces without treating the profile as a scientific verdict.
About the project
12Axes exists to make a political profile easier to explain and argue with: twelve defined dimensions, transparent comparisons, and clear limits on what a result means.
Or return to the 12Axes homepage for the product overview, report pricing and main FAQ.
Your political values are one run away
The test is free, needs no account, and scores your answers in this browser. Start with the recommended run, or take the longest one when two ideologies sit close together.