kryptonics.com website review

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

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

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

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

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

About 45 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 580 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Cloudflare and others), adding 246 KiB and 242 ms of main-thread time.

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

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

7 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 10.3 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 10.4 s. Good is under 3.8 s.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

KR_new_arrivals_2_300x_v-1692990725.png 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).

2 images are downloaded at several times the size a phone draws them, for example Krypto_Header_Web_1880_x_720_Past_Present_Future_v-167831719 at 1,880 px wide, shown at 390 px. Resized copies would save about 120 KiB.

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

1 element hidden from screen readers can still receive keyboard focus.

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

Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 22 characters: “Kryptonics Skateboards”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Your <h1> is empty.

The homepage links to 63 pages on kryptonics.com and 10 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 https://kryptonics.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.

Your homepage links to https://kryptonics.com/collections/skateboards, https://kryptonics.com/pages/about, https://kryptonics.com/collections/completes, https://kryptonics.com/collections/cruisers, https://kryptonics.com/collections/longboards and https://kryptonics.com/collections/accessories and 6 others, which answer with an error. Visitors hit a dead end and search engines drop them.

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

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

4 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://www.kryptonics.com/cdn/fonts/montserrat/montserrat_n4.1d581f6d4bf1a97f4cbc0b88b933bc136d38d1…”.

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

The homepage has only about 91 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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