Website review, no card needed

labcharge.com logo

labcharge.com website review

Visit site (opens in a new tab)Reviewed 20 November 202642 issues · 89 checks

This review found 42 issues worth fixing on labcharge.com, 20 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.2 s2.3 sMay 30Nov 142.8 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.4 s
Jun 6, 20262.5 s
Jun 13, 20262.7 s
Jun 20, 20262.8 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20263.0 s
Jul 25, 20263.1 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20262.9 s
Aug 22, 20262.8 s
Aug 29, 20262.7 s
Sep 5, 20262.8 s
Sep 12, 20262.9 s
Sep 19, 20263.1 s
Sep 26, 20263.1 s
Oct 3, 20263.0 s
Oct 10, 20262.9 s
Oct 17, 20262.7 s
Oct 24, 20262.7 s
Oct 31, 20262.8 s
Nov 7, 20262.8 s
Nov 14, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
180 ms151 msMay 30Nov 14154 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026161 ms
Jun 6, 2026169 ms
Jun 13, 2026175 ms
Jun 20, 2026173 ms
Jun 27, 2026171 ms
Jul 4, 2026162 ms
Jul 11, 2026159 ms
Jul 18, 2026161 ms
Jul 25, 2026161 ms
Aug 1, 2026163 ms
Aug 8, 2026162 ms
Aug 15, 2026154 ms
Aug 22, 2026154 ms
Aug 29, 2026158 ms
Sep 5, 2026162 ms
Sep 12, 2026170 ms
Sep 19, 2026177 ms
Sep 26, 2026173 ms
Oct 3, 2026171 ms
Oct 10, 2026163 ms
Oct 17, 2026161 ms
Oct 24, 2026160 ms
Oct 31, 2026162 ms
Nov 7, 2026160 ms
Nov 14, 2026154 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of labcharge.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. labcharge.com at 1.6 s1.6 s
  2. labcharge.com at 3.2 s3.2 s
  3. labcharge.com at 4.8 s4.8 s
  4. labcharge.com at 6.4 s6.4 s
  5. labcharge.com at 8.0 s8.0 s
  6. labcharge.com at 9.5 s9.5 s
  7. labcharge.com at 11.1 s11.1 s
  8. labcharge.com at 12.7 s12.7 s

Speed

14 to fix30
  • Reduce unused JavaScript

    2.7 s · 998 KiB

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

  • Use efficient cache lifetimes

    1.6 s · 711 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Main-thread work: 14.2 s

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

  • Mobile performance score: 30

    30/100

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

  • 3,276 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (alia-prod.com, Facebook and reddit and others), adding 1.6 MB and 2.7 s of main-thread time.

  • alia-prod.com adds 678 ms

    678 ms

    alia-prod.com costs a phone 678 ms of main-thread work and 310 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.

  • Facebook adds 452 ms

    452 ms

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

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    300 ms · 80 KiB

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

  • reddit adds 347 ms

    347 ms

    reddit costs a phone 347 ms of main-thread work and 29 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.

  • Google Tag Manager adds 325 ms

    325 ms

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

  • heatmap.com adds 310 ms

    310 ms

    heatmap.com costs a phone 310 ms of main-thread work and 146 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.

  • Reduce unused CSS

    170 ms · 58 KiB

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

  • Improve image delivery

    85 KiB

    6 images could be 85 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify JavaScript

    20 ms · 8 KiB

    8 KiB could be saved by minifying JavaScript.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 9 ms

    9 ms

    Your server sent the HTML in 9 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix100
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 12.5 s

    12.5 s

    Your largest element takes 12.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ADVANCED IONIC AIR PURIFIER The Best Ionic Air Purifier for…”.

  • Time to Interactive: 30.3 s

    30.3 s

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

  • Speed Index: 14.9 s

    14.9 s

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

  • Total Blocking Time: 2.1 s

    2.1 s

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Real-user FCP: 1.9 s

    1.9 s

    Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -5%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 161 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 12% slower for real visitors

    +12%

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

5 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 146 ms

    146 ms

    Real visitors wait 146 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 397 ms

    397 ms

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

  • Cumulative Layout Shift: 0.061

    0.061

    The layout barely moves while loading (CLS 0.061, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 5.2 MB in 396 requests

    5.2 MB

    Your homepage downloads 5.2 MB in 396 requests on a phone: scripts 2.7 MB (124), images 906 KiB (85) and other files 846 KiB (142). Under 2 MB keeps phones on slow connections fast.

  • About 1.5 g of CO₂ per visit

    1.46 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8491
  • 11 text elements with low contrast

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

  • 11 tap targets too small

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

  • Scrollable region must have keyboard access (5 elements)

    Scrollable region must have keyboard access: 5 elements on the page fail this check, rated serious by axe-core.

  • Summary elements must have discernible text (1 element)

    Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (19 elements)

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

  • 1 form field without a label

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

2 checks passed
  • Every image has alt text

    All 543 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9293
  • Title is long (76 characters)

    Your title is 76 characters, so Google will cut it off around 60: “Best Ionic Air Purifier | Silent & Buyer-Rated | Lab Charge – Lab Charge LLC”.

  • 67 internal links, 2 external

    The homepage links to 67 pages on labcharge.com and 2 external pages.

7 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “Shop the best ionic air purifier for home. Silent, compact, and backed by real buyer reviews. Free shipping, 30-day hom…”.

  • One H1 headline

    Your main headline reads: “The Best Ionic Air Purifier for Your Home”.

  • Canonical URL set

    The canonical URL is https://labcharge.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://labcharge.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,392 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://labcharge.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix67
  • 1 page without a title

    https://labcharge.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 7 linked pages hidden from search

    https://labcharge.com/customer_authentication/redirect, https://labcharge.com/products/lab-charge-ionic-air-purifier-wall-plug-in-air-purifier-for-home-filterless-copy, https://labcharge.com/products/summer-ionic-air-purifiers-new-drop-2, https://labcharge.com/products/summer-ionic-air-purifiers-new-drop-1, https://labcharge.com/products/summer-ionic-air-purifiers-new-drop-3 and https://labcharge.com/products/2pets and 1 other are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://labcharge.com/policies/shipping-policy, https://labcharge.com/customer_authentication/redirect and https://labcharge.com/products/black have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://labcharge.com/products/2pets and https://labcharge.com/products/3pets use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://labcharge.com/customer_authentication/redirect, https://labcharge.com/products/black, https://labcharge.com/products/summer-ionic-air-purifiers-new-drop-2, https://labcharge.com/products/summer-ionic-air-purifiers-new-drop-1 and https://labcharge.com/products/summer-ionic-air-purifiers-new-drop-3 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://labcharge.com/products/white, https://labcharge.com/products/2pets and https://labcharge.com/products/3pets took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

Best practices

4 to fixGoogle 7770
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17484561&Ver=2&mid=03c88a59-6724-4138-8813-f19fb2bdd2ff&bo=1&sid=669c94d0e4f211f18d2ea9c6b0977e5d&vid=669cc640e4f211f1a6fddd67a6a03077&vids=1&msclkid=N&pi=918639831&lg.

  • 27 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “_tfa is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • About 1,017 words of copy

    The homepage carries about 1,017 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW” and “Shop Now”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact Us”, “Shop Now” and “Shop All Colors”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Meta Pixel and Microsoft Clarity.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Ads and 4 mores (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.

  • 47 cookies set on arrival

    47

    Opening the homepage sets 47 cookies, 2 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 67 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at labcharge.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on labcharge.com, including 22 speed issues, 1 SEO issue and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25