Website review, no card needed

aalyria.com logo

aalyria.com website review

Visit site (opens in a new tab)Reviewed 3 November 202629 issues · 76 checks

This review found 29 issues worth fixing on aalyria.com, 12 of them high impact, across 76 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.9 s1.5 sMay 16Oct 312.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20261.9 s
Jun 13, 20261.8 s
Jun 20, 20261.7 s
Jun 27, 20261.6 s
Jul 4, 20261.7 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.8 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20262.0 s
Sep 26, 20262.2 s
Oct 3, 20262.6 s
Oct 10, 20262.6 s
Oct 17, 20262.6 s
Oct 24, 20262.6 s
Oct 31, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
108 ms62 msMay 16Oct 3169 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202697 ms
May 23, 202680 ms
May 30, 202679 ms
Jun 6, 202678 ms
Jun 13, 202678 ms
Jun 20, 202687 ms
Jun 27, 2026103 ms
Jul 4, 2026100 ms
Jul 11, 202690 ms
Jul 18, 202685 ms
Jul 25, 202677 ms
Aug 1, 202674 ms
Aug 8, 202674 ms
Aug 15, 202675 ms
Aug 22, 202684 ms
Aug 29, 202680 ms
Sep 5, 202680 ms
Sep 12, 202675 ms
Sep 19, 202670 ms
Sep 26, 202667 ms
Oct 3, 202670 ms
Oct 10, 202672 ms
Oct 17, 202673 ms
Oct 24, 202671 ms
Oct 31, 202669 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

Full-page screenshot of aalyria.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aalyria.com at 0.5 s0.5 s
  2. aalyria.com at 1.0 s1.0 s
  3. aalyria.com at 1.5 s1.5 s
  4. aalyria.com at 2.0 s2.0 s
  5. aalyria.com at 2.5 s2.5 s
  6. aalyria.com at 3.0 s3.0 s
  7. aalyria.com at 3.5 s3.5 s
  8. aalyria.com at 4.0 s4.0 s

Speed

5 to fix69
  • Improve image delivery

    7.2 s · 1.4 MB

    1 image could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.2 s faster on a phone.

  • Mobile performance score: 69

    69/100

    Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    600 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

  • Use efficient cache lifetimes

    450 ms · 81 KiB

    2 files are served with short cache lifetimes, so returning visitors download them again (81 KiB).

  • Reduce unused JavaScript

    320 ms · 72 KiB

    About 72 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 320 ms faster on a phone.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 150 ms. During a long task the page ignores taps.

  • 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.

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 431 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

    Your server sent the HTML in 3 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix67
  • 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.

  • Largest Contentful Paint: 30.3 s

    30.3 s

    Your largest element takes 30.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “By clicking “Accept All Cookies”, you agree to the storage …”.

  • Time to Interactive: 32.2 s

    32.2 s

    The page becomes fully interactive after 32.2 s. Good is under 3.8 s.

  • Speed Index: 5.9 s

    5.9 s

    Visually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.

  • Real-user LCP: 2.8 s

    2.8 s

    Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Largest content (LCP) got 46% slower for real visitors

    +46%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • 8 images without width and height

    8 images have no width and height attributes, so the layout jumps as each one loads.

8 checks passed
  • Real-user INP: 70 ms

    70 ms

    Real 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.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.8 s

    0.8 s

    Real visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 446 ms

    446 ms

    Real visitors wait 446 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 21% faster for real visitors

    -21%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 97 ms to 69 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 112 ms

    112 ms

    Scripts block the page for only 112 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix60
  • Page weight: 55.9 MB in 70 requests

    55.9 MB

    Your homepage downloads 55.9 MB in 70 requests on a phone: media 46.5 MB (22), images 9.0 MB (21) and scripts 253 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    aa-logo-opener.svg 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 far larger than shown

    191 KiB

    1 image is downloaded at several times the size a phone draws it, for example contact-linkedin.png at 1,200 px wide, shown at 54 px. Resized copies would save about 191 KiB.

  • 1 image in older formats

    1 image (194 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.

  • 1 image below the first screen load straight away

    1 image further down the page (194 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 15.8 g of CO₂ per visit

    15.85 g

    By the Sustainable Web Design model, a visit to your homepage emits about 15.85 g of CO₂e: 1901.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

7 to fixGoogle 8688
  • 5 text elements with low contrast

    5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Elements must only use permitted ARIA attributes (2 elements)

    Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • All page content should be contained by landmarks (44 elements)

    All page content should be contained by landmarks: 44 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.

2 checks passed
  • Every image has alt text

    All 37 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10088
  • Title is short (28 characters)

    Your title is only 28 characters: “Aalyria | Networks in Motion”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 15 H1 headlines

    There are 15 <h1> headlines (“Networks in Motion”, “Most wireless networks broadcast widely” and “Directionality solves the physical challenges”). One clear main headline is easier for people and search engines.

  • 9 internal links, 7 external

    The homepage links to 9 pages on aalyria.com and 7 external pages.

6 checks passed
  • Meta description: 109 characters

    Your meta description is 109 characters: “Aalyria enables commercial and government customers to operate resilient, high-throughput networks in motion.”.

  • Canonical URL set

    The canonical URL is https://www.aalyria.com/.

  • Structured data in place

    Structured data found: Organization.

  • 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.aalyria.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.aalyria.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.

3 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 (1,646 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 3 linked pages hidden from search

    https://www.aalyria.com/privacy-policy.html, https://www.aalyria.com/terms-and-conditions.html and https://www.aalyria.com/privacy-policy are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://www.aalyria.com/privacy-policy.html and https://www.aalyria.com/privacy-policy all use the title “Privacy Policy”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.aalyria.com/privacy-policy.html and https://www.aalyria.com/privacy-policy use the same meta description. A description written for each page earns more clicks.

  • 3 internal pages checked

    We fetched 3 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 3 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 3 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 3 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 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

    8 of 9 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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.

  • 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 751 words of copy

    The homepage carries about 751 words of visible text.

5 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “CONTACT”, “DOWNLOAD OUR WHITE PAPER” and “LEARN MORE”.

  • 3 short forms

    3 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 15 customer or partner logos and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 6 email links.

Privacy and tracking

  • 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.

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 aalyria.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
jQuery
Analytics
Google Analytics
Hosting
Vercel

Hiring

Hiring
31 open roles
Teams
Spacetime (24), Internal Engineering (3), Customer Success (2), Tightbeam (2)
Job board
rippling

Company

Employees
83
Headquarters
Livermore

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on aalyria.com, including 12 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25