jet.style website review

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

26 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and website-files.com and others), adding 5.0 MB and 768 ms of main-thread time.

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

website-files.com costs a phone 89 ms of main-thread work and 4.3 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.

Google Tag Manager costs a phone 266 ms of main-thread work and 326 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.

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

Polyfills for old browsers add 16 KiB JavaScript that modern phones do not need.

Desktop scores 82 but mobile only 48. A gap that wide usually means heavy scripts and images that hit phones hardest.

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 24.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

Your homepage downloads 5.4 MB in 128 requests on a phone: images 3.5 MB (50), scripts 880 KiB (31) and media 558 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Your title is 74 characters, so Google will cut it off around 60: “XR & Digital Product Development Company | AR, VR, UX/UI Design – JetStyle”.

Your meta description is 239 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 66 pages on jet.style and 21 external pages.

A phone browser shows 2,410 words, but the HTML your server sends has only 619. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://jet.style/screen-space-vr, whose canonical is https://jet.style/portfolio/screen-space-vr. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://jet.style/about, https://jet.style/how-we-work, https://jet.style/partners, https://jet.style/awards, https://jet.style/news and https://jet.style/testimonials and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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 2,410 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager, LinkedIn Insight, Meta Pixel, Microsoft Clarity and Yandex Metrica (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 4 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 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.