Website review, no card needed
agile.space website review
Visit site (opens in a new tab)Reviewed 24 October 202635 issues · 77 checks
This review found 35 issues worth fixing on agile.space, 6 of them high impact, across 77 checks. The most urgent: render-blocking 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
82B- #33,341 of 118,417 reviewed websitesbeats 66%
- #22,250 of 67,280 online storesbeats 60%
- #79 of 1,437 Squarespace websitesbeats 93%
Closest competitors among online stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.2 s |
| May 9, 2026 | 1.2 s |
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 71 ms |
| May 9, 2026 | 70 ms |
| May 16, 2026 | 70 ms |
| May 23, 2026 | 71 ms |
| May 30, 2026 | 71 ms |
| Jun 6, 2026 | 69 ms |
| Jun 13, 2026 | 70 ms |
| Jun 20, 2026 | 70 ms |
| Jun 27, 2026 | 70 ms |
| Jul 4, 2026 | 71 ms |
| Jul 11, 2026 | 72 ms |
| Jul 18, 2026 | 72 ms |
| Jul 25, 2026 | 74 ms |
| Aug 1, 2026 | 73 ms |
| Aug 8, 2026 | 73 ms |
| Aug 15, 2026 | 73 ms |
| Aug 22, 2026 | 74 ms |
| Aug 29, 2026 | 76 ms |
| Sep 5, 2026 | 71 ms |
| Sep 12, 2026 | 71 ms |
| Sep 19, 2026 | 71 ms |
| Sep 26, 2026 | 71 ms |
| Oct 3, 2026 | 72 ms |
| Oct 10, 2026 | 72 ms |
| Oct 17, 2026 | 72 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.8 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Improve image delivery
1.6 MB31 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
3 third-party services on the page
3 third-party services load with your homepage (Squarespace, sqspcdn.com and squarespace-cdn.com), adding 3.8 MB and 637 ms of main-thread time.
Mobile performance score: 68
68/100Your mobile performance score is 68 (desktop: 75). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 135 KiBAbout 135 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Squarespace adds 613 ms
613 msSquarespace costs a phone 613 ms of main-thread work and 1.5 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.
Reduce unused JavaScript
718 KiBAbout 718 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
300 ms · 111 KiBPolyfills for old browsers add 111 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 532 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
squarespace-cdn.com adds 0 ms
0 mssquarespace-cdn.com costs a phone 0 ms of main-thread work and 2.2 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.
1,558 HTML elements
The page has 1,558 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 150 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
6 KiB1 file is served with short cache lifetimes, so returning visitors download them again (6 KiB).
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: 51 ms
51 msYour server sent the HTML in 51 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 15.1 s
15.1 sThe page becomes fully interactive after 15.1 s. Good is under 3.8 s.
Largest Contentful Paint: 4.9 s
4.9 sYour largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Speed Index: 5.0 s
5.0 sVisually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 264 ms
264 msScripts block taps and scrolling for 264 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image 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-17, real Chrome visitors' tap response (inp) went from 71 ms to 72 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 70 ms
70 msReal visitors wait 70 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 510 ms
510 msReal visitors wait 510 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.0 MB in 117 requests
4.0 MBYour homepage downloads 4.0 MB in 117 requests on a phone: images 2.1 MB (35), scripts 1.5 MB (58) and stylesheets 172 KiB (13). Under 2 MB keeps phones on slow connections fast.
24 images below the first screen load straight away
24 images further down the page (937 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.1 g of CO₂ per visit
1.14 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.14 g of CO₂e: 136.7 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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 checks passed
Every image has alt text
All 39 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 0 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (22 characters)
Your title is only 22 characters: “Agile Space Industries”. Between 30 and 65 characters leaves room to say what you do and for whom.
9 H1 headlines
There are 9 <h1> headlines (“LEADING INNOVATORS OF”, “IN-SPACE CHEMICAL PROPULSION” and “ENGINES”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/634ee7b32099c80fdfc…”.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
208 internal links, 4 external
The homepage links to 208 pages on agile.space and 4 external pages.
5 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “Propelling humanity to an interplanetary future. An in-space propulsion solution provider, specializing in additively m…”.
Canonical URL set
The canonical URL is https://agilespaceindustries.com/.
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://agilespaceindustries.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://agilespaceindustries.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,330 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://agilespaceindustries.com/products is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://agilespaceindustries.com/about and https://agilespaceindustries.com/company all use the title “About Agile Space Industries, the thruster manufacturer that is chang…”. Search engines can't tell which page to show for a search, so each competes with the others.
10 pages without a meta description
https://agilespaceindustries.com/team, https://agilespaceindustries.com/press, https://agilespaceindustries.com/careers, https://agilespaceindustries.com/contact, https://agilespaceindustries.com/press/expands-to-seattle-area and https://agilespaceindustries.com/press/7qf1oob2til7owia45s9e1dgjp0qkv and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://agilespaceindustries.com/about and https://agilespaceindustries.com/company use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://agilespaceindustries.com/company, whose canonical is https://agilespaceindustries.com/about. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://agilespaceindustries.com/products, https://agilespaceindustries.com/contact, https://agilespaceindustries.com/press/7qf1oob2til7owia45s9e1dgjp0qkv and https://agilespaceindustries.com/press/bringing-payload-processing-to-where-its-needed have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://agilespaceindustries.com/contact, https://agilespaceindustries.com/press/7qf1oob2til7owia45s9e1dgjp0qkv and https://agilespaceindustries.com/press/bringing-payload-processing-to-where-its-needed 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 44 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/634ee7b32099c80fdfcc8cac/108/5c5…”.
2 checks passed
Tap targets are thumb-sized
7 of 7 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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 776 words of copy
The homepage carries about 776 words of visible text.
1 checks passed
5 calls to action
The homepage has 5 calls to action, for example “CONTACT” and “Join our team”.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
6 other companies contacted
Loading the homepage contacts 6 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 agile.space, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Squarespace
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on agile.space, including 17 speed issues, 4 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.