instantpot.com website review

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

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, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google Tag Manager, pricespider.com and Osano CMP and others), adding 1.6 MB and 2.0 s of main-thread time.

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

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

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

pricespider.com costs a phone 535 ms of main-thread work and 116 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.

7 images could be 364 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

Osano CMP costs a phone 293 ms of main-thread work and 83 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,595 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

About 113 KiB of CSS is downloaded but never applied on this page. 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).

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

Your largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Overhead view of the Sea Salt InstantChill™ Ice Cream Maker…”.

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

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

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

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

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

Your homepage downloads 30.1 MB in 247 requests on a phone: media 25.4 MB (2), scripts 2.4 MB (78) and images 1.3 MB (27). Under 2 MB keeps phones on slow connections fast.

Homepage_Desktop_Banners_37.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).

1 image (109 KiB) is 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.

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

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

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

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

Banner landmark should not be contained in another landmark: 1 element on the page fails 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.

1 tap target is too small or too close together to hit reliably with a finger.

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

Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (BreadcrumbList, OnlineStore, Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

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

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

Your <h1> is empty.

The homepage links to 154 pages on instantpot.com and 28 external pages.

/pages/about-instant-pot and /pages/product-manuals are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/pages/about-instant-pot, /pages/consumer-care-center, /pages/product-manuals, /pages/frequently-asked-questions, /pages/product-support and /pages/product-warranties and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/ip-3qt, /collections/ip-6qt, /collections/instant-pot-wide-base and /collections/ip-8qt use the same meta description. A description written for each page earns more clicks.

/pages/about-instant-pot, /pages/consumer-care-center, /pages/product-manuals, /pages/frequently-asked-questions, /pages/product-support and /pages/product-warranties and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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

Social proof on the homepage: 9 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 1,052 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). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 5 cookies (measured from a US location before any click).

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