loylty.com website review

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

39 images could be 4.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.

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

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

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

2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 179 KiB and 136 ms of main-thread time.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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.

Your largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Leading transformation in customer engagement with technolo…”. Most of its time is resource load duration (3.1 s).

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

The layout shifts by 0.307 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

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

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

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

Your homepage downloads 6.1 MB in 117 requests on a phone: images 5.5 MB (100), scripts 314 KiB (11) and fonts 305 KiB (1). Under 2 MB keeps phones on slow connections fast.

34 images (5.2 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.

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

3 images are downloaded at several times the size a phone draws them, for example consumer-loyalty.png at 522 px wide, shown at 163 px. Resized copies would save about 30 KiB.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 9 <h1> headlines (“Leading transformation in customer engagement wit…”, “Deliver customer delight,” and “Our expertise forged in a landscape of experience”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No XML sitemap at https://loylty.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at loylty.com/robots.txt, the first file search crawlers ask for.

3 links have no real href, so search engines can't follow them.

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

The homepage links to 50 pages on loylty.com and 3 external pages.

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.

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

https://loylty.com/technology/lidsys-xlii, https://loylty.com/technology/data-security, https://loylty.com/videos, https://loylty.com/about/who-we-are, https://loylty.com/about/clients and https://loylty.com/about/awards and 4 others all use the title “Loylty Rewardz”. Search engines can't tell which page to show for a search, so each competes with the others.

https://loylty.com/technology/lidsys-xlii, https://loylty.com/technology/data-security, https://loylty.com/videos, https://loylty.com/about/who-we-are, https://loylty.com/about/clients and https://loylty.com/about/awards and 4 others use the same meta description. A description written for each page earns more clicks.

https://loylty.com/technology/data-security, https://loylty.com/videos, https://loylty.com/about/contact-us and https://loylty.com/about/privacy-policy have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://loylty.com/menu/about/policy.png.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 528 words of visible text.

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

Opening the homepage sets 4 cookies (measured from a US location before any click).

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.

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