Website review, no card needed
omnifoodequipment.com website review
Visit site (opens in a new tab)Reviewed 5 November 202645 issues · 88 checks
This review found 45 issues worth fixing on omnifoodequipment.com, 14 of them high impact, across 88 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
75C- #82,587 of 126,428 reviewed websitesbeats 30%
- #51,988 of 70,467 online storesbeats 22%
- #48,996 of 63,968 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.5 s |
| May 23, 2026 | 3.3 s |
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.6 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.6 s |
| Oct 24, 2026 | 3.6 s |
| Oct 31, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 138 ms |
| May 23, 2026 | 139 ms |
| May 30, 2026 | 144 ms |
| Jun 6, 2026 | 143 ms |
| Jun 13, 2026 | 138 ms |
| Jun 20, 2026 | 134 ms |
| Jun 27, 2026 | 136 ms |
| Jul 4, 2026 | 143 ms |
| Jul 11, 2026 | 138 ms |
| Jul 18, 2026 | 140 ms |
| Jul 25, 2026 | 139 ms |
| Aug 1, 2026 | 139 ms |
| Aug 8, 2026 | 146 ms |
| Aug 15, 2026 | 162 ms |
| Aug 22, 2026 | 162 ms |
| Aug 29, 2026 | 167 ms |
| Sep 5, 2026 | 163 ms |
| Sep 12, 2026 | 161 ms |
| Sep 19, 2026 | 154 ms |
| Sep 26, 2026 | 146 ms |
| Oct 3, 2026 | 141 ms |
| Oct 10, 2026 | 135 ms |
| Oct 17, 2026 | 141 ms |
| Oct 24, 2026 | 156 ms |
| Oct 31, 2026 | 154 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.8 s
1.6 s
2.4 s
3.2 s
4.0 s
4.8 s
5.6 s
6.4 s
Speed
Render-blocking requests
1.8 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Reduce unused JavaScript
1.2 s · 483 KiBAbout 483 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
450 ms · 168 KiBAbout 168 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, OptiMonk and gravity-software.com and others), adding 1.5 MB and 377 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 521 ms. During a long task the page ignores taps.
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 231 ms
231 msShopify costs a phone 231 ms of main-thread work and 1.2 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.
1,783 HTML elements
The page has 1,783 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
200 ms · 219 KiB9 images could be 219 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Legacy JavaScript
250 ms · 28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Minify JavaScript
64 KiB64 KiB could be saved by minifying JavaScript.
Duplicated JavaScript
17 KiB17 KiB JavaScript is shipped twice across bundles.
Use efficient cache lifetimes
16 KiB5 files are served with short cache lifetimes, so returning visitors download them again (16 KiB).
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Real-user FCP: 3.4 s
3.4 sReal visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 16.2 s
16.2 sYour largest element takes 16.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 16.7 s
16.7 sThe page becomes fully interactive after 16.7 s. Good is under 3.8 s.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.4 s
3.4 sReal visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Total Blocking Time: 275 ms
275 msScripts block taps and scrolling for 275 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 138 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.5 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 186 ms
186 msReal visitors wait 186 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 571 ms
571 msReal visitors wait 571 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 4.1 MB in 286 requests
4.1 MBYour homepage downloads 4.1 MB in 286 requests on a phone: scripts 2.0 MB (138), other files 908 KiB (106) and images 769 KiB (14). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Gemini_Generated_Image_e5cxdie5cxdie5cx_800x.jpg 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 far larger than shown
19 KiB1 image is downloaded at several times the size a phone draws it, for example Shopify_Images_-_Glass_Display_Refrigerators_6cfd2d4d-0946-4 at 600 px wide, shown at 168 px. Resized copies would save about 19 KiB.
2 images in older formats
2 images (81 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.
About 1.2 g of CO₂ per visit
1.18 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.18 g of CO₂e: 141.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (18 elements)
Alternative text of images should not be repeated as text: 18 elements on the page fail this check, rated minor by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 45 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (19 characters)
Your title is only 19 characters: “Omni Food Equipment”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 1 problem
Structured data found (Organization, Store and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("omnifoodequipment.com")”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
236 internal links, 8 external
The homepage links to 236 pages on omnifoodequipment.com and 8 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://omnifoodequipment.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://omnifoodequipment.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
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.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,365 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://omnifoodequipment.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://omnifoodequipment.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://omnifoodequipment.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
11 pages without a meta description
https://omnifoodequipment.com/collections/omni-fall-clearance-sale, https://omnifoodequipment.com/collections/equipment, https://omnifoodequipment.com/collections/refrigeration-2/Refrigerators+Freezers+Coolers, https://omnifoodequipment.com/collections/cooking-equipment, https://omnifoodequipment.com/collections and https://omnifoodequipment.com/collections/smallware and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://omnifoodequipment.com/collections/refrigeration-2/Refrigerators+Freezers+Coolers, whose canonical is https://omnifoodequipment.com/collections/refrigeration-2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://omnifoodequipment.com/pages/financing-options and https://omnifoodequipment.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 172 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Best practices
9 small tap targets
9 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
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…”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Thin social proof
Social proof on the homepage: 68 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
About 562 words of copy
The homepage carries about 562 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
7 checks passed
9 calls to action
The homepage has 9 calls to action, for example “View all Contact Us”, “Learn more” and “Track Your Order”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 2 phone links and 5 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads (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.
21 cookies set on arrival
21Opening the homepage sets 21 cookies, 1 of them by other companies (measured from a US location before any click).
No consent tool detected
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.
32 other companies contacted
Loading the homepage contacts 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at omnifoodequipment.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 15 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Zapiet Pickup Delivery · Judge Me Reviews · Juicy Profit Analytics · Attentive · Microsoft Clarity · Ta Labels Badges · Optimonk Popup Cro A B Test · Quoter Request Quotes · Seo Manager Venntov · Inbox · Vol Fees Surcharge · Frontend · Ease Product Attachments · Progress Bar App · attn.tv
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on omnifoodequipment.com, including 18 speed issues, 6 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.