jtbcustom.com website review

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

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

14 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.9 s faster on a phone.

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

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

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

Google Maps costs a phone 115 ms of main-thread work and 394 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.

5 third-party services load with your homepage (Google Maps, Google Tag Manager and cdn-cookieyes.com and others), adding 688 KiB and 230 ms of main-thread time.

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

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

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 13.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Leading End-to-End SaaS Solution Enabling Brands to Off…”.

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

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

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

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

9 images are downloaded at several times the size a phone draws them, for example klean_kanteen-1.png at 1,920 px wide, shown at 320 px. Resized copies would save about 637 KiB.

Your homepage downloads 2.7 MB in 138 requests on a phone: images 1.4 MB (24), scripts 933 KiB (53) and stylesheets 240 KiB (50). Under 2 MB keeps phones on slow connections fast.

10 images (1.1 MB) are 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.

4 images further down the page (403 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 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.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

The homepage links to 56 pages on jtbcustom.com and 7 external pages.

https://vucustom.com/2026/06 and https://vucustom.com/2025/09 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://vucustom.com/setup, https://vucustom.com/about and https://vucustom.com/team all use the title “VU Custom - Enabling brands to offer customized products”. Search engines can't tell which page to show for a search, so each competes with the others.

https://vucustom.com/2026/06, https://vucustom.com/author/nohemi-cortes, https://vucustom.com/category/news and https://vucustom.com/2025/09 have no meta description, so Google writes the search snippet from whatever text it finds.

https://vucustom.com/setup, https://vucustom.com/about and https://vucustom.com/team use the same meta description. A description written for each page earns more clicks.

https://vucustom.com/case-studies, https://vucustom.com/about, https://vucustom.com/team, https://vucustom.com/careers, https://vucustom.com/latest-news and https://vucustom.com/book-a-demo and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://vucustom.com/case-studies, https://vucustom.com/latest-news and https://vucustom.com/book-a-demo 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.

https://vucustom.com/case-studies, https://vucustom.com/setup, https://vucustom.com/about, https://vucustom.com/team, https://vucustom.com/careers and https://vucustom.com/latest-news and 2 others took over 3 s to send their HTML from our server.

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

Chrome logged issues while loading the page (“Mixed content”).

Social proof on the homepage: 11 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

There is no form on the homepage, so every lead has to click through to another page first.

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

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

Opening the homepage sets 1 cookie (measured from a US location before any click).

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