oberto.com website review

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

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

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

Your mobile performance score is 50 (desktop: 74). Pages that score under 90 lose visitors before the first paint.

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

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

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

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

3 third-party services load with your homepage (Shopify, shop.app and config-security.com), adding 1.0 MB and 113 ms of main-thread time.

Shopify costs a phone 104 ms of main-thread work and 929 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.

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

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

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

Your largest element takes 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Oberto Snacks Inc.”.

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

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

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

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

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

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

Your homepage downloads 7.3 MB in 283 requests on a phone: images 5.2 MB (53), scripts 884 KiB (93) and other files 771 KiB (104). Under 2 MB keeps phones on slow connections fast.

17 images are downloaded at several times the size a phone draws them, for example Oberto_B_9.png at 1,024 px wide, shown at 238 px. Resized copies would save about 1.3 MB.

9 images further down the page (1.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

131_77bcf523-a27f-4c29-8681-8a2185468656.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 (248 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 2.07 g of CO₂e: 247.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

5 images have no alt text, which hurts accessibility and image search.

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

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 78 characters, so Google will cut it off around 60: “Oberto | Grass-Fed Beef Sticks & High Protein Meat Snacks – Oberto Snacks Inc.”.

There are 2 <h1> headlines (“.logo_image { max-height: unset!important; width:…” and “.logo_image { max-height: unset!important; width:…”). One clear main headline is easier for people and search engines.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 94 pages on oberto.com and 3 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://www.oberto.com/products/original-grass-fed-beef-sticks-pack-of-8 and https://www.oberto.com/collections/cocktail-pep/products/original-grass-fed-beef-sticks-pack-of-8 all use the title “Original Grass Fed Beef Sticks - 8 Pack – Oberto Snacks Inc.”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.oberto.com/collections/all, https://www.oberto.com/collections/grass-fed-sticks, https://www.oberto.com/pages/donations and https://www.oberto.com/collections/cage-free-chicken-sticks have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.oberto.com/products/original-grass-fed-beef-sticks-pack-of-8 and https://www.oberto.com/collections/cocktail-pep/products/original-grass-fed-beef-sticks-pack-of-8 use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.oberto.com/collections/cocktail-pep/products/original-grass-fed-beef-sticks-pack-of-8, whose canonical is https://www.oberto.com/products/original-grass-fed-beef-sticks-pack-of-8. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.oberto.com/collections/all, https://www.oberto.com/collections, https://www.oberto.com/collections/grass-fed-sticks, https://www.oberto.com/pages/contact-us, https://www.oberto.com/pages/careers and https://www.oberto.com/collections/cage-free-chicken-sticks have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.

Social proof on the homepage: 39 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The page uses urgency cues (a countdown or limited-time wording).

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