Website review, no card needed

nlight.net logo

nlight.net website review

Visit site (opens in a new tab)Reviewed 1 November 202630 issues · 80 checks

This review found 30 issues worth fixing on nlight.net, 9 of them high impact, across 80 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
1.6 s1.1 sMay 9Oct 241.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.2 s
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.2 s
Jun 20, 20261.3 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.3 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
75 ms64 msMay 9Oct 2470 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202671 ms
May 16, 202673 ms
May 23, 202674 ms
May 30, 202674 ms
Jun 6, 202673 ms
Jun 13, 202671 ms
Jun 20, 202670 ms
Jun 27, 202669 ms
Jul 4, 202670 ms
Jul 11, 202670 ms
Jul 18, 202671 ms
Jul 25, 202671 ms
Aug 1, 202669 ms
Aug 8, 202668 ms
Aug 15, 202666 ms
Aug 22, 202667 ms
Aug 29, 202670 ms
Sep 5, 202670 ms
Sep 12, 202670 ms
Sep 19, 202668 ms
Sep 26, 202665 ms
Oct 3, 202666 ms
Oct 10, 202669 ms
Oct 17, 202670 ms
Oct 24, 202670 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 nlight.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix61
  • Reduce unused JavaScript

    2.3 s · 551 KiB

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

  • Render-blocking requests

    2.3 s

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

  • Mobile performance score: 61

    61/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Squarespace, Cookiebot and Google CDN and others), adding 2.0 MB and 600 ms of main-thread time.

  • Reduce unused CSS

    650 ms · 147 KiB

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

  • Squarespace adds 359 ms

    359 ms

    Squarespace costs a phone 359 ms of main-thread work and 1.1 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.

  • Legacy JavaScript

    300 ms · 118 KiB

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

  • Improve image delivery

    310 KiB

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

  • squarespace-cdn.com adds 0 ms

    0 ms

    squarespace-cdn.com costs a phone 0 ms of main-thread work and 506 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.

  • Minify JavaScript

    200 ms · 41 KiB

    41 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    150 ms · 38 KiB

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

  • 3 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 1.4 s

    A phone's processor spends 1.4 s on main-thread work while loading, 632 ms of it running JavaScript. That is comfortably low.

  • Server response: 45 ms

    45 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 11.9 s

    11.9 s

    Your largest element takes 11.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 13.0 s

    13.0 s

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

  • Speed Index: 7.5 s

    7.5 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

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

    +20%

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

  • 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

    -3%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 70 ms

    70 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 533 ms

    533 ms

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

  • Total Blocking Time: 83 ms

    83 ms

    Scripts block the page for only 83 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.003

    0.003

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

Images and page weight

2 to fix81
  • Page weight: 2.2 MB in 82 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 82 requests on a phone: scripts 1.5 MB (54), images 506 KiB (11) and stylesheets 168 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    MountWeaseled_Stryker_Updated_BlueGreen_Lens.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.6 g of CO₂ per visit

    0.62 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 9296
  • 1 button without a name

    1 button has 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.

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

3 to fixGoogle 9284
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Structured data has 2 problems

    Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/67bc98f2403e741e307…”.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 76 internal links, 4 external

    The homepage links to 76 pages on nlight.net and 4 external pages.

6 checks passed
  • Meta description: 126 characters

    Your meta description is 126 characters: “Leading the world in high-power lasers for mission-critical directed energy, sensing, and advanced manufacturing applic…”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “nLIGHT | Semiconductor Fiber Lasers”.

  • Canonical URL set

    The canonical URL is https://www.nlight.net/.

  • 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://www.nlight.net/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (0 of 6 facts)

    Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.nlight.net/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Text is in the HTML

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

Other pages

3 to fix83
  • 6 linked pages hidden from search

    https://www.nlight.net/about, https://www.nlight.net/locations, https://www.nlight.net/nconnect, https://www.nlight.net/patents, https://www.nlight.net/sales and https://www.nlight.net/service are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 12 pages without a meta description

    https://www.nlight.net/defenselasers, https://www.nlight.net/additivefiberlasers, https://www.nlight.net/medical-fiber-lasers, https://www.nlight.net/semiconductor-lasers, https://www.nlight.net/optical-fibers and https://www.nlight.net/about and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://www.nlight.net/directed-energy, https://www.nlight.net/sensing, https://www.nlight.net/advanced-manufacturing, https://www.nlight.net/defenselasers, https://www.nlight.net/about and https://www.nlight.net/nconnect have 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 26 found) and read each the way a search engine does.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/67bc98f2403e741e30757770/17/5c5a…”.

2 checks passed
  • Tap targets are thumb-sized

    11 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • No opening hours

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

  • No form on the homepage

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

  • No map or directions link

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 255 words of copy

    The homepage carries about 255 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “RMA Request”, “Contact Us” and “Learn More”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 1 tracker load before any consent

    1

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

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies (measured from a US location before any click).

  • 11 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 nlight.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Squarespace
Framework
jQuery
Analytics
Google Analytics
Hosting
Squarespace

Company

Employees
707
Founded
2000
Headquarters
Vancouver

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on nlight.net, including 15 speed issues, 3 SEO issues and 3 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