ounjerun.com website review

11 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

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

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

Shopify costs a phone 227 ms of main-thread work and 667 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,702 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Shopify, Clarity and birdchime.com and others), adding 811 KiB and 358 ms of main-thread time.

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

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

1 long task block the main thread while loading, the longest for 85 ms. During a long task the page ignores taps.

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

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

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.

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

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

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

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

8 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 4.5 MB in 211 requests on a phone: images 2.6 MB (14), scripts 775 KiB (77) and other files 739 KiB (86). Under 2 MB keeps phones on slow connections fast.

3 images weigh 2.6 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example frying-pan_2C95B5.gif at 640 px wide, shown at 128 px. Resized copies would save about 1.9 MB.

4 images (3.0 MB) are 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.

1 image further down the page (48 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 8 characters: “OUNJERUN”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your <h1> is empty.

The homepage links to 51 pages on ounjerun.com and 1 external page.

https://ounjerun.com/collections/meal-plans, https://ounjerun.com/collections/ala-carte, https://ounjerun.com/collections/sides, https://ounjerun.com/pages/contact and https://ounjerun.com/pages/faqs have no meta description, so Google writes the search snippet from whatever text it finds.

https://ounjerun.com/products/3-meal-trial-plan, https://ounjerun.com/products/5-meal-plan, https://ounjerun.com/products/6-meal-plan, https://ounjerun.com/products/7-meal-plan, https://ounjerun.com/products/10-meal-plan and https://ounjerun.com/products/15-meal-plan use the same meta description. A description written for each page earns more clicks.

https://ounjerun.com/products/3-meal-trial-plan, https://ounjerun.com/products/5-meal-plan, https://ounjerun.com/products/6-meal-plan, https://ounjerun.com/products/7-meal-plan, https://ounjerun.com/products/10-meal-plan and https://ounjerun.com/products/15-meal-plan 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 17 found) and read each the way a search engine does.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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