siccups.com website review

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

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and Google CDN and others), adding 2.5 MB and 914 ms of main-thread time.

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

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

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

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

Klaviyo costs a phone 255 ms of main-thread work and 401 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 2,769 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

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.

3 KiB could be saved by minifying CSS.

3 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 11.4 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.

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 4.8 MB in 418 requests on a phone: scripts 1.6 MB (181), images 1.5 MB (39) and other files 1.1 MB (165). Under 2 MB keeps phones on slow connections fast.

5 images are downloaded at several times the size a phone draws them, for example 12-oz-lil-sic-dimpled-golf-water-bottle-873724.jpg at 2,048 px wide, shown at 334 px. Resized copies would save about 342 KiB.

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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.

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

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: 1 element on the page fails this check, rated minor by axe-core.

The homepage links to 106 pages on siccups.com and 7 external pages.

Your homepage links to /pages/collections, which answers with an error. Visitors hit a dead end and search engines drop it.

/collections/glacier-tumblers, /collections/glacier-bottles and /collections/new-arrivals have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://cdn.shopify.com/s/files/1/2142/7209/files/30-oz-tumbler-parrot-palms-519924.png?v=1762471137.

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

4 errors were logged to the browser console while the page loaded, for example “Error initializing managers Error: Endpoint key not set”.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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