getburple.com website review

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

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

8 third-party services load with your homepage (Wix, Google Tag Manager and Facebook and others), adding 5.4 MB and 1.4 s of main-thread time.

Wix costs a phone 797 ms of main-thread work and 4.8 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 58. Pages that score under 90 lose visitors before the first paint.

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

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

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

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

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

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

32 KiB JavaScript is shipped twice across bundles.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 8.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mom holding her baby with Burple Burp Catcher and Burp clot…”.

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

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

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

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

The first text or image appears after 2.0 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.

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.9 MB in 277 requests on a phone: images 3.5 MB (22), scripts 1.7 MB (108) and other files 1.4 MB (141). Under 2 MB keeps phones on slow connections fast.

663538_c66fc9ad514d41739721001e504024aa~mv2.gif weighs 3.3 MB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example 663538_c66fc9ad514d41739721001e504024aa~mv2.gif at 640 px wide, shown at 107 px. Resized copies would save about 2.5 MB.

1 image (3.3 MB) 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 1.97 g of CO₂e: 235.9 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”.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

There are 5 <h1> headlines (“Patent Protected Design”, “What Makes Burple Different?” and “FAQ”). One clear main headline is easier for people and search engines.

Structured data found (LocalBusiness and WebSite) but with 1 problem, for example “WebSite: missing name”.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 28 pages on getburple.com and 5 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.getburple.com/shop, https://www.getburple.com/aboutus, https://www.getburple.com/blog, https://www.getburple.com/contactus, https://www.getburple.com/product-page/burple-burp-catcher and https://www.getburple.com/termsandconditions and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.getburple.com/contactus has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 11 pages linked from your homepage and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “globalThis.defineStrictProperty is not a function”.

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Meta Pixel (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 10 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 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.