Website review, no card needed

aertecsolutions.com logo

aertecsolutions.com website review

Visit site (opens in a new tab)Reviewed 26 October 202632 issues · 77 checks

This review found 32 issues worth fixing on aertecsolutions.com, 10 of them high impact, across 77 checks. The most urgent: fails Core Web Vitals for real visitors. 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
9.6 s1.6 sMay 9Oct 244.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.5 s
May 16, 20262.9 s
May 23, 20262.5 s
May 30, 20262.7 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20264.2 s
Jul 4, 20264.2 s
Jul 11, 20265.6 s
Jul 18, 20265.9 s
Jul 25, 20266.1 s
Aug 1, 20266.2 s
Aug 8, 20266.9 s
Aug 15, 20268.7 s
Aug 22, 20268.7 s
Aug 29, 20268.7 s
Sep 5, 20265.6 s
Sep 12, 20264.1 s
Sep 19, 20265.7 s
Sep 26, 20265.8 s
Oct 3, 20265.4 s
Oct 10, 20265.2 s
Oct 17, 20264.6 s
Oct 24, 20264.4 s
Real-visitor tap response (INP)75th percentile, phones
387 ms117 msMay 9Oct 24356 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026148 ms
May 16, 2026149 ms
May 23, 2026171 ms
May 30, 2026173 ms
Jun 6, 2026174 ms
Jun 13, 2026170 ms
Jun 20, 2026170 ms
Jun 27, 2026279 ms
Jul 4, 2026283 ms
Jul 11, 2026313 ms
Jul 18, 2026322 ms
Jul 25, 2026316 ms
Aug 1, 2026316 ms
Aug 8, 2026310 ms
Aug 15, 2026304 ms
Aug 22, 2026293 ms
Aug 29, 2026276 ms
Sep 5, 2026201 ms
Sep 12, 2026202 ms
Sep 19, 2026273 ms
Sep 26, 2026291 ms
Oct 3, 2026311 ms
Oct 10, 2026338 ms
Oct 17, 2026344 ms
Oct 24, 2026356 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 aertecsolutions.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aertecsolutions.com at 0.9 s0.9 s
  2. aertecsolutions.com at 1.8 s1.8 s
  3. aertecsolutions.com at 2.8 s2.8 s
  4. aertecsolutions.com at 3.7 s3.7 s
  5. aertecsolutions.com at 4.6 s4.6 s
  6. aertecsolutions.com at 5.5 s5.5 s
  7. aertecsolutions.com at 6.4 s6.4 s
  8. aertecsolutions.com at 7.3 s7.3 s

Speed

2 to fix90
  • Google Tag Manager adds 289 ms

    289 ms

    Google Tag Manager costs a phone 289 ms of main-thread work and 333 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.5 s

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Hubspot and Google Analytics and others), adding 560 KiB and 450 ms of main-thread time.

  • Reduce unused JavaScript

    224 KiB

    About 224 KiB of JavaScript is downloaded but never used on this page.

  • 3 long tasks on the main thread

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

  • Use efficient cache lifetimes

    205 KiB

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

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

  • Forced reflow

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

2 checks passed
  • Mobile performance score: 90

    90/100

    Your mobile performance score is 90 (desktop: 94). That is in Google's “good” band (90 and up).

  • Server response: 109 ms

    109 ms

    Your server sent the HTML in 109 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: 5.4 s

    5.4 s

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

  • Real-user CLS: 0.33

    0.33

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

  • Real-user TTFB: 2.0 s

    2.0 s

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

  • Speed Index: 8.4 s

    8.4 s

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

  • Real-user INP: 314 ms

    314 ms

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

  • Tap response (INP) got 136% slower for real visitors

    +136%

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

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

    +40%

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

  • Real-user FCP: 2.6 s

    2.6 s

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

  • Time to Interactive: 6.9 s

    6.9 s

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

4 checks passed
  • Total Blocking Time: 169 ms

    169 ms

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Largest Contentful Paint: 1.1 s

    1.1 s

    Your largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Impulsando la aeronáutica hacia un futuro más inteligente, …”.

Images and page weight

1 to fix85
  • Page weight: 2.8 MB in 83 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 83 requests on a phone: media 1.9 MB (4), scripts 764 KiB (30) and stylesheets 72 KiB (34). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.81 g

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

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8790
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails 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.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 56 images in the HTML carry an alt attribute.

  • 33 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: 33 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10086
  • No H1 headline

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

  • Structured data has 1 problem

    Structured data found (Corporation, ImageObject, Organization and WebPage) but with 1 problem, for example “ImageObject: url is not an absolute URL ("https://aertecsolutions.com/wp-content/uploads/2025/02/Boton-arrow-and-more.svg")”.

  • 160 internal links, 14 external

    The homepage links to 160 pages on aertecsolutions.com and 14 external pages.

6 checks passed
  • Meta description: 128 characters

    Your meta description is 128 characters: “AERTEC ofrece ingeniería aeronáutica internacional, consultoría aeroespacial y soluciones para aeropuertos, industria y…”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “AERTEC – ingeniería aeronáutica internacional y consultoría”.

  • Canonical URL set

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

AI search readiness

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

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

Other pages

1 to fix95
  • 1 page without an H1

    https://aertecsolutions.com/infohub has no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages slow to respond

    https://aertecsolutions.com/aeropuertos/consultoria-aeronautica, https://aertecsolutions.com/aeropuertos/planificacion-aeroportuaria, https://aertecsolutions.com/aeropuertos/diseno-de-infraestructuras-aeroportuarias, https://aertecsolutions.com/aeropuertos/project-management, https://aertecsolutions.com/aeropuertos/operaciones-aeroportuarias and https://aertecsolutions.com/aeropuertos/consultoria-it-aeroportuaria and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10092
  • 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”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 18 words

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

  • No opening hours

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

  • No form on the homepage

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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
  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 8 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on aertecsolutions.com, including 12 speed issues, 2 SEO issues and 7 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