kylarmack.com website review

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

About 277 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

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

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

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

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

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

8 third-party services load with your homepage (Klaviyo, Reviews.io and IPONWEB and others), adding 552 KiB and 173 ms of main-thread time.

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

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

11 KiB could be saved by minifying JavaScript.

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.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Woman wearing Kylar Mack gold beaded bracelets”.

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

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

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

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

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

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

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

2 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: 4 elements on the page fail this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your meta description is 201 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.

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

The homepage links to 51 pages on kylarmack.com and 3 external pages.

The HTML your server sends has 293 of the 811 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

Your Organization JSON-LD is missing logo, 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://kylarmack.com/pages/build-your-own-stack, https://kylarmack.com/collections/homepage-collection and https://kylarmack.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://kylarmack.com/pages/contact has no <h1> headline, so visitors and search engines get no clear main topic.

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

5 errors were logged to the browser console while the page loaded, for example “Uncaught SyntaxError: Identifier 'doRatingSnippetReq' has already been declared”.

Social proof on the homepage: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 811 words of visible text.

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