snackhawaii.com website review

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

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

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

8 third-party services load with your homepage (csell.co, Google CDN and Shopify and others), adding 2.7 MB and 1.8 s of main-thread time.

About 1.5 MB of JavaScript is downloaded but never used on this page.

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

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

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

csell.co costs a phone 622 ms of main-thread work and 55 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.

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

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

Google CDN costs a phone 314 ms of main-thread work and 1.1 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.

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

Yotpo costs a phone 176 ms of main-thread work and 323 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.

Privy costs a phone 140 ms of main-thread work and 436 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.

Polyfills for old browsers add 59 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.

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

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

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Best Hawaiian Snacks and Candies: Snack Hawaii”.

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

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

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

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

Your homepage downloads 12.0 MB in 486 requests on a phone: images 6.4 MB (135), scripts 3.3 MB (105) and other files 1.2 MB (194). Under 2 MB keeps phones on slow connections fast.

Yummy-Gummy-Gif-Ad-Stop-Motion-edit-BG-03_512x512.gif weighs 719 KiB. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example best-crack-seed-stores-for-hawaiian-snacks_2550x1041.webp at 2,550 px wide, shown at 278 px. Resized copies would save about 839 KiB.

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

9 images (2.2 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.

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

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

Some list items are not inside a list.

2 tap targets are too small or too close together to hit reliably with a finger.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

4 elements have a tabindex above 0, which scrambles the keyboard order.

1 visible link has no text or label, so screen readers cannot say where it goes.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 335 pages on snackhawaii.com and 6 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.snackhawaii.com/collections/all, https://www.snackhawaii.com/collections/li-hing-mui, https://www.snackhawaii.com/collections/li-hing-mui-candy, https://www.snackhawaii.com/collections/crack-seed, https://www.snackhawaii.com/collections/gummy-candy and https://www.snackhawaii.com/collections/candy have no <h1> headline, so visitors and search engines get no clear main topic.

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

20 of 63 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 (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_EMPTY_RESPONSE”.

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

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 1,320 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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 21 cookies, 1 of them by other companies (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 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.