Website review, no card needed

airgigs.com logo

airgigs.com website review

Visit site (opens in a new tab)Reviewed 20 October 202642 issues · 83 checks

This review found 42 issues worth fixing on airgigs.com, 17 of them high impact, across 83 checks. The most urgent: use efficient cache lifetimes. 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.7 s2.2 sMay 2Oct 172.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.3 s
May 9, 20262.3 s
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.6 s
Aug 8, 20262.6 s
Aug 15, 20262.6 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
179 ms142 msMay 2Oct 17151 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026148 ms
May 9, 2026146 ms
May 16, 2026148 ms
May 23, 2026146 ms
May 30, 2026146 ms
Jun 6, 2026152 ms
Jun 13, 2026155 ms
Jun 20, 2026161 ms
Jun 27, 2026162 ms
Jul 4, 2026159 ms
Jul 11, 2026158 ms
Jul 18, 2026159 ms
Jul 25, 2026162 ms
Aug 1, 2026165 ms
Aug 8, 2026170 ms
Aug 15, 2026169 ms
Aug 22, 2026165 ms
Aug 29, 2026173 ms
Sep 5, 2026175 ms
Sep 12, 2026173 ms
Sep 19, 2026170 ms
Sep 26, 2026162 ms
Oct 3, 2026157 ms
Oct 10, 2026155 ms
Oct 17, 2026151 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 airgigs.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. airgigs.com at 0.4 s0.4 s
  2. airgigs.com at 0.8 s0.8 s
  3. airgigs.com at 1.1 s1.1 s
  4. airgigs.com at 1.5 s1.5 s
  5. airgigs.com at 1.9 s1.9 s
  6. airgigs.com at 2.3 s2.3 s
  7. airgigs.com at 2.6 s2.6 s
  8. airgigs.com at 3.0 s3.0 s

Speed

11 to fix42
  • Use efficient cache lifetimes

    9.2 s · 2.9 MB

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

  • Reduce unused JavaScript

    8.7 s · 1.5 MB

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

  • Improve image delivery

    4.0 s · 2.7 MB

    28 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.0 s faster on a phone.

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 42

    42/100

    Your mobile performance score is 42 (desktop: 57). 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 CDN, Google Tag Manager and helply.com and others), adding 3.0 MB and 1.6 s of main-thread time.

  • Google CDN adds 758 ms

    758 ms

    Google CDN costs a phone 758 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.

  • Main-thread work: 3.7 s

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

  • Google Tag Manager adds 250 ms

    250 ms

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

  • helply.com adds 212 ms

    212 ms

    helply.com costs a phone 212 ms of main-thread work and 344 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.

  • 2,061 HTML elements

    The page has 2,061 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Legacy JavaScript

    150 ms · 26 KiB

    Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 17 long tasks on the main thread

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

  • Reduce unused CSS

    30 ms · 39 KiB

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

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

1 checks passed
  • Server response: 55 ms

    55 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • First Contentful Paint: 11.1 s

    11.1 s

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

  • Largest Contentful Paint: 29.4 s

    29.4 s

    Your largest element takes 29.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BRING YOUR SONGS TO LIFE GET STARTED”.

  • Time to Interactive: 31.7 s

    31.7 s

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

  • Speed Index: 11.1 s

    11.1 s

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

  • Real-user TTFB: 931 ms

    931 ms

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

  • Total Blocking Time: 550 ms

    550 ms

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

  • 28 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

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

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

    +10%

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

5 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 118 ms

    118 ms

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (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.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix33
  • Page weight: 7.2 MB in 122 requests

    7.2 MB

    Your homepage downloads 7.2 MB in 122 requests on a phone: images 3.2 MB (48), scripts 2.9 MB (38) and other files 711 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    1.1 MB

    6 images are downloaded at several times the size a phone draws them, for example How-to-Become-More-Productive-as-a-Musician-1024x684.png at 1,024 px wide, shown at 108 px. Resized copies would save about 1.1 MB.

  • 10 images in older formats

    10 images (1.9 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.

  • 13 images below the first screen load straight away

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

  • About 2.0 g of CO₂ per visit

    2.04 g

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

Accessibility

11 to fixGoogle 6882
  • Orphan list items

    Some list items are not inside a list.

  • 13 text elements with low contrast

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 7 images without alt text

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

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

    All page content should be contained by landmarks: 21 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.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • 16 links without text

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

  • 12 form fields without a label

    12 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (11 elements)

    Alternative text of images should not be repeated as text: 11 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4), 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 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 11 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 7586
  • 3 H1 headlines

    There are 3 <h1> headlines (“Bring Your Songs to Life”, “Bring Your Songs to Life” and “Find Top Session Pros”). One clear main headline is easier for people and search engines.

  • Meta description is long (188 characters)

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

  • 18 links with vague text

    18 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

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

  • 258 internal links, 40 external

    The homepage links to 258 pages on airgigs.com and 40 external pages.

6 checks passed
  • Title: 64 characters

    Your title is a healthy 64 characters: “Hire Pro Studio Musicians, Vocalists & Audio Engineers | AirGigs”.

  • Canonical URL set

    The canonical URL is https://www.airgigs.com/.

  • Structured data in place

    Structured data found: Organization.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.airgigs.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

3 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: 5 of 6 facts

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,095 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

2 to fixGoogle 9687
  • 9 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://replay.airgigs.com/ingest/v1/web/start' from origin 'https://www.airgigs.com' has been bloc…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • A 8-field form

    Your longest form asks for 8 fields (3 required). Every extra field lowers completion.

  • 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 489 words of copy

    The homepage carries about 489 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “START SELLING” and “SIGNUP”.

  • 23 calls to action

    The homepage has 23 calls to action, for example “Start Selling”, “Sign up today for more info!” and “sign up now!”.

  • Social proof on the page

    Social proof on the homepage: 5 testimonial or review blocks, 2 customer or partner logos, a star rating and 7 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 2 mores (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.

  • 15 cookies set on arrival

    15

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

  • 26 other companies contacted

    Loading the homepage contacts 26 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 airgigs.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 Analytics | Google Tag Manager | Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on airgigs.com, including 19 speed issues, 4 SEO issues and 1 conversion gap. 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