145.aero website review

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

A phone's processor spends 4.9 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (hsappstatic.net, Shopify and Hubspot and others), adding 2.6 MB and 1.1 s of main-thread time.

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

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

19 images could be 236 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

hsappstatic.net costs a phone 489 ms of main-thread work and 719 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.

Shopify costs a phone 260 ms of main-thread work and 1.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.

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

The page has 2,019 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

34 KiB JavaScript is shipped twice across bundles.

Polyfills for old browsers add 33 KiB JavaScript that modern phones do not need.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Engine Oils, Hydraulic Fluids & Mineral Greases”.

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

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

Scripts block taps and scrolling for 436 ms in total while the page loads. Good is under 200 ms.

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

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

Your homepage downloads 4.5 MB in 452 requests on a phone: scripts 2.1 MB (180), other files 933 KiB (132) and images 909 KiB (62). Under 2 MB keeps phones on slow connections fast.

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

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

5 images have no alt text, which hurts accessibility and image search.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

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

Your meta description is 230 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/aircraftshopsupply-newlogo.png")”.

No XML sitemap at https://145.aero/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at 145.aero/robots.txt, the first file search crawlers ask for.

1 link has no real href, so search engines can't follow it.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Your <h1> is empty.

The homepage links to 301 pages on 145.aero and 6 external pages.

https://145.aero/collections/engine-oil-hydraulic-fluid-mineral-greases has no meta description, so Google writes the search snippet from whatever text it finds.

https://145.aero/collections/engine-oil-hydraulic-fluid-mineral-greases, https://145.aero/collections/piston-oils, https://145.aero/collections/turbine-oils, https://145.aero/collections/engine-preservation-oil-preservatives and https://145.aero/collections/mineral-greases have no <h1> headline, so visitors and search engines get no clear main topic.

https://145.aero/collections/engine-oil-hydraulic-fluid-mineral-greases, https://145.aero/collections/piston-oils, https://145.aero/collections/turbine-oils and https://145.aero/collections/engine-preservation-oil-preservatives took over 3 s to send their HTML from our server.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 606 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 28 cookies, 7 of them by other companies (measured from a US location before any click).

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