Website review, no card needed
jacto.com website review
Visit site (opens in a new tab)Reviewed 20 November 202633 issues · 51 checks
This review found 33 issues worth fixing on jacto.com, 15 of them high impact, across 51 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 7.4 s |
| Jun 6, 2026 | 7.2 s |
| Jun 13, 2026 | 7.2 s |
| Jun 20, 2026 | 7.3 s |
| Jun 27, 2026 | 7.4 s |
| Jul 4, 2026 | 7.6 s |
| Jul 11, 2026 | 7.7 s |
| Jul 18, 2026 | 7.3 s |
| Jul 25, 2026 | 6.7 s |
| Aug 1, 2026 | 6.1 s |
| Aug 8, 2026 | 5.6 s |
| Aug 15, 2026 | 5.5 s |
| Aug 22, 2026 | 5.5 s |
| Aug 29, 2026 | 5.5 s |
| Sep 5, 2026 | 5.4 s |
| Sep 12, 2026 | 5.4 s |
| Sep 19, 2026 | 5.5 s |
| Sep 26, 2026 | 5.6 s |
| Oct 3, 2026 | 5.7 s |
| Oct 10, 2026 | 5.9 s |
| Oct 17, 2026 | 5.8 s |
| Oct 24, 2026 | 5.7 s |
| Oct 31, 2026 | 5.7 s |
| Nov 7, 2026 | 5.8 s |
| Nov 14, 2026 | 5.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 246 ms |
| Jun 6, 2026 | 244 ms |
| Jun 13, 2026 | 241 ms |
| Jun 20, 2026 | 241 ms |
| Jun 27, 2026 | 239 ms |
| Jul 4, 2026 | 239 ms |
| Jul 11, 2026 | 238 ms |
| Jul 18, 2026 | 237 ms |
| Jul 25, 2026 | 243 ms |
| Aug 1, 2026 | 248 ms |
| Aug 8, 2026 | 262 ms |
| Aug 15, 2026 | 268 ms |
| Aug 22, 2026 | 270 ms |
| Aug 29, 2026 | 273 ms |
| Sep 5, 2026 | 272 ms |
| Sep 12, 2026 | 273 ms |
| Sep 19, 2026 | 277 ms |
| Sep 26, 2026 | 280 ms |
| Oct 3, 2026 | 289 ms |
| Oct 10, 2026 | 290 ms |
| Oct 17, 2026 | 296 ms |
| Oct 24, 2026 | 304 ms |
| Oct 31, 2026 | 305 ms |
| Nov 7, 2026 | 307 ms |
| Nov 14, 2026 | 302 ms |
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
Speed
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 5.8 s
5.8 sReal visitors wait 5.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.80
0.80For real visitors the layout shifts by 0.80 (75th percentile). Good is under 0.1.
Real-user FCP: 4.4 s
4.4 sReal visitors see the first content after 4.4 s (75th percentile). Good is under 1.8 s.
Real-user INP: 299 ms
299 msReal visitors wait 299 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 246 ms to 302 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
1 checks passed
Largest content (LCP) got 21% faster for real visitors
-21%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 7.4 s to 5.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 5.6 MB
5.6 MBYour homepage downloads 5.6 MB on a phone, 2.2 MB of it images (39%). Under 2 MB keeps phones on slow connections fast.
About 1.6 g of CO₂ per visit
1.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.59 g of CO₂e: 190.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Images must have alternative text (10 elements)
Images must have alternative text: 10 elements on the page fail this check, rated critical by axe-core.
5 buttons without a name
5 buttons have no accessible name, so screen readers announce just “button”.
23 text elements with low contrast
23 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No page title
Your page has no <title>, so Google has to invent the blue link in search results.
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.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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 XML sitemap
No XML sitemap at https://jacto.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at jacto.com/robots.txt, the first file search crawlers ask for.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 266 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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://jacto.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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Best practices
9 small tap targets
9 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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.
About 266 words of copy
The homepage carries about 266 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “LEARN MORE”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
13 cookies set on arrival
13Opening the homepage sets 13 cookies (measured from a US location before any click).
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.
26 other companies contacted
Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 jacto.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on jacto.com, including 7 speed issues, 9 SEO issues and 3 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.