kits.com website review

244 files are served with short cache lifetimes, so returning visitors download them again (8.2 MB).

About 2.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.9 s faster on a phone.

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

About 386 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

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

23 images could be 5.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, Intercom and Google CDN and others), adding 2.1 MB and 2.6 s of main-thread time.

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

80 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 600 ms faster on a phone.

Intercom costs a phone 414 ms of main-thread work and 462 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.

23 KiB could be saved by minifying JavaScript.

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

Google Maps costs a phone 217 ms of main-thread work and 392 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,229 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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.

For real visitors the layout shifts by 0.26 (75th percentile). Good is under 0.1.

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

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

Your largest element takes 41.0 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 28.5 s (Speed Index). Good is under 3.4 s.

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

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

Real visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.8 s (75th percentile). 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-10-17, real Chrome visitors' tap response (inp) went from 187 ms to 170 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 15.7 MB in 424 requests on a phone: images 9.4 MB (177), scripts 5.0 MB (120) and other files 498 KiB (82). Under 2 MB keeps phones on slow connections fast.

3 images weigh 4.1 MB together. On a phone connection a single image that size takes seconds.

13 images are downloaded at several times the size a phone draws them, for example May28-2026-Trending-Carousel-6.jpg at 3,024 px wide, shown at 203 px. Resized copies would save about 4.6 MB.

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

7 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

1 element has a tabindex above 0, which scrambles the keyboard order.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

No Open Graph image (also missing: og:title, og:description), 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.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 371 pages on kits.com and 15 external pages.

There is no https://www.kits.com/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.

https://www.kits.com/favorites and https://www.kits.com/quiz/glasses all use the title “Kits.com”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.kits.com/kits-plus, https://www.kits.com/order-status, https://www.kits.com/shipping, https://www.kits.com/favorites and https://www.kits.com/quiz/glasses use the same meta description. A description written for each page earns more clicks.

https://www.kits.com/autoship, https://www.kits.com/kits-plus, https://www.kits.com/order-status, https://www.kits.com/shipping, https://www.kits.com/contactus and https://www.kits.com/kits-experience and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 87 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=5037735&tm=gtm002&Ver=2&mid=50db4ec5-c0a4-44ce-b001-2f9e84de5b2b&bo=1&sid=bffdc740cf0c11f1a728cfb85f9773a7&vid=bffdbba0cf0c11f180782b26a31d2fca&vids=1&msclkid=N&pi=918.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

4 errors were logged to the browser console while the page loaded, for example “Uncaught SyntaxError: Invalid or unexpected token”.

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

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

Social proof on the homepage: 3 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.

The homepage carries about 431 words of visible text.

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