loyaltyplant.com website review

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

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

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

Your mobile performance score is 31 (desktop: 69). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Hubspot and others), adding 4.0 MB and 2.5 s of main-thread time.

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

Google CDN costs a phone 913 ms of main-thread work and 1.5 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.

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

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

Hubspot costs a phone 439 ms of main-thread work and 499 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.

hsappstatic.net costs a phone 364 ms of main-thread work and 784 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.

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

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

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

Desktop scores 69 but mobile only 31. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

3 KiB could be saved by minifying CSS.

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

Your largest element takes 21.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “mobile-mobile”.

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

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

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

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.

Your homepage downloads 6.8 MB in 135 requests on a phone: scripts 3.7 MB (46), images 1.6 MB (47) and other files 719 KiB (17). Under 2 MB keeps phones on slow connections fast.

8 images (1.0 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.

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

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

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

8 tap targets are too small or too close together to hit reliably with a finger.

1 image has no alt text, which hurts accessibility and image search.

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

The homepage links to 55 pages on loyaltyplant.com and 7 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://loyaltyplant.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://loyaltyplant.com/mobile-app-for-restaurants and https://loyaltyplant.com/mobile-app-for-restaurant all use the title “Mobile app for restaurants”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://loyaltyplant.com/mobile-app-for-restaurants and https://loyaltyplant.com/mobile-app-for-restaurant use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://loyaltyplant.com/case-studies, whose canonical is https://loyaltyplant.com/restaurant-case-studies. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://loyaltyplant.com/mobile-app-for-restaurants, https://loyaltyplant.com/loyalty-program-for-restaurants, https://loyaltyplant.com/restaurant-crm-system, https://loyaltyplant.com/restaurant-marketing, https://loyaltyplant.com/restaurant-integrations and https://loyaltyplant.com/blog/smart-landing-pages-turn-clicks-into-orders-instantly and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://loyaltyplant.com/mobile-app-for-restaurants, https://loyaltyplant.com/loyalty-program-for-restaurants, https://loyaltyplant.com/restaurant-crm-system, https://loyaltyplant.com/restaurant-marketing, https://loyaltyplant.com/restaurant-integrations and https://loyaltyplant.com/blog/smart-landing-pages-turn-clicks-into-orders-instantly and 9 others have 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.

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

4 images failed to load on a phone, for example https://loyaltyplant.com/.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “wp is not defined”.

Chrome logged issues while loading the page (“Cookie”).

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.

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

Your longest form asks for 9 fields (4 required). Every extra field lowers completion.

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

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

The homepage carries about 648 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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