colitt.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and loox.io and others), adding 2.9 MB and 1.4 s of main-thread time.

Google Tag Manager costs a phone 669 ms of main-thread work and 890 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.

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

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

loox.io costs a phone 192 ms of main-thread work and 998 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,831 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

Shopify costs a phone 78 ms of main-thread work and 351 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 51 KiB JavaScript that modern phones do not need. 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).

About 40 KiB of CSS is downloaded but never applied on this page.

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

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.

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 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

Real visitors wait 310 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Your homepage downloads 4.4 MB in 255 requests on a phone: scripts 1.9 MB (85), images 1.1 MB (33) and other files 946 KiB (112). Under 2 MB keeps phones on slow connections fast.

4 images further down the page (295 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

5 images (382 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.23 g of CO₂e: 148.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your <h1> is empty.

The homepage links to 57 pages on colitt.com and 6 external pages.

/products/colitt-fishing-advent-calendar and /products/colitt-fishing-tackle-countdown-gempages all use the title “Fishing Tackle Countdown | Colitt Fishing Advent Calendar”. Search engines can't tell which page to show for a search, so each competes with the others.

/products/colitt-fishing-catapult-rod, /products/colitt-outdoorsman-advent-calendar, /products/fishing-rod-building-block-set, /products/golf-advent-calendar, /collections/best-sellers and /apps/order-tracking and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

/products/colitt-fishing-advent-calendar and /products/colitt-fishing-tackle-countdown-gempages 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 /products/colitt-fishing-tackle-countdown-gempages, whose canonical is /products/colitt-fishing-advent-calendar. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/collections/best-sellers, /pages/contact, /pages/about-us, /apps/order-tracking, /pages/shipping-information and /collections/all have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 26 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: the server responded with a status of 404 ()”.

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

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

1 link go through two or more redirects, for example https://colitt.com/customer_authentication/redirect?locale=en&region_country=US.

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.

colitt.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

colitt.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.

Social proof on the homepage: “100,000+ customers”. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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