Website review, no card needed
signal-ai.com website review
Visit site (opens in a new tab)Reviewed 5 November 202639 issues · 88 checks
This review found 39 issues worth fixing on signal-ai.com, 12 of them high impact, across 88 checks. The most urgent: page weight: 20.3 MB in 190 requests. 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.8 s |
| May 23, 2026 | 3.8 s |
| May 30, 2026 | 4.0 s |
| Jun 6, 2026 | 4.2 s |
| Jun 13, 2026 | 4.2 s |
| Jun 20, 2026 | 4.3 s |
| Jun 27, 2026 | 4.1 s |
| Jul 4, 2026 | 4.0 s |
| Jul 11, 2026 | 4.0 s |
| Jul 18, 2026 | 3.9 s |
| Jul 25, 2026 | 3.9 s |
| Aug 1, 2026 | 3.8 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.8 s |
| Sep 12, 2026 | 3.7 s |
| Sep 19, 2026 | 3.6 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.3 s |
| Oct 24, 2026 | 3.5 s |
| Oct 31, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 230 ms |
| May 23, 2026 | 248 ms |
| May 30, 2026 | 253 ms |
| Jun 6, 2026 | 255 ms |
| Jun 13, 2026 | 260 ms |
| Jun 20, 2026 | 288 ms |
| Jun 27, 2026 | 307 ms |
| Jul 4, 2026 | 307 ms |
| Jul 11, 2026 | 294 ms |
| Jul 18, 2026 | 269 ms |
| Jul 25, 2026 | 249 ms |
| Aug 1, 2026 | 229 ms |
| Aug 8, 2026 | 215 ms |
| Aug 15, 2026 | 218 ms |
| Aug 22, 2026 | 228 ms |
| Aug 29, 2026 | 229 ms |
| Sep 5, 2026 | 275 ms |
| Sep 12, 2026 | 275 ms |
| Sep 19, 2026 | 280 ms |
| Sep 26, 2026 | 289 ms |
| Oct 3, 2026 | 269 ms |
| Oct 10, 2026 | 269 ms |
| Oct 17, 2026 | 274 ms |
| Oct 24, 2026 | 289 ms |
| Oct 31, 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
Minify JavaScript
1.1 s · 42 KiB42 KiB could be saved by minifying JavaScript.
Mobile performance score: 48
48/100Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.1 s
A phone's processor spends 5.1 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Unpkg, Google Tag Manager and b-cdn.net and others), adding 20.1 MB and 1.6 s of main-thread time.
b-cdn.net adds 157 ms
157 msb-cdn.net costs a phone 157 ms of main-thread work and 18.3 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
650 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
Unpkg adds 576 ms
576 msUnpkg costs a phone 576 ms of main-thread work and 572 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Google Tag Manager adds 547 ms
547 msGoogle Tag Manager costs a phone 547 ms of main-thread work and 695 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Reduce unused JavaScript
150 ms · 380 KiBAbout 380 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
2,912 HTML elements
The page has 2,912 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 263 ms. During a long task the page ignores taps.
website-files.com adds 110 ms
110 mswebsite-files.com costs a phone 110 ms of main-thread work and 441 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Use efficient cache lifetimes
50 ms · 174 KiB33 files are served with short cache lifetimes, so returning visitors download them again (174 KiB).
Improve image delivery
186 KiB4 images could be 186 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
25 KiBAbout 25 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
16 KiBPolyfills for old browsers add 16 KiB JavaScript that modern phones do not need.
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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 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 FCP: 3.6 s
3.6 sReal visitors see the first content after 3.6 s (75th percentile). Good is under 1.8 s.
Time to Interactive: 19.6 s
19.6 sThe page becomes fully interactive after 19.6 s. Good is under 3.8 s.
First Contentful Paint: 5.1 s
5.1 sThe first text or image appears after 5.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 5.1 s
5.1 sYour largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Signal AI gives Chief Communications Officers and Chief Ris…”. Most of its time is element render delay (2.3 s).
Speed Index: 7.1 s
7.1 sVisually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 672 ms
672 msScripts block taps and scrolling for 672 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.8 s
3.8 sReal visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 372 ms
372 msReal visitors wait 372 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-10-31, real Chrome visitors' tap response (inp) went from 230 ms to 302 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 964 ms
964 msReal visitors wait 964 ms for your server to start answering (75th percentile). Good is under 800 ms.
25 images without width and height
25 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.8 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.012
0.012The layout barely moves while loading (CLS 0.012, good is under 0.1).
Images and page weight
Page weight: 20.3 MB in 190 requests
20.3 MBYour homepage downloads 20.3 MB in 190 requests on a phone: media 17.3 MB (5), scripts 1.8 MB (80) and fonts 548 KiB (8). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
134 KiB1 image is downloaded at several times the size a phone draws it, for example 6a7dde66ddc8a07bc0a97f9e_01-Elisa-Pasculli-META-PleaseCredit at 1,707 px wide, shown at 80 px. Resized copies would save about 134 KiB.
About 5.8 g of CO₂ per visit
5.76 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.76 g of CO₂e: 691.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
Frames without titles
2 frames have no title, so screen-reader users cannot tell what they contain.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 86 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
Meta description is long (210 characters)
Your meta description is 210 characters; Google truncates after about 160, so the end of your pitch is cut.
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
96 internal links, 4 external
The homepage links to 96 pages on signal-ai.com and 4 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Thesignalsyou need forthe decisions thatmatter most”.
Title: 64 characters
Your title is a healthy 64 characters: “Signal AI | AI-Powered Reputation Management & Risk Intelligence”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://signal-ai.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://signal-ai.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,946 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://signal-ai.com/solutions/reputation-intelligence, https://signal-ai.com/solutions/reputation-intelligence/reputation-pr-measurement, https://signal-ai.com/solutions/reputation-intelligence/media-monitoring, https://signal-ai.com/solutions/reputation-intelligence/crisis-communications, https://signal-ai.com/solutions/reputation-intelligence/corporate-communications-strategy and https://signal-ai.com/solutions/reputation-intelligence/media-outreach and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 39 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 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.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 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 “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
10 of 10 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 1,164 words of copy
The homepage carries about 1,164 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book a demo”.
14 calls to action
The homepage has 14 calls to action, for example “Book a demo”, “Subscribe now” and “Risk Register Monitoring”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 9 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Xandr (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
14 cookies set on arrival
14Opening the homepage sets 14 cookies (measured from a US location before any click).
32 other companies contacted
Loading the homepage contacts 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
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 signal-ai.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Webflow
- Framework
- Tailwind CSS
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Company
- Headquarters
- London
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 signal-ai.com, including 24 speed issues, 4 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.