Loading Report View…
0/ 100
theoricode.com Website Audit Report
theoricode.com scored 86 out of 100 in this SavageAudit website audit covering Performance, SEO, Design, Copy, User Experience, and Conversion. The report uses captured website evidence to explain what is working, what is limiting the experience, and which improvements deserve attention first.
“Elegant shell, leaky funnel, and a trust deficit dressed as mysticism.”
The Ori Blueprint looks like it went to finishing school and came back forgetting how to sell. Gorgeous manners, vague intentions, and a cookie banner barging in like it owns the place.
https://www.theoricode.com/en
TECHNICAL SUMMARY
The good news: crawlability, canonicals, and schema are clean, with no console errors and strong indexation signals. The bad news: the page is still dragging around 129 KiB of unused JavaScript, 35 KiB of unused CSS, and 810 ms of render-blocking savings while LCP sits at 4.8 s and interactive lands at 4.9 s. Two broken fetches to /en/ugly-pdf?_rsc=... are the kind of user-facing paper cuts that turn a polished brand into a slightly haunted one.
Where It Burns
6 categoriesWebsite Audit Findings for theoricode.com
SavageAudit identified 36 visible findings and recommendations across 6 audit categories. Each section below combines the category score with observed evidence and prioritized fixes.
8501 PERFORMANCELCP 4.8 s9602 SEOSEO score 1008003 DESIGNFont families 148404 COPYWord count 1829605 UXBroken assets 26306 CONVERSIONCTA count 1
01
PERFORMANCE AUDIT
85
LCP4.8 sInteractive4.9 sUnused JS savings129 KiBRender-blocking savings810 ms
- 🔥Your unused JavaScript is sitting on 129 KiB of potential savings like a kitchen with three blenders and no dinner.
💀
Fast enough to tease, slow enough to make people check their watch.
- →Defer or code-split the largest client bundles and eliminate the 129 KiB of unused JavaScript.
- →Remove unused CSS and purge dead utility classes to recover the 35 KiB currently bloating the page.
- →Inline critical above-the-fold CSS and postpone nonessential scripts to cut the 810 ms of render-blocking delay.
02
SEO AUDIT
96
SEO score100Schema blocks2Parse errors0Heading skiph1→h3
- 🔥The SEO is doing its job so well that the page earned a perfect 100 score and still found time to skip from h1 to h3 like it forgot the middle child exists.
💀
Technically polished, with one heading tantrum trying to ruin the peace.
- →Insert an h2 between the h1 and h3 to repair the heading hierarchy.
- →Add Product schema for the report offering so rich results have something more useful than pure vibes.
- →Keep the canonical, robots, and language tags as-is, then validate schema changes after deployment.
03
DESIGN AUDIT
80
Font families14Images4Buttons8Trust signals0 visible
- 🔥Four images and 14 font families is not typography; it’s a mood board that escaped supervision.
💀
Pretty, orderly, and just chaotic enough to feel expensive in the wrong places.
- →Reduce the font stack to 2–3 families and use weights/styles consistently across the page.
- →Add testimonials, press mentions, or security/trust badges near the main CTA to support the premium feel.
- →Tighten the heading structure visually so the h1, h2, and h3 levels clearly read as one system.
04
COPY AUDIT
84
Word count182Sentences12CTA count1Social proof elements1
- 🔥182 words across 12 sentences is concise, but the page still sounds like it’s introducing a concept, not selling a result.
💀
Elegant language, vague payoff, and just enough proof to keep the suspense alive.
- →Rewrite the hero line to name the outcome first, then the report type, in plain language.
- →Align the H1 more closely with the title keywords so the brand name supports the offer instead of replacing it.
- →Add 2–3 proof points near the CTA, such as user counts, testimonials, or outcome-based examples.
05
UX AUDITUSER EXPERIENCE AUDIT
96
Broken assets2Console errors0Buttons8Forms0
- 🔥Two broken fetches to /en/ugly-pdf?_rsc=... are a lovely way to greet users with net::ERR_ABORTED twice for emphasis.
💀
Mostly usable, occasionally haunted, and still tripping over its own paperwork.
- →Fix the two aborted fetches to /en/ugly-pdf and verify the asset loads reliably across sessions.
- →Audit the navigation and button labels so the 21 links point to clearly differentiated user goals.
- →Add a low-friction form or inline capture mechanism if the journey depends on user contact or report generation.
06
CONVERSION AUDIT
63
CTA count1Social proof elements1Forms0Links21
- 🔥One CTA on a page with 21 links is not a funnel; it’s a single lifeboat in a very well-labeled ocean.
💀
A lovely invitation to nowhere, wrapped in expensive-looking restraint.
- →Add a secondary CTA and a short comparison or explanation block so users know what happens after clicking.
- →Introduce a simple lead-capture form or quiz entry point with 2–4 fields to reduce friction and increase intent capture.
- →Place stronger proof near the primary CTA, including testimonials, sample outputs, or outcome-oriented evidence.
Audit overview
theoricode.com Audit Summary
The good news: crawlability, canonicals, and schema are clean, with no console errors and strong indexation signals. The bad news: the page is still dragging around 129 KiB of unused JavaScript, 35 KiB of unused CSS, and 810 ms of render-blocking savings while LCP sits at 4.8 s and interactive lands at 4.9 s. Two broken fetches to /en/ugly-pdf?_rsc=... are the kind of user-facing paper cuts that turn a polished brand into a slightly haunted one.
Based on the category scores in this report, SEO is the strongest area while Conversion has the most room for improvement.
How SavageAudit Evaluated theoricode.com
SavageAudit evaluated the public website at https://www.theoricode.com/en across performance, technical SEO, design, copy, user experience, and conversion signals. Scores and recommendations reflect the website evidence available when this audit was generated on April 2, 2026.
Similar Website Audit Reports
Compare this result with other public SavageAudit reports that received a similar overall website score.