Website review, no card needed
airmee.com website review
Visit site (opens in a new tab)Reviewed 18 October 202639 issues · 83 checks
This review found 39 issues worth fixing on airmee.com, 10 of them high impact, across 83 checks. The most urgent: page weight: 13.0 MB in 42 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 1.4 s |
| May 2, 2026 | 1.4 s |
| May 9, 2026 | 1.4 s |
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 105 ms |
| May 2, 2026 | 105 ms |
| May 9, 2026 | 105 ms |
| May 16, 2026 | 107 ms |
| May 23, 2026 | 108 ms |
| May 30, 2026 | 111 ms |
| Jun 6, 2026 | 110 ms |
| Jun 13, 2026 | 112 ms |
| Jun 20, 2026 | 111 ms |
| Jun 27, 2026 | 111 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 109 ms |
| Jul 18, 2026 | 113 ms |
| Jul 25, 2026 | 113 ms |
| Aug 1, 2026 | 112 ms |
| Aug 8, 2026 | 113 ms |
| Aug 15, 2026 | 112 ms |
| Aug 22, 2026 | 112 ms |
| Aug 29, 2026 | 112 ms |
| Sep 5, 2026 | 115 ms |
| Sep 12, 2026 | 116 ms |
| Sep 19, 2026 | 111 ms |
| Sep 26, 2026 | 111 ms |
| Oct 3, 2026 | 110 ms |
| Oct 10, 2026 | 110 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
Speed
Use efficient cache lifetimes
11.1 MB27 files are served with short cache lifetimes, so returning visitors download them again (11.1 MB).
Improve image delivery
5.4 MB13 images could be 5.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page.
Mobile performance score: 82
82/100Your mobile performance score is 82 (desktop: 67). Pages that score under 90 lose visitors before the first paint.
6 third-party services on the page
6 third-party services load with your homepage (Google CDN, Intercom and Google Tag Manager and others), adding 1.3 MB and 764 ms of main-thread time.
Google CDN adds 324 ms
324 msGoogle CDN costs a phone 324 ms of main-thread work and 730 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.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 238 ms. During a long task the page ignores taps.
Document request latency
190 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce unused CSS
164 KiBAbout 164 KiB of CSS is downloaded but never applied on this page.
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: 44 ms
44 msYour server sent the HTML in 44 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 19.9 s
19.9 sThe page becomes fully interactive after 19.9 s. Good is under 3.8 s.
Total Blocking Time: 499 ms
499 msScripts block taps and scrolling for 499 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
3 images without width and height
3 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-10, real Chrome visitors' tap response (inp) went from 105 ms to 110 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 114 ms
114 msReal visitors wait 114 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 356 ms
356 msReal visitors wait 356 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.2 s
3.2 sVisually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.
Largest Contentful Paint: 2.3 s
2.3 sYour largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 13.0 MB in 42 requests
13.0 MBYour homepage downloads 13.0 MB in 42 requests on a phone: images 6.1 MB (21), media 4.0 MB (1) and scripts 2.1 MB (13). Under 2 MB keeps phones on slow connections fast.
9 images over 500 KB
9 images weigh 6.1 MB together. On a phone connection a single image that size takes seconds.
9 images in older formats
9 images (6.1 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.
8 images below the first screen load straight away
8 images further down the page (5.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.7 g of CO₂ per visit
3.68 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.68 g of CO₂e: 441.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
16 images without alt text
16 images have no alt text, which hurts accessibility and image search.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://airmee.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at airmee.com/robots.txt, the first file search crawlers ask for.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
One H1 headline
Your <h1> is empty.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
13 internal links, 12 external
The homepage links to 13 pages on airmee.com and 12 external pages.
2 checks passed
Meta description: 91 characters
Your meta description is 91 characters: “The new standard in last mile delivery. Fast deliveries to your doorstep or closest locker.”.
Title: 35 characters
Your title is a healthy 35 characters: “Airmee | Fossil free, fast delivery”.
AI search readiness
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://airmee.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.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (290 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share 2 titles
/ and https://airmee.com/en all use the title “Airmee | Fossil free, fast delivery”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://airmee.com/assets/sustainability-2025.html has no meta description, so Google writes the search snippet from whatever text it finds.
7 pages share a meta description
https://airmee.com/en, https://airmee.com/en/download-app, https://airmee.com/en/about, https://airmee.com/en/for-retailers, https://airmee.com/en/support and https://airmee.com/for-retailers and 1 other use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://airmee.com/assets/sustainability-2025.html has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://airmee.com/en/download-app, https://airmee.com/assets/sustainability-2025.html and https://airmee.com/en/contact have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
8 internal pages checked
We fetched 8 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 8 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 8 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://airmee.com/en/assets/news/news_7_60.jpg.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “ERROR Error: Uncaught (in promise): TypeError: Cannot read properties of undefined (reading 'nativeElement')”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
7 of 7 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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 317 words of copy
The homepage carries about 317 words of visible text.
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Download appIOS & Android” and “Contact sales”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads 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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
7 other companies contacted
Loading the homepage contacts 7 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 airmee.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2022.
Stack
- Framework
- Angular
- Analytics
- Google Analytics
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on airmee.com, including 11 speed issues, 6 SEO issues and 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.