tank-jacket.com website review

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

4 images could be 1,017 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

3 third-party services load with your homepage (cloudfront.net, cloudflare.com and JSDelivr CDN), adding 1.6 MB and 319 ms of main-thread time.

cloudfront.net costs a phone 286 ms of main-thread work and 1.6 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 356 KiB of JavaScript is downloaded but never used on this page.

1 long task block the main thread while loading, the longest for 184 ms. During a long task the page ignores taps.

Polyfills for old browsers add 18 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.

1 file is served with short cache lifetimes, so returning visitors download them again (2 KiB).

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

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

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

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

tank_jacket_09421808202601.png weighs 854 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.8 MB in 31 requests on a phone: other files 1.4 MB (4), images 1.3 MB (5) and scripts 566 KiB (7). Under 2 MB keeps phones on slow connections fast.

1 image (854 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 1.08 g of CO₂e: 130.0 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.

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

The robots meta tag says “noindex,nofollow”: Google is told not to list this page at all.

Google's crawler is blocked from indexing this page.

Your meta description is only 37 characters: “Neoprene Tank Jacket - Just Hit Print”. 70 to 160 characters is enough to sell the click.

3 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 411 pages on tank-jacket.com and 5 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 1 page by a URL that isn't its canonical one, for example https://www.justhitprint.com/business-cards/magnet-business-cards, whose canonical is https://www.justhitprint.com/marketing-material/magnets/magnet-business-cards. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/ has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.justhitprint.com/business-cards/standard-business-cards, https://www.justhitprint.com/business-cards/brown-kraft-business-cards, https://www.justhitprint.com/business-cards/circle-business-cards, https://www.justhitprint.com/business-cards/dual-raised-business-cards, https://www.justhitprint.com/business-cards/endurace-business-cards and https://www.justhitprint.com/business-cards/foil-worx-business-cards and 5 others took over 3 s to send their HTML from our server.

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

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'controller')”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage carries about 264 words of visible text.

Opening the homepage sets 2 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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.