24hr.supply website review

About 812 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.

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

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

Signyfyd costs a phone 1.3 s of main-thread work and 244 KiB 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.

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

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

8 third-party services load with your homepage (Signyfyd, Google Tag Manager and Hotjar and others), adding 2.9 MB and 2.4 s of main-thread time.

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

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

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

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

Bigcommerce costs a phone 155 ms of main-thread work and 1.1 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.

ZenDesk costs a phone 128 ms of main-thread work and 428 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.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

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 21.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Decorative image”.

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

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

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

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

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

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

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

Your homepage downloads 3.5 MB in 191 requests on a phone: scripts 2.2 MB (83), images 575 KiB (40) and fonts 357 KiB (7). Under 2 MB keeps phones on slow connections fast.

homehero-mobile.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

3 elements hidden from screen readers can still receive keyboard focus.

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

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

13 visible links have no text or label, so screen readers cannot say where they go.

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

Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

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

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

The homepage links to 861 pages on 24hr.supply and 6 external pages.

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

/shipping-policy, /90-day-return-policy, /faq, /heating/baseboard-heaters and /heating/baseboard-heaters/embassy-heaters have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 196 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=97213155&tm=gtm002&Ver=2&mid=9b791944-962c-447b-9eeb-bfd66edab498&bo=1&sid=3c1df5e0d5ed11f18c37114e1f603ec2&vid=3c1e2110d5ed11f1b87351d5b04394ec&vids=1&msclkid=N&pi=91.

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

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

4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v5.7.0/css/all.css' from origin 'https://24hr.supply'…”.

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

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

HSTS is set, but max-age is 0 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

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

24hr.supply 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.

24hr.supply'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.

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.

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 525 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 Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 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 24 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 52 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.