takeultra.com website review

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

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

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

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

A phone's processor spends 6.7 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 (alia-prod.com, Facebook and Google Tag Manager and others), adding 1.6 MB and 1.6 s of main-thread time.

18 images could be 498 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.

alia-prod.com costs a phone 455 ms of main-thread work and 289 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 1,612 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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

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.

Your largest element takes 18.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 178 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 2.4 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 16.0 MB in 455 requests on a phone: media 11.7 MB (21), scripts 2.3 MB (138) and other files 958 KiB (184). Under 2 MB keeps phones on slow connections fast.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

The homepage links to 82 pages on takeultra.com and 31 external pages.

https://takeultra.com/products/focus-pouches-v2 and https://takeultra.com/products/focus-pouches-v2-1 all use the title “Focus Pouches – Ultra Pouches”. Search engines can't tell which page to show for a search, so each competes with the others.

https://takeultra.com/policies/terms-of-service and https://takeultra.com/policies/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://takeultra.com/products/focus-pouches-v2 and https://takeultra.com/products/focus-pouches-v2-1 use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://takeultra.com/products/focus-pouches-v2, whose canonical is https://takeultra.com/products/focus-pouches-v2-1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

1 image failed to load on a phone, for example https://segment.prod.bidr.io/associate-segment?buzz_key=tatari&segment_key=tatari-19540&value=&uncacheplz=7942504107.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “fbq is not defined”.

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.

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

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