operationgratitude.com website review

cloudfront.net costs a phone 1.1 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

8 third-party services load with your homepage (cloudfront.net, YouTube and Other Google APIs/SDKs and others), adding 2.2 MB and 1.6 s of main-thread time.

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

About 1.0 MB of JavaScript is downloaded but never used on this page.

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

YouTube costs a phone 538 ms of main-thread work and 967 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.

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

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

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

Polyfills for old browsers add 10 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.

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.

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

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

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

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

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

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

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

2 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-17, real Chrome visitors' tap response (inp) went from 177 ms to 169 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.6 MB in 59 requests on a phone: images 8.4 MB (10), scripts 2.0 MB (28) and stylesheets 128 KiB (7). Under 2 MB keeps phones on slow connections fast.

2 images weigh 3.7 MB together. On a phone connection a single image that size takes seconds.

2 images (3.7 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.

3 images are downloaded at several times the size a phone draws them, for example pillar-how-we-do-it.jpg at 1,122 px wide, shown at 358 px. Resized copies would save about 381 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 3.02 g of CO₂e: 362.0 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”.

1 frame has no title, so screen-reader users cannot tell what it contains.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

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

A phone browser shows 663 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 663 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, 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 6 cookies, 2 of them by other companies (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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.