Website review, no card needed
insiderone.com website review
Visit site (opens in a new tab)Reviewed 28 October 202636 issues · 87 checks
This review found 36 issues worth fixing on insiderone.com, 16 of them high impact, across 87 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.4 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.2 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 195 ms |
| May 16, 2026 | 202 ms |
| May 23, 2026 | 210 ms |
| May 30, 2026 | 206 ms |
| Jun 6, 2026 | 212 ms |
| Jun 13, 2026 | 208 ms |
| Jun 20, 2026 | 205 ms |
| Jun 27, 2026 | 211 ms |
| Jul 4, 2026 | 208 ms |
| Jul 11, 2026 | 211 ms |
| Jul 18, 2026 | 202 ms |
| Jul 25, 2026 | 204 ms |
| Aug 1, 2026 | 194 ms |
| Aug 8, 2026 | 198 ms |
| Aug 15, 2026 | 203 ms |
| Aug 22, 2026 | 205 ms |
| Aug 29, 2026 | 211 ms |
| Sep 5, 2026 | 213 ms |
| Sep 12, 2026 | 212 ms |
| Sep 19, 2026 | 200 ms |
| Sep 26, 2026 | 191 ms |
| Oct 3, 2026 | 178 ms |
| Oct 10, 2026 | 181 ms |
| Oct 17, 2026 | 190 ms |
| Oct 24, 2026 | 200 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
Use efficient cache lifetimes
3.9 s · 636 KiB37 files are served with short cache lifetimes, so returning visitors download them again (636 KiB).
Reduce unused JavaScript
3.2 s · 654 KiBAbout 654 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.2 s faster on a phone.
Render-blocking requests
1.8 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Reduce unused CSS
1.1 s · 140 KiBAbout 140 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Improve image delivery
7.7 MB47 images could be 7.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Duplicated JavaScript
300 ms · 37 KiB37 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 785 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
jotfor.ms adds 260 ms
260 msjotfor.ms costs a phone 260 ms of main-thread work and 344 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.
2,681 HTML elements
The page has 2,681 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (jotfor.ms, Insider and jotform.com and others), adding 720 KiB and 429 ms of main-thread time.
Legacy JavaScript
150 ms · 10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
150 ms · 8 KiB8 KiB could be saved by minifying JavaScript.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 116 ms. During a long task the page ignores taps.
Minify CSS
12 KiB12 KiB could be saved by minifying CSS.
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: 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.
First Contentful Paint: 9.2 s
9.2 sThe first text or image appears after 9.2 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 42.4 s
42.4 sYour largest element takes 42.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The only self-improving agentic customer engagement system …”.
Speed Index: 27.2 s
27.2 sVisually, the page fills in at 27.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 45.4 s
45.4 sThe page becomes fully interactive after 45.4 s. Good is under 3.8 s.
Real-user INP: 235 ms
235 msReal visitors wait 235 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 32% slower for real visitors
+32%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.4 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
37 images without width and height
37 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 195 ms to 200 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user TTFB: 675 ms
675 msReal visitors wait 675 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.065
0.065The layout barely moves while loading (CLS 0.065, good is under 0.1).
Total Blocking Time: 58 ms
58 msScripts block the page for only 58 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 16.0 MB in 282 requests
16.0 MBYour homepage downloads 16.0 MB in 282 requests on a phone: images 11.7 MB (208), media 2.9 MB (1) and scripts 982 KiB (26). Under 2 MB keeps phones on slow connections fast.
16 images far larger than shown
3.5 MB16 images are downloaded at several times the size a phone draws them, for example comp-6-bg.png at 1,440 px wide, shown at 390 px. Resized copies would save about 3.5 MB.
1 image over 500 KB
hp-new.png weighs 1.8 MB. On a phone connection a single image that size takes seconds.
35 images in older formats
35 images (9.5 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.
22 images below the first screen load straight away
22 images further down the page (4.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.5 g of CO₂ per visit
4.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.54 g of CO₂e: 545.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
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.
120 images without alt text
120 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
16 links without text
16 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
17 links with vague text
17 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
166 internal links, 16 external
The homepage links to 166 pages on insiderone.com and 16 external pages.
8 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Insider One is the #1 Customer Engagement AI Platform for marketing teams. Unify CDP, personalization & journey orchest…”.
One H1 headline
Your main headline reads: “The only self-improving agentic customer engagement system”.
Title: 60 characters
Your title is a healthy 60 characters: “Insider One | #1 Platform for AI-Powered Customer Engagement”.
Canonical URL set
The canonical URL is https://insiderone.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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://insiderone.com/sitemap_index.xml.
AI search readiness
4 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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (3,997 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://insiderone.com/llms.txt (1 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without an H1
https://insiderone.com/agent-one, https://insiderone.com/agent-one/teams and https://insiderone.com/agent-one/audiences have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 82 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
6 broken images
6 images failed to load on a phone, for example https://insiderone.com/wp-content/themes/insiderone/assets/img/dynamic/icons/.svg.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
4 distorted images
4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
81 of 86 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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,778 words of copy
The homepage carries about 1,778 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: “CONTACT US” and “Get a demo”.
24 calls to action
The homepage has 24 calls to action, for example “Contact Us”, “Get a demo” and “Learn More”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 5 customer or partner logos, a star rating, 42 trust badges and “TRUSTED BY 2,000+ CUSTOMERS”.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel, Hotjar, HubSpot and Cloudflare Web Analytics.
Privacy and tracking
8 cookies set on arrival
8Opening the homepage sets 8 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.
11 other companies contacted
Loading the homepage contacts 11 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 insiderone.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
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Cloudflare
Hiring
- Hiring
- 119 open roles
- Teams
- Sales (62), Customer Success (25), Software Development (7), Marketing Design (6)
- Job board
- lever
- Careers page
- insiderone.com/careers (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on insiderone.com, including 19 speed issues, 2 SEO issues and 1 conversion gap. 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.