lungtank.com website review

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

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

15 images could be 15.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Firebase and others), adding 2.1 MB and 1.8 s of main-thread time.

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 200 ms faster on a phone.

28 files are served with short cache lifetimes, so returning visitors download them again (1,007 KiB).

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

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

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

Facebook costs a phone 320 ms of main-thread work and 213 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.

Firebase costs a phone 277 ms of main-thread work and 5 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.

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

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

instant.one costs a phone 141 ms of main-thread work and 565 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 53 KiB JavaScript that modern phones do not need.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

About 25 KiB of CSS is downloaded but never applied on this page.

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 22.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Lung Tank T-500”.

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

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

Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

11 images weigh 36.4 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 19.4 MB in 264 requests on a phone: images 15.9 MB (31), scripts 2.2 MB (79) and other files 924 KiB (107). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example bfe7a8e9-64ce-47da-a1ca-8bedf837b1b6_1.gif at 640 px wide, shown at 195 px. Resized copies would save about 12.0 MB.

13 images (36.4 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.

By the Sustainable Web Design model, a visit to your homepage emits about 5.51 g of CO₂e: 660.7 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: 8 elements on the page fail this check, rated moderate by axe-core.

There are 2 <h1> headlines (“” and “BREATHEUNDERWATER”). One clear main headline is easier for people and search engines.

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

The homepage links to 77 pages on lungtank.com and 10 external pages.

https://lungtank.com/products/lung-t-1000, https://lungtank.com/products/lung-t-1000-sub-mask-turbocharger and https://lungtank.com/products/lung-t-1000-turbocharger all use the title “Lung Pro-Mask for T-500 | Diving Mask – Lung Tank”. Search engines can't tell which page to show for a search, so each competes with the others.

https://lungtank.com/pages/faqs, https://lungtank.com/pages/tutorials and https://lungtank.com/pages/contact have no meta description, so Google writes the search snippet from whatever text it finds.

https://lungtank.com/products/lung-t-1000, https://lungtank.com/products/lung-t-1000-sub-mask-turbocharger and https://lungtank.com/products/lung-t-1000-turbocharger use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://lungtank.com/products/lung-t-500%E2%84%A2-hand-pump-sub-mask, whose canonical is https://lungtank.com/products/lung-t-500%e2%84%a2-hand-pump-sub-mask. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://lungtank.com/collections/all has no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo 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 18 cookies, 2 of them by other companies (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 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.