krischislett.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and ksrndkehqnwntyxlhgto.com and others), adding 6.4 MB and 589 ms of main-thread time.

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

12 images could be 742 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.

publit.io costs a phone 0 ms of main-thread work and 5.2 MB 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.

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

Google Tag Manager costs a phone 387 ms of main-thread work and 905 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 34 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

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

35 KiB could be saved by minifying JavaScript.

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

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 21.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalize content, provide social media…”.

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

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

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

21 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-31, real Chrome visitors' tap response (inp) went from 284 ms to 393 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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.

Your homepage downloads 15.8 MB in 259 requests on a phone: media 12.1 MB (3), scripts 2.0 MB (92) and images 959 KiB (53). Under 2 MB keeps phones on slow connections fast.

7 images are downloaded at several times the size a phone draws them, for example Marche-Cortier.png.webp at 938 px wide, shown at 97 px. Resized copies would save about 574 KiB.

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

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

ARIA tooltip nodes must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

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

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

The homepage links to 93 pages on krischislett.com and 9 external pages.

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

2 of 8 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 “Failed to load resource: net::ERR_FAILED”.

Your longest form asks for 17 fields (5 required). Every extra field lowers completion.

The homepage carries about 2,817 words of visible text.

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