greenlight.com website review

8 third-party services load with your homepage (Google Tag Manager, Segment and Facebook and others), adding 1.7 MB and 1.0 s of main-thread time.

Your mobile performance score is 54 (desktop: 64). Pages that score under 90 lose visitors before the first paint.

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

7 images could be 622 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

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

52 KiB JavaScript is shipped twice across bundles.

About 48 KiB of CSS is downloaded but never applied on this page.

43 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 22.8 MB in 232 requests on a phone: media 18.9 MB (8), scripts 2.7 MB (116) and images 691 KiB (31). Under 2 MB keeps phones on slow connections fast.

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

1 button has no accessible name, so screen readers announce just “button”.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Elements with visible text labels do not have matching accessible names. (2 elements).

There are 2 <h1> headlines (“The #1 family finance and safety app.” and “The #1 family finance and safety app.”). One clear main headline is easier for people and search engines.

The homepage links to 44 pages on greenlight.com and 20 external pages.

/chores-and-allowance-app-for-kids is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/privacy, /level-up-financial-literacy-game and /no-hidden-fees have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17003826&tm=gtm002&Ver=2&mid=0e0df9e3-e085-4c95-99e2-ad2fa92f2bdc&bo=1&sid=9464cea0d1b411f1a9f1bdbb5d2e619e&vid=9464ed10d1b411f18ccb71e489e98326&vids=1&msclkid=N&pi=91.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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

3 links from your homepage to your own site are broken, for example https://greenlight.com/blog/parents-guide-to-chores-and-allowances (404).

http://greenlight.com does not redirect to https, so some visitors land on the insecure version.

3 links go through two or more redirects, for example https://greenlightme.onelink.me/vRh4/f5636726.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

greenlight.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

greenlight.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 1,050 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 6 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.

Opening the homepage sets 30 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 49 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.