whistle.ltd website review

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

8 third-party services load with your homepage (hsappstatic.net, Google Tag Manager and website-files.com and others), adding 12.7 MB and 1.7 s of main-thread time.

website-files.com costs a phone 269 ms of main-thread work and 10.6 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.

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

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

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

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

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

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

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

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

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

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

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

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

13 KiB could be saved by minifying CSS.

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 23.7 s. Good is under 3.8 s.

Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Accelerate your pipeline generation”.

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

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

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

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

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

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

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

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

Your homepage downloads 13.3 MB in 213 requests on a phone: images 10.2 MB (90), scripts 2.3 MB (81) and other files 376 KiB (25). Under 2 MB keeps phones on slow connections fast.

33 images (2.9 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.

23 images further down the page (2.3 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 3.77 g of CO₂e: 452.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 34 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

Headings skip levels (h1 → h5, h3 → h6 and h1 → h4), which makes the page harder to scan with a screen reader.

There are 7 <h1> headlines (“More”, “$100K” and “7X”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 85 pages on whistle.ltd and 1 external page.

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

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 “Failed to load resource: the server responded with a status of 410 ()”.

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

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

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.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

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 2,157 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (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 17 cookies, 9 of them by other companies (measured from a US location before any click).

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