jott.com website review

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

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

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

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

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

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

43 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

8 third-party services load with your homepage (Shopify, weglot.com and Didomi and others), adding 1.6 MB and 764 ms of main-thread time.

Shopify costs a phone 308 ms of main-thread work and 846 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.

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

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.

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

11 KiB JavaScript is shipped twice across bundles.

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.

4 KiB could be saved by minifying JavaScript.

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 21.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Welcome to JOTT! With your agreement, we and our 16 partner…”.

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

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

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.1 s (75th percentile). Good is under 1.8 s.

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

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

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

2 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 159 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 20.5 MB in 495 requests on a phone: media 13.9 MB (2), images 2.6 MB (106) and scripts 2.2 MB (108). Under 2 MB keeps phones on slow connections fast.

1 image (61 KiB) is 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 5.80 g of CO₂e: 695.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

All page content should be contained by landmarks: 11 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.

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

25 tap targets are too small or too close together to hit reliably with a finger.

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

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

Structured data found ((untyped)) but with 8 problems, for example “untyped block: missing @context (expected "https://schema.org")”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://jott.com/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 259 pages on jott.com and 7 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.

Your homepage links to https://jott.com/en-eu/collections/all and https://jott.com/en-eu/pages/storelocator, which answer with an error. Visitors hit a dead end and search engines drop them.

https://jott.com/en-eu/pages/page-reassurance, https://jott.com/en-eu/pages/femme, https://jott.com/en-eu/pages/homme and https://jott.com/en-eu/pages/enfant use the same meta description. A description written for each page earns more clicks.

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

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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.

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

Before a visitor clicks anything, the page loads Google Tag Manager, Pinterest Tag and TikTok Pixel (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 16 cookies (measured from a US location before any click).

Loading the homepage contacts 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.