Website review, no card needed
astranis.com website review
Visit site (opens in a new tab)Reviewed 29 October 202638 issues · 81 checks
This review found 38 issues worth fixing on astranis.com, 11 of them high impact, across 81 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.0 s |
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 213 ms |
| May 16, 2026 | 207 ms |
| May 23, 2026 | 219 ms |
| May 30, 2026 | 218 ms |
| Jun 6, 2026 | 221 ms |
| Jun 13, 2026 | 222 ms |
| Jun 20, 2026 | 230 ms |
| Jun 27, 2026 | 227 ms |
| Jul 4, 2026 | 213 ms |
| Jul 11, 2026 | 203 ms |
| Jul 18, 2026 | 172 ms |
| Jul 25, 2026 | 161 ms |
| Aug 1, 2026 | 144 ms |
| Aug 8, 2026 | 126 ms |
| Aug 15, 2026 | 126 ms |
| Aug 22, 2026 | 128 ms |
| Aug 29, 2026 | 127 ms |
| Sep 5, 2026 | 136 ms |
| Sep 12, 2026 | 138 ms |
| Sep 19, 2026 | 141 ms |
| Sep 26, 2026 | 142 ms |
| Oct 3, 2026 | 144 ms |
| Oct 10, 2026 | 136 ms |
| Oct 17, 2026 | 136 ms |
| Oct 24, 2026 | 140 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.7 s
1.4 s
2.2 s
2.9 s
3.6 s
4.3 s
5.0 s
5.8 s
Speed
Render-blocking requests
3.9 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.9 s.
Reduce unused JavaScript
1.6 s · 669 KiBAbout 669 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Mobile performance score: 30
30/100Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
5.3 MB20 files are served with short cache lifetimes, so returning visitors download them again (5.3 MB).
8 third-party services on the page
8 third-party services load with your homepage (website-files.com, Google CDN and Google Tag Manager and others), adding 26.1 MB and 558 ms of main-thread time.
website-files.com adds 172 ms
172 mswebsite-files.com costs a phone 172 ms of main-thread work and 24.6 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 621 ms. During a long task the page ignores taps.
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
278 KiB5 images could be 278 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google CDN adds 128 ms
128 msGoogle CDN costs a phone 128 ms of main-thread work and 357 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,563 HTML elements
The page has 1,563 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Adobe TypeKit adds 11 ms
11 msAdobe TypeKit costs a phone 11 ms of main-thread work and 560 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 CSS
150 ms · 64 KiBAbout 64 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
10 KiB10 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.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 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.2 s
3.2 sReal visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 8.9 s
8.9 sThe first text or image appears after 8.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 107.6 s
107.6 sYour largest element takes 107.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 107.9 s
107.9 sThe page becomes fully interactive after 107.9 s. Good is under 3.8 s.
Total Blocking Time: 1.7 s
1.7 sScripts block taps and scrolling for 1.7 s in total while the page loads. Good is under 200 ms.
Speed Index: 8.9 s
8.9 sVisually, the page fills in at 8.9 s (Speed Index). Good is under 3.4 s.
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 TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 161 ms
161 msReal visitors wait 161 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.
Tap response (INP) got 34% faster for real visitors
-34%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 213 ms to 140 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 26.3 MB in 88 requests
26.3 MBYour homepage downloads 26.3 MB in 88 requests on a phone: other files 18.3 MB (8), media 4.9 MB (4) and scripts 1.2 MB (25). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
66e202cffb3ca3599af3c121_image 28 (1)-p-500.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image in older formats
1 image (96 KiB) is 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.
About 7.5 g of CO₂ per visit
7.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.45 g of CO₂e: 894.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
All page content should be contained by landmarks (33 elements)
All page content should be contained by landmarks: 33 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 23 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 4 failed. 3 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.
29 internal links, 5 external
The homepage links to 29 pages on astranis.com and 5 external pages.
7 checks passed
Meta description: 114 characters
Your meta description is 114 characters: “Astranis designs, builds, and operates the world’s most advanced high orbit satellites for sovereign connectivity.”.
One H1 headline
Your main headline reads: “The world's only dedicated satellite networks”.
Title: 36 characters
Your title is a healthy 36 characters: “High orbit infrastructure | Astranis”.
Canonical URL set
The canonical URL is https://www.astranis.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://www.astranis.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://www.astranis.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 (628 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.astranis.com/newsroom and https://www.astranis.com/blog/arcturus-usg-demo-ecaa0 all use the title “Get the latest Geostationary Satellite News | Astranis”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.astranis.com/blog/astranis-brings-anuvu-satellites-online-marking-debut-of-private-geo-network has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.astranis.com/newsroom and https://www.astranis.com/blog/arcturus-usg-demo-ecaa0 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://www.astranis.com/blog/arcturus-usg-demo-ecaa0, whose canonical is https://www.astranis.com/newsroom. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
6 pages without an H1
https://www.astranis.com/blog/stc-group-advances-saudi-arabia-connectivity-with-dedicated-satellite, https://www.astranis.com/blog/astranis-partners-with-thaicom-to-provide-thaicom-9-satellite-over-asia-18f83, https://www.astranis.com/blog/astranis-rgps-announcement-a8oc, https://www.astranis.com/blog/astranis-tapped-as-prime-contractor-for-u-s-space-forces-protected-tactical-satcom-global-pts-g-program, https://www.astranis.com/blog/astranis-brings-anuvu-satellites-online-marking-debut-of-private-geo-network and https://www.astranis.com/blog/chunghwa-telecom-and-astranis-sign-strategic-agreement-to-launch-taiwans-first-dedicated-satellite 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 17 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
11 of 11 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 6 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 691 words of copy
The homepage carries about 691 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Reserve a time”.
4 calls to action
The homepage has 4 calls to action, for example “Reserve a time”, “CONTACT” and “Talk to Sales”.
Analytics in place
Analytics detected: Google Tag Manager.
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). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
18 other companies contacted
Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 astranis.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
- Analytics
- Google Tag Manager
- Hosting
- Webflow
Hiring
- Hiring
- 188 open roles
- Teams
- Payload Internships (20), Production & Manufacturing Internships (17), Software Internships (15), Mechanical Engineering Internships (12)
- Job board
- greenhouse
- Careers page
- www.astranis.com/careers (opens in a new tab)
Company
- Employees
- 437
- Headquarters
- San Francisco
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on astranis.com, including 22 speed issues, 1 SEO issue and 2 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.