aalo.com website review

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

17 files are served with short cache lifetimes, so returning visitors download them again (12.4 MB).

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

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

8 third-party services load with your homepage (website-files.com, JSDelivr CDN and Cloudflare CDN and others), adding 1.7 MB and 274 ms of main-thread time.

website-files.com costs a phone 127 ms of main-thread work and 1.4 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.

4 images could be 169 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

About 38 KiB of CSS is downloaded but never applied on this page.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 KiB could be saved by minifying JavaScript.

The first text or image appears after 2.9 s on a phone. Good is under 1.8 s.

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

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

Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Mass-manufactured nuclear power plants, purpose-built to po…”. Most of its time is element render delay (1.4 s).

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

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

Your homepage downloads 17.3 MB in 59 requests on a phone: media 15.3 MB (4), images 1.2 MB (25) and scripts 627 KiB (17). Under 2 MB keeps phones on slow connections fast.

6a4b99ecaf48385ceb81b830_Rectangle%201455-p-500.avif 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).

9 images further down the page (320 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example 6a4b99ecaf48385ceb81ba3b_69f9faf4d4652956a31ecc17_Screenshot at 1,296 px wide, shown at 332 px. Resized copies would save about 21 KiB.

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

3 buttons have no accessible name, so screen readers announce just “button”.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

4 visible links have no text or label, so screen readers cannot say where they go.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

There are 3 <h1> headlines (“Mass-manufactured nuclear power plants, purpose-b…”, “Why sodium.” and “Why sodium.”). One clear main headline is easier for people and search engines.

Structured data found (Organization) but with 1 problem, for example “Organization: url is not an absolute URL ("/")”.

The homepage links to 57 pages on aalo.com and 6 external pages.

/careers is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/news and /updates all use the title “Latest Updates from Aalo Atomics | Nuclear Innovation News”. Search engines can't tell which page to show for a search, so each competes with the others.

/post/powering-the-ai-boom-inside-the-factory-building-cybertruck-sized-nuclear-reactors-forbes, /post/loading-graphite-into-a-nuclear-reactor-core, /post/3-matt-loszak-aalo-atomics-innovative-approach-to-next-gen-nuclear-deployment and /post/tickling-the-dragon-ft-matt-loszak-of-aalo-atomics have no meta description, so Google writes the search snippet from whatever text it finds.

/news and /updates use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /updates, whose canonical is /news. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/news and /updates have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

aalo.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 879 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and 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.

Opening the homepage sets 3 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.