Free read · outside-in
pinescriptstrategy.com
Report/r/c34f874f0c84
Published by the site owner, who proved control of pinescriptstrategy.com on 2026-11-07.
0 of 44 checks need work
0 fail·0 weak·44 pass
64 is Lighthouse's score for speed on this page. It counts nothing above, and a page can score 100 there and still fail 0 checks here.
What each layer scored
- Server runtime one check0/10%
- Discovery and AI readiness3/743%
- Doors a scanner knocks on7/978%
- Email and DNS4/580%
- Crawlability and indexation6/6100%
- On-page basics8/8100%
- Security headers8/8100%
The short version
Nothing needs fixing. All 44 checks passed.
The checks are listed in section 02, including what each one looked at.
Of 44 checks, 0 fail and 0 are weak. Nothing fails outright. This reads the instructions your site sends to browsers and mail servers, not the quality of what you make. Every check behind the three check figures is in section 02.
A visitor on a mid-range phone waits 5.4 s before the main content appears, and the page asks them to download 0.56 MB to see it.
01Change since the last audit
What changed since your last audit
Nothing changed that this audit measures: the sitemap lists the same addresses as it did on 7 November 2026, and the tracking container and the response headers are unchanged.
02Everything we checked
What you can fix yourself, without us
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.
Nothing cheap is left: what remains is structural.
Not requested: the PII audit. Nothing in this report says anything about it.
| Check | State | What it is, and what closes it |
|---|---|---|
| Discovery and AI readinessall 7 pass | ||
| 7 passed XML sitemap, Pages read, Sitemap named in robots.txt, llms.txt for AI agents, Favicon, Web app manifest, RSS feed. | ||
| Crawlability and indexationall 6 pass | ||
| 6 passed Search engines allowed, Indexable, Canonical tags, HTTP redirects to HTTPS, www and bare domain agree, Missing pages return 404. | ||
| On-page basicsall 8 pass | ||
| 8 passed Page titles, Meta descriptions, One H1 per page, Social preview tags, Structured data, Image alt text, Page language declared, Mobile viewport. | ||
| Security headersall 8 pass | ||
| 8 passed HSTS, Content Security Policy, MIME sniffing blocked, Clickjacking protection, Referrer policy, Permissions policy, Cross-origin opener policy, Server banner. | ||
| Email and DNSall 5 pass | ||
| 5 passed Receives email at the domain, SPF, DMARC, DKIM, Branded email. | ||
| Doors a scanner knocks onall 9 pass | ||
| 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 runtimeall 1 pass | ||
| 1 passed PHP runtime. | ||
no container found in the HTML. A container is optional: this says nothing about the site tracking you, only that this page loads no tag manager.
03What we measured
The pages we read
| Page | Title | H1 | Description | Canonical | Alt text |
|---|---|---|---|---|---|
| / | 43 ch | 1 | 123 ch | self | 100% |
| /about | 45 ch | 1 | 147 ch | self | 100% |
| /posts/calculating-the-correct-commission-type-for-strategies | 54 ch | 1 | 160 ch | self | 100% |
| /posts/top-5-pine-script-backtesting-mistakes-to-avoid | 47 ch | 1 | 160 ch | self | 100% |
| /testimonials | 30 ch | 1 | 112 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.
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 | 212 ms |
Lighthouse's own estimates for this page. They describe where the time goes, not what a rebuild costs.
Lighthouse
- Performance64
- Accessibility67
- Best practices73
- SEO100
- Largest paint5.4 s
- Page weight574 KB
What would buy the most, in milliseconds:
- Reduce unused JavaScript610 ms
- Initial server response time was short212 ms
Lighthouse 13.5.0, mobile, run on a real browser.
The numbers above, drawn. Each one shows how it is on the left and what it should be on the right.
A visitor waits 5.4 s before the main content appears
The page asks for 574 KB and paints its main content after 5.4 s, measured on a mid-range phone.
0 s5.4 s
That is what a new visitor sees: an empty screen, then the page. The score above is this, once.
This report read 6 of 44 pages
Everything below is measured on those 6. The other 38 were not opened, so nothing here speaks for them.
A sample is a sample. The claim is what was read, never the whole site.
04The next step
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.
This site has proved control, so it can carry these marks. Tap one for the code.
Badge for your own site: <a href="https://zpe.vc/audit/r/c34f874f0c84"><img src="https://zpe.vc/audit/b/c34f874f0c84.svg" width="220" height="52" alt="Audited outside-in, pinescriptstrategy.com"></a>
Want the deeper report, the half that needs read-only access to your server? Ask for it.
05Limits and help
Where we could help
- 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.
The launch gate, read against this site
Our own pre-launch gate: fourteen gates and 110 lines, the list every site of ours is walked through before it serves a stranger. This is not that list repeated as advice. It is the part one reading from outside can settle, with the rest named and the reason it cannot. 23 settled, 0 not met, 24 of the 110 lines checkable this way.
1. it answers, everywhere, correctly 5 of 5 settled
- settled Unknown paths answer a deliberate 404, never a stack trace real 404
- settled One canonical host: apex and www agree both end at pinescriptstrategy.com
- settled HTTPS is the way in yes
- settled One h1, headings in order every page read has exactly one H1
- settled Alt text on every image every page with images describes at least 80% of them
- cannot be seen from outside mixed content, what a browser fetches at load, the page with JavaScript off, the layout at 390 and 1280, the redirect map of old addresses, and whether a preview worker still shows a mock these need a browser running the page, or the tree the site was built from
2. the copy is defensible none of it can be settled here
- cannot be seen from outside every line of it: whether a claim traces to a source, whether a promise is regulated, whether the proof is real, and whether the price is shown a reading measures what a page says, not whether it is true; this gate is the owner's own, and the answers are paperwork
3. money and legal none of it can be settled here
- cannot be seen from outside the payment rail in live mode, refunds, terms, privacy, consent, labels, filings and retention each is a decision with a document behind it, and none of it is visible from one request
4. measurement, before the first visitor none of it can be settled here
- cannot be seen from outside whether analytics was proven by a real visit, the conversion event, the UTM convention, Search Console, the alert path, and the number read weekly the audit can find a tracking container; it cannot read the store it writes to
5. discovery, so the site can be found and described 8 of 9 settled
- settled robots.txt answers and points at the sitemap 1 Sitemap line(s)
- settled Sitemap answers, and the pages in it are the site's own routes found at /sitemap_index.xml
- settled robots.txt does not disallow the pages that matter no site-wide block
- settled A canonical tag on the page self-referencing and absolute on all 6 pages read
- settled Structured data parses and validates JSON-LD on every page read
- settled A unique title, within 60 characters all 6 pages title themselves in 65 characters or fewer
- settled A unique description, within 155 characters all 6 pages describe themselves in 80 to 200 characters
- settled A share card: og:title, og:description, og:image, twitter:card all 6 pages preview properly
- cannot be seen from outside llms.txt at the root this run did not make the check (llms)
- cannot be seen from outside hreflang pairs, whether the share card renders on X, LinkedIn, WhatsApp, Telegram and Slack, the AI crawler policy chosen in robots.txt, whether the money page is two clicks from the root, the backlink list, and a link check over the whole built tree cards and policy choices are decisions, and the render check needs five other companies' surfaces
6. security audit 6 of 6 settled
- settled HSTS, with a year and includeSubDomains max-age=31536000; includeSubDomains; preload
- settled A Content Security Policy on the response present, script-src locked, style-src still allows inline
- settled MIME sniffing blocked nosniff
- settled A referrer policy strict-origin-when-cross-origin
- settled Clickjacking protection SAMEORIGIN
- settled A permissions policy camera=(), microphone=(), geolocation=(), payment=(self)
- cannot be seen from outside whether the CSP still allows unsafe-inline somewhere, the dependency audit, the secret scan over the tree and the bundle, the rate limits, server-side validation, what an error response says, PII in logs, the backup and its restore, and who holds the deploy credential each needs the tree, the logs, or the account, and a response header is the only part of this gate that faces outward
7. page and accessibility audit 1 of 1 settled
- settled Speed measured on a throttled phone, not estimated measured, and the score is in this report
- cannot be seen from outside an axe scan with zero serious findings, the keyboard pass, contrast on every pair, the performance budget as a number to fail, images at the size they render, self-hosted fonts, HTML validity, and the page in print one of these needs a headless browser with a network profile, and the rest need a person with a keyboard
8. email 3 of 3 settled
- settled SPF published for the sending domain one record, ends in -all
- settled DKIM published key on s1, s2, mail, resend, 2048-bit
- settled DMARC published policy p=quarantine
- cannot be seen from outside a real message read in Gmail, Outlook and Yahoo, the authentication results from the received headers, every transactional path, the reply path, unsubscribe, bounces, and the list export the DNS records face outward and are read here; the message itself needs an inbox
9. form and signup testing none of it can be settled here
- cannot be seen from outside the happy path with a read-back from the store, bad input, duplicates, spam, the rate limit, the confirmation, the mobile keyboard, and the removal path a form that writes into a hole looks identical to a working one from outside
10. load and stress none of it can be settled here
- cannot be seen from outside the capacity number, the load test at 1x, 5x and 10x, the breaking point, how it fails, and the cost at 10x the audit makes one request at a time, which is the opposite of a load test
11. operations, so a bad day is survivable none of it can be settled here
- cannot be seen from outside uptime and certificate-expiry alerting, the incident runbook, the rollback and its drill, scheduled backups with a tested restore, DNS TTL, log retention, and where the credentials live these are the owner's arrangements, not the site's behaviour
12. launch day none of it can be settled here
- cannot be seen from outside the fifty places worked in order, one message in three channels, who answers replies for 24 hours, and who may pull the launch this one is the launch, and it happens after the gate
Past launch day the gate changes shape: the post-launch runbook runs D+1 to D+90 and every stage ends in one of four decisions, keep, change the copy, change the channel or stop. Its D+1 job is that every row of the product register answers at its own address. That is the same job as the broken pages in the full crawl, one address at a time, and the crawl is the faster way to do it.