promealfood.com website review

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

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

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

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

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

azurefd.net costs a phone 59 ms of main-thread work and 330 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.

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

About 196 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 8.6 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 9.5 s. Good is under 3.8 s.

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

Your homepage downloads 4.4 MB in 394 requests on a phone: images 2.0 MB (35), other files 1.3 MB (249) and scripts 792 KiB (81). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example pm-figma-fresh-video-poster.png at 2,989 px wide, shown at 472 px. Resized copies would save about 354 KiB.

3 images (97 KiB) 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.

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

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

[role="img"] and [role="image"] elements must have alternative text: 3 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

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

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

Your title is only 7 characters: “PROMEAL”. 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.

2 links have no real href, so search engines can't follow them.

The homepage links to 54 pages on promealfood.com and 9 external pages.

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

https://promealfood.com/pages/quiz-page, https://promealfood.com/pages/cibus, https://promealfood.com/collections/%D7%9B%D7%9C-%D7%94%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D-%D7%9C%D7%90-%D7%9B%D7%95%D7%9C%D7%9C-%D7%9E%D7%90%D7%A8%D7%96-%D7%94%D7%99%D7%9B%D7%A8%D7%95%D7%AA, https://promealfood.com/pages/%D7%9E%D7%90%D7%A8%D7%96-%D7%A2%D7%9C%D7%99%D7%99%D7%94-%D7%91%D7%9E%D7%A1%D7%94, https://promealfood.com/pages/%D7%9E%D7%90%D7%A8%D7%96-%D7%99%D7%A8%D7%99%D7%93%D7%94-%D7%91%D7%9E%D7%A9%D7%A7%D7%9C and https://promealfood.com/collections/%D7%A2%D7%99%D7%A7%D7%A8%D7%99%D7%95%D7%AA and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 12 pages by a URL that isn't their canonical one, for example https://promealfood.com/collections/%D7%9B%D7%9C-%D7%94%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D-%D7%9C%D7%90-%D7%9B%D7%95%D7%9C%D7%9C-%D7%9E%D7%90%D7%A8%D7%96-%D7%94%D7%99%D7%9B%D7%A8%D7%95%D7%AA, whose canonical is https://promealfood.com/collections/%d7%9b%d7%9c-%d7%94%d7%9e%d7%95%d7%a6%d7%a8%d7%99%d7%9d-%d7%9c%d7%90-%d7%9b%d7%95%d7%9c%d7%9c-%d7%9e%d7%90%d7%a8%d7%96-%d7%94%d7%99%d7%9b%d7%a8%d7%95%d7%aa. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://promealfood.com/pages/%D7%9E%D7%90%D7%A8%D7%96-%D7%A2%D7%9C%D7%99%D7%99%D7%94-%D7%91%D7%9E%D7%A1%D7%94, https://promealfood.com/pages/%D7%9E%D7%90%D7%A8%D7%96-%D7%99%D7%A8%D7%99%D7%93%D7%94-%D7%91%D7%9E%D7%A9%D7%A7%D7%9C and https://promealfood.com/pages/%D7%A9%D7%90%D7%9C%D7%95%D7%AA-%D7%95%D7%AA%D7%A9%D7%95%D7%91%D7%95%D7%AA have no <h1> headline, so visitors and search engines get no clear main topic.

https://promealfood.com/pages/cibus, https://promealfood.com/pages/%D7%9E%D7%90%D7%A8%D7%96-%D7%A2%D7%9C%D7%99%D7%99%D7%94-%D7%91%D7%9E%D7%A1%D7%94, https://promealfood.com/pages/%D7%9E%D7%90%D7%A8%D7%96-%D7%99%D7%A8%D7%99%D7%93%D7%94-%D7%91%D7%9E%D7%A9%D7%A7%D7%9C, https://promealfood.com/collections/%D7%A4%D7%A8%D7%95%D7%9E%D7%99%D7%9C-%D7%90%D7%A7%D7%A1%D7%98%D7%A8%D7%94-%D7%9C%D7%90%D7%A8%D7%92, https://promealfood.com/collections/%D7%A4%D7%A8%D7%95%D7%9E%D7%99%D7%9C-%D7%A4%D7%A8%D7%95 and https://promealfood.com/collections/%D7%AA%D7%95%D7%A1%D7%A4%D7%95%D7%AA and 6 others have 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 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

The homepage has only about 56 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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