Website review, no card needed

alaport.com logo

alaport.com website review

Visit site (opens in a new tab)Reviewed 18 October 202639 issues · 66 checks

This review found 39 issues worth fixing on alaport.com, 14 of them high impact, across 66 checks. The most urgent: render-blocking requests. 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
6.0 s3.3 sApr 25Oct 103.6 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20265.4 s
May 2, 20265.5 s
May 9, 20265.5 s
May 16, 20265.6 s
May 23, 20265.6 s
May 30, 20265.6 s
Jun 6, 20265.6 s
Jun 13, 20265.7 s
Jun 20, 20265.7 s
Jun 27, 20265.7 s
Jul 4, 20265.6 s
Jul 11, 20265.6 s
Jul 18, 20265.6 s
Jul 25, 20265.6 s
Aug 1, 20265.6 s
Aug 8, 20265.5 s
Aug 15, 20265.3 s
Aug 22, 20265.2 s
Aug 29, 20265.1 s
Sep 5, 20265.1 s
Sep 12, 20265.1 s
Sep 19, 20264.7 s
Sep 26, 20264.4 s
Oct 3, 20263.9 s
Oct 10, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
1.3 s170 msApr 25Oct 10305 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026984 ms
May 2, 20261.0 s
May 9, 2026995 ms
May 16, 20261.0 s
May 23, 20261.0 s
May 30, 20261.0 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.0 s
Sep 19, 2026742 ms
Sep 26, 2026459 ms
Oct 3, 2026342 ms
Oct 10, 2026305 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 alaport.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alaport.com at 0.7 s0.7 s
  2. alaport.com at 1.4 s1.4 s
  3. alaport.com at 2.1 s2.1 s
  4. alaport.com at 2.8 s2.8 s
  5. alaport.com at 3.5 s3.5 s
  6. alaport.com at 4.2 s4.2 s
  7. alaport.com at 4.9 s4.9 s
  8. alaport.com at 5.6 s5.6 s

Speed

8 to fix73
  • Render-blocking requests

    1.0 s

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

  • Use efficient cache lifetimes

    5.4 MB

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

  • Improve image delivery

    4.8 MB

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

  • Mobile performance score: 73

    73/100

    Your mobile performance score is 73 (desktop: 96). 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 (binclusive.io, Cloudflare and posthog.com and others), adding 6.0 MB and 179 ms of main-thread time.

  • tav.aero adds 0 ms

    0 ms

    tav.aero costs a phone 0 ms of main-thread work and 5.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.

  • Reduce unused CSS

    460 ms · 26 KiB

    About 26 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 460 ms faster on a phone.

  • binclusive.io adds 168 ms

    168 ms

    binclusive.io costs a phone 168 ms of main-thread work and 329 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.

  • Reduce unused JavaScript

    150 ms · 88 KiB

    About 88 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.

  • 4 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 1.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 895 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

10 to fix0
  • 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.

  • Real-user LCP: 4.1 s

    4.1 s

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

  • Real-user CLS: 0.68

    0.68

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

  • Largest Contentful Paint: 4.8 s

    4.8 s

    Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ALMATY INTERNATIONAL AIRPORT”. Most of its time is element render delay (2.1 s).

  • Time to Interactive: 7.6 s

    7.6 s

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

  • Real-user INP: 237 ms

    237 ms

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Speed Index: 5.8 s

    5.8 s

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

  • 2 images without width and height

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

5 checks passed
  • Real-user TTFB: 714 ms

    714 ms

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

  • Tap response (INP) got 68% faster for real visitors

    -68%

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

  • Largest content (LCP) got 31% faster for real visitors

    -31%

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

  • Cumulative Layout Shift: 0.037

    0.037

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

  • Total Blocking Time: 48 ms

    48 ms

    Scripts block the page for only 48 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix35
  • Page weight: 6.5 MB in 192 requests

    6.5 MB

    Your homepage downloads 6.5 MB in 192 requests on a phone: images 5.6 MB (38), scripts 703 KiB (94) and other files 112 KiB (30). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    ilyas_dautov_ljw3m_B_Wuw_TA_unsplash_760ea55e64.webp weighs 2.2 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    2.1 MB

    1 image is downloaded at several times the size a phone draws it, for example ilyas_dautov_ljw3m_B_Wuw_TA_unsplash_760ea55e64.webp at 6,000 px wide, shown at 390 px. Resized copies would save about 2.1 MB.

  • About 1.8 g of CO₂ per visit

    1.85 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

3 to fixGoogle 10097
  • All page content should be contained by landmarks (2 elements)

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

7 to fixGoogle 10052
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 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 social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • Only 0 internal links

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

2 checks passed
  • 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://cms.tav.aero/api/strapi-5-sitemap-plugin/sitemap.xml.

AI search readiness

1 to fix83
  • 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://alaport.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
  • 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.

Best practices

2 to fixGoogle 9287
  • 9 small tap targets

    9 of 29 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was 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 (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • 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.

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • Only about 92 words

    The homepage has only about 92 words of visible text; thin pages give Google and first-time buyers little to go on.

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

1 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more”.

Privacy and tracking

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

  • 3 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

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 alaport.com, including 18 speed issues, 7 SEO issues and 5 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