Website review, no card needed

pioneerlasers.com logo

pioneerlasers.com website review

Visit site (opens in a new tab)Reviewed 21 October 202642 issues · 80 checks

This review found 42 issues worth fixing on pioneerlasers.com, 16 of them high impact, across 80 checks. The most urgent: render-blocking requests. 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

Full-page screenshot of pioneerlasers.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pioneerlasers.com at 0.4 s0.4 s
  2. pioneerlasers.com at 0.8 s0.8 s
  3. pioneerlasers.com at 1.1 s1.1 s
  4. pioneerlasers.com at 1.5 s1.5 s
  5. pioneerlasers.com at 1.9 s1.9 s
  6. pioneerlasers.com at 2.3 s2.3 s
  7. pioneerlasers.com at 2.6 s2.6 s
  8. pioneerlasers.com at 3.0 s3.0 s

Speed

8 to fix47
  • Render-blocking requests

    2.4 s

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

  • Reduce unused JavaScript

    1.6 s · 555 KiB

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

  • Mobile performance score: 47

    47/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, preordernowapp.com and Hotjar and others), adding 759 KiB and 824 ms of main-thread time.

  • Reduce unused CSS

    750 ms · 129 KiB

    About 129 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 Tag Manager adds 443 ms

    443 ms

    Google Tag Manager costs a phone 443 ms of main-thread work and 355 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 on the main thread

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

  • Main-thread work: 2.2 s

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

  • Legacy JavaScript

    150 ms · 9 KiB

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

  • Improve image delivery

    150 ms · 5 KiB

    1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Font display

    50 ms

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

  • Use efficient cache lifetimes

    42 KiB

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

  • Minify JavaScript

    14 KiB

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

1 checks passed
  • Server response: 14 ms

    14 ms

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

Core Web Vitals

6 to fix52
  • Largest Contentful Paint: 8.8 s

    8.8 s

    Your largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Our website use cookies. If you continue to use this site w…”.

  • Time to Interactive: 14.7 s

    14.7 s

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

  • First Contentful Paint: 4.2 s

    4.2 s

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

  • Speed Index: 6.7 s

    6.7 s

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

  • Total Blocking Time: 538 ms

    538 ms

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

  • 2 images without width and height

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

  • Not enough real-visitor data yet

    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.

1 checks passed
  • Cumulative Layout Shift: 0.02

    0.02

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

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.43 g

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

4 checks passed
  • Page weight: 1.5 MB in 115 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 115 requests on a phone: scripts 1.1 MB (43), stylesheets 184 KiB (14) and fonts 106 KiB (5). That is a lean page.

  • 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

10 to fixGoogle 5581
  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

  • 1 text element with low contrast

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

  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 4 form fields without a label

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

  • 2 links without text

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

  • Headings skip levels

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

1 checks passed
  • 27 automated accessibility rules passed

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

SEO

4 to fixGoogle 6970
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 53 internal links, 7 external

    The homepage links to 53 pages on pioneerlasers.com and 7 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Pioneer Dental Diode Lasers & Parts | CAO Group”.

  • Canonical URL set

    The canonical URL is https://caogroup.com/collections/pioneer-lasers.

  • 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://caogroup.com/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    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.

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

  • llms.txt published

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

Other pages

4 to fix41
  • 2 linked pages are broken

    Your homepage links to https://caogroup.com/products/hubble-digital-vision-head-set and https://caogroup.com/collections/warehouse-deals, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 12 pages without a title

    /, https://caogroup.com/collections/all, https://caogroup.com/collections/teeth-whitening, https://caogroup.com/collections/diode-lasers, https://caogroup.com/collections/clinical and https://caogroup.com/collections/delivery-tips and 6 others have no <title>, so Google invents the link text in results.

  • 12 pages without a meta description

    /, https://caogroup.com/collections/all, https://caogroup.com/collections/teeth-whitening, https://caogroup.com/collections/diode-lasers, https://caogroup.com/collections/clinical and https://caogroup.com/collections/delivery-tips and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

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

  • 15 internal pages checked

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

2 checks passed
  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

3 to fixGoogle 7785
  • 17 small tap targets

    17 of 21 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 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix70
  • No social proof

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

  • Only about 111 words

    The homepage has only about 111 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop CAO” and “Login/Register”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop CAO”, “Login/Register” and “Contact Us”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • 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
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 1 more (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.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies, 4 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.

  • 27 other companies contacted

    Loading the homepage contacts 27 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 pioneerlasers.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on pioneerlasers.com, including 14 speed issues, 4 SEO issues and 5 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