Website review, no card needed

aeropost.com logo

aeropost.com website review

Visit site (opens in a new tab)Reviewed 26 October 202636 issues · 73 checks

This review found 36 issues worth fixing on aeropost.com, 12 of them high impact, across 73 checks. The most urgent: reduce unused JavaScript. 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.0 s1.3 sMay 9Oct 241.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.4 s
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.8 s
Sep 5, 20261.7 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
233 ms214 msMay 9Oct 24231 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026219 ms
May 16, 2026219 ms
May 23, 2026219 ms
May 30, 2026218 ms
Jun 6, 2026219 ms
Jun 13, 2026221 ms
Jun 20, 2026220 ms
Jun 27, 2026221 ms
Jul 4, 2026221 ms
Jul 11, 2026220 ms
Jul 18, 2026218 ms
Jul 25, 2026216 ms
Aug 1, 2026217 ms
Aug 8, 2026220 ms
Aug 15, 2026224 ms
Aug 22, 2026226 ms
Aug 29, 2026223 ms
Sep 5, 2026222 ms
Sep 12, 2026222 ms
Sep 19, 2026223 ms
Sep 26, 2026226 ms
Oct 3, 2026227 ms
Oct 10, 2026227 ms
Oct 17, 2026227 ms
Oct 24, 2026231 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 aeropost.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aeropost.com at 0.7 s0.7 s
  2. aeropost.com at 1.3 s1.3 s
  3. aeropost.com at 2.0 s2.0 s
  4. aeropost.com at 2.7 s2.7 s
  5. aeropost.com at 3.3 s3.3 s
  6. aeropost.com at 4.0 s4.0 s
  7. aeropost.com at 4.7 s4.7 s
  8. aeropost.com at 5.3 s5.3 s

Speed

9 to fix43
  • Reduce unused JavaScript

    1.3 s · 504 KiB

    About 504 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.

  • Mobile performance score: 43

    43/100

    Your mobile performance score is 43 (desktop: 80). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.1 MB and 1.5 s of main-thread time.

  • Google Tag Manager adds 980 ms

    980 ms

    Google Tag Manager costs a phone 980 ms of main-thread work and 687 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.

  • Use efficient cache lifetimes

    700 ms · 219 KiB

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

  • Improve image delivery

    350 ms · 413 KiB

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

  • 13 long tasks on the main thread

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

  • Main-thread work: 3.4 s

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

  • Facebook adds 266 ms

    266 ms

    Facebook costs a phone 266 ms of main-thread work and 223 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.

  • Render-blocking requests

    150 ms

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Reduce unused CSS

    26 KiB

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

  • Legacy JavaScript

    21 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 80 but mobile only 43. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 15 ms

    15 ms

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

Core Web Vitals

9 to fix33
  • 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: 18.5 s

    18.5 s

    Your largest element takes 18.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “¡Welcome to”.

  • Time to Interactive: 21.1 s

    21.1 s

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

  • First Contentful Paint: 4.8 s

    4.8 s

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

  • Total Blocking Time: 783 ms

    783 ms

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user INP: 282 ms

    282 ms

    Real visitors wait 282 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Speed Index: 5.2 s

    5.2 s

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

  • 19 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +5%

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

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

    +11%

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

4 checks passed
  • Real-user CLS: 0.08

    0.08

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 560 ms

    560 ms

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

  • Cumulative Layout Shift: 0.021

    0.021

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

Images and page weight

4 to fix35
  • Page weight: 5.6 MB in 103 requests

    5.6 MB

    Your homepage downloads 5.6 MB in 103 requests on a phone: images 2.1 MB (24), media 1.7 MB (3) and scripts 1.4 MB (24). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    service2.png weighs 589 KiB. On a phone connection a single image that size takes seconds.

  • 4 images in older formats

    4 images (1.4 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.

  • 1 image far larger than shown

    44 KiB

    1 image is downloaded at several times the size a phone draws it, for example image at 1,140 px wide, shown at 350 px. Resized copies would save about 44 KiB.

  • 1 image below the first screen load straight away

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

  • About 1.6 g of CO₂ per visit

    1.57 g

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

Accessibility

3 to fixGoogle 8793
  • 2 buttons without a name

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

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

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

  • 5 links without text

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

2 checks passed
  • Every image has alt text

    All 36 images in the HTML carry an alt attribute.

  • 26 automated accessibility rules passed

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

SEO

4 to fixGoogle 9288
  • No structured data

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

  • Meta description is long (166 characters)

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

  • Only 2 internal links

    The homepage links to only 2 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

6 checks passed
  • One H1 headline

    Your main headline reads: “¡Welcome to”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “International Shipping with aeropost: From the US & Worldwide”.

  • Canonical URL set

    The canonical URL is https://aeropost.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://aeropost.com/sitemap/sitemap.xml.

AI search readiness

1 to fix88
  • 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://aeropost.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 (816 words), so crawlers that don't run JavaScript still read it.

Best practices

1 to fixGoogle 9292
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Blocked by cross-origin policy”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: “100K Customers”. 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 517 words of copy

    The homepage carries about 517 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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.

  • 11 cookies set on arrival

    11

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

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

  • 21 other companies contacted

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

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 aeropost.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Nuxt
Analytics
Microsoft Clarity
Hosting
Vercel

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on aeropost.com, including 18 speed issues, 4 SEO issues and 4 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

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