natpats.com website review

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

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

A phone's processor spends 6.6 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 Tag Manager, Klaviyo and Shopify and others), adding 2.1 MB and 1.4 s of main-thread time.

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

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

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

About 703 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

Klaviyo costs a phone 194 ms of main-thread work and 612 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.

Shopify costs a phone 168 ms of main-thread work and 305 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 218 ms. During a long task the page ignores taps.

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

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

24 KiB could be saved by minifying JavaScript.

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

2 KiB JavaScript is shipped twice across bundles.

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

Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “12-hour bite defence. No DEET. No spray battle.”.

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

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

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

Scripts block taps and scrolling for 326 ms 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.6 MB in 493 requests on a phone: scripts 2.5 MB (167), images 2.1 MB (86) and other files 1.3 MB (171). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example natpat-mosquito-protection-patches-for-kids-safe-easy-to-use at 1,841 px wide, shown at 44 px. Resized copies would save about 536 KiB.

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

62 buttons have no accessible name, so screen readers announce just “button”.

1 dropdown has no label.

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

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

Google's crawler is blocked from indexing this page.

Your canonical URL points to natpat.com, not natpats.com, so Google may credit that host instead.

There are 6 <h1> headlines (“Born inAustralia”, “12-hour bite defence. No DEET. No spray battle.” and “Peel. Stick. Sleep.”). One clear main headline is easier for people and search engines.

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

The homepage links to 131 pages on natpats.com and 41 external pages.

https://natpats.com/collections/homepage, https://natpats.com/collections/outdoor-protection, https://natpats.com/collections/wellness-cognitive, https://natpats.com/collections/pets, https://natpats.com/collections/respiratory-allergy-relief and https://natpats.com/collections/swag and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://natpats.com/pages/bundle-builder, https://natpats.com/pages/awards, https://natpats.com/pages/science and https://natpats.com/pages/natpat-reviews have no meta description, so Google writes the search snippet from whatever text it finds.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=52011094&tm=gtm002&Ver=2&mid=7018f302-cd0c-4a8c-933c-4e08bfbd79a7&bo=1&sid=ea62a7f0dcbd11f18d507df257dc63dd&vid=ea629e20dcbd11f18fa5d5422ffe6b53&vids=1&msclkid=N&gtm_t.

14 of 36 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.”).

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and LinkedIn Insight and 7 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 25 cookies, 1 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 71 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.