counter.com website review

The page goes through 2 redirects before it starts loading, costing about 3.9 s. Link and advertise the final URL directly.

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

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

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

About 716 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 670 ms faster on a phone.

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

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

8 third-party services load with your homepage (Shopify, Clarity and Klaviyo and others), adding 1.1 MB and 559 ms of main-thread time.

Shopify costs a phone 325 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.

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

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

7 images could be 118 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

The HTML itself could arrive about 100 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

2 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

Your homepage downloads 121.4 MB in 514 requests on a phone: media 117.3 MB (21), scripts 1.4 MB (148) and images 1.2 MB (169). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

The homepage links to 255 pages on counter.com and 3 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.

There is no /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.

/products/jellies-collectibles-customize-your-set, /collections/all, /collections/all-products, /collections/exclusive-merch, /collections/bestsellers and /collections/skincare have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/all, /collections/all-products, /collections/exclusive-merch, /collections/bestsellers and /collections/skincare have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

counter.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

The homepage carries about 1,543 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Klaviyo, Microsoft Clarity and Taboola (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 9 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 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.