Website review, no card needed
trueventus.com website review
Visit site (opens in a new tab)Reviewed 26 October 202639 issues · 78 checks
This review found 39 issues worth fixing on trueventus.com, 20 of them high impact, across 78 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.2 s |
| May 9, 2026 | 4.1 s |
| May 16, 2026 | 3.7 s |
| May 23, 2026 | 3.7 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.8 s |
| Jun 13, 2026 | 4.3 s |
| Jun 20, 2026 | 4.5 s |
| Jun 27, 2026 | 4.6 s |
| Jul 4, 2026 | 4.3 s |
| Jul 11, 2026 | 4.3 s |
| Jul 18, 2026 | 4.2 s |
| Jul 25, 2026 | 4.3 s |
| Aug 1, 2026 | 4.9 s |
| Aug 8, 2026 | 4.3 s |
| Aug 15, 2026 | 4.3 s |
| Aug 22, 2026 | 4.0 s |
| Aug 29, 2026 | 3.8 s |
| Sep 5, 2026 | 4.0 s |
| Sep 12, 2026 | 3.9 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.8 s |
| Oct 10, 2026 | 4.4 s |
| Oct 17, 2026 | 4.8 s |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
2.0 s
4.0 s
6.0 s
8.0 s
10.0 s
12.1 s
14.1 s
16.1 s
Speed
Use efficient cache lifetimes
6.3 s · 1.5 MB95 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).
Improve image delivery
4.1 s · 675 KiB9 images could be 675 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.1 s faster on a phone.
Render-blocking requests
3.7 s32 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.7 s.
Mobile performance score: 44
44/100Your mobile performance score is 44 (desktop: 74). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused JavaScript
760 ms · 120 KiBAbout 120 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 760 ms faster on a phone.
Font display
650 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 650 ms).
Reduce unused CSS
460 ms · 80 KiBAbout 80 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 460 ms faster on a phone.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 439 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify JavaScript
150 ms · 33 KiB33 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 3 KiB3 KiB could be saved by minifying CSS.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 67 ms. During a long task the page ignores taps.
1 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 178 KiB and 0 ms of main-thread time.
Phones get a much slower page than desktops
Desktop scores 74 but mobile only 44. A gap that wide usually means heavy scripts and images that hit phones hardest.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 4.5 s
4.5 sReal visitors wait 4.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.2 s
3.2 sReal visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.5 s
2.5 sReal visitors wait 2.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 17.3 s
17.3 sYour largest element takes 17.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is element render delay (7.9 s).
Speed Index: 15.3 s
15.3 sVisually, the page fills in at 15.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 17.4 s
17.4 sThe page becomes fully interactive after 17.4 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.312
0.312The layout shifts by 0.312 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.2 s to 4.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.1 MB in 115 requests
4.1 MBYour homepage downloads 4.1 MB in 115 requests on a phone: images 3.3 MB (48), scripts 366 KiB (29) and fonts 180 KiB (8). Under 2 MB keeps phones on slow connections fast.
8 images in older formats
8 images (1.6 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
An image on the first screen is lazy-loaded
bg-text1-23.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 1.1 g of CO₂ per visit
1.15 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.15 g of CO₂e: 137.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
35 links without text
35 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 43 images in the HTML carry an alt attribute.
30 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 5 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (10 characters)
Your title is only 10 characters: “Trueventus”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
41 internal links, 1 external
The homepage links to 41 pages on trueventus.com and 1 external page.
3 checks passed
Canonical URL set
The canonical URL is https://www.trueventus.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.trueventus.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.trueventus.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
1 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Other pages
5 pages without a meta description
https://www.trueventus.com/events, https://www.trueventus.com/about-us, https://www.trueventus.com/our-clients, https://www.trueventus.com/careers and https://www.trueventus.com/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://www.trueventus.com/events, https://www.trueventus.com/about-us, https://www.trueventus.com/our-clients, https://www.trueventus.com/careers and https://www.trueventus.com/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.trueventus.com/our-clients and https://www.trueventus.com/contact-us have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
5 internal pages checked
We fetched 5 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 5 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 5 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Syntax error, unrecognized expression: {"status":"Nothing found"}”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
37 of 38 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 111 words
The homepage has only about 111 words of visible text; thin pages give Google and first-time buyers little to go on.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
1 checks passed
2 calls to action
The homepage has 2 calls to action, for example “REGISTER” and “CONTACT”.
Privacy and tracking
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at trueventus.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2010.
Stack
- CMS
- WordPress
- Framework
- jQuery
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on trueventus.com, including 18 speed issues, 5 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.