Programmable

Website review, no card needed

loyalty.run logo

loyalty.run website review

Visit site (opens in a new tab)Reviewed 8 November 202622 issues · 67 checks

This review found 22 issues worth fixing on loyalty.run, 5 of them high impact, across 67 checks. The most urgent: 93 text elements with low contrast. 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

Site score

79C

Closest competitors among Shopify stores

Compare side by side

One score from every part of this review. How it works

www.loyalty.run (opens in a new tab)
Full-page screenshot of loyalty.run (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. loyalty.run at 0.6 s0.6 s
  2. loyalty.run at 1.1 s1.1 s
  3. loyalty.run at 1.7 s1.7 s
  4. loyalty.run at 2.2 s2.2 s
  5. loyalty.run at 2.8 s2.8 s
  6. loyalty.run at 3.4 s3.4 s
  7. loyalty.run at 3.9 s3.9 s
  8. loyalty.run at 4.5 s4.5 s

Speed

7 to fix71

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Facebook and reddit and others), adding 637 KiB and 1.1 s of main-thread time.

  • Mobile performance score: 71

    71/100

    Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 718 ms

    718 ms

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

    290 ms · 381 KiB

    About 381 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 290 ms faster on a phone.

  • 10 long tasks on the main thread

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

  • Facebook adds 278 ms

    278 ms

    Facebook costs a phone 278 ms of main-thread work and 212 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.9 s

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

  • Use efficient cache lifetimes

    217 KiB

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

  • Render-blocking requests

    150 ms

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

  • Legacy JavaScript

    48 KiB

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

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

    2 ms

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

Core Web Vitals

5 to fix74

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Time to Interactive: 9.4 s

    9.4 s

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

  • Speed Index: 4.8 s

    4.8 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 15 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed

  • Largest Contentful Paint: 2.0 s

    2.0 s

    Your largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “One curated feed of flights, with per-program efficiency at…”.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100

  • About 0.3 g of CO₂ per visit

    0.35 g

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

4 checks passed

  • Page weight: 1.2 MB in 86 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 86 requests on a phone: scripts 1.0 MB (35), images 83 KiB (20) and fonts 54 KiB (2). That is a lean page.

  • 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

1 to fixGoogle 9698

  • 93 text elements with low contrast

    93 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

2 checks passed

  • Every image has alt text

    All 70 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

2 to fixGoogle 10088

  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Loyalty Run — Best AAdvantage, Avios, Qantas & Alaska Flight Deals”.

  • Meta description is long (211 characters)

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

  • 64 internal links, 0 external

    The homepage links to 64 pages on loyalty.run and 0 external pages.

6 checks passed

  • One H1 headline

    Your main headline reads: “Find flight dealsthat level up yourAmerican Airlineselite status.”.

  • Canonical URL set

    The canonical URL is https://www.loyalty.run/.

  • Structured data in place

    Structured data found: ItemList and 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.loyalty.run/sitemap.xml.

AI search readiness

100

  • Opted out of AI training for 1 crawler

    robots.txt blocks CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.loyalty.run/llms.txt (3 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix86

  • 9 pages share 3 titles

    https://www.loyalty.run/aa/deal/flights/ce42df1e-ad4c-47c7-ad4e-719234e2a474, https://www.loyalty.run/ba/deal/flights/ce42df1e-ad4c-47c7-ad4e-719234e2a474 and https://www.loyalty.run/qf/deal/flights/ce42df1e-ad4c-47c7-ad4e-719234e2a474 all use the title “BOM to KUL Business Flight — Loyalty Run”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages share a meta description

    https://www.loyalty.run/contact, https://www.loyalty.run/aa/deal/flights/ce42df1e-ad4c-47c7-ad4e-719234e2a474, https://www.loyalty.run/ba/deal/flights/ce42df1e-ad4c-47c7-ad4e-719234e2a474, https://www.loyalty.run/qf/deal/flights/ce42df1e-ad4c-47c7-ad4e-719234e2a474, https://www.loyalty.run/aa/deal/flights/8f605466-a9df-47bd-9e5a-df8675879d1d and https://www.loyalty.run/ba/deal/flights/8f605466-a9df-47bd-9e5a-df8675879d1d and 5 others use the same meta description. A description written for each page earns more clicks.

  • 7 pages without an H1

    https://www.loyalty.run/aa/deal/flights/ce42df1e-ad4c-47c7-ad4e-719234e2a474, https://www.loyalty.run/ba/deal/flights/ce42df1e-ad4c-47c7-ad4e-719234e2a474, https://www.loyalty.run/qf/deal/flights/ce42df1e-ad4c-47c7-ad4e-719234e2a474, https://www.loyalty.run/aa/deal/flights/8f605466-a9df-47bd-9e5a-df8675879d1d, https://www.loyalty.run/ba/deal/flights/8f605466-a9df-47bd-9e5a-df8675879d1d and https://www.loyalty.run/qf/deal/flights/8f605466-a9df-47bd-9e5a-df8675879d1d and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.loyalty.run/contact has 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.

  • 15 internal pages checked

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

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

  • 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

Google 100100
3 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    28 of 28 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50

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

    The homepage carries about 461 words of visible text.

2 checks passed

  • 4 calls to action

    The homepage has 4 calls to action, for example “Sign In / Sign Up” and “Contact”.

  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

1 to fix

  • 5 trackers load before any consent

    5

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

  • 9 cookies set on arrival

    9

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

  • 12 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Next.js
E-commerce
Shopify;Shopify Plus
Analytics
Google Analytics
Hosting
Vercel

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on loyalty.run, including 12 speed issues, 2 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

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