snacknation.com website review

9 images could be 501 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.

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

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

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

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

9 long tasks block the main thread while loading, the longest for 2.7 s. During a long task the page ignores taps.

8 third-party services load with your homepage (Google Tag Manager, Unbounce and Facebook and others), adding 1.3 MB and 939 ms of main-thread time.

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

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

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

Google Tag Manager costs a phone 369 ms of main-thread work and 651 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,617 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

Real visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

The layout shifts by 0.312 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 263 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Your homepage downloads 5.0 MB in 174 requests on a phone: images 2.5 MB (40), scripts 1.6 MB (50) and fonts 602 KiB (15). Under 2 MB keeps phones on slow connections fast.

6 images (677 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.

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

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

1 element has a tabindex above 0, which scrambles the keyboard order.

All page content should be contained by landmarks: 35 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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 66 characters, so Google will cut it off around 60: “Healthy Snack Delivery Service for Offices and Homes | SnackNation”.

Structured data found (BreadcrumbList, ImageObject, Organization and SoftwareApplication) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.

The homepage links to 122 pages on snacknation.com and 18 external pages.

There is no https://snacknation.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://snacknation.com/blog/category/corporate-gifting, https://snacknation.com/blog/category/company-swag, https://snacknation.com/blog/category/employee-recognition, https://snacknation.com/blog/category/team-building and https://snacknation.com/blog/category/employee-engagement have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

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 405 ()”.

Large scripts ship without source maps.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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 131 words of visible text; thin pages give Google and first-time buyers little to go on.

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