Outside-in audit
pinescriptstrategy.com
Published by the site owner, who proved control of pinescriptstrategy.com on 2026-10-30.
Badge for your own site: <a href="https://zpe.vc/p/audit/r/5599457209df"><img src="https://zpe.vc/p/audit/b/5599457209df.svg" width="220" height="52" alt="Audited outside-in, pinescriptstrategy.com"></a>
Mobile performance
Lighthouse band: poor
A visitor on a mid-range phone waits 5.9 s before the main content appears, and the page asks them to download 0.55 MB to see it.
0 fail 2 warn 67 accessibility 100 SEO
What you can fix yourself, without us
- Write a meta description of 120 to 160 characters; it is the sentence search results show.
- Add the missing security headers (HSTS, CSP, Referrer-Policy, framing protection). They are free and they close the cheap attacks.
- Publish an llms.txt: a short markdown map of your best pages, so AI assistants quote you accurately.
These are free, and you are welcome to do them with a developer you already trust. If that is enough, this audit has done its job.
This pass read 6 pages. The whole site crawl is free: every page, every internal link, and an inventory you can hand to a developer. It asks for an address, and the report is a link that keeps working after you close the tab.
Want the deeper report? With read-only access we can see plugin versions, database size, backups and what you actually pay each month, which is the half that decides whether a migration is worth it.
Speed, measured by Lighthouse
Lighthouse 13.5.0, mobile, run on a real browser
Measured from a server in Helsinki, Finland, using a simulated mid-range phone on a mobile connection. Where that server sits is part of the score: visitors closer to it see faster times than visitors further away, so a site with customers on the other side of the world can score lower here than it feels in practice. Every audit is measured from the same place, which is what lets you compare one report against another. One run also moves by a few points on its own, so treat a change as real only when it repeats.
| Biggest single wins | Time | Bytes |
|---|---|---|
| Reduce unused JavaScript | 610 ms | |
| Initial server response time was short | 346 ms |
Lighthouse's own estimates for this page. They describe where the time goes, not what a rebuild costs.
Everything we checked
44 checks across 8 layers. A FAIL is something a scanner can act on. A WARN is a door that is common but does not need to be open.
Not requested: the PII audit. Nothing in this report says anything about it.
Discovery and AI readiness
7 clear
| 7 passed XML sitemap, Pages read, Sitemap named in robots.txt, llms.txt for AI agents, Favicon, Web app manifest, RSS feed. |
Crawlability and indexation
6 clear
| 6 passed Search engines allowed, Indexable, Canonical tags, HTTP redirects to HTTPS, www and bare domain agree, Missing pages return 404. |
On-page basics
1 warn · 7 clear
| Meta descriptions | WARN | 1 of 6 pages are missing a description or sit outside 80 to 200 characters/about 2 |
|---|---|---|
| 7 passed Page titles, One H1 per page, Social preview tags, Structured data, Image alt text, Page language declared, Mobile viewport. | ||
Security headers
1 warn · 7 clear
| Content Security Policy | WARN | present but allows inline or evaldefault-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanag |
|---|---|---|
| 7 passed HSTS, MIME sniffing blocked, Clickjacking protection, Referrer policy, Permissions policy, Cross-origin opener policy, Server banner. | ||
Email and DNS
5 clear
| 5 passed Receives email at the domain, SPF, DMARC, DKIM, Branded email. |
Doors a scanner knocks on
9 clear
| 9 passed What the site runs, Version disclosed in markup, readme.html, Author names via API, XML-RPC, Login page, Uploads listing, Debug log, .env file. |
Server runtime
1 clear
| 1 passed PHP runtime. |
The pages we read
| Page | Title | H1 | Description | Canonical | Alt text |
|---|---|---|---|---|---|
| / | 43 ch | 1 | 123 ch | self | 100% |
| /about | 45 ch | 1 | 2 ch | self | 100% |
| /posts/free-trader-risk-tolerance-assessment-quiz | 65 ch | 1 | 163 ch | self | 100% |
| /posts/trading-psychology-profile-assessment-quiz | 46 ch | 1 | 163 ch | self | 100% |
| /tools | 48 ch | 1 | 116 ch | self | 100% |
| /tools/strategy-optimizer-pro | 45 ch | 1 | 149 ch | self | 100% |
Every check below ran on every page in this table, and each finding names the worst page it found it on.
Where we could help
- Security hardening: the headers this audit found missing, set and tested.
- On-page basics: titles, descriptions, headings and alt text, written per page rather than templated.
- A migration: the site as static files on Cloudflare's edge, with the editing workflow kept or replaced entirely.
What this audit cannot see
It ran without server access, so it cannot see plugin versions, the database, backups, logs, or your invoices. Three measurements a Worker cannot make are also absent rather than guessed: TLS certificate details, the HTTP protocol version, and whether the origin compresses. So is the PHP version under your site, unless the server volunteers it in a response header, which none of the twenty-two sites we sampled did. That layer is worth naming because two remote code execution flaws in PHP itself are being exploited in the wild as of 21 October 2026, and no scanner outside your server can see whether you are patched. They are in the deeper report.