highcampsupply.com website review

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

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

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

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

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

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

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

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

azurefd.net costs a phone 61 ms of main-thread work and 329 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.

8 third-party services load with your homepage (Facebook, Clarity and Google Tag Manager and others), adding 882 KiB and 403 ms of main-thread time.

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

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

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

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 JavaScript is shipped twice across bundles.

Your largest element takes 13.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

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

Your homepage downloads 2.4 MB in 210 requests on a phone: images 1.1 MB (39), scripts 931 KiB (82) and stylesheets 147 KiB (52). Under 2 MB keeps phones on slow connections fast.

2026.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).

3 images are downloaded at several times the size a phone draws them, for example packing_box.png at 600 px wide, shown at 117 px. Resized copies would save about 126 KiB.

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

4 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

There are 2 <h1> headlines (“” and “Thank You for Submitting the Form!”). One clear main headline is easier for people and search engines.

Your meta description is 222 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 179 pages on highcampsupply.com and 8 external pages.

https://highcampsupply.com/collections/gardenias, https://highcampsupply.com/collections/peonies, https://highcampsupply.com/collections/garden-roses and https://highcampsupply.com/collections/lilys have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

Social proof on the homepage: 6 customer or partner logos. 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.

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,243 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 16 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 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.