kiefer.com website review

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

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

Your mobile performance score is 64 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

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

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

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

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

8 third-party services load with your homepage (Shopify, okendo.io and shop.app and others), adding 231 KiB and 0 ms of main-thread time.

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 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Swimmer kicking underwater holding an arena kickboard”.

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

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

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

Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

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

11 images 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 112 ms to 116 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 7.4 MB in 134 requests on a phone: media 5.5 MB (1), images 1.2 MB (35) and scripts 339 KiB (41). Under 2 MB keeps phones on slow connections fast.

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

1 image is downloaded at several times the size a phone draws it, for example lgs47-15b_1_1.jpg at 1,200 px wide, shown at 148 px. Resized copies would save about 121 KiB.

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

2 buttons have no accessible name, so screen readers announce just “button”.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is only 15 characters: “Kiefer Aquatics”. Between 30 and 65 characters leaves room to say what you do and for whom.

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 870 pages on kiefer.com and 33 external pages.

https://kiefer.com/collections/kiefer-swimwear-tech-suits-womens-competition-swimwear-two-piece-swimsuits is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://kiefer.com/collections/all, https://kiefer.com/pages/store-locations-hours, https://kiefer.com/collections/fall-winter-2026-team-suits and https://kiefer.com/collections/kiefer-swimwear-tech-suits-womens-competition-swimwear-two-piece-swimsuits have no meta description, so Google writes the search snippet from whatever text it finds.

https://kiefer.com/collections/all, https://kiefer.com/pages/store-locations-hours, https://kiefer.com/collections/kiefer-swim-team, https://kiefer.com/collections/fall-winter-2026-team-suits, https://kiefer.com/collections/spring-summer-2026-team-suits and https://kiefer.com/collections/kiefer-swim-team-womens-one-piece and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://kiefer.com/collections/kiefer-swim-team-mens-briefs and https://kiefer.com/collections/kiefer-swim-team-boys-brief have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 15 pages linked from your homepage (of 199 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: net::ERR_FAILED”.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 863 words of visible text.

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

Before a visitor clicks anything, the page loads 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 5 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.