cghunter.com website review

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

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

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

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

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

8 third-party services load with your homepage (route.com, Klaviyo and Clarity and others), adding 1.9 MB and 1.2 s of main-thread time.

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

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

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

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

route.com costs a phone 349 ms of main-thread work and 542 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.

Klaviyo costs a phone 324 ms of main-thread work and 636 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.

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

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

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

13 KiB could be saved by minifying CSS.

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.

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

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

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

The first text or image appears after 2.7 s on a phone. Good is under 1.8 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-11-07, real Chrome visitors' tap response (inp) went from 110 ms to 117 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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 5.0 MB in 472 requests on a phone: scripts 2.0 MB (141), other files 1.4 MB (271) and images 1.2 MB (26). Under 2 MB keeps phones on slow connections fast.

2 images (196 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.

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

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

The homepage links to 439 pages on cghunter.com and 11 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://cghunter.com/pages/maxwell-sienna and https://cghunter.com/pages/disney-holiday-wreath use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://cghunter.com/collections/the-hunter-collection/Hunter+New-Arrivals, whose canonical is https://cghunter.com/collections/the-hunter-collection. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://cghunter.com/pages/maxwell-sienna, https://cghunter.com/pages/disney-holiday-wreath and https://cghunter.com/pages/dorm-room-decor-essentials have no <h1> headline, so visitors and search engines get no clear main topic.

https://cghunter.com/collections/summer-porch-decor, https://cghunter.com/pages/dorm-room-decor-essentials, https://cghunter.com/collections/stem-bundles and https://cghunter.com/collections/under-100 took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187147057&Ver=2&mid=e8d8b611-0e8f-4397-bbea-62ecabe11448&bo=1&sid=a84737e0de7411f1a21d7b6658275a43&vid=a8475b10de7411f1bc5ee9151cebe23c&vids=1&msclkid=N&pi=918639831&l.

The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Social proof on the homepage: 24 testimonial or review blocks. 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 797 words of visible text.

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