aaig.llc website review

About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.5 s faster on a phone.

About 325 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.

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

8 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

7 third-party services load with your homepage (YouTube, Google CDN and Other Google APIs/SDKs and others), adding 5.3 MB and 1.2 s of main-thread time.

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

YouTube costs a phone 772 ms of main-thread work and 2.0 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.

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

Google CDN costs a phone 331 ms of main-thread work and 1.1 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.

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

googleusercontent.com costs a phone 0 ms of main-thread work and 1.8 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.

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

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

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

Your largest element takes 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Part 107 FAA Certified Remote Pilots, Licensed & Insured Dr…”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 5.3 MB in 76 requests on a phone: scripts 2.8 MB (25), images 1.8 MB (12) and stylesheets 351 KiB (8). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example APXyLQfkWyrNBsJ5_5tw-Io_ZptnjViyM0ZQdeLfGcYHLEwGupgDwb_LccpK at 1,280 px wide, shown at 67 px. Resized copies would save about 1.1 MB.

APXyLQfkWyrNBsJ5_5tw-Io_ZptnjViyM0ZQdeLfGcYHLEwGupgDwb_LccpK weighs 588 KiB. On a phone connection a single image that size takes seconds.

7 images (1.8 MB) are 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.

6 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

All page content should be contained by landmarks: 19 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 8 characters: “AAIG.LLC”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 4 <h1> headlines (“Call Or Email Us Today & Book An Inspection”, “Our Certified Pilots & Technicians Conduct Accura…” and “Clients Receive Data Packages of Photos, Videos &…”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://www.aaig.llc/sitemap.xml, so Google discovers your pages only by following links.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 9 pages on aaig.llc and 7 external pages.

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.

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

/ and https://www.aaig.llc/home all use the title “AAIG.LLC”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.aaig.llc/home and https://www.aaig.llc/video-production have no meta description, so Google writes the search snippet from whatever text it finds.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://play.google.com/log?format=json&hasfast=true&authuser=0' from origin 'https://www.aaig.llc'…”.

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

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

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

There is no form on the homepage, so every lead has to click through to another page first.

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

Before a visitor clicks anything, the page loads Google Ads (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 1 cookie, 1 of them by other companies (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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.