Website review, no card needed
armory.io website review
Visit site (opens in a new tab)Reviewed 20 October 202623 issues · 80 checks
This review found 23 issues worth fixing on armory.io, 7 of them high impact, across 80 checks. The most urgent: webflow.services adds 2.0 s. 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
77CClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.5 s |
| May 9, 2026 | 4.3 s |
| May 16, 2026 | 4.3 s |
| May 23, 2026 | 4.2 s |
| May 30, 2026 | 4.1 s |
| Jun 6, 2026 | 4.1 s |
| Jun 13, 2026 | 4.0 s |
| Jun 20, 2026 | 4.0 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 3.9 s |
| Jul 11, 2026 | 3.8 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.8 s |
| Sep 5, 2026 | 3.7 s |
| Sep 12, 2026 | 3.6 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 232 ms |
| May 9, 2026 | 231 ms |
| May 16, 2026 | 237 ms |
| May 23, 2026 | 239 ms |
| May 30, 2026 | 232 ms |
| Jun 6, 2026 | 229 ms |
| Jun 13, 2026 | 230 ms |
| Jun 20, 2026 | 230 ms |
| Jun 27, 2026 | 227 ms |
| Jul 4, 2026 | 229 ms |
| Jul 11, 2026 | 218 ms |
| Jul 18, 2026 | 211 ms |
| Jul 25, 2026 | 210 ms |
| Aug 1, 2026 | 204 ms |
| Aug 8, 2026 | 200 ms |
| Aug 15, 2026 | 206 ms |
| Aug 22, 2026 | 216 ms |
| Aug 29, 2026 | 292 ms |
| Sep 5, 2026 | 285 ms |
| Sep 12, 2026 | 272 ms |
| Sep 19, 2026 | 259 ms |
| Sep 26, 2026 | 201 ms |
| Oct 3, 2026 | 213 ms |
| Oct 10, 2026 | 211 ms |
| Oct 17, 2026 | 210 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
webflow.services adds 2.0 s
2.0 swebflow.services costs a phone 2.0 s of main-thread work and 752 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 7.0 s
A phone's processor spends 7.0 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3 third-party services on the page
3 third-party services load with your homepage (webflow.services, Google Tag Manager and relyance.ai), adding 1.1 MB and 2.4 s of main-thread time.
Mobile performance score: 60
60/100Your mobile performance score is 60 (desktop: 98). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Google Tag Manager adds 296 ms
296 msGoogle Tag Manager costs a phone 296 ms of main-thread work and 190 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.
1,884 HTML elements
The page has 1,884 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 248 ms. During a long task the page ignores taps.
Reduce unused JavaScript
207 KiBAbout 207 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
47 KiB1 file is served with short cache lifetimes, so returning visitors download them again (47 KiB).
Improve image delivery
18 KiB1 image could be 18 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
Reduce unused CSS
12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 98 but mobile only 60. 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: 46 ms
46 msYour server sent the HTML in 46 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 TTFB: 1.8 s
1.8 sReal visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 8.6 s
8.6 sThe page becomes fully interactive after 8.6 s. Good is under 3.8 s.
Total Blocking Time: 767 ms
767 msScripts block taps and scrolling for 767 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 4.4 s
4.4 sYour largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Code Deployments for the Autonomous SDLC”.
Real-user LCP: 3.5 s
3.5 sReal visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 211 ms
211 msReal visitors wait 211 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Speed Index: 5.4 s
5.4 sVisually, the page fills in at 5.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 232 ms to 210 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Largest content (LCP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.5 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
About 0.3 g of CO₂ per visit
0.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.33 g of CO₂e: 39.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.2 MB in 60 requests
1.2 MBYour homepage downloads 1.2 MB in 60 requests on a phone: scripts 574 KiB (20), fonts 345 KiB (6) and other files 99 KiB (22). That is a lean page.
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
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 40 images in the HTML carry an alt attribute.
29 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 29 WCAG 2.2 A/AA and best-practice rules on the phone render: 29 passed and 0 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
98 internal links, 12 external
The homepage links to 98 pages on armory.io and 12 external pages.
8 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “Accelerate deployments with AI, GitOps, and script-free releases with Harness Continuous Delivery. Achieve efficient, s…”.
One H1 headline
Your main headline reads: “Code Deployments for the Autonomous SDLC”.
Title: 57 characters
Your title is a healthy 57 characters: “Continuous Delivery Platform with AI Automation | Harness”.
Canonical URL set
The canonical URL is https://www.harness.io/products/continuous-delivery.
Structured data in place
Structured data found: BreadcrumbList, FAQPage, Organization, SoftwareApplication 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://www.harness.io/products/sitemap.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (2,097 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.harness.io/llms.txt (9 KiB, 53 links), a plain-text guide to the site for AI tools.
Other pages
1 page slow to respond
https://www.harness.io/products/runtime-protection-agent took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 62 found) and read each the way a search engine does.
7 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.
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
7 small tap targets
7 of 32 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “fbq is not defined”.
1 checks passed
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 2,107 words of copy
The homepage carries about 2,107 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: “Start for Free” and “See a Demo”.
10 calls to action
The homepage has 10 calls to action, for example “Pricing”, “See a Demo” and “Start for Free”.
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.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
3 other companies contacted
Loading the homepage contacts 3 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 armory.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Tag Manager
Hiring
- Hiring
- 2 open roles
- Teams
- Business Development (1), Product (1)
- Job board
- ashby
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 23 issues on armory.io, including 17 speed 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.