Turn this website into the experiment.
Press one button to test Solithra's actual published homepage and logo from your browser. View response time, file size and SHA-256 integrity through different observation lenses. Every measurement comes from your run, not a fictional dashboard.
The site we're measuring
These are the reference files saved with this release. They're not traffic counts or real-time response times.
Reference route: /
Reference route: /static/solithra-logo.jpeg
Each run downloads real site resources, rather than calculating simulated speeds.
Run a fresh site test
We'll request the homepage three times, then the logo three times, measuring each response and checking the returned bytes against the published reference fingerprints.
Tests start only when you press Run. Measurements stay in this browser unless you explicitly download the evidence. This demo doesn't create accounts, cookies or its own visitor analytics. The hosting provider may retain ordinary server access logs.
One experiment. Multiple ways to see it.
Switch perspectives without changing the measurements. These are browser-based demonstrations of CFLab's observation principles, not execution of its desktop lens plugins.
Response time
Compare observed full-download times. Results reflect this visitor's device, connection, server and caching conditions.
Downloaded content size
Compare the decoded bytes received. These are not bandwidth or compressed bytes on the wire.
SHA-256 integrity
Compare the returned files against this release's published fingerprints. A mismatch can also mean a newer website version or a cached copy—not necessarily tampering.
| Resource | Observed SHA-256 | Result |
|---|---|---|
| No samples yet | ||
No completed experiment
Reproducible evidence includes the test settings, timestamps, response times, decoded file sizes, HTTP status and SHA-256 fingerprints. The browser does not sign this record or prove where it originated.
What's real—and what this cannot claim.
What this test actually measures
For each of two same-origin HTTPS resources, the browser issues three GET requests with unique query values and asks its cache to reload. It records elapsed time from the start of each fetch through reading the response body, decoded body size, HTTP status and SHA-256.
Varnish or other intermediate caching may still serve the resource. A browser run measures the end-to-end experience at that moment, not server CPU, website uptime or global average speed.
How this relates to CFLab
Experiment: repeated identical requests under a fixed protocol. Original evidence: independent timing and content readings. Lenses: response-time comparison, numerical size comparison and cryptographic integrity checking. JSON export preserves a reproducible record of observed inputs and outputs.
This limited browser demo does not run the CFLab desktop engine, calculate Bitcoin mining proof-of-work, predict mining winners, or claim scientific validation.